Is that the case? Or does the event need to be known and programmed?
e.g., I have reconfigured a CMC-TP and a CMC-FD to send and receive various midi messages, and the touch faders update. If someone knows what channel and command to use then they can create an implementation.
Locked, in my view would mean that even if a person knew the right commands to send to the unit it would still not work.
Well, it’s still just a simple MIDI controller. Every button press and every rotary movement sends simple MIDI data. So it will work in every DAW you want it to work in.
Only the visual feedback needs some scripting work. In this day an age almost all DAWs have open scripting environments for external hardware support. So this shouldn’t be a problem. The only major DAWs without an open scripting API are Cubase and Nuendo but for these we have/had the official driver…
StudioOnePro. I have most things working except the pan knob on the CC121 is sending a channel selection message in S1. Im using the FADERPORT 2018 Device in S1 but you know things dont line up function wise.
Presonus doesnt provide a CC121 DEVICE and Steinberg doesnt give one to load up in other DAWS.
Like Martin is saying, it’s mainly a matter of midi in, midi out. Does Studio One have something akin to the Generic Remote? If so, you can program your own.
StudioOne does NOT have a Generic Remote in order to do this. Thats why Im using the FaderPort 2018 Device in Studio One as its the closest not including the pan knob
Logic : Use Mackie Control surface (tracks in logic will not follow track selection, you must advance tracks by using the channel select on the CC121, track in Logic has to be manual selected to match up, monitor on/off does not function)
StudioOnePro: Use FaderPort 2018 ( pan does not work, pan does track selection so you must do that in S1)
I did a complex Python script to fully integrate it into Ableton Live:
The tricky part is, that you need to send a “keep-alive” message every second to keep it turned on. Without sending this command every second, the CC121 is in idle mode with be blue Cubase Ready LED flashing.
This midi message is a system common message [0xF0, 0x43, 0x10, 0x3E, 0x15, 0x00, 0x01, 0xF7]
I think every 2s should be fine too.