🔥 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.

Dynamic Send Control using modifiers

Submitted by tebgeronimo on Sat, 04/02/2022 - 07:10
tebgeronimo
Control Surface Studio User

I have a pretty reasonable working understanding of CSS.

For the last 4 hours I have been bashing my head up against a wall.

Here is what I am stuck on.

I have a modifier (m1) that I am changing based on selected track. (it is being posted to AL' s status bar to confirm change)

I have a track selector with a send that is supposed to correspond to M1.

I.E. Select Send, Use Modifier M1

IT IS NOT WORKING AT ALL.

PLEASE HELP!

I think it is a bug. I have tried on Ableton 10 and 11.

Topic Category: 

5 Responses

Comments

tebgeronimo
Control Surface Studio User
#1

I looked inside the script and found this line:

self.send_1_id_6["module"] = "self.song().tracks[self.track_num(0)].mixer_device.sends[-1]"

I changed it to
self.send_1_id_6["module"] = "self.song().tracks[self.track_num(0)].mixer_device.sends[self.get_modifier_value('m1')]"

Now it works.

I am not happy to have to do this in the future as I plan to use modifiers a lot for sends, and it is already a massive hassle having to edit the text file to add pitch-bend functionality..

I think I can confirm this is a bug that requires dix ups to work.

thank you

tebgeronimo
Control Surface Studio User
#2

NB forum won't display my inline code. lame.
self.send_1_id_6["module"]
=
"self.song().tracks[self.track_num(0)]
.
mixer_device.sends[self.get_modifier_value("m19")]"

JohnC
Forum Admin
#3

Hi tebgeronimo,
Thank you for the in depth report, we have now fixed this issue.
As this was fixed on the server, you can simply re-install your script into Ableton and your sends with modifiers should now be using the correct code.

tebgeronimo
Control Surface Studio User
#4

WOW, Thanks, that was a fast turn around. I am so glad to know it was a bug, I was really starting to question my self.
Fastest bug response ever.
One impressed and grateful customer.
T

JohnC
Forum Admin
#5

No problem, glad to hear it's now working for you :)