Re: any workflow "workarounds" for lack of automation trim in vanilla?
I ran into a (very frustrating) edition of this limitation yesterday.
In my case I have a mix I did on the big PTHD/D-Command system. I was then working on it on the little Vanilla/Command-8 system. I have SATB choral overdub tracks each with existing automation to balance the parts. I want to make a slight adjustment to the whole choir at a few spots with a little ride of the fader. On the HD/D-Command system I'd enable the appropriate group(s), put the track into touch automation mode with trim, grab the fader, and make my tweak. The trim gets coalesced into the main volume lane. If I want to tweak later, I just repeat the process as many times as I want. It makes life so easy that I forget I can't do this in vanilla PT.
On the Vanilla/Command8 system, without automation trim if I grab the fader and start writing automation I am not adjusting the existing automation but replacing it. This destroys the part balancing I worked so hard to create.
It seems I have a few workaround choices:
1) Re-write the automation with the fader track by track by watching the old curve and following it "a little bit different."
2) insert a trim plugin and automate its gain. This is still track by track because I can't seem to get my plugins to follow groups on Vanilla PT. And I can only do complex moves once this way.
3) select a section of the automation lanes and use the mouse to "trim"the section up or down. No smooth fades for large adjustments, but at least groups work in this case.
4) bus my choir. In this project I am using sends to generate a poor man's surround mix so if I do that I lose routing flexibility.
|