Feedback on Sound Forge Pro 15 vs SF Audio Studio 17 on Windows 11?

GRB wrote on 6/30/2024, 10:01 AM

Does anyone have experience with both Sound Forge Pro 15 and Sound Forge Audio Studio 17 on a Windows 11 machine?

Working well for you?

Notice any Pro/Cons with either in use compared to one another for consideration? In particular, SFP15 since it was released years ago, but technically after Win 11 release... so any compatibility issues? I'll be using alongside MM2025Prem, Samplitude Music Studio X8 (possibly Pro X5 if also ok w Win 11), and ACID PRO 11 mainly. I do also own various other DAWs, but trying to make good focus/use/learn decisions on limited space drive laptop.

I own both mentioned and are only for a humble home studio, so making decisions what products to load/keep/use on my newer Win 11 laptop after retiring my old "workhorse" Win 10 machine, finally....

Comments

GRB wrote on 6/30/2024, 10:19 AM

I will also create a support ticket with Magix to ask the same so I know the inside scoop.... expectations.

rraud wrote on 6/30/2024, 1:10 PM

I have no experience with Win 11. however regarding Sound Forge 16 and 17 (Pro & Audio Studio) in general had VST problems, so I mostly used SFP-15. Most of the VST issues have been addressed in Sound Forge Pro 18. AFAIK, SF Audio Studio 18 has not been published, so the SFAS 16/17 issues remain.

GRB wrote on 6/30/2024, 10:21 PM

I have no experience with Win 11. however regarding Sound Forge 16 and 17 (Pro & Audio Studio) in general had VST problems, so I mostly used SFP-15. Most of the VST issues have been addressed in Sound Forge Pro 18. AFAIK, SF Audio Studio 18 has not been published, so the SFAS 16/17 issues remain.

Great info.

What kind of Vst issues to expect/look for?

And if I read correctly, sounds like SPF15 "does not" have them in your experience? ... and SFAS17 does?

So, I just loaded my newest SFAS17 and not SFP15 in trying to stay more current (assumed safest and more issue free). Maybe I "assumed" too much.

Thanks So Much btw!

rraud wrote on 7/1/2024, 9:46 AM

Specifically, in SF-16 & 17 (both AS and Pro) do not display 32 bit third-party VST-2 plug-ins correctly showing only a fraction of the plug-in's UI window. SF-15 did not have this issue. Another annoyance with SF-17 was, the legacy dBFS peak meter was removed for unknown reasons, it was reinstated in SF-18, but it is lacking the peak factor it also can not longer be resized sufficiently.
FWIW, the 32 bit versions of SF 16/17 do not have the VST-2 display issue, but then, 64 bit plug-ins cannot be used so we are SOL either way. though both the 32 and 64versions of SF can be installed w/o issue.

GRB wrote on 7/1/2024, 10:19 AM

Specifically, in SF-16 & 17 (both AS and Pro) do not display 32 bit third-party VST-2 plug-ins correctly showing only a fraction of the plug-in's UI window. SF-15 did not have this issue. Another annoyance with SF-17 was, the legacy dBFS peak meter was removed for unknown reasons, it was reinstated in SF-18, but it is lacking the peak factor it also can not longer be resized sufficiently.
FWIW, the 32 bit versions of SF 16/17 do not have the VST-2 display issue, but then, 64 bit plug-ins cannot be used so we are SOL either way. though both the 32 and 64versions of SF can be installed w/o issue.

Caught me online looking.....

Oh ok, thats why I hadn't seen it myself is that I don't use 32bit plugins or programs anymore....

thanks for clarifying for me!