Do you have your Twister set to factory settings? Our controller template assumes that you are using these midi settings.

Would a buffer be useful? A list on your computer that temporarily stores the data coming from Ableton and that feeds that data at a slower pace to your devices? I don’t know enough about this sort of stuff to be useful at this moment. Maybe you could ask on Stack Exchange as well?

It could be that the loop is starting at the number 0 (meaning the first device has loop_number 0, second device has loop_number 1, etc…) while the numbering inside the Parameter Mapping starts at 1 for the first device. If so, this would mean you need to add 1 to the stored loop_number to get […]

Hi Glenn, thanks a lot for your efforts! I will try it. Regards Dieter

Hello again, I found a solution to the problem that occurred with the “solution” given in my first comment, namely that we’d have to manually insert the code everytime we’d regenerate our CSS script. The solution is to make a Reaction that dynamically adds the “send_midi” method to the class instance. You can find the […]

Hi, I also was stumped by this problem a while back and today I finally found (some kind of) a solution. The _send_midi method is part of the ControlSurface module. Looking inside the module’s code I found that it then sends the bytes to the method _do_send_midi, which in turn sends the bytes to self._c_instance.send_midi […]

Hi, let “z” be the rgb-value in decimal, then you can calculate red, green and blue parts in the form: red = z//65536 z = z – red*65536 green = z//256 blue = z – green*256 Regards Dieter

Hi  John, first, thank you for “keep password” in the app login – sometimes the small things make me happy ;-). I’m still struggling with selecting devices and listeners for parameter names or values to send out via midi sysex (there are several threads in this forum about this problems). It works quite unreliable without […]

I’m not entirely sure but I don’t think it can be done natively in CSS with how the code is processed. This is how i think it’s processed: in Ableton’s main loop, Ableton checks MIDI messages. If you were to code with a delay to those messages, then the main loop is put on hold […]

If you open the json file there are a bunch of “null,” entries. I removed these and the template loaded ok. Not sure why they are there