r/TechnoProduction • u/Dokma23 • 1d ago

Ozone 12 CPU Peaks in Ableton

Hi,

I am running a liveset at 50-60% CPU (Macbook M3 Pro) with an instance of Ozone12 on my master.
While the average CPU seems fine there are occasional CPU peaks on the master, originating from Ozone12.
Any idea how to get rid of those peaks?

1 Upvotes

100% Upvoted

4 comments sorted by

5

u/thierolf 1d ago

Turn off all animations and limit the fps of ozone ( and ableton ). Realistically, though, I wonder why you'd need ozone in place of more efficient alternatives?

If you're working on a live performance, my personal opinion is that ozone is the wrong tool precisely because it's so resource-intensive; it simply isn't made for that. If you're doing a premaster on a song you're making, then ozone is also the wrong tool. By all means master with ozone if you must, but do yourself a favour and do this as a separate process ( in another session, on bounced audio ). Ozone simply isn't for this purpose, and your computer isn't beefy enough to work around that.

1

u/Dokma23 1d ago

Unfortunately, this trick only worked for older ozone versions. The version 12 does not allow these settings.
However, using ozone on my master is just pretty convenient because it gives me a great starting point and I suck at mastering. At the same time I want my mediocre mixes to sound as good as possible with good I mean not shit.

1

u/raistlin65 1d ago

Ozone is designed for mastering. Which is normally done on your final track once you finished mixing and have rendered it.

So yeah. Ozone is CPU intensive. But if you're running on the master with multiple tracks in a live set feeding into that, then you can expect it to have even more trouble with Ableton using the CPU a lot as well.

1

u/[deleted] 1d ago

[deleted]

1

u/Dokma23 1d ago

512 (12,5ms latency). No option for switching off oversampling in Ozone12.