@ohmrun The recent Generic Flexi script has what's called Function Layers, which means you can set up the *same* MIDI message to do a different API call depending on which layer is active.
I'm really unlikely to paint myself into a corner, the programmable space is yuge.
This is fkn lovely. so tactile.
Programmable enough to do wildly complex stuff, but I'm not having to figure out a graphics api to have programmed screen feedback.
64 setups of 64 parameters (32 buttons with up to 16 steps, 32 knobs) on the MIDI side is *plenty*.
I've got around the limitations of the current script by using a Bitwig MIDI splitter extension and virtual MIDI ports.
I can make a DrivenByMoss generic flexi script for device and track navigation in MIDI mode (Melbourne Instruments seems to be using channel 16)
The other issue I'm having with thinking about the Roto-Control is that say I want to bypass the manufacturers programming and use OSC, I'm not sure if I can set screen text or colours via MIDI on the fly, so I couldn't do a Bitwig controller script that changes device context.
There's an app they provide, so I suppose it's possible, but the protocol isn't published in the manual.
ohmrun
ohmrun
teezdalien