Help me rickywander , you're my only hope! Lol...but for real...looks like Stray hasn't been on here at all since November...hope he's just busy and is otherwise doing alright.
I just tried replacing the XY pads with faders, to see if that would make a difference, but nope...all four faders are binding to the first parameter, even if I try changing the channel and CC#s...all four labels (/x1/name, /y1/name, /x2/name, /y2/name) are also displaying the same value as /k1/name.
I don't recall Stray or any of the instructional videos stating that there's a limit on how many parameters you can bind to? I'm pretty sure in the demo video he actually has more than 8 parameters bound with the Pro Bindings accessory. And note that I'm NOT grouping the plugins and using rack macros knobs, I just configured the parameters using Live's configure option....hold on...
While I was typing this out and thinking about it...I realized that maybe Ableton groups each set of 8 parameters into a bank...I just never realized this nor did I ascertain it from reading the manual, until I was typing this out and it clicked. So I'm leaving everything as-is for those who come after, to learn from me bumbling my way through this (LOL).
The command that gets the bindings to the right place is as follows:
DEV Bn Pp X (where n is the bank number and p is the parameter number within that bank)
If no bank is specified, the default is bank 1 (the so-called "Best-of-Bank"). I've been using Ableton for well over 10 years and never realized it was called this...
So the following code in Encoder Bindings.txt works:
Post by rickywander on Jan 10, 2021 9:35:35 GMT -5
Not totally sure if this is the case, but only eight P are allowed.
When B is not specified, P1 to P8 are the "Best of bank" parameters, after those you have B1 P1, B1 P2, B1 P3.... for the second block of 8 parameter to remote, as shown in the lessons included (DEVICE PARAMETER REFERENCE)
Post by rickywander on Feb 4, 2021 18:17:34 GMT -5
When you REINIT you will asset the variables (and macros) to their original values. Then one can change them both at any moment. They will retain their values until a REINIT or a new reassignment is triggered.
I'm testing this feature and its amazing (the OSC-output), just exchanging opinions. I'm getting my Computer a bit overwhelmed by the OSC messages, I don't know if any of you have the same latency issues, in order to troubleshoot this myself I'm listing the factors may be involved as well in my case: - My device's layout is formed of (broadly) 32 Binded MIDI Encoders and OSC is reporting broadly 70 Values at a time (35 being /OSC/name 35 being /OSC/value) - I'm using "Open-Stage-Control" , running the server on the same Computer as the DAW . (I get like 20% of CPU usage just for o-s-c while the 50% ish is used by Ableton). - My Computer is not high-end , "AMD E1-7010 APU" 1,50 GHz with 6 GB of RAM (4,96 usable) . (Quite a bit of a bottle-neck probably in here, I'm just having delivered an i7 with 16 GB of RAM and touchscreen soon ) - My "Preferences.txt" is routed to the loopback device (127.0.0.1) with a refresh rate (I've tried with 5 and even with 1).
Many factors in here, I don't known where is the bottle-neck in here, if my device is a bit of an Over-kill for the current computer Specs (I will try with the i7), or I may have used OSC a bit too extendedly?. Or maybe using a "o-s-c" running in other host will actually sort that. Or may be the ClyphX code not optimized to send such a many information in that short period of time?