been using ozone 11 for several months...works okay SF 18

my 2 cents

I've been using Ozone 11 in SFPro18.0 for about 2 weeks now and it's working fine except It doesn't open the previous preset used, may it be custom or built-in. This issue was the other way around in v16.0. I'm still waiting for customer support reply about this. Ozone 11 doesn't work in SFPro 16.1.4. It display as ARA but then when you use it, it doesn't do anything. It works in SFPro 15.0 though. I haven't use SFPro 17.0 because I didn't like the metering (Devs removed the Peak Meter V2) and some plug-in issue from v16.0 were never fix.

Correction: Ozone 11 works in SF 16.0 (Img1. Ozone11). It's Ozone RX 11 Advanced that doesn't work in v16.0. I realized my mistake when I checked my ticket to customer support. Ozone RX 11 display as ARA, 64 Bit instead of VST3, 64 Bit (Img2. Ozone RX11) and doesn't do anything when use. Additionally, although "RX 11 Spectral Editor" display as VST3, 64 Bit when use the result is "Spectral Editor ARA is not available for this host" (Img3. RX11 in SF v18.0). This is also true with SF v15 & v16. In Summary RX 11 does not work in SF v16 but works in SF v15 & v18. Ozone 11 works in v15, v16 & 18.

Magix fixes Sound Forge issues very slowly. Because Magix's priority is Vegas. They just released Vegas 22.

@john_barr

It's a pity why they do that. I really like SF since it was owned by Sonic Foundry then by Sony because of its simplicity and ease of use. I think until version v16.0 that everything went downhill. Their devs fixed things that weren't broke. Ex. Batch Converter in v.15.0, removed Peak Meter (V2) in v17.0. Is it something they do just because or to make management happy that they are doing something?