In 2.8+ the log file is in the panel on the bottom right (you can drag it up to expand it) Latest MIDI data is displayed below this in the very bottom right. (This is when you’re in the script editor) More details on 2.8 changes here: https://youtu.be/GeMFgf1VRwU?si=Owqf0feJLc4fgyxs

Hi, do you also have mappings setup for the knobs? Set any knob feedback to custom > uncheck ‘send LED feedback’ The reason I say this is we ran into LED feedback issues on buttons recently when workiing on our MIDImix script. It turned out to be conflicting MIDI messages being sent to knobs, preventing […]

Are you referring to Modes? https://youtu.be/_gtgD9eExTo?si=UQ35C9veHQUihtZH

agreed!

Hi, The first thing I would recommend to do is clear the log, this is located in the bottom right panel. As CSS continually monitors the contents of the log.txt file, as this grows it can cause CSS to become sluggish.

@JohnC Does your script “flatten” the controller to a series of empty buttons/sliders so that it’s an empty slate to build onto? And in that case what kind of data does your script contains and what is it that you actually did to prepare the device? I’m on the fence for investing some time mapping […]

UPDATE: I’ve figured out how to program a reaction that does device parameter control based on the selected device but now I’m trying to figure out how to implement “value scaling” into this process. Any tips?

Is there a newer tutorial for parameter banking for version 2.8 or higher? I am not seeing a mapping for parameter banking in version 2.8 like you do in 2.7. Also an updated tutorial for modifiers would be great. Both of these mappings failed to import properly to 2.8 when I migrated.

Hi, I appreciate your generosity but please don’t upload the .py files. You can export and upload the json files for your script and controller templates, this is fine and people can use them. Thanks

Yeah, thanks again. The script *is* showing after I rebuilt it in 2.8, but still no ‘Track Arm’… 🙁