That restriction seems fine, if you can bank within the surface group.
I'd be putting things together in surface groups anyway and keep certain controls local to such a group.
For example, a surface group that functions as a custom zone that puts FX parameters of the selected track(s) at your fingertips is my priority. That's the time saver I need.
If I have to keep all the controllers I want to use for that inside one surface group, that's fine.
I'll use my MCU as one surface group for bankable control of track parameters, and everything else as another surface group to control FX parameters.
Is it possible to to change what a surface group is doing dynamically ?
I ask because at times, I'd like to use faders to control send volumes 1-8 for selected tracks for example, instead of volume or pan. So I'm wondering if switching to another set of definitions for a surface group is possible on the fly. If they duplicate what another surface group does, will this still work ? (Surface Group A controls send volume, Surface Group B does as well...)
|