Pro Tools OMF to Avid

[Terence Curren]

You can’t go that direction. Only from Avid to ProTools.

The reason for that is you can edit at the sample rate in ProTools, in Avid you can only edit at the frame rate.

In other words, in Avid you can only cut audio at 30, or 24, or 25 frames. Right on the frame.

In ProTools, if you are working at 48K, you can edit at 1/48,000th of a second. So how would that possibly come back into Avid land?

Automatic Duck worked around this on the FCP side by just rounding the edit point up or down on the return trip. But Avid has never supported this.

Terence Curren
http://www.alphadogs.tv
http://www.digitalservicestation.com
Burbank,Ca

[Job Ter burg]

PT has an Avid Compatibility mode, which places all cuts at frame borders. However, you can’t retain all things added in PT, unless you do destructive renders on everything.

[Terence Curren]

Learn something new every day.

Terence Curren
http://www.alphadogs.tv
http://www.digitalservicestation.com
Burbank,Ca

[Maria-luisa Meredith]

Hi

Thanks for all the helpful replies, I guess it’s back to the drawing board on this one. Cheers

Maria

[Gabriel Guy]

In my workflow we exchange OMFS (AAFs now actually due to new Avid requirements) often between Protools & Avids. However when exporting an AAF from ProTools to Avid I can’t seem to retain Protools volume automation when the AAF is opened in Media Composer.

Any thoughts?

Thanks so much for any/all help.

~Gabe Guy

Sound Engineer
Walt Disney Animation Studios

Gabe.Guy@disney.com

[Job Ter burg]

As Terry wrote, going from PT to Avid is not the way that Tewksbury has imagined us to go. With the “Avid compatibility” settings it is at least possible to go from PT to Avid, but as said, some things (like automation I guess) are not meant to travel that way.
If you are bouncing temp elelements, could you actually bounce them (mix them down to new tracks), or would that not suffice?

[Gabriel Guy]

Update for all of you is so far it appears volume automation does NOT travel from ProTools to Avid unfortunately, even with Avid compatability ON.

This link recommended turning Avid Compatibility OFF

https://books.google.com/books?id=n5j7lk_BQ34C&pg=PA337&lpg=PA337&dq=pro+tools+exporting+aaf&source=web&ots=0y7XLMB54U&sig=nxTTOD1tzxUVGBUXsJO2hOZKGOk&hl=en&sa=X&oi=book_result&resnum=7&ct=result#PPA337,M1

which still didn’t work either.

I’ve re-imported my own AAF back into ProTools and volume automation DOES come back so it’s in the AAF file, it seems the Avid has a problem importing it as clip gain data (unlike Protools which has the “convert clip-based gain to automation” feature upon import.

For the record yes I can create mixdowns in Protools to send but that’s not the most advantageous way to work in animation.

Thanks for the insight and advice.

~Gabe