| OMF export [message #109910] |
Sun, 13 December 2020 14:46  |
Josh Herzog
Messages: 8
Registered: June 2005
|
Junior Member |
|
|
Hi, I am trying to export an OMF and it keeps hanging up at 20% and not finishing. Is there a trick to getting it to work?
Thanks for any help!
Josh
[Updated on: Sun, 13 December 2020 14:46] Report message to a moderator |
|
|
|
| Re: OMF export [message #109924 is a reply to message #109910] |
Tue, 19 January 2021 11:39  |
|
|
Hi Josh - I’m sorry that we never got back to you sooner, I’ve been caught up in lots of new projects lately. There’s a substantial entry on this in the wiki, but as the Wiki hasn’t been resurrected from the post-php upgrade fiasco from my server, I’ll do what I can from memory.
The bad news first: there are two factors that can kill an OMF export in its tracks. And once you have exported it (correctly) there’s only one app that can read it directly, and it’s not cheap: it’s the excellent AATranslator.
Then the good news: it’s easy to work around all of those factors if you prepare in advance, and the one app that can read it directly can translate it into a vast range of file formats.
The two factors that can kill an OMF export from Paris are 1) improper naming of audio files/regions and 2) a corrupted audio segment.
1) This one’s easy to fix. Look at all of your channel strips and make sure they only use alphanumeric characters – no punctuation or non-letter/number characters. After that, go into your audio bin and delete any region names (For example, if you have an audio file called “CHORUSVOX” and you have pasted it into three different choruses, naming them say “CHORUSVOX/Chorusvox1”, CHORUSVOX/Chorusvox2” and “ CHORUSVOX/Chorusvox3” you will want to delete the portions after the slash. The nearest I can figure is that characters that are permitted in track names aren’t necessarily permitted in OMF and this didn’t get “bug fixed” before discontinuation - and the same with the “slash” character, which it inserts between the file and region name.
2) This next is generally not hard either: corrupted audio. If there is an audio region that’s ever caused you grief in the session, start there. The stuff that chokes OMF is contained in the file headers, so my solution was to force Paris to create a new file, with a fresh new header. To do that I selected the segment, duplicated it and told Paris to use the duplicate. The extreme (but also extremely simple) version of this would be to create a new directory, point Paris to that as the new recording file path, force Paris to duplicate all files, verify they’re all in the new directory, and then tell the Paris session to use those new files instead.
Between those two fixes, I was able to achieve 100% success in OMF exports, and AATranslator was then able to convert Paris OMFs into whatever I liked. Hope this helps!
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Thu, 11 February 2021 16:50] Report message to a moderator |
|
|
|
|
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
