Quote:
Originally Posted by Geoff Waddington
Exactly, or even things like:
Each row is a zone
Each column is a zone
Each quadrant (2x2 buttons on a Maschine) is a zone
etc.
This, along with Layers on the axt/fxt side, seems to make much more sense than the discussion about a matrix approach we had a while back.
Seems like navigation doesn't really make sense in a huge row column way, but rather in a "clusters" of surface controls/actions way.
Perhaps a better word for Layer is Overlay, that conveys the sense that these are temporary overrides of the normal functionality (e.g. fxt overlay), dunno...
|
Yes, the Zone and Overlay concepts sound very clean and useful to me. *thumbsup*
By the way: the current FX overlay / mapping method still does not work well for me, it gets often confused what FX to map to the surface requiring mouse clicks to get it right.
Also, I have found no way yet to unmap the overlay from the surface so that the original page mapping becomes active again. Am I missing something obvious?