Post by systemexklusiv on Feb 14, 2020 12:16:59 GMT -5
Hello everybody :-)
I am in the midst of setting up the Xtouch mini controller and I want to control the Freeze-Button of the Ableton-Delay. Unfortunately the XTouch mini is lacking a "local off" function and the internal OS (in case of a momentary button) is setting the LED to on if one presses and turning the LED off if the button is released.
1) I'd like the LED to be turned on when the freeze is active and and only off if the freeze is inactive. 2) I'd like the CC Momentary button to be used by Ableton (thus ignoring the 0-values and just counting the presses)
Here is what I tried: a) Bound the Button in the Button Bindings.txt
# Works almost since only the "PRESSED" state is taken for advancing in the (PSEG) list it acts like toggling but still the Xtouch's internal # LED-OFF overrides the 1st "PRESSED" state thus the LED is off
It would work If I could insert "WAIT" in the (PSEG)-Seuquence than I could delay the midi-action for turning the delay on for some milis but WAIT cannot be used in (PSEQ).
I wonder if I missed some functionality since I own ClyphXpro for 2 Days - does anybody have some thoughts/suggestions on this?
Haven't used that controller, but I've read that it supports MCU emulation, so I'd try putting it in its "MC mode". In that mode, the buttons should send notes and their LEDs should not be locally controlled. If that's true, you could simply use bindings.
Post by systemexklusiv on Feb 14, 2020 14:21:55 GMT -5
Awww this is slightly off topic but I noticed that the MC-Implementation has RELATIVE_SIGNED_BIT mapping mode - it is working from Controller -> Ableton but this way I can not update the Encoder-Ring on the xtouch mini properly because there is no translating back to an absolute value for the encoder ring.
The buttons work very good now. The xtouch mini has a global channel in order to receive messages for controlling the LEDs but this way I loose the cool BIND functionality which is awesome
Regardless of the mapping mode, the output ClyphX Pro sends will always be absolute. I don't have an actual MCU here, so can't check, but I think its rings are controlled by a different MIDI message than the MIDI message the encoder sends. Bindings doesn't currently have a way of dealing with cases like that since it's somewhat unusual. If you could find the MIDI messages for the rings though, you could just create two bindings for each encoder; one for the encoder and one for its ring.
As far as the buttons, I'm not sure what you mean. AFAICT, the buttons use channel 1, which is fine and wouldn't prevent you from using the BIND action to rebind them.
Post by systemexklusiv on Feb 15, 2020 8:00:49 GMT -5
I decided to move the 2-Bindings issue to a new thread as your suggestions regarding the button LED-Feedback has solved the problem. In MCU-Mode the buttons of the X-Touch are updated by incomming NoteOns and not by the Behringer OS on the device.
Great :-) thank you for your help !!
In respect of the 2-Bings thing I opened up this one: