dubdisciple
I did not get those errors. The only oddness i got was, one of the tracks was blank (and I'm sure that was my fault since it was an unfrozen midi track) and although thr OMF opened fine in Sonar, all tracks were silent when opened in Audition
Cheers for your cross check Mr D.
The problem I guess is that I have - rather than a test project - a project where theres 49 tracks, 10 busses and god knows how many edits, fades, automation and thus it just could be the age old problem with OMF's in general (i.e they are flaky as hell), or that theres a problem in the way Sonar handles them or both...I can totally sympathize with Sonar and OMFs in that they (OMF's) are gremlin ridden and the room for error is high.
What I would like to see is some sense in the OMF Sonar errors that can help me troubleshoot the issue, or some better dialogue on the export, or for Sonar to support handles, or for Sonar to support fades. Either way I do believe a further update to Sonar addressing OMF/AAF multi DAW post Production compatibility would just be a Godlike implementation for me.