That sounds awesome!

Anyone out there care to update these instructions for CSS 2.8 since the workflow handyman laid out is no longer possible? I have tried for 2 days to achieve this exact setup and still cannot seem to get it right.

Thanks fluxiia, was just about to post this.

Martin, this is probably due to the log.txt file size rather than MIDI data. https://remotify.io/community/question/if-css-running-slow-read-comment-…

I would like to push this request but because it seems that CSS sometimes gets unresponsive handling (a lot) of midi data ? For example I often see incoming midi from the Midi Fighter Twister (simple CC midi data) then CSS get’s unresponsive and although I even physically disconnect the controller CSS still shows incoming […]

Hi, I disabled the log function in CSS and use the Terminal on macOS with: “tail -F path-to-the-log-file”. Although it’s not that convenient as the built-in log at least it doesn’t freeze CSS.

Regarding your first comment: Its probably this listener which is causing the error (in test.json): self.song().view.selected_track.devices[0].parameters[26].add_value_listener When the mode loads, if the selected track doesn’t have a device at position zero containing 26 parameters then it will cause this error. Also note, the listener will only update when you reload the mode. It won’t update […]

There are tabs at the top, “My Scripts” and “My Controller Templates”. Here are a couple of videos using the new interface: Basics of using CSS (2.8): https://youtu.be/sdDZxPobh0s?si=DPPVt923JKNE3GhN UI changes: https://youtu.be/GeMFgf1VRwU?si=TRT6LohkH9XhTlpC

Not me, but cool stuff!

First thing to do would be to find out what the Yaeltex controller requires for lighting its LEDs. I’m sure they would tell you if you ask them 🙂