OMF vs AAF

[justmarvin]

What's the difference between these two? I thought OMF was the standard. Is AAF less compatible to other editing systems than OMF?

I was trying to export my project into an OMF file but it won't let me because it said that my project was an MXF and to transcode it to OMF. So I did just that and transcoded it but I am still getting that same error. Anyone know what's wrong?

Thanks,

JM

 

[milksac]

OMF is the old standard AAF is positioned to be the new standard. Right now we're in the middle of the transition between the two - meaning some apps don't support AAF yet. What are you exporting to? Pro Tools handles both formats.

 

[Noiz2]

In general AAF is the better choice if it works for the two systems. It is a bit more of a "standard" than OMF in that there is a a lot of variability of what constitutes "support" for OMF. As I understand it AAF will be a bit more uniform in what "support" means. And it transfers "better". File names stay intact with AAF, OMF creates new filenames that are very cryptic and are hard to trace back to the source if you need to for some reason. I think AAF also supports bringing more automation info over, though like OMF that is an area where there is likely to a big variance in what is "supported" by various apps. The only AAF's I've gotten have been from FCP (I'm on PT), but so far it has been smoother than OMF has been.

 

[Daygola814]

The only AAF's I've gotten have been from FCP (I'm on PT), but so far it has been smoother than OMF has been.

Final Cut Pro exports AAFs? Are you sure about that? Last time I checked, FCP didn't support exporting AAFs & I heard their XML was what they used for similar results.