When you say that sonar is crashing, give us some details about exactly what's going on.
 
you open sonar, you hit play?  you insert ozone?  sonar disappears?  puts up a pop up saying it's sending a trouble report?    give us as much detail as you can.

Upgrade to the E patch. It fixes a lot of bugs. 

John
Upgrade to the E patch. It fixes a lot of bugs. 

No problems with Ozone 5 here, all good with X3e!

By all means you should update to X3e as soon as reasonably possible, but I doubt that it is the version of Sonar that is causing the symptoms you are seeing, unless the installation is somehow corrupt. I have been running Ozone 5 on every version of Sonar since Ozone 5 came out with virtually no problems.
 
I say virtually no problems because there does seem to be a small miscommunication between Sonar X3 and the VST3 version of Ozone 5 that results in Sonar displaying the symbol for 32 bit audio processing, even though Izotope support assured me it is processing audio in 64 bit. Other than that, it works fine. The VST2 version does not have this issue, so that's the one I use, since there is no difference in functionality between the two versions and I like to be absolutely sure that the audio is using 64 bit processing.
 
Hope you get it figured out soon!

Hi Everyone, 
 
Again, thanks. OK, let me be more specific.
 
I have an audio/video only machine. i7 fast processor, 16 Gigs of fast ram, SSD drives, no other programs except Sonar X3b and Adobe Creative Cloud CC for video editing. Windows 7 Pro 64 bit. No virus software, no connection to the internet (except for activations). I've also used the Viper tweaks.
 
I upgraded from Sonar 8.5 to Sonar X1 (didn't use it too much) and then to Sonar X3b, where I am now and has worked well on 5 projects. I'm hesitant to upgrade to E now that I am in the middle of an important project that people are waiting for.
 
After I installed Ozone 5, Sonar is freezing, giving me a NOT RESPONDING error message up top, and 8 times out of 10 it WILL recover after long waits of 20-30 seconds, and then sometime give me a pop up box saying Not Responding, close program or look for solution, blah, blah. This will happen as soon as click on something or try to start playback with the spacebar. Even after I removed Ozone from my master bus, the program still was herky jerky and not responsive.
 
My guess is that either I should do a complete uninstall, clean, and reinstall going to the E version (after this project) and try again with Ozone (Ozone is now uninstalled so that I can continue mixing), or maybe its my project.
 
I have 6 instruments using Dimension Pro, one True Piano, one Lounge Lizard, one guitar track that was recorded, one lead vocal and three backup singers (with one singer doing 8 takes of harmonies and accents).
 
I know this is wrong, now, after I've done some reading, but I've got 4 instances of the Sonitus Compressor, three instances of Breverb, one instance of EQ, and one instance of that vocal processor that has the De-esser, EQ, Compression and Doubler (only using the Doubler and De-esser).
 
Could my problem be that I need to combine things to delete some compressors and verbs, and then also Bounce the MID/Sample tracks to audio tracks, and then this will free up processor power to allow Ozone to not freeze the computer by simply adding it to my master buss as I did?
 
Thanks again.
 

And this goes to Ptheisen:

ptheisen
<<By all means you should update to X3e as soon as reasonably possible, but I doubt that it is the version of Sonar that is causing the symptoms you are seeing, unless the installation is somehow corrupt. I have been running Ozone 5 on every version of Sonar since Ozone 5 came out with virtually no problems.
 
I say virtually no problems because there does seem to be a small miscommunication between Sonar X3 and the VST3 version of Ozone 5 that results in Sonar displaying the symbol for 32 bit audio processing, even though Izotope support assured me it is processing audio in 64 bit. Other than that, it works fine. The VST2 version does not have this issue, so that's the one I use, since there is no difference in functionality between the two versions and I like to be absolutely sure that the audio is using 64 bit processing.>>
 
When I re-install Ozone, do I choose 32 or 64 bit or both? And then you said you are using the VST2 version and THAT one is what you use for 64 bit? If so, the VST3 version has what supposed advantage? I'm just wondering if I choose one over another (don't know which one I was using but I "think" I installed only the 64 bit version), if it would help. 
 
Thanks.

Assuming that you don't have any old projects that used 32 bit Ozone 5, there is no reason for you to install the 32 bit version at all, since you're using a 64 bit OS. Within the 64 bit version, you still have choices. You can install the VST2 version, the VST3 version, or both. I'm pretty sure there is no actual difference in functionality between those two.
 
I have both installed, but I use the VST2 version, only because Sonar correctly indicates the 64 bit audio processing when it is inserted in the effects bin, while Sonar displays the 32 bit indicator when the VST3 version is inserted in the effects bin. I describe those indicators as double quotes (64 bit) versus single quotes (32 bit), since that's what they look like to me.
 
In case you're wondering, the audio processing bits are a completely different parameter than the OS bits, so I hope I didn't confuse you with that. Both 32 and 64 bit plugins can use either 32 or 64 bit audio processing, it's up to the plugin vendor to make that decision. Like you, I am on a 64 bit OS, so I only use 64 bit plugins, but in addition to that, I try to only use plugins that process the audio using 64 bits. Some do (Izotope, Voxengo e.g.) and some don't (IK Multimedia, Native Instruments e.g.).
 
Ozone is somewhat resource hungry, but with the hardware that you listed, the project you described should not overload your machine, unless something else is wrong. You may want to determine whether there are any hardware issues, and also check things such as whether Sonar is configured to use multiple cores of your processor.

Thanks so much, Ptheisen.
 
How exactly can I tell if Sonar is configured to use multiple cores? I'll Google this later or check the documentation as I can't right now, but I think you may have it as now I remember I used to see four processor windows (version 8.5?) and now only remember seeing one.

Preferences > Audio  > Configuration File variable ThreadSchedulingModel. To see the Configuration File option make sure Advanced in selected at the bottom of the Preferences dialog. Read about ThreadSchedulingModel here http://www.cakewalk.com/D...;help=INI_Files.6.html

Thanks so much Scook. Yes, using all cores. This is an update on my project crashing/freezing.
 
I save manually every 10 minutes or so, then backup up to two separate internal hard drives with a separate program.
 
I'm up to version 131 of my project, which is the problem project.
 
I kept opening older versions until I found that version 110 and earlier, all open and play back fine. It was at version 120 that I had installed Ozone 5, and even though it's now uninstalled, versions between 111 and 120 still crash/freeze. So I don't understand how that could be or how Ozone could be at fault. Just wanted to let you all the that weirdness.
 
At this point, I can lose all of my edits and at least start editing again at version 110, or, continue to trouble shoot.
 
I'm wondering if creating a new project and then copying in everything from my latest project, version 131, would solve the problem. I never did this, so I'm not exactly sure how to do it, but I'll go try. I'm assuming it's just "New Project", and then copy and paste everything over? Not near my music computer now, but if anyone ever done this, I'd be curious to how it's done and if it worked for a problem project file.
 
Thanks, all.