Comments

rraud wrote on 9/14/2022, 10:06 AM

Hi @walter-howerton,

from a recent topic, (rraud): "Unfortunately, Sound Forge Pro 16 (and 16.1 has numerous issues with VST plug-ins... Many of us use SFP-15 (or earlier), until the SFP-16 VST bugs are fixed."

(Comment from Magix: " There is an update that will be released very soon that updates the VST back-end, so hopefully this will be resolved soon! "

emmrecs wrote on 9/14/2022, 10:31 AM

@walter-howerton

Ozone 10 is VST3 only. I believe Magix has acknowledged that VST3s don't work in SF 16.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

craig-d wrote on 9/15/2022, 1:03 AM

hi Walter, i hope you're doing well! vst 3 plugins do actually work in SFP16...there was an issue that many wouldn't show up after upgrading to 16.1--this is because 16.1 redesigned the vst engine, and so all third party plugins received new plugin id numbers...so users need to rescan their plugins manually by clicking Options > Preferences > Vst Effects and click Refresh.

That being said: (and as I believe we talked about previously) there are issues with iZotope plugins and Waves version 14 plugins in vst3. As far as I know, the iZotope issues have been fixed and an update is coming very shortly that should be released this month that fixes those...the Waves issue is more of a matter of how the Waves licensing works. At first, I could only use the vst2 versions of Waves version 14 plugins, but after updating my Waves Central to version 14 and reinstalling my Waves Shell, they all showed up fine again and I can use them. I don't have Ozone 10 (yet), but I'll ask the developers if the issue with 10 is also fixed with the other iZotope issues (i imagine that's the case), and follow up here in the forum. thanks!

john_barr wrote on 9/15/2022, 7:34 AM

Hi craig. Waves Central continues at version 13. Latest version is 13.3.2

walter-howerton wrote on 9/15/2022, 7:38 AM

Yes, you sent me a prior build installer, Craig. Thank you. That build (prior to the VST engine change) does run most of the plug-ins that 16.1 won't. However, that prior build won't run Ozone 10. Since I also have Magix VEGAS Pro, I tried Ozone 10 in that program, and found that it works. This became more important, because iZotope decided to eliminate their stand-alone program version of Ozone, and make Ozone 10 plug-in ONLY. Since Sound Forge Pro is my Audio Editor-of-choice, I am hopeful that I can use the utilities I have in it.
I look forward to testing the September update to SF Pro 16.x...

craig-d wrote on 9/16/2022, 1:33 AM

hi @john_barr, yes, sorry, you're right--the latest version for Central is 13.3.2, thanks! sorry about that. But yes, once I updated, I can now find and use all of my Waves 14 plugins (such as all that are included in the Renaissance Maxx plugin group, the Vocal Rider, the API-2500, and more. I don't have every Waves 14 plugin, but all of the ones I have do show up and work now in VST3 64 bit. They didn't before, and I updated my Waves Central and uninstalled and reinstalled/activated my Waves plugins via Waves Central and now everything is fine. I think the issue was more of a Waves issue, because the W14 plugins I have also didn't show up in Ableton or Pro Tools at the time either before I updated and uninstalled, reinstalled. Please let me know if you still can't use them.

 

Hi @walter-howerton, i didn't realize that Ozone 10 wouldn't have a standalone version! i don't have it yet, so i can't test it...i think the reason for the ozone 10 issue (as well as the advanced versions of ozone 9, rx8, neutron, etc, is because they were designed with the updated juce, and the essential versions were not (vegas 20 also has updated juce, but not SF16). this is something that will be addressed in the upcoming 16 update/patch. i will double check with the developers on that, to make sure, and write back shortly. thanks for your patience!

john_barr wrote on 9/16/2022, 10:12 AM

Hi craig. I updated Waves Central. Sound Forge takes a few seconds to get ready to work.

FX Plug-Ins take some time to appear.

john_barr wrote on 9/16/2022, 10:55 AM

When I open a plugin for the first time, it takes a while. When I open it for the second time, it opens fast.

craig-d wrote on 9/19/2022, 12:55 AM

hi @john_barr  thanks for letting me know. i can't quite remember how it was for me at first, but i think after i updated and opened them for the first time they also took a minute to load...but going through them now, it seems that they are loading and working ok...i have to go through all of them again, though, so i make sure i'm not leaving any of them out. thanks again!

john_barr wrote on 9/20/2022, 9:10 AM

I just updated Sound Forge to version 16.1.2
The first scan took about 3 minutes. The FX Plug-Ins tab appears quickly.
VST2 plugins appear faster than VST3.
Preset Untitled is not fixed yet.
Some adjustments still need to be made.

 

john_barr wrote on 9/20/2022, 9:31 AM

VST3 slow to appear.

walter-howerton wrote on 9/20/2022, 10:09 AM

[[MENTION:undefined]]
[[MENTION:277575]]
Sound Forge Pro 16.1.2.55 update FIXES my observed issues with 64-bit VST3 plug-ins from iZotope, including the brand-new Ozone 10. This latest version of SFPro appears ready for serious use now.
Thanks, Magix!

john_barr wrote on 9/20/2022, 10:27 AM

[[MENTION:undefined]]
[[MENTION:277575]]
Sound Forge Pro 16.1.2.55 update FIXES my observed issues with 64-bit VST3 plug-ins from iZotope, including the brand-new Ozone 10. This latest version of SFPro appears ready for serious use now.
Thanks, Magix!

Sound Forge has improved, but still needs some adjustments.

rraud wrote on 9/20/2022, 6:06 PM

This latest version of SFPro appears ready for serious use now.

Not for me... The other third-party 32 bit VST issues seem to remain. I am in the process of removing as much of the old SF-16 and 16.1 data as I can find (in addition to Revo Uninstall advanced scan mode) and try it again..

craig-d wrote on 9/21/2022, 3:13 AM

hi @walter-howerton, i'm glad you're up and running now!

hi @john_barr, yes, the 'Untitled' preset issue is still there...that is irritating, but they are still working on it. However, my Waves plugins show up very quickly, I watched your video and can see that it is slow for you, but I can't seem to reproduce it. However, there was an issue a while back that was discovered by users back in version 13 or 14, and the issue had to do with iZotope (and I believe Waves plugins as well). I do not know if it applies to you, but if by chance you are using an iLok device, but have deactivated PACE, then it will slow down your loading times and cause various other issues such as that...so if you are using iLok for your Waves or iZotope licenses, make sure that PACE is enabled. other than that, I don't have an issue getting my Waves stuff to load or to pop up in the FX Plugins menu. Please keep us posted on your experience so we can keep making the necessary adjustments. Thanks again everyone for your feedback!

john_barr wrote on 9/24/2022, 12:34 PM

Hi rraud. You are right. Third-party 32-bit plugins continue to have issues in SFP 16.1.2

rraud wrote on 9/25/2022, 10:59 AM

Hi rraud. You are right. 32-bit plugins continue to have issues in SFP 16.1.2

I did a complete uninstall of Sound Forge Pro 16 with 'Revo Uninstall' (adv. scan mode) and manually deleted as much other remaining data and registry entries as I could find, but the third-party 32 bit VST-2 issue remains.
Here are screenshots using TDR's 'Limiter #6' as an example:

FWIW, ??? I also do not know why there are three (3) Appdata folders (16/16.0/16.1) and the same for other SFP-16 system file entries.. (the reinstall of 16.1.2 recreated them all).

The limited narrowing function of the meter toolbar, remains as well, but that is a minor annoyance and can be temporarily resolved by using a 'window layout' file from SFP-15 or earlier. The same behavior exists in AS-16, but using a layout file from an earlier version does not work.

john_barr wrote on 9/25/2022, 11:55 AM

Waves 10 VST2 32-bit also doesn't work on SFP 16.1.2

john_barr wrote on 9/25/2022, 3:12 PM

I hope CLAP becomes the default and ends the VST mess.

craig-d wrote on 9/26/2022, 1:12 AM

hi! yes, when i saw @rraud 's comment about it, i also tested it and sent a report to the developers so they are in the process of fixing that. that's super annoying and it is a mess for sure, but at least they know about it know and are taking care of it. thanks for commenting on it, and sorry for the huge inconvenience!

john_barr wrote on 9/26/2022, 3:10 PM

Waves 10 VST2 32-bit

john_barr wrote on 9/26/2022, 3:16 PM

Morphoder appears but freezes

john_barr wrote on 9/26/2022, 4:27 PM

john_barr wrote on 9/26/2022, 8:10 PM

Waves 11 doesn't have these problems, it only works with 64-bit plugins. These problems only happen with 32-bit plugins.