iZotope Ozone 10 works in VEGAS 20, but NOT in Sound Forge Pro 16

walter-howerton wrote on 9/14/2022, 8:39 AM

Can anyone else duplicate this? iZotope Ozone 10 works in VEGAS 20, but does not work in Sound Forge Pro 16.
Alternate question: If anyone has iZotope Ozone 10 and Sound Forge Pro 15, could you check if it works? I may just revert to version 15, if so. Thanks.

Back to post

Comments

craig-d wrote on 9/27/2022, 3:46 AM

@john_barr yes, you are right...it's third party vst2 32x plugins that seem to be having these issues...the devs are working on it at the moment so hopefully this will be straightened out soon. thanks for your info, also, by the way...it's always good to get as much info about each issue as possible, as it helps to isolate the issue and opens the door to helping the developers solve it. thanks!

john_barr wrote on 9/27/2022, 6:06 AM

hi craig. VST3 32-bit as well.

john_barr wrote on 10/1/2022, 8:08 AM

SFP 16.1.2 Navigating between some submenus is a little slow. Not with Waves only. I don't know if it only happens to me.

john_barr wrote on 10/1/2022, 3:20 PM

If no one else has this problem, I will need to change the computer.

David-Hovel wrote on 11/25/2022, 11:40 AM

Same thing, Windows 10, simple WAV file editing using iZotope Ozone 10, VST3, x64. Works fine with Ozone 9, VST3, x64. Please advise. Several crash files have been sent to MAGIX.

john_barr wrote on 11/25/2022, 3:40 PM

Hi, David-Hovel. Magix developers are slow to fix Sound Forge problems.