Greetings to all,
I had a situation the other night with ozone. While doing some (on the fly) editing in Sonar Pro I tried to change a setting inside ozone and got a horrible noise/static. When I changed back all was good again. Tried another change with same results. This has never happened before. I have settings for 48x512. I did not try raising the 512 to 1024. That might be the fix. Just wondering if anyone has run into this. Just have not had this happen before.
Sonar Professional, I7 2.8 Dell,16g ram, win 10
Thanks
 MJ

I use Ozone 5 all the time.  I usually go for a 1024 setting in my buffer.     What was the change you made inside ozone?  Where was ozone inserted?  I typically use it on the Master Buss.  Often when it is engaged I experience some latency and potential Midi Drop outs - so I just work around it and freeze my synths before I get into ozone.  As far as a feedback loop - I have not experienced anything that dramatic

I was a little surprised. I also usually use the 1024 in mixing but haven't been in a little while. Was doing the change between presets just to listen to other possibilities. Change made in the master bus. I probably will bump the buffer.

Yes, Ozone 5 is CPU heavy, and it depends on what you already have going on in a project (#of tracks, fx ,dynamic plugins,automation etc.) besides Ozone. Some projects can get glitchy with CPU being overloaded and some can fly right through. I have found the same solution to be the answer, raise buffering.

I just posted on this a few days ago in this forum and mentioned I had Ozone instantiated  but was not sure my issue was ozone and my overall issue (which I now think is a combo of little things) is perhaps slightly different. But twice now in recent weeks, I got a static / noise when making EQ changes in Ozone 5. I have ozone on a bus fed by two acoustic guitars. This happened on two separate projects and I am now mixing down a third project. I will be watching specifically for this as I am now gun shy about making EQ changes in Ozone. My buffers are also at 1024 for mixing and I assumed it was a cpu issue since I am marginal in that area. But I can't say anything for certain, I am just going to watch carefully for it now that I have experienced this noise twice. Note, I am also using 8.5.

Trying to load a full preset with the transport going will cause freaky things to occur. The ins/outs are still "active" as far as SONAR can see, but the guts are getting jumbled and need to come online. It should stabilize once it does, but it seems that when you did this it "stuck" that way? Did stop/starting the transport have effect? I have not swapped presets in Ozone 5 recently with the transport running, so not specifically tested this. If it is CPU-related, it should stabilize and run the buffer through... if it takes 15 seconds you might want to check upstream processing to lighten the load, as it were. If it truly "stuck" that way, something is up.
 
Getting such from making an EQ change I would definitely not expect. Ozone 5 is CPU-heavy, so freezing/bouncing things to free up CPU might help. I tend to bounce/render things a lot because of CPU-paranoia although I am probably more over zealous than I need to be.

mettelus
Getting such from making an EQ change I would definitely not expect. Ozone 5 is CPU-heavy, so freezing/bouncing things to free up CPU might help. I tend to bounce/render things a lot because of CPU-paranoia although I am probably more over zealous than I need to be.

Thanks for the advice!
 
I have a bunch of very small projects I am wrapping up, e.g. 2 acoustic guitars L&R with a single electric guitar up the middle. I am not seeing a cpu or disc drain, I just assumed there is a lot of load with Ozone. Still, like I say, I suspect there are additional things happening on my aging pc and interface. I'm just going to monitor carefully certain things and see if I can see anything definite or just a bunch of suspicions.

Thanks to all. When doing these kind of changes I usually bypass all other ozone effects. I definitely will bump my buffer. Never had this problem before win10. I was hoping this was not the prob. Thanks again MJ

I've had this problem, intermittently in the past with Ozone 5, trying different presets.  But, its been a while and when I was on Sonar X3.  I haven't had the problem since upgrading to Platinum.

I think it's best to bounce your mix to a wave file and master the track in a separate session with Ozone. Much less stress on the CPU and also allows you to separate mixing and mastering.