Big Alkie Posted March 17, 2020 Posted March 17, 2020 I been using Ozone 9 and Nectar 3 since they released they worked fine in Bandlab. Now all of a sudden both vsts are very slow when trying to use them. Any suggestions on how to fix?
0 David Baay Posted March 17, 2020 Posted March 17, 2020 (edited) Slow? You mean GUI response to the mouse or meter/spectrum analyzer animations or... something else? Possibly you enabled CPU Conservation Mode with the Pause key that reduces UI updates to once per second...? Edited March 17, 2020 by David Baay
0 Big Alkie Posted March 22, 2020 Author Posted March 22, 2020 Both actually. When I try to click on master assistant it takes 5-10 seconds after I click it to work. And when I try to EQ things the waves doesnt move to the current sound I'm tryin to EQ. It's very slow. And it was working flawlessly when it 1st came out.
0 JonD Posted March 23, 2020 Posted March 23, 2020 Try a reinstall of either one and see if it changes anything.
0 Big Alkie Posted March 23, 2020 Author Posted March 23, 2020 The reinstall did not solve the latency issue
0 JonD Posted March 24, 2020 Posted March 24, 2020 Did you try a reset/rescan of VSTs? Wouldn't hurt at this point.
0 Starship Krupa Posted March 25, 2020 Posted March 25, 2020 Do you have any other VST hosts to try them in? That may help narrow down the issue to "working on your system" vs. "working with Cakewalk on your system."
0 Big Alkie Posted March 26, 2020 Author Posted March 26, 2020 I use Fl studio and it does the same thing. But when I open up Ozone 8 it runs perfect. Ozone 9 and nectar 3 just so slow
0 JonD Posted March 27, 2020 Posted March 27, 2020 Have you tried both the VST2 and VST3 versions, and do they behave in the same way?
0 Big Alkie Posted March 27, 2020 Author Posted March 27, 2020 They both respond the same. I noticed since they been updated it's been moving so slow
0 JonD Posted March 28, 2020 Posted March 28, 2020 Are you running Windows 10? If you don't control the O.S. updates, Win 10 is notorious for causing problems - which is why it's best to disable the auto-update and only do so when you know it's safe OR have the ability to roll back to a previous system-state in case things go south. If you determine that the last OS update likely caused this problem, there are ways to roll back: https://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/ Have you consulted with or reported the issue to Izotope? If they have a user forum, that would be a better place to report your problem (since you are experiencing it with two different DAWS) 1
0 Big Alkie Posted April 1, 2020 Author Posted April 1, 2020 Yep I'm running windows 10 with all the latest updates. I emailed someone from izotope but they gave me troubleshooting steps that didnt do too much of nothing. When I told them ozone 8 works fine but ozone 9 was acting up they stop responding.
0 HIBI Posted April 1, 2020 Posted April 1, 2020 Same result in standalone mode? If getting same result, graphics driver or its settings could be a cause. 1
0 Big Alkie Posted April 7, 2020 Author Posted April 7, 2020 Same results using ozone 9 as standalone
0 Casper Posted May 3, 2020 Posted May 3, 2020 I've got the same problem in Cubase. In one projekt it works fine but in another it's realy slow. Any updates on how to fix it?
0 Jerry Marcus Posted August 14, 2020 Posted August 14, 2020 I have the same problem and.. What I did was uninstall the microsoft office and clean its registry, restart my pc and problem solved. This method is working fine for me. I don't know why but maybe (I'm not really sure) it's has to do with the microsoft office.
0 Promidi Posted August 14, 2020 Posted August 14, 2020 What are your PC specs. CPU, speed, ram ?? Are all of your hardware drivers up to date. Check this with the actual websites of the hardware's manufacturers , not Microsoft.
0 noynekker Posted August 14, 2020 Posted August 14, 2020 I noticed when I first purchased Ozone 9 that it took considerably longer to load than all other plugins . . . but once loaded it works just fine. So, now you're saying they are very slow when trying to use them . . . I haven't had that problem, just the load times are much longer.
0 Tez Posted August 26, 2020 Posted August 26, 2020 (edited) On 8/14/2020 at 12:56 AM, noynekker said: I haven't had that problem, just the load times are much longer. Ditto... I also got the Tonal Balance Bundle, everything but O9, the O9 individual module VSTs and Tonal Balance load quickly, but these slow pokes take 15-20 seconds, once loaded no problem, and the standalone starts up fine... @noynekker Out of curiosity what machine do you have I'm wondering if it's an OEM issue as this slow load time also occurs in another DAW not just CbB & Splat for me. If it's a registry issue iZotope support hasn't helped, and all my other iZotope plugins load just fine! Edited August 26, 2020 by Tez
0 Glenn Stanton Posted August 26, 2020 Posted August 26, 2020 one note - the Ozone 9 and related newer version of Nectar, RX7 - they are very very sensitive to your screen resolution settings and therefore the related patch levels for the graphics and screen resolution. i spent part of a month troubleshooting this: it would randomly work at the proper UI refresh rate (e.g. not take 5 seconds to load a menu!!!) when i set the UI to 1920x1280 or 1440x900, and then it would stop on the next reboot. eventually i noticed my intel drivers were about 3 years old, so i updated them and now it's stable at all resolutions. Ozone 7, Nectar 2, Trash 2, etc all worked fine so it was a very annoying problem to identify.
Question
Big Alkie
I been using Ozone 9 and Nectar 3 since they released they worked fine in Bandlab. Now all of a sudden both vsts are very slow when trying to use them. Any suggestions on how to fix?
32 answers to this question
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now