🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Remove all value listeners and control affectations for a certain mode

CSS Questions
Submitted by NiXtAn on Sun, 02/27/2022 - 03:02
NiXtAn
Control Surface Studio User

Hi,

I created a controller template using all the controls on my midi keyboard (Alesis V49). I created 4 different modes triggered by the buttons, but, for the first mode (Perform), I need to be able to use the notes and drums pads that are affected to different functions in the other 3 modes. Is there a way to remove all value listeners and control affectations for that specific mode?

Thanks!

Topic Category: 

3 Responses

Comments

aventham77
Control Surface Studio User
aventham77 - Sun, 02/27/2022 - 17:12
#1

Not currently, except via a somewhat awkward workaround of targeting parameters on a Max device that can translate them back to midi; but a few of us have been discussing it and hopefully it will be investigated further: https://remotify.io/community/question/send-cc-controller-max4live-device

NiXtAn
Control Surface Studio User
NiXtAn - Sun, 02/27/2022 - 19:51
#2

I just found out that the reason why unassigned controls are captured by the script anyway was because of placeholder value listeners on each of them. I just deleted them in the main script and all the unassigned controls/notes are now recognized directly in Live while those I assigned are picked up by the script. I don't know what these placeholder are used for except preventing input in Live, but it should be an option in css since note ccs can be used. They should still be recognized as notes in Live when not assigned.

Feature request:
https://remotify.io/community/question/placeholder-value-listeners-toggle

aventham77
Control Surface Studio User
aventham77 - Mon, 02/28/2022 - 11:01
#3

Am I right in understanding that you started with a controller template in which your keys and pads were defined as controls?
This will intercept all their midi data as you say, unless you remove them.
At the moment it's "either/or" - either you register them for use in the script, or they bypass the script altogether - unless you want to go to the extra trouble of hooking certain registered controls to the parameters of a Max utility device to convert their values back to midi, in a particular mode.