Thinking about the few requests for receives that have shown up recently.
Also been pondering CSI inconsistency between EuCon Sends/FX and Midi/OSC Sends/FX mapping.
It really boils down to x vs y, row vs column, etc.
Say you have an 8 channel controller.
The way we map Sends now (except EuCon) is to take the Sends for the selected Track and spread them out on a set of surface controls -- let's use the 8 Pan pots on the 8 channel controller as an example.
Ok, let's call that x layout -- side to side -- the Sends are laid out left to right on the Pan pots.
We could also easily envision a layout where (like EuCon) you don't need to select a Track, the Sends for each track are always displayed -- the difference is, only one Send for each track is displayed -- you need to navigate in the up - down direction -- the Y direction -- to get to a different Send for a Track.
So in the Y layout, the 8 Sends shown on the Pan pots will be for the respective tracks -- Pan pot 1 has a Send for the Track on Channel 1, Pan pot 2 associates with the Track on Channel 2, etc.
Right now we use for X layout:
Code:
SelectedTrackNavigator
MapSelectedTrackSendsToWidgets
MapSelectedTrackReceivesToWidgets -- to be added
MapSelectedTrackFXToWidgets
MapSelectedTrackFXToMenu
We just need something for Y layout:
Code:
TrackNavigator
MapTrackSendsToWidgets
MapTrackReceivesToWidgets
MapTrackFXToWidgets
MapTrackFXToMenu
We already have the notion of TrackNavigator and it is syntactically and programmatically spot on for this usage.
Looks like we just need the new Y mapping Actions and we are good.
Actually, if you think about it, the Y layout also needs an up/down pair of navigation buttons to navigate up and down the "slots".
I think if we do this, we will satisfy a whole bunch of feature requests.
See any holes ?
Comments ?
Suggestions ?