Automatic Duck Alternative

[Michael Gissing]

As a picture and sound post facility, I can assure you that the one feature I don’t need is to transfer any level information from any edit system to the audio system. I even make sure that clip levels don’t translate.

The reasons are simple. Mixing for broadcast requires that pre mix stems are generated. So when you pull down the clip level on a music track under VO, I have to take that dip out and actually apply it to the stem return signal. Undipped pre mix stems are a delivey item so every one of those clip level manipulations has to be deleted.

Secondly, most edit rooms have poor audio monitoring. Mix judgements are often less than ideal.

Thirdly audio post is much more than just levels. Once EQ is applied and dynamics processing like compressor/ limiters then the original clip levels simply don’t work as a mix.

Fourthly, getting levels correct for broadcast specs is not likely to be close from a system like FCP. So again, your levels are not going to be useful. If you give a sound facility rendered aifs, they should say thanks, but no thanks. No handles, locked in levels that should be changed – not much use really. If offered, I usually don’t even waste time loading them. Sure, put a mix guide track on your seqeunce playout.

If you need a quick and dirty mix, then stay in house and use Sountrack.

[Chris Borjis]

While we’re on the subject of Pro Tools anqd OMF,

Does anyone know why there is a problem with OMF files above 2GB?

What the heck are long form programs supposed to do?

I made an OMF that either had the error or was larger than 2gb and pro tools hd 7.1 would not import it.

[Jim Fink]

one place that this would happen would be sending the sequence to an Avid Via autoDuck, then the rubber banding will show up in the sequence, but I am not sure you could link to OMF audio elements unless they also would come across.

The rubber banding in the avid timeline would certianly work if you recaptured.

but, every omf audio export or import I have ever done, although not on FCP, was clean, no efx, or leveles. the bare bones.
j

[Jeremy Garchow]

You have to break up your file.

It’s the OMF standard to not accept files over 2GB

[John Pale]

The OMF standard is very old. Avid never really updated it after a certain point…though you can work around the limitation on Avid systems by using Linked OMF files instead of embedded, which is what FCP uses. Avid has moved toward AAF with their latest MXF based media, so don’t expect the 2GB limit to change, as it is essentially being phased out.

Just make several timelines with 2-4 tracks of your audio. Export from each and put it all back together in ProTools. Easy.

[Chris Borjis]

sounds good

thanks