Hi,
since my x-touch mini got mechanical problems with the encoders I wanted to switch to Arturia Beatstep (non pro). I used it with my MAC M1 to control Capture 1 and other Programs.
The difference and the problem is, that the beatstep does not fire any midi signals when it arrives the value of 127 or 1.
The x-touch’s encoders also got a button function, so that I could reset the value from 127 to 64 in a container in order to rotate the encoder further on.
How can I solve the problem?
Thanks a lot for helping!
First of all, what mechanical problems do you have with the encoders on your X-touch MINI. It is possible you just have it set for Mackie (MC) mode and setting it to another mode might work for you. Perhaps you could use MT Pro to capture a log of the encoder incoming messages and point out to me what is wrong with them.
Yes, this will be the case if your encoders are in absolute mode, however, you could set it to relative mode and then use MT Pro to convert to absolute and continue to send 127 and one when it reaches the endpoints. If Capture one can handle relative mode directly , that would be even better.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thank you for your fast relpy
The X-touch MINI worked well for nearly 3 years but now 2 encoders don`t work very reliable. I ordered new ALPS encoders to replace them.
How can I change Mackie (MC) mode to another mode?
beatstep
How can I set the beatstep to relative mode? … with Arturia software?
Thank you Steve!
Everything workes fine!
Here is my summary for others, who wants to work with the ARTURA BeatStep & CAPTURE ONE:
Frist: Betastep needs to be configured to “Relative Mode” with MIDI Control Center
Example settings for encoder (knob) in
Clockwise direction:
INCOMING
Channel: 0 - 1
CC#: 10 (first knob)
Value: 65
RULES:
No settings
OUTGOING:
Keystroke: type in your Shortcut
Counterclockwise direction:
INCOMING
Channel: 0 - 1
CC#: 10 (first knob)
Value: 63
RULES:
No settings
OUTGOING:
Keystroke: type in your Shortcut
INCOMING
Channel: 0 - 1
CC#: 10 (first knob)
Value: Any set to qq
RULES:
if qq<64 then exit rules, skip outgoing action
OUTGOING:
Keystroke: type in your Shortcut
Counterclockwise direction:
INCOMING
Channel: 0 - 1
CC#: 10 (first knob)
Value: Any set to qq
RULES:
if qq>64 then exit rules skip outgoing action
OUTGOING:
Keystroke: type in your Shortcut
That way if you turn the knob faster, it will still work.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Would you mind sharing why this would be better? Not sure if I have encountered any problems with the 63/65 method but before I change the hundreds of translators, I like to know if it is worth it… Thank you!
The method described here in the linked post where you asign the Value to qq using rules to make sure that the values below 64 have an output for clockwise and above 64 anti clockwise. I just came past this post and wondered what the reasoning behind this method was.
That is one of a few messages to define relative encode behavior. This behavior is usually preferred for outgoing actions require endless encoders. Some controllers do not support relative encoders in which case we need to convert absolute to relative.
