Ozone 12 Advanced Plugin Not Recognized in Sound Forge Audio Studio 17

RodrigoFla86 wrote on 10/12/2025, 6:20 PM

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.

Comments

RossV wrote on 10/23/2025, 12:43 PM

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.

SP. wrote on 10/23/2025, 1:26 PM

@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.

RossV wrote on 10/23/2025, 1:36 PM

Hmmm. If I upgrade from SFAS17 to SFPro 18 for US$79.99, will that also solve the problem?

 

SP. wrote on 10/23/2025, 1:38 PM

@RossV I don't know. Why not try the free way first?

RossV wrote on 10/23/2025, 2:13 PM

Success! Thank you very much. I'll share this with the tech support team at Sweetwater so they can spread the word.

RodrigoFla86 wrote on 10/23/2025, 2:33 PM

Wouldn't it be more prudent for magix to release a patch update than to modify the original files in the folder?

SP. wrote on 10/23/2025, 2:42 PM

@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.

RodrigoFla86 wrote on 10/23/2025, 2:48 PM

The amazing thing is that ozone 12 opens on my older SOUND FORGE Audio Cleaning Lab 4

SP. wrote on 10/23/2025, 3:12 PM

@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.