Comments

rraud wrote on 3/30/2023, 10:24 AM

Many legacy plug-ins are not available in the VST-3 format. I have some 32-bit plug-in that have a distinctive sound and there are no VST-3 alternatives. I do not think VST-2 is the cause of the VST-3 issues.

john_barr wrote on 3/30/2023, 11:23 AM

Audition supports VST2 and VST3 plugins and both work great. The problem is not in the plugins but in Sound Forge.

SP. wrote on 3/30/2023, 11:33 AM

@john_barr The developers changed the VST integration with SF 16. This caused these new problems. I believe in SF 15 this wasn't the case because it still used the old code.

john_barr wrote on 3/30/2023, 1:32 PM

I would like to ask a question. Is it really necessary for Sound Forge to have a plugin in VST2 and VST3 if both do the same thing?

Mark-Cotton wrote on 4/22/2023, 2:17 PM

Magix developers have removed the old Show Peak Meter.

I have just upgraded and the meters are so annoying now. They are not clear at all ... seems like a backwards set to me.

rraud wrote on 4/22/2023, 3:40 PM

the meters are so annoying now. They are not clear at all ... seems like a backwards set to me.

Yes, I agree, the 'new' meter layout sucks!.. and the most important..'full scale peak' can only be viewed in a cluttered combination with VU, PPM or other. The devs should have concentrated on fixing the issues from SF-16 instead of f*cking up the GUI and adding a feature very few will actually use (i.e.: external Fx).
I am beyond frustrated.

JoaoBC wrote on 4/22/2023, 8:22 PM

Waves' "GEQ Graphic Equalizer" plug-in has two types: modern and classic. The classic type doesn't work in VST3, only in VST.

JoaoBC wrote on 4/23/2023, 7:53 PM

what is the latest version (release) of Sound Forge that all plug-ins work correctly? 32 and 64 bit?

rraud wrote on 4/24/2023, 11:59 AM

what is the latest version (release) of Sound Forge that all plug-ins work correctly? 32 and 64 bit?

Sound Forge 15. There is a minor issue with some of plugs' preset default name (init1), but other than that, most plug-ins work OK.

I think the initial builds of SF-16 worked ok but was f*cked-up after build 79 (as I recall).

john_barr wrote on 4/27/2023, 4:22 PM

The devs should have concentrated on fixing the issues from SF-16 instead of f*cking up the GUI and adding a feature very few will actually use

You are right. But if I had said that, the comment would be deleted.

Braxton-Koch wrote on 5/3/2023, 6:12 AM

Off/On topic but... Just "upgraded" from SF studio to "pro suite". I'm noticing a pattern in ALL of magix software. They have some useful features in cheaper versions but then the functions are no longer there in "upgraded" versions. SF 17 being a great example. It comes with Wizard Fx, cool, then the upgrade comes with CoreFx, even cooler... However, why can I no longer even access my wizard fx plug-ins!? And I'm not talking about the instant actions (which should also be modifiable), I'm talking plug-ins in general, from the drop-down menu or otherwise. HELP!

I've noticed them doing the same thing in video software. Total bummer. If this is truly an "upgrade" to a "Pro suite" than it should be full scale, every feature, PLUS! (As I believe they are bold enough to advertise yet fail to deliver.) "Every feature PLUS... A,B,C." I LOVE magix, don't get me wrong just not sure why they're selling themselves (and the customers) short. 1 would think a simple update could solve these discrepancies?

SP. wrote on 5/3/2023, 6:43 AM

@Braxton-Koch If you own a stand-alone license for wizard FX you can just add them to Sound Forge Pro by scanning the VST plugin path. Otherwise you need to buy a stand-alone license from https://www.magix.com/int/music/audio-plugin-union/wizardfx-suite/

The wizard FX that is part of Sound Forge Audio Studio might not be the standalone license and might only work inside Sound Forge Audio Studio.

Braxton-Koch wrote on 5/4/2023, 8:35 AM

@Braxton-Koch If you own a stand-alone license for wizard FX you can just add them to Sound Forge Pro by scanning the VST plugin path. Otherwise you need to buy a stand-alone license from https://www.magix.com/int/music/audio-plugin-union/wizardfx-suite/

The wizard FX that is part of Sound Forge Audio Studio might not be the standalone license and might only work inside Sound Forge Audio Studio.

Just blows my mind that 1 it doesn't auto-scan, 2 it doesn't import from earlier version(s)! But yes, Thank You, kindly. Was buggin me out because when I search for the location of them in acid, it would refer to a folder that didn't even exist!? lolbvs I did find them in the sound forge 17 studio folder tho and they did import! Was like what the heck...

Don't suppose you have any insight into if there's a way to get my FxHome plug-ins to work in Vegas Pro 20, by chance? Talk about buggin out, I'm waiting to hear back about Vegas not launching while connected to the internet. Could you imagine being a hub subscriber and experiencing that. smh What is going on over there??

SP. wrote on 5/4/2023, 9:15 AM

@Braxton-Koch I would guess that the validation period of some security certifcate ran out so Vegas wasn't able to start. Usually all programs that use VST plugins do it in the same way: you open the program settings, enter the correct VST paths and scan the paths. Then the plugins should be available.

Shawn-Rogers wrote on 2/24/2024, 1:06 PM

Will there be an update to Sound Forge Pro 17 soon that will stop it from crashing every 3 processes? Please fix this on windows 10. This was such an amazing program but now it is so unstable.