On the simplest project (one audio track), if I have Ozone 6/6.1 (VST2 or 3) on the master bus and minimize the Ozone window, the time line becomes jerky, and the Now Time also stutters. Can anyone reproduce this?
 
It's not the pause/break key thingy - checked that. Also, Ozone 5 doesn't have this problem.
 
Cheers, Peter.
 

Can anyone reproduce this problem before I submit bug reports to Cakewalk and iZotope?

It does it here with the Ozone 6.1 trial version, my Ozone 5 doesn't do it, just like you reported.  Looks like yet another reason to skip Ozone 6.  If past experience with Cakewalk and iZotope is any guide there is 0% chance this will be fixed.  I'd be amazed if they even bother to look at it.
 

I have Ozone 6.1 Adv but don't have any problem with it in Sonar Platinum.

Hey Mudgel - I wonder if you'd mind trying something for me. Open a new project that includes the Metronome bus. Insert Ozone on the master bus, minimize the Ozone window, and hit play. Does it stutter? I've found that deleting the metronome bus (or sending it's output to other than the Master bus) fixes the problem.
 
Cheers, Peter.

No wait, wrong tree. So long as any audio at all is routed through Ozone, the stutter occurs with the Ozone window minimized. By deleting the metronome in an otherwise empty project (or changing to a MIDI metronome), I deleted the only source of audio to the Master bus, even through the metronome was not activated. Since a muted audio track still gives the stutter effect, I'm guessing activating the metronome is like unmuting an audio track.
 
So, Mudgel, do you see this issue if you have audio routed through Ozone and the Ozone window is minimized (so you see the little window header in the lower left corner of the screen)?

I don't use 6.1 in Sonar. It works brilliantly as a standalone, and - for me at least - helps me focus on getting the mix right first before going to the mastering stage. I used to run O5 in Sonar and that was good but shifting to the more intense IRC3, used to really tax the system. Had to end up bouncing tracks if I wanted to minimize CPU overload. So it's really great to have the standalone option available.

I just tried it with mine.  With the VST 3 Ozone 6 on any track, the master or an individual track and minimized it won't play.  However, the VST 2 (32 bit) version does not do this and plays OK when minimized.
 

You're right - the 32 bit version doesn't do this. Curious. The window doesn't turn up as a small header in the bottom left of the screen when minimized, but turns up in the taskbar instead, and everything plays fine. Thanks for the extra info.

Hi Peter,
 
I am seeing the same behavior in Platinum/Ozone 6.1 VST3. Thanks for the catch.