Ozone can be a system resource hog and yes, the playback can suffer when the computer is struggling to keep up. Both Ozone and Melodyne are "high maintenance" plug ins that require a lot of computer power to run them in real time.

I actually had similar problems when I was using my Dell Laptop. My CPU usage would go above 50% and often higher... the result was playback issues.

The Solution: Depending on the DAW you are using.... I will refer to Sonar for this answer because that's what I use.

I will use the "Process Audio" command which takes the plug-in and it's settings and then applies the effect of the plug-in to the track and then removes the plug and the required processing in real time and leaves simply a wave that the computer can easily handle. Bounce to track is also a workable option, however, it creates a new track with the wave but it also leaves the old track and the plug-in in the project.

I started to use the Process Audio command with my laptop and since it works so well, I continue to use it even now with my custom built studio DAW which has plenty of power to handle everything I throw at it.


BTW: I use Ozone in the master with a custom tweeked preset. I also use Ozone in the vocal bus as well as in the bass/drum kit bus. All the instances are custom presets. Most of them are left to run live during the mix down since my DAW can easily handle them. When I insert Melodyne, I always process it out and leave the wave. I don't need Melodyne to run live in all my vocal tracks..... as I sometimes have 5 or more vox tracks. My DAW could probably handle it but I don't need to push the envelope that far.

So try that. Bounce or process the plugs out to audio. See if that makes a difference in playback.

You can find my music at:
www.herbhartley.com
Add nothing that adds nothing to the music.
You can make excuses or you can make progress but not both.

The magic you are looking for is in the work you are avoiding.