automation follows edit bug?

[Matt Chan]

when i draw out a region with the trim tool, it is screwing up breakpoint plugin automation that comes afterwards. it is basically destroying the node that keeps the following automation flat and creating a ramp between the preceding value and the next breakpoint. i checked on a 6.4 system and it doesn't exhibit the same behaviour.

to replicate:

1. create a track and write some plug in automation between two points
2. within those two points create a region of tone and trim it back a bit.
3. select the trimmed region and write some new plugin automation to it
4. draw out the region back to its original length
5. look at the breakpoint automation playlist for one of the plug in parameters

if this is a bug, then it is potentially very serious since, by going back to an earlier point in a mix and drawing out a region, i could potentially jepoardize anything that comes afterwards.

if someone could please recreate and confirm that it is weird, it would be much appreciated.

thanks,
matt

PT7.2
HD3 Accel
Dual 2.5 Ghz G5
Mac OSX 10.4.6

[CCash]

Have to ask, under Operations, do you have Automation Follows Edit unchecked?

[Matt Chan]

i have it checked.

[DigiTechSupt]

Matt -

I tested this and wasn't seeing anything strange.

What automation mode (write, latch, touch/latch, etc) are you in when you make the first pass? What about the second pass?

Does the behavior change when 'automation follows edit' is not selected?

[CD Productions]

If "automation follows edit" is not selected, I do not have this problem. However, if I extend a region, my automation does not extend with it. If "a.f.e." is selected and I "option-apple-/" automation on a region and then extend or fade that region, the automation for that region is now down the entire track. I think this is the same problem Matt is having.

[Matt Chan]

yep - what charles said. i'll try again:

the impact of this is particularly apparent if you "black" your tracks with baseline automation before mixing.

- write a baseline value for say, volume at unity gain between say the 1 hour mark and 2 hour mark (select between 1 and 2 hours and write to all enabled with volume enabled and fader at unity)
- create or insert a new region with no automation attached to it within the 1 hour and 2 hour mark. shorten the region back a bit using the trim tool.
- double click the region with the grabber or cursor tool
- write different volume automation (say +12db) to that region using a write to all enabled command (with volume enabled) or the trim tool (viewing the volume playlist)
- go back to waveform view and extend the region using the trim tool

now if you look at the volume playlist - instead of seeing the volume maintained at unity gain after the newly extended region, you should see it ramp from +12 to unity at the 2 hour mark. the baseline automation is completely compromised.

hope that is more clear....

to answer your question:
- we "black" our automation (vol/pan/send level/send mute/plugin) before we start mixing. our first pass is generally done in latch. then we final using touch or touch/latch.
- when i turn off automation follows edit, i believe it just doesn't follow my edit at all - ie. the automation remains unchanged. this is what i would expect but this is NOT a workaround since we need to carry our automation when copying and pasting stuff around.

the current workaround pointed out in the post forum is to make sure you are selecting beyond the clip boundaries when writing automation to a selection. this ensures that the automation isn't tied to the clip itself. extending the region past a breakpoint in this manner will not blow it away.

please let us know.

matt

[Matt Chan]

sorry, please try this with plug in automation, not volume.

i am using a Q10's 4th band gain automation for the tests...