preserving dialog editor\'s volume automation
 

we sometimes receive tracks from editors with volume automation written to the tracks and the mixers of course prefer to have all the faders flat to start. in the past we had tried copying the automation into a trim plugin. but due to the latency of that plugin, we would sometimes get clicks, pops, or snippets where the automation just wouldn't translate properly.

i would like to try copying this automation into the trim *playlist*, now that it can stay separate from the volume playlist. has anyone else done this successfully? it seems like it should work but i know that the trim value is just a delta value so i'm wondering if there is something i'm not considering.

thanks,
matt

Re: preserving dialog editor\'s volume automation
 

Copying unequal information is posssible. You need to paste the information by using the ctrl-key additionally: CTRL+COMMAND+V.
On the other hand you could duplicate the track and just tick the automation to be duplicated.
Or paste the volume automation into the volume trim automation, and deactivate the volume trim automation.

Hope this helps,

Timothy

Re: preserving dialog editor\'s volume automation
 

thanks timothy. yes i know how to copy it over. i would cntrl copy the volume playlist to the trim playlist and then flatten out the volume playlist.

i'm more interested to know if it would translate ok. since trim is a relative value and volume is an absolute value....

Re: preserving dialog editor\'s volume automation
 

Another way is to copy the volume information to the input automation of the EQ plug-in of each track.

Re: preserving dialog editor\'s volume automation
 

that would be cool but this mixer has a waves q10 at the top of his chain and its range is from -24 to zero so i don't believe it would translate properly. is there a particular eq plugin you've used that works?

Re: preserving dialog editor\'s volume automation
 

You will end up with automation that starts at a nulpoint that's 12db lower, so you rais the output of the Q1O to maximum.

I still find it completely unacceptable that there is latency on the trim plugin.

Re: preserving dialog editor\'s volume automation
 

aha! that is great. i'll propose that as well then. thanks mark.

Re: preserving dialog editor\'s volume automation
 

Matt,
Henchmans idea is a good one except in your case the Q10 has a problem with hot peaks. It sounds like a screen door slamming when it gets hit too hard.I lower the input 3db and raise the output 3db so it's back at unity. If you don't and now you input hot dialog it will sound bad.

Re: preserving dialog editor\'s volume automation
 

True. What I've been doing is using the Q10 as an RTAS plug-in. This distortion then does not occur. I think it's because the RTAS is 32 bit float.

I prefer the Equim plugin for notch filtering over the Q10, but most studio's don't have it. So, you use what they got, and be happy.

Re: preserving dialog editor\'s volume automation
 

Is this true? RTAS plugins have 32bit floating input/output bus path vs. 24bit fixed input/output bus path of TDM?

Phil