Ohhh gotcha. Yeah, I'm still in the process of wrapping my head around bindings/X-controls, didn't realize bindings were specifically referring to that aspect of it. I'll update the thread subject for clarity.
In any case, I've already tried the hotfix (and gone through that other troubleshooting thread), to no avail. It just seems odd to me that some X-controls would work and not others...
Last Edit: Jul 25, 2020 0:41:19 GMT -5 by batmundo
Ok figured it out - I realized that because I was confused about bindings versus X-controls, I had put everything into the Button/Encoder Bindings.txt files instead of X-Controls.txt. I knew it was something stupid...
So just to make sure I have this right - are bindings purely for controlling parameters (dynamically)? Hence why something like:
b1 = note, 3, 0, 0, 127, up
...would not work in the Button Bindings file; i.e. the command is not related to any specific device parameters, hence no response?
Also, I noticed the manual says Button Bindings are:
"...really only useful in cases where LED feedback from a parameter is needed. In most cases, X-Controls should be preferred."
Is there a reason for this? Say, if I wanted to have a set of mute/arm toggles for different sets of grouped tracks - wouldn't I want to use bindings to toggle between "layers" of assignments? Or is it still possible to do this with just X-Controls?
Post by rickywander on Jul 26, 2020 6:59:35 GMT -5
Bindings are for dinamically remoting parameters like levels, pan, sends, macros or eq type switch. use knobs here.
In the case of button Bindings the main advantage (probably the only) is the light feedeback they provide.
But, as Bindings can remote only one parameter at a time, in the case of Button the Actions (via X/G-Controls) are better suited also because you can use Actions Lists (more then one Action at a time). Also button are perfect for triggering pure Actions.
So for buttons go with X-Controls or G-Control (for ex. short press: mute, long press: arm).
In order to have a similar to binding behaving with the last, you will use X-Modes that will change on the fly the Actions a button does. The way X-Modes works is via Macros reassignments (Macros.txt), so something like this : create some Macros in Macros.txt, assign them to X/G-Control in the respective .txt files, then reassing the Macros assignment to buttons, for some group of buttons, changing the X-Mode
Resuming : Bindings is for dinamically remoting parameters (even automatically displaying those on a tablet with OSC) while X-Modes are for dinamically reassign Actions (via Macros) to buttons.
Hope it clarify something! Join our group on Facebook, we are always happy to help basic- intermediate level users! where we cannot help the Forum is the only resource!