Hey all,
 
I've opened a lot of OMFs, mostly without issue, but I haven't had the need to export them very often yet. Now I do, and I ran into an issue. I have around 20 tracks routed to a few buses, ending up at the master bus. Some softsynths and some audio recordings. I froze all softsynths so that the audio would be included. There are still some fx plugins on the tracks and some automation, I'm assuming that it will either be ignored or converted, either is fine really, it's more about transporting the audio with all the tracks correctly labeled and all the clips in the right place. I'd just bounce tracks but with many small clips it'd take a lot of unnecessary space so I thought this would be more useful.
 
I chose the OMF2 option, told Sonar to included the audio in the OMF file (the way I've always gotten my files), and told it to save. I chose the default WAV format and no stereo demixing.
Sonar goes to work for a while writing/copying various WAV files as preparation for writing the OMF, and eventually it ends up saying:
"Problem exporting OMF:
[project name.omf]
OMFI_ERR: Failed a semantic check on an input data"
 
Does anyone have a clue what might be wrong?
I'm on Win7 Ultimate SP1 x64, Sonar X3e x64.

I know there's a 2 Gb limit on OMFIs and that exceeding this limit will generate nonsensical error messages. Is it possible that your audio content sums up to more than 2 gigs?

It's not likely to even reach 1GB. More like 400/500MB.

Don't know. Sounds like a question for tech support

I'll try, there's so much good advice floating around here that I was hoping someone might know what's up.

I view OMFI export as a bonus feature (in any DAW): If it works, cool but I'd never depend on it. 

Well I can still bounce the individual tracks, I was just hoping it'd be more convenient. If I'm pressed for time I'll bounce the tracks, but for now I'd like to figure out where that error is coming from.

I did a whole thread on this. Dub and I even used Sonars test project and tried to export that as an OMF and every time Sonar threw out the error you mentioned and a couple of others.
 
I bang on about this all the time. Sonar PLEASE sort out the OMF issue.
 
SvenArne, Its a huge deal for me and others that work in the film industry. If Sonar could do this reliably I would never have to use Pro Tools again (which suits me down to the ground)
 

markyzno
SvenArne, Its a huge deal for me and others that work in the film industry. If Sonar could do this reliably I would never have to use Pro Tools again (which suits me down to the ground)
 

 
Sure it is useful, but the OMFI protocol seems very frail. I've transferred or tried to transfer *.OMF between SONAR and Cubase and back, Logic to SONAR, Pro Tools to Logic and so on. A LOT of times the files couldn't be imported, are reported as corrupt or giving back weird error messages. Fail rate in my experience is about 50%, followed by phone call to client/collaborator: "Sorry, dunno what went wrong but you'll have to try bouncing all tracks the old way".
 
Sven
 
 
 

Yes it is frail which is why AAF are better. But having said that I still need OMF, Sonar doesnt seem to handle it very well at all and I cant have bounced tracks as I need the handles and edit points for Dialogue.