I scan the plugin in the folder where it was installed but it doesn't appear. Can anyone help? It's amazing that in Sound Forge Audio Cleaning Lab 4 it opens right away.
I'm having the same problem with Ozone 12 Elements and Sound Forge Audio Studio 17. The tech support team at Sweetwater looked into it, and they contacted both Magix and iZotope: they are aware of the problem, but offered no workarounds (and neither made any promises about fixing the issue). Here's what I've found on my own: SFAS17 won't recognize Ozone 12 Elements; it won't recognize the latest update to Ozone 11 Elements; but if I reinstall the version of Ozone 11 Elements that was bundled with SFAS17, it works as expected. Magix suggested installing another DAW to see what happens: I downloaded Reaper and it recognized 11 and 12, no problem.
@RossV There are plugin scan server exe files inside the Sound Forge program folder which are responsible for recognizing the plugins.
Some users reported it helps to replace them with newer versions. So, you could try to simply install the free trial version of Sound Forge Pro 18 and open its program folder and copy and paste the files from there to your Audio Studio 17 folder and replace the old ones (don't forget to make a backup first!).
Then check again if Sound Forge AS 17 loads your plugins correctly.
Hmmm. If I upgrade from SFAS17 to SFPro 18 for US$79.99, will that also solve the problem?
Success! Thank you very much. I'll share this with the tech support team at Sweetwater so they can spread the word.
Wouldn't it be more prudent for magix to release a patch update than to modify the original files in the folder?
@RodrigoFla86 I don't think there is anyone to create a patch. Sound Forge was maintained by the Samplitude team and these developers no longer work at Magix, they all left or went to Boris FX.
The previous developers, who worked on Sound Forge under Sony, only worked on Vegas since Magix acquired them in 2016. To my understand they are now again responsible for Sound Forge, but it might take a long while until something happens.
The amazing thing is that ozone 12 opens on my older SOUND FORGE Audio Cleaning Lab 4
@RodrigoFla86 Sound Forge Audio Cleaning Lab is technically a different software. It's a special version of Samplitude with a custom user interface. This could explain why it works fine there.
In the past it had names like Audio & Music Lab or Audio Cleaning Lab or Video Sound Cleaning Lab. It has nothing to do with Sound Forge except it was renamed to Sound Forge Audio Cleaning Lab for its last couple of releases.
Soundforge won't open Izotope plugins in my version 15. Not a single one of them. SF sees them all as ARA plugins. In the Izotope map in Program files the plugins are VST3. In the SF Preferences finding path they are also VST3. But finally in the SF Plugin manager the VST3 plugins are converted to ARA. None of the ARA plugins opens in Soundforge. I installed version 17 and that is even worse. It doesn't recognise not only my iZotope plugins but also my Waves plugins. I think it is time for the developers to look into this problem. After all ....what good is Sound Forge to me (and others) if I cannot use it with these important mastering tools/software. It is worthless to me now.
Hope for a solution soon.
@Roel-Sleurink Have you tried the suggestions mentioned above?
O Soundforge não abre plugins do Izotope na minha versão 15. Nenhum deles. O SF vê todos eles como plugins ARA. No mapa Izotope nos arquivos de programa, os plugins são VST3. No caminho de busca de preferências de SF, eles também são VST3. Mas finalmente, no gerenciador de plugins do SF, os plugins VST3 são convertidos para ARA. Nenhum dos plugins ARA abre no Soundforge. Instalei a versão 17 e isso é ainda pior. Ele não reconhece não só meus plugins do iZotope, mas também dos plugins do Waves. Acho que está na hora dos desenvolvedores investigarem esse problema. Afinal de contas.... de que adianta o Sound Forge para mim (e para outros) se eu não posso usá-lo com essas ferramentas/softwares importantes de masterização? Agora não vale mais nada para mim.
Espero uma solução em breve.
I ended up buying an upgrade license from Sound Forge Audio Studio 17 (x64) to Sound Forge Pro 18, and incredibly, both are now opening Ozone 12.