Bakers. OMFs in Platinum? For the Sound Designers/Film massive.

Not yet. Though we might make some changes to video in the Windows 9 time frame. I've been in touch with Microsoft about the current shortcomings in Media foundation video.

Thanks for the reply Noel, for me the video engine is no deal break as I dont have any issues with the old engine as far as playback is concerned and I dont expect Sonar to be video capable, its just a plus.
 
However, the OMF issue for me is slightly troublesome as I have previously reported. All my OMFs are sent to me from editors usually via AVID or some other video editing software and I think here lies the issue. Compatibility with the OMFs from one platform to another. Of course I'll still use Sonar as my ultimate creative tool and always will but it does pain me to have to open up Pro Tools to open the OMF and then to export the stems into Sonar.
 
Oh well, would have been nice but again thanks for the reply and Dub mate, am glad you are fairing better with the pesky things, but I reckon as stated above its because I am getting them from Video Editors (they did used to work pre X series tho)...
 
Anyway, I have a workaround, albeit an expensive one.

I hear you, but when OMFs worked pre X series there must have been *some* tweak or bug that is in there.
 
I also have my cheat sheet and advise Editors to send me the most stripped down of OMFs but the X series just cant handle ANY OMF from an editor thrown at me, a pain. But I have a workaround and as I love Sonar so much I dont tell anyone in the industry of my buggy woes.

+100000000

Hi Noel, I havent reported any for a while as its the same issue I had originally and the problem got closed off.
Dub and I in a thread from a while back extensively tested an OMF with the Sonar test Project file and came to the same conclusions.
 
I can though re-generate the issue no problem and report it if it is any help for you chaps?
 
 

1. <File> <open>
2. locate OMF (exported from Avid as a non embdedded OMF - this is important as most embedded OMF files break)
3. <open>
4. Make sure sample rates match (in this instance 48100, bit depth original, tempo(doesnt matter as i'm working in film), Check store Project Audio in own folder, Name project, set location)
5. <ok>
6. Immediately "Sonar has closed unexpectedly" etc, 
7. Have to end process to restart Sonar
 
Notes:-
I can confirm that I have no issues in my non OMF work with Sonar i.e very few crashes and my system is stable, I have no issues with 32 bit plug ins or other anomalies, I am fully licensed, OMFs open fine in PT 10, this also happens with embedded OMF's in Sonar.
 
These files come mostly from FCP(final cut pro), but have had the same issues with Premiere also. If it helps the Bakers I can document the versions of the software and OS's they are generated from in the future.
 
 
I havent tested exporting OMF's from Sonar as I usually have to export stems (such is the nature of my non music related work) 
Also worth noting is that if I move the OMF session file into a different folder from the reference files then I will be prompted to search for the it but when I point Sonar to the file its back to step 6 (see above)
 
Expected behaviour (as was pre X series) was all of the above but step 6 would be....
 
6. Locate file
7. Point Sonar to source file (i.e 568b.wav, 569c.wav etc etc)
8. Sonar picks up the files and populates them into the project.
9. An Open OMF.
10. Bingo.
 
Hope this helps?
 

Have read that Dub, good article.
 
In essence, the file type was never intended to become an industry standard in the film world, but it has, and I seriously feel sorry for the poor coders that have to wade through the complications of supporting the file type. Almost as much as I feel sorry for the poor Users that have to wade through the minefield of workarounds (such as myself and my other poor colleagues).
One of the hardest things you have to do on a project is to set up the project and thats before you have even started the creative process.
So, this thread isnt a gripe at Sonar but clearly a gripe as a professional at the unprofessional "standard" that we have to endure cross platform.
Dub, your idea is great in practice but how would one go about lacing together a single platform to glue together compatability cross platform? 
 
A third party plug in that could open an OMF and then to re-point it to a DAW would be a good start, so an opening dialogue such as.
<openOMF>
<Select Source>
<then select either FCP, PREMIERE, PRO TOOLS etc etc>
<Select bit rate etc etc etc>
<Select Source file folder>
<Create target folder>
<Create name>
<Select Output source>
<Sonar, PT, Cubase etc etc etc>
<Check output settings>
<Export>

markyzno
Have read that Dub, good article.
 
In essence, the file type was never intended to become an industry standard in the film world, but it has, and I seriously feel sorry for the poor coders that have to wade through the complications of supporting the file type. Almost as much as I feel sorry for the poor Users that have to wade through the minefield of workarounds (such as myself and my other poor colleagues).
One of the hardest things you have to do on a project is to set up the project and thats before you have even started the creative process.
So, this thread isnt a gripe at Sonar but clearly a gripe as a professional at the unprofessional "standard" that we have to endure cross platform.
Dub, your idea is great in practice but how would one go about lacing together a single platform to glue together compatability cross platform? 
 
A third party plug in that could open an OMF and then to re-point it to a DAW would be a good start, so an opening dialogue such as.
<openOMF>
<Select Source>
<then select either FCP, PREMIERE, PRO TOOLS etc etc>
<Select bit rate etc etc etc>
<Select Source file folder>
<Create target folder>
<Create name>
<Select Output source>
<Sonar, PT, Cubase etc etc etc>
<Check output settings>
<Export>

I'm thinking it could be tackled in one of two ways either:
 
1) an app that strips out all but the simplest characteristics,  leaving only audio files, lenght, time and other simple traits or two
2)  along the lines of the structure you pointed out. I'm guessing some proprietary code knoweledge for each platform would be required. 

Nothing yet.