SoundForge Pro 16 upgrade installed - lost all Ozone RX

BScott-Fischer wrote on 6/16/2022, 11:16 AM

Hi again,

I just installed the update for SF Pro 16 "Build 11" and it eliminated all my Ozone Rx 7 & 8 capabilities. (W10 PC)

I can use the separate RX7 & 8 program (they work) - but not the built in SF Pro 16 RX 7 &8 capabilities.

Yes, I tried reinstalling them only - but they still do not work... did not want to re-install the whole SF program as it doesn't have the new "Build 11".

rraud, please come to my rescue again!

And please refresh my memory as to HOW I can email Pro Audio support...I keep going in circles clicking on the website between support pro audio support SF pro audio support...I can't find the landing spot! Craig always has been so helpful...I just can't reach him!

Comments

PATIENT-X wrote on 6/16/2022, 12:53 PM

@BScott-Fischer

Hello, welcome

See @rraud instructions to contact support here.

Stephen

Forum Moderator

Last changed by PATIENT-X on 6/16/2022, 12:53 PM, changed a total of 1 times.

Pc self build by me.

Azza Pyramid 804 case

Intel Core i5-13600K Processor 3.5GHz

Kingston FURY Beast 32GB (16GB x 2) 4800MHz DDR5

Geforce RTX2080 Founders edition

Firecuda 530 1tb SSD Nvme

Team Group T-FORCE DELTA MAX RGB LITE 2.5" 1TB SATA III

Corsair RM1000x 80 PLUS Gold Fully Modular ATX 1000 Watt Power Supply

5in LCD Screen

Lian Li UNI SL120 V2 triple fans

MSI Meg Unify Z690 motherboard

 

 

craig-d wrote on 6/17/2022, 4:56 AM

Hi @BScott-Fischer! the developers are looking at this issue now, as they've been able to reproduce it. the vst 2 version does still load fine and works well...and the strange thing for me is that after running the vst2 version, the vst3 version started working fine again...very weird, but they are working on it now and there is another update targeted for late august.

john_barr wrote on 6/17/2022, 6:36 AM

With waves plugins the same thing happens. VST2 loads fast, but VST3 takes a while to load.

BScott-Fischer wrote on 6/17/2022, 10:45 AM

Hi again...so sorry I meant to say the Izotope RX's NOT Ozone!!! D'OH!

craig-d wrote on 6/20/2022, 2:12 AM

hi @BScott-Fischer  yes, the vst 2 of RX should also still work fine...please check that and let us all know if that isn't the case for you. thanks!

BScott-Fischer wrote on 6/29/2022, 12:34 PM

Hi again all...Sorry I was away for a while...VX2 is 32 bit and only Bit Machine...it is distorted and will not load.

Plug-in: 'RX 7 De-reverb    (VST3, 64 Bit)' failed to load. Make sure this plug-in is installed properly.IS THE ERROR message I get with any RX7 0r 8 attempt.

Thanks,

Scott

Hopefully the team can find a solution...in the mean time Pro 15 works fine!
 

walter-howerton wrote on 7/25/2022, 4:36 PM

New update today (16.1.1.30) ... VST3 still won't work in SoundForge Pro since update from 16.0 to newer versions. This is a showstopper, because some plugins have moved to exclusively VST3.

rraud wrote on 7/26/2022, 12:17 PM

@walter-howerton, confirm both 32 and 64 bit VST-3 folders are designated in the VST search folder dialog "Options> Preferences> VST Effects".
For some reason my 64 bit search folders vanished in the 16.1.1 update so I needed to add them,
Include "Program Files> Common files> VST-3" and 'Program Files (x86)> Common files> VST-3".

walter-howerton wrote on 7/26/2022, 2:15 PM

@walter-howerton, confirm both 32 and 64 bit VST-3 folders are designated in the VST search folder dialog "Options> Preferences> VST Effects".
For some reason my 64 bit search folders vanished in the 16.1.1 update so I needed to add them,
Include "Program Files> Common files> VST-3" and 'Program Files (x86)> Common files> VST-3".

Thank you, @rraud . I confirmed that the VST folders are specified in the SoundForge Pro 16.1.1.30 Options. VST3 effects do not work in SF Pro 16.1 or 16.1.1; the program crashes when any VST3 effect is selected to be applied to audio.

I have read that this is a known issue that began with version 16.1 (and I can confirm that they did work in version 16.0) -- if you or any other user has successfully applied a VST3 plug-in within SF Pro 16.1 or 16.1.1, then please mention that fact. I am very curious if it's not 100% common that all installations of 16.1 and 16.1.1 fail in the same manner with VST3. Thanks!

rraud wrote on 7/26/2022, 5:06 PM

Are they available in the plug-in manger? do they load?.. or they load but just do not work? How about in the chainer?

john_barr wrote on 7/26/2022, 6:35 PM

LoudMax VST3 64bit works fine on Sound Forge Pro 16.1.1

rraud wrote on 7/26/2022, 7:12 PM

LoudMax VST3 64bit works fine on Sound Forge Pro 16.1.1

Same here. So does Ozone Elements and my other 64 bit VST-3 plugs seem to work as well.

The third-party 32 bit VST-2 plugs are still unusable due to the display bug (off-center with many parameters hidden).

BScott-Fischer wrote on 7/27/2022, 9:39 AM

Hi all,

I just installed SF Pro 16 1.1 build 30 x 64 and nothing has changed...no isotope VX 2 or 3 available to use.

I'll stick with SF pro15...it works perfectly.

Scott Fischer

walter-howerton wrote on 7/27/2022, 5:30 PM

Are they available in the plug-in manger? do they load?.. or they load but just do not work? How about in the chainer?

@rraud The plug-ins are all listed in the plug-in manager, and in the menu structure. The directory where they reside is correctly specified in the options/plug-ins, and before & after "rescan," they are properly listed in the program. Attempting to use any of them - via menu or plug-in manager - results in immediate crash of SFPro 16.1.1, with the "Send / Do Not Send" Error Report dialog box popping up.

Since I read that someone got some VST3 plug-ins to work, I will mention what plug-ins I have: iZotope RX9 (all plugins in Advanced version), iZotope Ozone 9 (all plug-ins in Advanced version), iZotope Nectar 3 Plus, iZotope Neutron 4... (basically everything iZotope).

rraud wrote on 7/27/2022, 6:07 PM

The VST-3 plug-ins seem to work as they should on my Win 10 PCs, including the iZ Ozone and RX Elements plugs as well as my Plug-in Alliance Fx. There are other issues that need to be fixed as well, so use SFP-15 if you have it,. You can also email Magix support infoservice@magix.net for their advice or opinion.
16.1 is mostly useless (to me) as well since my third-party 32 bit VST-2 plug-ins cannot be used due to the display bug. I have to use SFP-15 if I need both VST 3 and 32 bit VST 2 plug-ins.

walter-howerton wrote on 7/31/2022, 10:13 PM

The VST-3 plug-ins seem to work as they should on my Win 10 PCs, including the iZ Ozone and RX Elements plugs as well as my Plug-in Alliance Fx. There are other issues that need to be fixed as well, so use SFP-15 if you have it,. You can also email Magix support infoservice@magix.net for their advice or opinion.
16.1 is mostly useless (to me) as well since my third-party 32 bit VST-2 plug-ins cannot be used due to the display bug. I have to use SFP-15 if I need both VST 3 and 32 bit VST 2 plug-ins.

Thank you for sharing your insight and experience on this. I uninstalled all my iZotope software, cleared out the folders where they had been installed, for the few plugins that somehow lingered, rescanned VST in SFP16.1.1, then reinstalled some key iZotope stuff I particularly wanted to use. SOME of the VST3 began to work after that in SFP16.1.1, but not all.

Therefore, I re-installed Sound Forge Pro version 15, and of course all the plugins I use did work fine in it.

For info: I am running Windows 11 Pro, 22H2, 22622.440