Automapping layers
Hello!:)
I’m an absolute noob and I would like to ask for assistance to set up layered macro automapping.
For instance, my controller would get automapped ( Xtouch mini / Midimix) to the first 8 macro on a device, then switch to the next set of 8 after a press of a button. Where do I need to start?
Thanks!
I’m fairly new to CSS as well, only been making scripts for the last month or so. Prior to that I had started this spreadsheet to get a sense of the possibilities and to have a more search-friendly way for finding the Condition or Action I needed. Since then, I’ve been trying to make it a sort of go-to for any documentation around CSS and MIDI controllers.
Here are a few scripts:
– My earliest is the Nektar Pacer script where I wanted to see if I could manage Listeners from within a single Reaction: instead of having a “Select + Arm Track” Reaction for each Listener, I made one such Reaction that listens to all 5 Listeners and reacts accordingly. It also includes a Reaction that starts recording in the next empty Clip Slot on the selected Track when its Listener is pressed again (with “again” meaning each later press after the Track has been selected and armed by the first press). The third Reaction is a “Play/Stop” button that loops through the Clip Slots of a Highlighted Track and starts playing the last Clip in the list (or stops any playing Clip).
– The second script I made was for someone on Remotify who wanted to be able to control the Macro’s of a Device in a Chain that had been activated through firing a Clip. I had to recreate his situation, because i didn’t even know you could automate Device selection or that you could add that automation to Clips. One thing I also wanted to add was that the currently activated Device would show up in Detail View (the window where you can see the Devices at the bottom). It took me some time to find the option in the menu because it wasn’t obvious to me; you can find the option at: Live Object Model > Song > Select Device
– The last script I made was for a guy who wanted his Akai APC40 MK2 to make the Clip colors (of Clips in a session box) show up on his pads. I don’t own his MIDI controller so I tested it with my MIDI Fighter Twister and then changed the colors and buttons for his APC40. Haven’t heard feedback from him so I don’t know if it’s working at all for him. I resorted to custom Python coding for this one, it seemed easier to me. It’s a script that could still be made more advanced. The part I struggled with was making a button color change dynamically whenever a Clip’s color changed. I couldn’t find a way to add a color_index_listener to a newly selected Clip Slot. Later I found a comment from JohnC that Listeners are hard-coded to a mode. To add a new Listener, you need to re-activate the Mode.
The last thing I worked on was some custom code to change the colors on the Nektar Pacer with because you can’t use velocity messages to change the Pacer’s colors with, you have to use raw MIDI messages.
Whatever complex setup you’re trying to achieve with your MIDI controller, I’d suggest breaking it up in many little parts. Test out if the Conditions and Actions that you think you’ll need will work the way you expect them to.
MIDI Controllers and CSS can have certain unexpected limitations (like the inability to change colors on the Nektar Pacer with velocity values, or how Listeners are hard-coded to a Mode in CSS), so I’m not sure if everything you’re envisioning with your controller will be possible without using any custom code or some work-around (or at all). But until you’ve reached that hurdle, there’s no need to worry about it.
Sign up
User registration is currently not allowed.