|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
OMF AAF Volume Automation
Avid state that "AAF is the new format and contains more information than the OMF. OMF loses the volume automation and names of the tracks when exporting and importing from one application to another. AAF retains the volume automation and the track names"
https://avid.secure.force.com/pkb/ar...S/FAQ/en331113 I’ve had been using OMF for decades prior to the AAF. The volume automation has always transferred from FCP into Protools using OMFs. Why does all Avid/Protools affiliated sites state this when i have OMF sessions from over 10 years ago that proves to me that OMFs do transfer volume automation? Other non avid related sites support my claim. Here's an example i made https://vimeo.com/619438950/bc308f8092 I'd really like to find out why this is Avid's take on it. |
#2
|
|||
|
|||
Re: OMF AAF Volume Automation
That document is from 2009. How important is this issue to you? This is a user forum so don't expect an answer from Avid here.
OMF is long dead. There were limitations on automation and clip data depending on the source program. I believe Pro Tools itself would not export volume automation in an OMF.
__________________
~Will |
#3
|
|||
|
|||
Re: OMF AAF Volume Automation
It was incorrect in 2009, it still is in 2021.
what does it matter? I'm not new to the subject, I've been a member here since 2002 and been using protools since 1994. I've often seen Avid representatives responding in the DUC. That may well be how it is for yourself and many others. However, I still receive OMF's from film makers who haven't upgraded from FCP7, so for them OMF is very much alive. Mike Thornton recently did a piece on ProTools Expert stating the differences between AAF & OMF, while quoting from the 2009 document line that OMFs don't transfer automation. It's alive enough for him to talk about it. Quote:
AAF's also have limitations and react differently when importing into PT depending on the NLE & version it was created in. Exporting an OMF from PT is not something I consider, as its not part of my workflows. I'm referring to importing an OMF (created in an NLE like FCP7), into protools, as per the video link, There must be a valid reason that line was taken. I'm looking for any facts on the matter. |
#4
|
||||
|
||||
Re: OMF AAF Volume Automation
Same with Premier Pro, i.e. volume automation transfers from Premier Pro into Protools using OMFs. So yeah, that AVID doc is incorrect or outdated.
__________________
Desktop build: PT 2020.5 / Win 11 / i9-11900K @ 5.1GHz / 64GB / 4TB NVMe PCIe 4 / Gigabyte Z590 Vision D / PreSonus 2626 Laptop: PT 2020.5 / Win 11 / i5-12500H / 16GB / 1TB NVMe / Lenovo IdeaPad 5i Pro / U-PHORIA UMC1820 Ancient/Legacy (still works!): PT 5 & 6 / OS9 & OSX / Mac G4 / DIGI 001 Click for audio/video demo Click for resume Last edited by EGS; 10-05-2021 at 07:28 PM. |
#5
|
||||
|
||||
Re: OMF AAF Volume Automation
Quote:
G
__________________
Composer/Sound Designer/Protools 2024.3 Ultimate, MTRXII-TB3, DADMAN MOM, Cisco SG350-10MP EthernetHUB, KLANG:quelle 4 Channel Dante™Headphone Amp, DVS,MADI, Mac Studio Ultra,128 RAM/4TB SSD, Ventura 13.6.6, DP 11.3.1, Logic Pro X 10.8.1 DOLBY ATMOS Facility/MPSE Motion Picture Sound Editors Avid Certified Professional ProTools/Dolby ATMOS |
#6
|
|||
|
|||
Re: OMF AAF Volume Automation
Wow didn't expect a point by point rebuttal.
On the NLE side they can use either keyframe volume or track volume automation. One or the other, sometimes both, sometimes neither would make it into the OMF. Maybe that's what the document was referring to. Or maybe it was a mistake. But again, it is from 2009 hence the question how much it matters. If it really bothers you file a support request with Avid, see if you get a response. I cannot fathom anyone still using FCP7 but if they are it was capable of exporting AAF like 15 years ago via Automatic Duck. OMF is dead.
__________________
~Will |
#7
|
|||
|
|||
Re: OMF AAF Volume Automation
The clip keyframe and track keyframe is what I was referring to when AAFs don’t transfer uniformly across from different NLEs.
A lot film makers are not tech orientated people but make great films, aren’t interested in the upgrade path and just use what they have, because it does the job. The only reason I put it here was because there are many other experienced users my age that would have come across this and may know why Avid states otherwise. I’m not trying to fix anything, 10years 15 years, what does it matter if it means something to me, if it doesn’t to you then ignore this thread. I’m just trying to reach out to those in the broader community that understands that just because a version software has been superseded, doesn’t meant it’s obsolete. It’s not the latest software that makes an operator good. The best music producer I know uses protools 8. |
#8
|
|||
|
|||
Re: OMF AAF Volume Automation
Quote:
However, have you received an OMF that failed to transfer automation, if so from what NLE did it originate? |
#9
|
|||
|
|||
Re: OMF AAF Volume Automation
Quote:
Not outdated, just wrong, as this has been happening for decades now. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Volume vs Volume Trim Automation? | snowplaysmusic | Getting Started | 2 | 06-25-2021 11:20 PM |
Converting Volume Automation to Clip Gain = Higher Volume! | EricWillhelm | Pro Tools 10 | 8 | 11-01-2011 11:12 AM |
need help with volume automation | Digitalsound1 | Tips & Tricks | 4 | 07-17-2010 09:00 PM |
Volume Automation | Robbie Hollywood | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 6 | 09-24-2007 03:20 PM |
Volume Automation | hookiefree | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 8 | 08-31-2003 07:01 PM |