hmm, controlling a previously selected parameter might be possible if you save the selected parameter object to a modifier, maybe you could use a button which triggers this to be stored. Then in the action section of the action block, switch to custom code and change this part: to the modifier: You would need 2 […]
Hello, This is still not possible??
All errors in your log appear to be coming from script not built using CSS: MiniLab.py and KeyLab88.py. So I would recommend deactivating these scripts as a starting point. “I also discovered that when I disconnect the MIDI input to my controller, the volume faders work normally, so it’s clear that the MIDI feedback is […]
Have you checked the log panel in CSS for errors being generated by the script in Ableton?
You can’t generate midi notes from nowhere. CSS takes incoming midi messages sent from your midi controller and attaches Ableton specific functionality to them.
Hi, We are aware of this issue and working on a fix, thanks.
second this request ^^
I never used 2.7 but agree that it takes a lot of clicks and scrolling to set up Mappings/Reactions. And having seen the tutorial videos, the use of dedicated columns where all parameters were easily accessible seemed more intuitive to me than having to click through the different sections like we have to do now. […]
Hi! I’m experiencing the same thing, meaning the Takeover Mode selection in the midi settings is ignored when a parameter is controlled by a control surface script rather than a manual midi mapping. Just for testing I mapped the first fader to volume on Track 1 using the Track Volume function in css and then […]
Hi John, same bug for appointed device: Regards, mj