Skip to main content
A
AJ5EE9
Participant
January 17, 2021
Question

Adobe Audition 3.0 crashes when enabling Waves Gold v10 Plugins

  • January 17, 2021
  • 1 reply
  • 1108 views

After IT rebuilt my studio computer I now can't load Waves Gold V10 plugins on Adobe Audition 3.0. Adobe crashes every time I try to enable them in the VST manager. Waves support says the plugins are not compatible with AA 3.0, however I had no issue with this plugin package on two other machines using AA 3.0. Tried reinstalling everything but no luck. Using Windows 10.  Any advice? Thanks.

This topic has been closed for replies.

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
January 17, 2021

Waves are pretty clear about this on this page where they potentially give you a workaround. However you look at it, you had to be running something like this previously in order for them to run at all on Audition 3 which is resolutely 32-bit - that or use jBridge.

A
AJ5EE9Author
Participant
January 18, 2021

Thanks. Actually I don't believe I ran that on the previous machines.  Both had v10 and were 64-bit just like this rebuild.  That's why this is so perplexing.  Another forum suggested updating AA to 3.0.1 but I am skeptical.

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
January 18, 2021

Maybe I am the only one in the world that made it work twice!  LOL.  All kidding aside, the Gold package contains 32 and 64 bit, but none will load even when only enabling just the 32's in VST manager - nothing shows up, no VST directory in Effects.  The Waves workaround link says it's for 32-bit operating systems.  Mine is 64-bit.  Your saying this still may "work" for my issue? I am not familiar with jBridge. Thanks.


Hmm... I think I can see what might be going on. When you run 32-bit Audition 3 on a Windows 10 64-bit OS you are actually running an emulation - so effectively it's not running directly on the OS itself. In a way it's good that Microsoft let you do this in pretty much an invisible way (unlike Apple, who really couldn't give a stuff about people with older software they want to run), but I suspect that when it comes to the .dlls necessary to run VST plugins, it has to be configured differently in some way before they'll run at all. Also this may have something to do with the way RAM is addressed, but there are other possibilities too. So it's potentially a bit of a minefield...

 

All the comments I've read about this sort of issue recommend jBridge as being a good solution, FWIW.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices