 PARIS OMF - finally solved! [message #104783] |
Mon, 15 February 2010 13:37  |
|
|
Hi all. Some of you might recall our suspicions that file and segment info, which seemed to be missing from PARIS-generated OMFs, might actually have been included in those OMFs all along but in a way that other OMF-importing programs (including PARIS itself) were finding impossible to read on import.
I don't want to jump the gun here, but it now looks like this suspicion was correct. It would appear that PARIS-generated OMFs store and provide all the information needed to reconstruct sessions properly, as long as one approaches their import from the proper angle.
The insights which proved to be the key were provided, to our enormous gratitude, by user OMFoo on the Reaper forums yesterday.
It's all about what's done on import, so that insight would be a mere curiosity if we didn't have a developer who was interested in taking it and implementing it in their app.
So I'm also happy to say that user Runaway (AATranslator) has combined these insights with his own and has now announced PARIS OMF support in an upcoming release of AATranslator which is expected shortly.
In practical terms this means that PARIS-generated OMFs can now be opened in AATranslator and properly translated into a host of formats readable by a wide range of apps which include Nuendo, Cubase, Studio One, Vegas, Reaper and many others. This won't yet include PARIS mix automation, but if there's sufficient interest from the PARIS community he'll look into pulling that out of the OMFs too (it's in there).
I've been in email contact with Runaway of AATranslator throughout this process. He's a one-man operation, and he delayed the upcoming release of AATranslator specifically to spend long hours grinding on this. He was certainly not so crass as to hint at this - but I'll lay out the math as I see it: we just got at least a thousand dollars worth of skilled time focused on this issue.
Pending confirmation that this all works properly - 20 licenses would send a message from the PARIS community that this was "work actually worth doing". 30 or 40 licenses might say "...and it's worth tackling reading the automation info out of those OMFs too".
If you think the ability to export your PARIS OMFs and translate them into a host of other widely-compatible formats with a couple of mouse clicks is something you'll want to use (or even if you just think it's extremely cool that people are still thinking of us and helping us solve our issues) - then please consider buying an AATranslator license as soon as possible.
Your license is an important way of showing Runaway (and incidentally any other developers who might be wondering if supporting PARIS is worth stealing time from their other development priorities) that the PARIS community knows how to say "thanks" to people who step up to the plate for us. And every single license takes us a significant percentage of the way towards that goal.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Mon, 15 February 2010 20:38] Report message to a moderator |
|
|
|
|
|
| Re: PARIS OMF - finally solved! [message #104787 is a reply to message #104784] |
Mon, 15 February 2010 17:39  |
|
|
OMF is an old platform-independent file format that was used to transfer digital media session between apps, with audio in sync and volume/pan/mute automation in place [edited to add - I'm going to have to check my facts on the automation to be sure][edited once again to add - apparently so - and we're working on it for the next subrelease in a few weeks]. We used OMF all the time for film and TV work. OMF has been superseded by more modern formats like AAF, but since it's what PARIS has to offer (and it's pretty good) - and since it never actually worked from Day One - this'd be pretty groundbreaking news.
Working OMF will get your session *out* of PARIS painlessly, say for exporting to film/TV or to an external (ie non-PARIS) mixing facility. OMF *for sure* will not do plugin settings or EQ (I have no idea if there's any platform-independent format that would, for that matter), but it's still very useful.
Nothing can make, say, Nuendo read a PARIS OMF directly. But with AATranslator as an intermediary, it won't matter; you'd just export your OMF from PARIS and run it through AATranslator to turn it into whatever format you wanted. For some apps, that would even give multiple choices of formats.
I'll get to the second part of that question later...
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Wed, 17 February 2010 21:45] Report message to a moderator |
|
|
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
