Mike - 32 or 64 bit Ozone? I remember asking about a display bug related to Ozone back in March, and you said yours was fine. Others discovered it was only the 64 bit version slowing the display down. So maybe you use 32 bit Ozone. In which case, the current problem may also be related to Ozone 64 only. Craig also mentioned problems with a 64 bit plugin. Maybe that's a clue?
Cheers, Peter.
 

I run full 64 bit. I did have some display issues around that time. That's what I was referring to in my previous post.

It was only happening in Sonar but it was caused by a Windows display enhancement I had set. That is something like Mouse hover activates window. Once I switched that off all my weird Sonar display issues went away completely and have not come back since.

OK, this gets weirder. Screen grab below shows Send Bus B (with Sonitus Reverb) outputting at +9dB and totally freaking out SPAN on the Master bus - note the RMS values (1.$), correlation at -1, and spectrum maxed out at all frequencies. This is before Ozone gets involved. Que? (to quote Fawlty Towers)
 

I'm not in front of Sonar at the moment.

Having a view of a bus at+9db isn't much help without seeing the tracks that feed it. The master bus is showing -0.1 so there must be something bring the level down.

There are 2 vocal tracks feeding that bus with send levels at -12dB. Neither have any audio at that point in the project. The Master bus is limited by Ozone's maximizer, where I set a ceiling of -0.1dB. This just doesn't make any sense. The project is fine until this problem randomly occurs.

It sounds to me like your audio interface was hit by a power surge. Do you have it plugged into a UPS?
 
I used to use surge protectors until I lived in a small town where frequent lightning storms and power outages taught me to use a UPS. Damage to gear is random, too. Sometimes things will still work, but do odd things from time to time... like what's happening with you.
 
I'd try a few things:
- another USB port,
- another AI,
- another computer (with your AI).

Yes I have noticed this very rarely though and yes in older projects have not paid attention to what plug in are used. One thing I've noticed is if you switch apps the effect disappear i.e. here is what meters look like after pressing stop
 
Now anything you do switch apps, minimize screen, or press task bar will make meters goto normal.
Don't know why image will not post.

Yes, you're right, that's a great observation. If Sonar is not the foreground app, the meters don't max out. However, I exported audio and swapped apps in the middle of doing this. The resulting audio was maxed out the entire time, so I suspect what you are noticing is a visual thing rather than an audio thing. You gave me another idea - check the CPU when Sonar is foreground and background. About 10% foreground, 1% background. Very strange.

rontarrant
It sounds to me like your audio interface was hit by a power surge. Do you have it plugged into a UPS?
 
I used to use surge protectors until I lived in a small town where frequent lightning storms and power outages taught me to use a UPS. Damage to gear is random, too. Sometimes things will still work, but do odd things from time to time... like what's happening with you.
 
I'd try a few things:
- another USB port,
- another AI,
- another computer (with your AI).

 Thanks Ron, but I suspect this is a software thing. It happens when exporting audio, which doesn't touch the hardware. Also, I can change the Master bus output to "None" and it's still happening.

Are you sharing your audio interface drivers with windows? In the Windows sound card settings there is also "give programs exclusive control" to check... if windows is trying to reset sample rate to another application, that will cause serious nonsense.