The PARIS Forums


Home » The PARIS Forums » PARIS: Main » UPDATE: PARIS and OMF Export
UPDATE: PARIS and OMF Export [message #104748] Wed, 10 February 2010 10:22 Go to next message
kerryg is currently offline  kerryg   CANADA
Messages: 1529
Registered: February 2009
Senior Member
Administrator
Hi folks. I came back to find this info at the Reaper forum. User "Runaway" is the developer for AATranslator, a utility that translates between various DAW formats.

Quote:
I guess because I like pain I decided to 'have a go' at the Paris omf cited earlier in this thread. Well I think I have this converting - all the output looks good but will confirm when i can get to a daw to test.

Just downloading the other one (245mb) and will let you know how that one goes.

<b>So it looks like Paris omfs may be supported in the next AATranslator release due in a few days time.</b>

BTW It looks like Paris omfs do not contain frame rates or if they do they are hidden under some obscure entry and not the 'standard' "TCCP" either way we have a work around for it by a user selectable rate.

Just converted that 'crop circles' omf only issue with both is associating each clip with the correct audio - I will try and get that sorted tonight.
__________________
www.aatranslator.com.au
www.mediasweeper.com.au
Last edited by Runaway; 12-07-2009 at 06:21 PM.


Quote:
Quote:
Originally Posted by kerryg:
The hypothesis I want to test is that rather than PARIS OMFs just accidentally omitting all that info, that it's actually in those OMFs *somewhere* but not properly parsed, and it might just be a matter of locating it and allowing for it.

Would it be useful for me to open and export the same PARIS project as an OMF several times, with trivial changes between them - say just changing track names before re-export - to let us look at what changes occur between those resulting OMFs? - k


What you are saying may well be the case. I would be more than happy take what you can give me and see what we can sort out.

Might I suggest also (if the option allows) both embedded and reference omfs.

If you could also give me a summary of what I should be seeing with any values in samples that would be excellent.

<b>If we can get this organised soon hopefully any Paris specific changes can make our next release.</b>
__________________
www.aatranslator.com.au
www.mediasweeper.com.au


I want to get to the bottom of why some of this info doesn't show up so I've started generating more comprehensive OMF test files, changing a small detail (starting with framerate) and looking for changes in the resulting OMF. This should tell us if the info is simply omitted, or is in the resulting OMF in some obscure entry that a developer like Runaway can track down and decipher.

But I've rediscovered some interesting things en route. Even if it's simply omitted, the "export segment list" in PARIS' Audio window contains some of the essential info that "OMF export" seems to garble.

So whether or not PARIS OMF export omits or garbles that info, a segment list exported at the same time would likely include enough info to cover some essential gaps. While this is not a terribly useful observation in isolation, with the cooperation of the developer of AATranslator, a properly built file might be created from importing both a PARIS OMF and a PARIS segment list at the same time. At that point we'd be translatable on some level into anything that AATranslator supports.

Of course, I'd consider these to all be temporary fixes until we hit the broader goal, which is to obtain or create documentation for the PPJ format. This would permit any cooperating developer to build direct import for PPJs into their app (and for that matter, with that info and the Reaper SDK we could build our own PPJ import plugin for Reaper easily enough). I'd like this much better, since OMF seems hardly worth dignifying with the word "standard".

But for now - I don't use OMF much myself, so I don't know what users would consider essential. Framerate, samplerate, bit depth and audio locations and lengths are all pretty obvious, but let me know what other info you'd consider essential in an export from PARIS.

If you consider the ability to export from PARIS to some other format an essential feature that would speed your workflow, and want to take a few minutes to contribute some exported OMFs (accompanied by an exported segment list - the whole process is only a couple of minutes) so we can do more comprehensive testing, let me know and I'll give you an FTP address to upload them to.


"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon

[Updated on: Wed, 10 February 2010 10:38]

Report message to a moderator

icon4.gif  Re: UPDATE: PARIS and OMF Export [message #104780 is a reply to message #104748] Mon, 15 February 2010 11:25 Go to previous message
kerryg is currently offline  kerryg   CANADA
Messages: 1529
Registered: February 2009
Senior Member
Administrator
OK, really big news - thanks to users on the Reaper forum we appear to have had a fundamental breakthrough in understanding PARIS-generated OMFs. I'll put it in its own thread and link.




"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
Previous Topic: Need help getting system back up and running
Next Topic: PARIS OMF - finally solved!
Goto Forum:
  


Current Time: Mon Nov 18 18:26:50 PST 2024

Total time taken to generate the page: 0.01557 seconds