HELP!!! Export to OMF causes crash

I've done this a few times and found OMF support to be, let's say "sketchy". I think there's a size limit of 2GB (for the complete file) and possibly also an event limit. The only way I got it working was by making sure I comped everything down and had only a single take lane per track. Also, I removed all plugins.

Still more reliable is simply exporting stems, if that's an option for you.

You might be better off just exporting the raw tracks to a folder along with a detailed text file on track contents.
If im correct, your sending this to another producer to mix down, so exporting any automation is not really a factor.
Your basically sending him raw tracks of the project that line up/in synch.
 
I do this quite a bit and created a thread in the techniques section of this forum
http://forum.cakewalk.com/Orginizing-Labeling-Audio-and-Midi-Tracks-m3448904.aspx
On how label everything to send it out. I uploaded a Word template as well.
 
Stems are groups of tracks IE- Sub mixes, Bus mixes, Drum mixes,exc.
If your producer wants individual tracks and not groups, export the tracks.
 
Im not sure why OMF is crashing I really cant give you any insight on that to be honest.
But like I said if your producer is going to mix the project for you I wouldn't worry much about OMF.
(I could be wrong but I believe you'll only be missing tempo changes, markers and automation)
 
In my travels, I have found it is best to make sure everything lines up correctly
(bounce all your clips together to create one whole track VS. 20 clips on track 10).
Place a dummy note at 101:00 on your midi tracks so they also line up from project start, this way everything is totally in synch.
Send him a detailed report of tracks (he will love you for it).
And do as much house cleaning (what I call pre production): Melodyne fixes, Autosnap/synch corrections before you send it. This not only saves your producer from headaches but will also save you a few bucks.

if you want to send only audio tracks to the mix engineer, without any bus/sends things etc....and without doing an export out of Sonar.
you could bounce the clips in the track view (bounce to clips), to include any automation (gain, pan etc), then extend those clips (tracks) to the beginning and end, so all clips/tracks are same length and start at 0.
then bounce the clips again. (and name the clips/tracks if you want).
then if you save the project to a new folder and tick 'copy all audio', in the new 'audio' folder are all your tracks, that you could send to the engineer.
it's not a quick workaround though... and not sure if you get the good render algorithms (izotope Pow)...

OMF does not support MIDI.
 
http://www.soundonsound.c...f-transfer-sonar-files

You can still export your MIDi tracks so they can be brought into PT.
Or render to audio is the best, as there's no guarantee that your producer has the same Instruments you have and the same settings etc. better you render the them.

1 way is to select the midi clip by clicking on it, then simply drag/drop the midi into any folder..

Yes, I found doing things in steps helped a lot:
- save the original version, then remove all FX in the effects bin, enable the master FX bypass (for prochannel effects)
- remove any MIDI tracks from the project
- bounced down all comped tracks so each had one long clip per track.  I think the key was for me to do them one at a time (or a couple tracks at a time) as opposed to letting the OMF do all these during OMF creation, this way I could find the track which was causing an issue.  I did have one or two tracks in a project which seemed to have issues when bouncing down - not sure if there was corruption in one of the WAVs, but once I deleted the comp for that track and bounced it down again, all seemed to work well.
- OMF has a 2 Gbyte filesize limit.  I found the resulting error code wasn't very intuitive - it just said something like 'error creating OMF', but didn't mention anything about file size.  So I would watch the file size increment in file manager as the OMF was being created, so I knew whether or not that was an issue.  If I exceeded the 2 GB limit (which I did in many cases, since my projects were 40-50 tracks of 24 bit / 96 KHz audio), I needed to break the project down into two OMFs by deleting half the tracks, creating an OMF, then reopening the file, deleting the other half and creating another OMF.
 
Hope that helps.
Russ

Ohh and by the way...many times I thought Sonar crashed at the end of the render...and it did, but the OMF was fine despite the crash.   Check it out.

Jimbo 88
Ohh and by the way...many times I thought Sonar crashed at the end of the render...and it did, but the OMF was fine despite the crash.   Check it out.

Yes, the same thing happened to me once or twice.  It was strange, but I was happy to see the OMF was ok.