There are eight of these each :
- Adjust track send 1 volume (MIDI CC/OSC only)
- Adjust track send 1 pan (MIDI CC/OSC only)
- Send: Mute track send #1
- Send: Mute track receive #1
That's pretty limited for those of us actually using this. It's a limit I personally bump up against when designing my mix templates. These actions are supposed to make things easier, and if you only have eight sends, or eight receives, it's great to a certain degree(see below).
Two actions in particular stand out already.
Send: Mute track send #1The OSC implementation does not cover send mutes, which is the reason I need to use these actions to toggle the send mutes on and off. And all that without feedback to my OSC control surface because there are only these actions.
I've got plenty of buttons and midi triggers, but only eight actions. Bummer.
Send: Mute track receive #1A great concept with an featureless interface implementation.
Reverb sends get more than 8 receives a lot of the time. That's one aspect that needs extending.
There's zero feedback outside the I/O window of a track. You'll only know by looking at the send displays on the source tracks, which is what you didn't want to do by using receive mutes. Same for the routing matrix. It's send-specific, not for receives at all.
Even if you use the I/O window, it's a feature desert. No clicking+drag on a mute button there to toggle more than one send mute.
Shouldn't there be
at least 16 of these actions, and a LOT more for receives ? 64 ? 128 ?
And what about
adjusting receive volume levels for receive 1 of selected tracks ?
And OSC support for send mutes ?