Encoder Ring Parameter Value Update
Parameter position update when selecting devices
I have a set of encoders dedicated to “device control..” When I select a track those encoders now controls the 2nd device on that track. The Device function seems to be working. What is not working is that the encoder ring does not update to the parameter values when I go back to a device/track that had previously been altered. How do I get configure CSS so that when I select a device it updates the encoder rings to represent the current parameter values?
I’ve attached my controller and script files for a better understanding.
I am new to CSS, so any guidance is appreciated.
P.S. below are other topics I am trying to solve for that may or may not be related:
– Dedicated device mapping – My Goal: I have one button that I would like to dedicate to control of a specific parameter on a specific device in a specific track, and have that button change functions in a different mode. I want the button to stay focused/dedicated to the specific parameter, regardless of which track I have selected. (FYI, in my first mode I intend to dedicate this button to the Loopers “multi-button”)
– Track Select & Arm – I have a row of buttons for selecting and arming tracks. My goal is that. When I click a track button that it selects the track, arms the track, and turns the LED red. When I click the track button a second time the track stays selected, but is no longer armed and the LED turns white.
(I would be OK with select first and arm second too). In Ableton preferences I have exclusive arm select and in the options.text feature I use -EnableArmOnSelection. These work well for my Push 2 workflow. Right now, the current (undesired) behavior I am getting is some tracks are arming first, some are selecting first, and many are staying armed when I select a different track.
Hi Nicholas,
It sounds like you’re making progress but I’ll chime in here with your latest questions:
With regards to the ‘selected parameter’, are you using Reactions for this? as we don’t have a selected parameter option in the other mapping types – I wasn’t aware of the issue with Ableton beta, things for reporting this.
When you say you need to change tracks at least once, so I understand correctly, do you mean that on session load the faders do not show the correct values, but once you change tracks they then update?
With regards to the blue key blinking in Ableton, this happens whenever a midi signal is sent from a connected controller, as far as I know, there’s no way for the css script to affect it.
With regards to the Ableton Beta issue, unfortunately that’s out of our control, scripts can only hook into and use what is working in the Ableton API.
And with regards to 2, you could try forcing a refresh when the script is loaded,
Add a reaction which has the listener ‘script > script is initialised’
Then in an action reload the mode (in your case mode 1). Reloading a mode includes a refresh of the attached LEDs so that should update all of your connected controls.
I’ve updated your script with this reaction and attached it below.
“you have to “select” the device in the ableton rack – perhaps there is an easier method where i just set it to device 1 since i rarely later chain devices.”
yes you can set the device selection to a specific device number on either a specific track or the selected track if you like.
I think this video covers all of that: https://youtu.be/SSfaVfDqt7M
And with the beta issue, as its a beta, by design there’s unfortunately going to be broken things in there and it sounds like the selected parameter functionality is one of them.
Our scripts only ‘hook’ into and utilise this functionality. Live itself is the thing that updates which parameter is the ‘selected parameter’ and then exposes this via their api.
Maybe it’s something you could notify Ableton about via their beta feedback portal?
Unfortunately, we can’t support issues related to Beta versions of Ableton which don’t appear in the full release version.
Sign up
User registration is currently not allowed.