I like Ozone and want to use it for mastering especially, but as shown in the screenshot the latency - 173.6 ms – is way more than any other single or combined fx I have on other tracks. Usually the latter are a couple of ms to maybe a double digit, not this.
This ends up messing with the entire project’s ability to faithfully execute sampling, tempo, etc. Ozone uses 1 to several modules, but even turning all off except one still results in the same amount of latency.
My card (Behringer UMC204HD 192K)'s ASIO is decent - 44.100 Hz, 128 samples, and Cubase shows Input latency at 4.399, Output 5.510, so not the problem as far as I know.
So for now, I don’t use Ozone (I only added it to my master bus to illustrate the latency for this posting.)
I hope someone has a solution - before I try to contact Izotope support. Using Constrain Delay Compensation is not a solution - only a temporary remedy that makes the project sound like crapiola and no way to mix or arrange…
I’m not sure what your question is. Many plugins introduce latency, Ozone more than most. That’s what latency compensation is for…it keeps your tracks aligned in spite of that latency. This is a basic operating principle of digital audio workstation apps like Cubase. If you want to monitor input, turn on CDC so those latent plugins aren’t in your monitor signal path. If you’re mixing or mastering, not monitoring, turn off CDC and the timing should be fine.
Well, the question is pretty obvious - 173.6 ms. latency is unacceptable. I’ve played around with it all, and I think I’m just going to stick to a more basic option - Ozone Equalizer - 0 ms. latency.
I am one of those people that uses compressors or limiters in very small, subtle instances, so no need for multiple modules of Ozone Standard 11.
But this topic could still be of some use to someone at some point. Or not. Not every OP one posts here gets resolved. C’est la vie.
A plugin with latency like that is quite normal. Not only is it acceptable, but the latency is compensated when mixing, so there are no ill effects on the playback.
If you’re having a problem, I’m sure someone could help you if you describe what that problem is.
Well, since I’m not a pro engineer, I’ll take your word for it.
All I’m going by is what I see in my MixConsole - the most intensive plugin I use is GuitarRig 6 with 9 stacked racks parked on 4 different lead guitar VSTi tracks, to weave a nice combo of Gibson and Strat sounds (my musical style is kind of Pink Floyd-ish, so I like spatial stuff…) – its latency per track/instance is 0.4 ms.
That’s a far cry from 173.6. ms.
I just know that on an other project the Ozone plugin really messed with how the project synced and don’t want that to happen again. I also don’t have pro system, but it’s pretty decent too: AMD Ryzen 9 5950X 16-core, 32-Thread, 64 Gb RAM.
Call me cautious or paranoid. I’d rather play it safe.
As said previously, Ozone introduces a high latency but this is normal. If used for mastering this shouldn’t be an issue since at this stage, you’re done recording.
Could you expand on this? It shouldn’t affect timing of recorded track or tempo changes using the Tempo Track.
That’s the main premise for Ozone Advanced. Same functionality, but broken up into individual modules so you use only the ones you need, which reduces latency (for mixing), in addition to the all-in-one module you get with the basic version.
For mastering, just increase your buffer and turn on latency compensation.
The main Ozone plugin is supposed to be used for mastering and not at the mix stage.
Maybe try using some of the modules in their standalone plugin format?
And you can always turn that plugin off as opposed to bypassing it. It will the keep your settings but the latency will go away.
Interesting but from what I can tell, it requires a second OS on a network . I only have one computer. As they describe it:
“AudioGridder is a plugin host that allows for offloading the DSP processing of audio plugins to remote computers running macOS or Windows. The DSP code of the loaded plugins will be executed on the server machine and the plugin UIs will be streamed over the wire”
Latency can be an issue when you’re trying to play an instrument, but at the mixing and mastering stage it’s not that important is it? I’ve used Ozone quite a bit in Cubase and never even noticed the latency
Exactly this! You’re not supposed to have a mastering powerhouse plugin active while you are composing, recording or performing your tracks… You could even do the final mixdown first and create an own corresponding mastering project (with one or more tracks), and do the Ozone processing there. That’s what I tend to do (when I don’t have the budget for a mastering engineer, that is).
OK, now I remember why I nixed Ozone on my master bus prior to this current project: I was trying to record using my old Korg Trinity workstation and it was impossible to play it due to the latency.
