Ozone 11 killing my sessions

[jalan]

Sometimes literally. I can only run it for about 20 minutes before playback gets choppy, things freeze and I have to shut down.

My laptop literally has a issue with the processor fan that's in need of repair, so I assume that's part of it, but no other plugin crushes my system like Ozone 11.

Just wondering if any other Reaperites have had this experience...?

[mschnell]

Ozone sometimes takes a lot of CPU power. As this heats up a single CPU, weird things can happen if the chip runs hot.

[jalan]

Thanks for the quick reply. Make sense. Hoping to see a big difference once I can part with my laptop long enough to get it fixed

[AudioWonderland]

Originally Posted by mschnell

Ozone sometimes takes a lot of CPU power. As this heats up a single CPU, weird things can happen if the chip runs hot.

I always struggled with Ozone on a few levels. It cause issues occasionally as you have seen but I also never really like the results I was getting from it. All in my head perhaps but I ended up moving on from it and went a different path. I hope you have better luck with it. Nothing worse than a tool that is killing your flow no matter how good it may be

[mschnell]

I often use Ozone 11 (elements) on the master track if I am too lazy to tweak a bunch of effects on the sum. Ozone very easily creates a rather nicely mastered result.
I would always recommend it for this task, and to those who don't want to bother with more sophisticated mastering at all, as the element version (at least sometimes) is rather cheap.

[Fin]

In general, I am regularly using Izotope Ozone 11 software on my Windows 11 machine and don't have any issues (used on two songs posted to Wikiloops today).

However, today I did experience some weird behavior and the problem was fixed immediately once I took Ozone out of the mix. The behavior was slowing my recording down to a much longer delay reading than what Reaper was reporting. I had the software set to 11 milliseconds and it was about a full 500 milliseconds to print my recording (plus I could detect a massive delay when recording with Reaper). I regularly use Overloud TH-U for getting my basic guitar sound and had no issue with that plugin at the same time. I had turned off Ozone 11 and left TH-U running. Once that was done the software behaved just fine and I didn't need to close Reaper or reboot.

I haven't had any issues at all with overheating and I monitor my temps through some software to make sure everything runs smoothly.

I would first try the simplest thing - reboot. If that doesn't fix the issue, start getting worried about high temps.

[inthevoid]

Not with Ozone specifically, but I have found Reaper slow down considerably and become extremely choppy, and my CPU temps spike with even 1 or 2 heavy mixing/mastering plugins active on my master chain (things like Pro-L 2, soothe2, tape emulation plugins etc.) I don't have these on my actual master track but on a track that all my other tracks route to before going to the Reaper master track.

The GUI slows down so much to the point where I basically try and write music with as few mixing plugins online as possible until the very last minute (and certainly at that point I try and have the MIDI editor closed as much as possible, which when open slows things down even more with a lot of plugins in the project).

Following this thread in case someone has some insights - I don't get this slowdown/choppiness at all with the same plugins on my master in Cubase, Logic, etc.

[King Stupid]

Originally Posted by inthevoid

Not with Ozone specifically, but I have found Reaper slow down considerably and become extremely choppy, and my CPU temps spike with even 1 or 2 heavy mixing/mastering plugins active on my master chain (things like Pro-L 2, soothe2, tape emulation plugins etc.) I don't have these on my actual master track but on a track that all my other tracks route to before going to the Reaper master track.

The GUI slows down so much to the point where I basically try and write music with as few mixing plugins online as possible until the very last minute (and certainly at that point I try and have the MIDI editor closed as much as possible, which when open slows things down even more with a lot of plugins in the project).

Following this thread in case someone has some insights - I don't get this slowdown/choppiness at all with the same plugins on my master in Cubase, Logic, etc.

System specs? the plugins that cause this? Screenshot of reaper performance window under these circumstances?

[inthevoid]

Originally Posted by King Stupid

System specs? the plugins that cause this? Screenshot of reaper performance window under these circumstances?

Mac M2 Max 12 cores / Mac OS Ventura 13.6.6 / 96GB RAM

https://streamable.com/zhgm36
Here's an example of the lag when the MIDI editor is open. You can see when I select items the whole application freezes, I get the beach ball cursor for a few seconds before it updates the MIDI editor. When the MIDI editor is closed selecting items becomes instantaneous and snappy again.

Some plugins that seem to cause it are Pro-L 2, Soothe2, Waves J37, Waves Abbey Road TG Mastering, to name a few. It's not consistent behaviour and seems to get worse over time so I can't name them for sure.

I don't have a screenshot of the performance window to hand - will generate one when I next get a sec.

[Jonatan Corcico]

Originally Posted by inthevoid

Mac M2 Max 12 cores / Mac OS Ventura 13.6.6 / 96GB RAM

https://streamable.com/zhgm36
Here's an example of the lag when the MIDI editor is open. You can see when I select items the whole application freezes, I get the beach ball cursor for a few seconds before it updates the MIDI editor. When the MIDI editor is closed selecting items becomes instantaneous and snappy again.

Some plugins that seem to cause it are Pro-L 2, Soothe2, Waves J37, Waves Abbey Road TG Mastering, to name a few. It's not consistent behaviour and seems to get worse over time so I can't name them for sure.

I don't have a screenshot of the performance window to hand - will generate one when I next get a sec.

I notice the same exact issue with MIDI editor in heavy projects. But this happens when are using some certain plugins that use higher size of oversampling (at least 8x). And, in general, different plugins using oversampling at the same time. Turning off the oversampling in some of this plugins (not all plugins that use oversampling cause this issue) solve this.

[serr]

Don't cook your CPU and logic board! Fans and new heat sink paste are cheap and easy. Just do it! Because many things are not cheap and easy...
ifixit might have a tear down guide.

A sensor reads the max temperature and throttles the CPU and then finally shuts the machine down. Firmware controlled. Stop beating up on that.

[inthevoid]

Originally Posted by serr

Don't cook your CPU and logic board! Fans and new heat sink paste are cheap and easy. Just do it! Because many things are not cheap and easy...
ifixit might have a tear down guide.

A sensor reads the max temperature and throttles the CPU and then finally shuts the machine down. Firmware controlled. Stop beating up on that.

Appreciate the warning! The laptop is pretty much new and nothing else I do on it makes the CPU temps raise above 45-50 degrees or so so I'm not concerned about the thermal paste/fans effectiveness. I've got a temperature sensor and I can see it's not getting anywhere near thermal throttling even at max load in Reaper. As I say I don't get this behaviour in other DAWs with the same plugins at all so I'm inclined to say the choppiness is likely a Reaper thing rather than a hardware limitation.

[inthevoid]

Originally Posted by Jonatan Corcico

I notice the same exact issue with MIDI editor in heavy projects. But this happens when are using some certain plugins that use higher size of oversampling (at least 8x). And, in general, different plugins using oversampling at the same time. Turning off the oversampling in some of this plugins (not all plugins that use oversampling cause this issue) solve this.

Thanks, this is very useful info - will look into this further!

[serr]

Originally Posted by inthevoid

Appreciate the warning! The laptop is pretty much new and nothing else I do on it makes the CPU temps raise above 45-50 degrees or so so I'm not concerned about the thermal paste/fans effectiveness. I've got a temperature sensor and I can see it's not getting anywhere near thermal throttling even at max load in Reaper. As I say I don't get this behaviour in other DAWs with the same plugins at all so I'm inclined to say the choppiness is likely a Reaper thing rather than a hardware limitation.

That sounds more like the plugin or something crashing then.
Sorry for not reading that more accurately! I think the 20 minute bit sounded like something warming up to me.

Why it would crash in Reaper and not anywhere else... Reaper does have a more extensive control set that leads to making it easy to make errant settings. Are you playing live through this or just doing post? If post, do you have a large block size? Take a look at longest block in the Reaper performance meter and make sure your block size covers that.

[inthevoid]

Originally Posted by serr

That sounds more like the plugin or something crashing then.
Sorry for not reading that more accurately! I think the 20 minute bit sounded like something warming up to me.

Why it would crash in Reaper and not anywhere else... Reaper does have a more extensive control set that leads to making it easy to make errant settings. Are you playing live through this or just doing post? If post, do you have a large block size? Take a look at longest block in the Reaper performance meter and make sure your block size covers that.

To be clear, I'm experiencing choppiness / freezing with the GUI in Reaper only, not the audio - playback is unaffected, for example when it's playing back and I select some items like in the video example above, I can't click or do anything in the program until it unfreezes but everything is still playing back happily. The MIDI editor is the culprit when it's freezing for several seconds like in the example above though, as it's just a minor GUI slowdown (for e.g. selecting tracks becomes slightly 'laggy'), etc when that is closed. But I need to have the MIDI editor open virtually at all times because I'm mostly working with large MIDI orchestral sample templates.

When I have these mastering plugins active I'm basically just doing post, but of course playing back the track with VSTs active, etc. My block size is set at 1024 for post stuff and I could even go lower - 512 works fine too I just like to have a bit of wiggle room.

[serr]

Oh, this is one of the M series Macs! I got confused with the original posts from forever ago, sorry.

Well, hmmm...
So graphics system crashes. We keep seeing reports of this kind of stuff from the M series Macs. My suggestions would have been to use a SSD and that you probably need a metal compatible graphics card... which you already have!

Something with Reaper not working the new M series language set just right? (Because post-Jobs Apple doesn't disclose anything unless you get in bed with them. And Reaper hasn't.)

I only get the slightest GUI pauses like that on my 2009 Mac Pro with 400 track projects and if I'm also trying to run one off an archive drive that's a HDD spinner. The solution is always to use a SSD for highest performance and get a newer metal graphics card if you don't have one yet. And you're already there with all that. There's some unknown with the M series Macs with this.

[EpicSounds]

Originally Posted by inthevoid

Mac M2 Max 12 cores / Mac OS Ventura 13.6.6 / 96GB RAM

https://streamable.com/zhgm36
Here's an example of the lag when the MIDI editor is open. You can see when I select items the whole application freezes, I get the beach ball cursor for a few seconds before it updates the MIDI editor. When the MIDI editor is closed selecting items becomes instantaneous and snappy again.

Just curious if you have "disable media buffering for tracks with open MIDI editors" enabled or not, and also Anticipative processing for tracks with open MIDI editors

[inthevoid]

Originally Posted by EpicSounds

Just curious if you have "disable media buffering for tracks with open MIDI editors" enabled or not, and also Anticipative processing for tracks with open MIDI editors

Disable media buffering for tracks with open MIDI editors is checked, as is Anticipative processing for tracks with open MIDI editors, yes

[EpicSounds]

Originally Posted by inthevoid

Disable media buffering for tracks with open MIDI editors is checked, as is Anticipative processing for tracks with open MIDI editors, yes

try turning off the one for anticipative fx

[inthevoid]

Originally Posted by EpicSounds

try turning off the one for anticipative fx

This unfortunately causes a lot of crackling in my session when playing back

[serr]

You said originally the audio was fine and it was GUI crashes.
Put the audio stuff back to default (or where you had it). Anticipative FX, etc. Focus on the graphics system.

I don't have a suggestion for what exactly to mess with. Might be a MacOS workaround needed? But go after the graphics, not the audio. (If your audio is in fact solid.)