7.2 automation offline Latch prime bug

[Steve MacMillan]

I was playing the the new 7.2 offline latch prime feature, which is a very cool thing. Used with Manual Write automation buttons on the automation control panel, you can think of it as a way to take fader snap shots or enter trim amounts for selections without rolling the transport.



Heres the bug. Allow Latch Prime in stop must be selected in the preference panel. Say you have some fader moves and you make a selection that contains them. Then with the fader in latch-trim and without playing the transport, make a fader offset and click the Manual Write front to back button (middle button). The moves within the selection are trimmed by the fader offset amount. The selection is still highlighted, make another fader offset and click the Manual Write button. Now the entire automation playlist is trimmed from the beginning of the session to the end, ignoring the highlighted selection. That can't be right.

STeve

[Stig Eliassen]

Yes, I can confirm this behavior. The second trim completely ignores the selection.

[SessionKat]

I was playing the the new 7.2 offline latch prime feature, which is a very cool thing. Used with Manual Write automation buttons on the automation control panel, you can think of it as a way to take fader snap shots or enter trim amounts for selections without rolling the transport.



Heres the bug. Allow Latch Prime in stop must be selected in the preference panel. Say you have some fader moves and you make a selection that contains them. Then with the fader in latch-trim and without playing the transport, make a fader offset and click the Manual Write front to back button (middle button). The moves within the selection are trimmed by the fader offset amount. The selection is still highlighted, make another fader offset and click the Manual Write button. Now the entire automation playlist is trimmed from the beginning of the session to the end, ignoring the highlighted selection. That can't be right.

STeve

Indeed, Steve that is not right. I just reproduced it as you describe. It only happens in a TRIM mode, as I suspect the secondary Trim offset is 'breaking' the selection.

I'll investigate some more....thanks!

-tv