Dave Labrecque
03-29-2005, 06:46 PM
Hi Bob,
RE: this new feature...
" The I, R and O Jump To Channel zones have been enhanced to eliminate jumping to blank module sections on the Return and Output channels. Whenever you jump to a different module type, the vertical offset is now adjusted to display the fader section of the module."
Seems that it only works when navigating using the IRO hot zones. Navigating any other way (clicking on a track in the MT, on a channel in a Mixer view, or scrolling in any of these) works as in the past.
Also -- I notice that the new feature defaults to the fader position on the switched-to channel regardless of whether or not there's a common module between the channels. E.g. if I'm looking at the FX module of an input channel and I switch to an output channel, it goes straight to the fader module of the output channel. Would it be tough to have it track to the FX module of the output track in such a scenario?
Tha same could apply to label, assign, and aux modules (return only on the aux). And having it work bi-directionally would be nice. I see the current implementation is not bi-directional, as for output- (or return-) to-input channel navigating.
RE: this new feature...
" The I, R and O Jump To Channel zones have been enhanced to eliminate jumping to blank module sections on the Return and Output channels. Whenever you jump to a different module type, the vertical offset is now adjusted to display the fader section of the module."
Seems that it only works when navigating using the IRO hot zones. Navigating any other way (clicking on a track in the MT, on a channel in a Mixer view, or scrolling in any of these) works as in the past.
Also -- I notice that the new feature defaults to the fader position on the switched-to channel regardless of whether or not there's a common module between the channels. E.g. if I'm looking at the FX module of an input channel and I switch to an output channel, it goes straight to the fader module of the output channel. Would it be tough to have it track to the FX module of the output track in such a scenario?
Tha same could apply to label, assign, and aux modules (return only on the aux). And having it work bi-directionally would be nice. I see the current implementation is not bi-directional, as for output- (or return-) to-input channel navigating.