IANAE - but... Can you set 16 of the 20 CSS "memory elements" to represent "this Knob's Button is currently pressed" which you set and unset inside each "Button Press" Event Handler and then branch accordingly inside each "Knob Turn" Event Handler?
I'm lucky i got this far. For now I can probably just sacrifice some of the controllers or use the side button. But since I'm controlling all of this while I'm trying to play drums, it's a bit if of a juggling act.
This mess is what I'm going for. My next step is to integrate more looping control, so I can setup and control grooves. I'm thinking I'll do that with sends to a bus, which would be cool with a twist click.
There are definitely CSS tutorials on YouTube that demonstrate use of the "memory" slots. I suspect that's the only way you can make a combination event like that. When the Knob turns, the event handling code needs to know if the associated Button is also pressed in order to know whether to adjust "Track volume" or "Send level" for example, so your code checks a variable (the memory slot). If you want to follow through with that though, I think you'll have to lose the Muting on (same?) Button press.
Comments
Hi BillW,
IANAE - but... Can you set 16 of the 20 CSS "memory elements" to represent "this Knob's Button is currently pressed" which you set and unset inside each "Button Press" Event Handler and then branch accordingly inside each "Knob Turn" Event Handler?
I have no idea what that even means. Lol.
I'm lucky i got this far. For now I can probably just sacrifice some of the controllers or use the side button. But since I'm controlling all of this while I'm trying to play drums, it's a bit if of a juggling act.
This mess is what I'm going for. My next step is to integrate more looping control, so I can setup and control grooves. I'm thinking I'll do that with sends to a bus, which would be cool with a twist click.
https://www.youtube.com/watch?v=i9bwSw0dGPc&ab_channel=wolfereeno
There are definitely CSS tutorials on YouTube that demonstrate use of the "memory" slots. I suspect that's the only way you can make a combination event like that. When the Knob turns, the event handling code needs to know if the associated Button is also pressed in order to know whether to adjust "Track volume" or "Send level" for example, so your code checks a variable (the memory slot). If you want to follow through with that though, I think you'll have to lose the Muting on (same?) Button press.