If you’ve received an AAF or OMF with this error, there’s not much you can do about it in Pro Tools
Instead they just say, “sorry, we just can’t do it.” How do I get around it? Why can’t it deal with capitalized words?” Pro Tools should be able to deal with this but it doesn’t. What is happening instead is it’s throwing out an error like “Translate does not support references to capitalized words.” Your reaction would probably be, “Huh? This seems to obvious. According to Translate’s design (and it’s purpose), it should be able to do it. So let’s say we have a document in English that we want to translate to Spanish. Translate acts as an interpreter between two languages. The video software is doing what it should be, the file format is designed to work with it, but Pro Tools doesn’t do it (for an unknown reason).Īnother way to think of it is like Google translate. It makes sense because video software and audio software can have multi-channel tracks with stereo files, 5.0, 5.1 etc. The file formats AAF and OMF were designed to allow for multi-channel audio files.
I cover more about how AAFs and OMFs work in Post-Production Basics: What Is An OMF Or AAF, And Why Does It Matter? It’s a way to get from video software (like Adobe Premiere or Avid Media Composer) to audio software (like Pro Tools or Cubase). AAF and OMF are file formats that exist to move media (like audio files) from one software to another.