Graphic EQ Plug-in and accompanying plug-ins compatibility issues...

ZoltanG wrote on 01/11/2019, 14:21

Hello all,

Since the last two upgrades or so of Sound Forge from earlier versions which were under SONY and Sonic Foundry, the Audio_x64 folder plug-ins (Windows 10 Pro 64 bit) ... such as sfppack1_x64.dll, sfppack2_x64.dll, etc. total of about 18 dll files have been also updated by MAGIX to newer dates and evidently some changes.

However, ever since the dates of these files indicate the year 2018-2019 from the earlier dates of 2015 or earlier, for example, the Graphic EQ plug-in (sfppack2_x64.dll) and others, cause an issue in my Cakewalk SONAR Platinum or now Bandlab Cakewalk DAW, by whenever this EQ SFX is selected on any given track, with no input, a rhythmic 'blip-ping' sound is outputted to the master bus, and indicated on the track's VU meters. If I replace these DLL files from and earlier copy, this blipping every 2-3 seconds is eliminated. However, every-time MAGIX puts out a new Sound Forge version, these files are updated to the defective ones causing these symptoms.

I would appreciate if someone would come up with a cure other than having to revert back to previous files of earlier working Sound Forge software.

Thanks.

ZoltanG

Comments

emmrecs wrote on 01/11/2019, 16:19

@ZoltanG

Welcome to the Magix forums.

I'm not sure I fully understand what you are saying but I think you are asking why certain Magix plugins do not work in other DAWs. Is that correct?

If so, the answer is quite simple: Magix design and build their plugins to work with one or more of their own software products; they are not intended to be used in software other than that for which they were designed.

The fact that earlier versions did work with other software is clearly a bonus but the current versions apparently do not offer this facility.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

ZoltanG wrote on 01/11/2019, 16:37

Jeff,

@ZoltanG

Welcome to the Magix forums. THANKS!!

I'm not sure I fully understand what you are saying but I think you are asking why certain Magix plugins do not work in other DAWs. Is that correct? THAT IS CORRECT!!

If so, the answer is quite simple: Magix design and build their plugins to work with one or more of their own software products; they are not intended to be used in software other than that for which they were designed.

The fact that earlier versions did work with other software is clearly a bonus but the current versions apparently do not offer this facility.

Jeff

Well, first of all MAGIX took over the exact same programs as was originally Sonic Foundry and SONY as in VEGAS, and Sound Forge, and if I am not mistaking whenever I start either of those programs it does a slew of folder checks for ALL and EVERY MANUFACTURERS' PLUG-INS that WORK with both software irregardless of who's! Why would MAGIX discriminate and not allow another DAW to use the SAME plug-ins from the same manufacturers and from it's OWN from previous providers that MAGIX took over and continued to expand or (maybe) improve on? That is purely ridiculous.

Zoltan

emmrecs wrote on 01/11/2019, 20:16

@ZoltanG

That is purely ridiculous.

That is your opinion, to which you are perfectly entitled but it is not necessarily Magix' opinion.

When Magix took over several products which had been previously owned/manufactured by Sonic Foundry and Sony there was no undertaking that future development of any of the products would entail use of the sort of open architecture that your opinion demands. Yes, manufacturers of plugins do want/need their products to be accessible by any DAW; manufacturers of DAWs do not necessarily want/need their included plugins to be available to other DAWs.

As an example: I have and run Adobe Audition CC; its included (= proprietary) plugins are NOT available to any other DAW which I also run.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

ZoltanG wrote on 02/11/2019, 13:09

So they INTENTIONALLY sabotage plug-ins, that worked from their 'inherited' providers and on which previously paid users might depend on and have DAW projects which included those plug-ins, with a 'bleeping sound' so they cannot use it anymore?? Nice going .. remind me NOT to buy MAGIX products any more down the line. Thanks.

emmrecs wrote on 02/11/2019, 16:21

@ZoltanG

Please carefully re-read my last post. I specifically mentioned that Adobe do exactly the same thing with plugins that are intended to be used solely and exclusively with their own software. This is not something which only Magix does, it is quite commonplace. There is no thought at all of "intentionally sabotaging" anything, IMO. Rather, those Magix plugins are being continuously developed to function as well as possible in the latest version of the intended host DAW.

The fact that earlier versions of some plugins you have could be used in other DAWs in no way negates this situation: all DAW manufacturers have to make decisions about exactly what can and what cannot be included in any new version of software or plugin.

Perhaps you should also ask the makers of your other DAWs whether they have actually made changes to their software which actively prevent the plugins you wish to use from functioning fully?

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

rraud wrote on 02/11/2019, 20:00

Even the old (Direct X) IZotope mastering suite plugs (I really like the multi-band Comp/Limter) that were included w/ SCS SF Pro 9 and 10 would only run on the SF,Vegas, Acid, ect, However, I think the IZotope Elements plugs that came with SF Pro 12 & 13 will run on any PC VST host app. I'm not 100% sure about this though.

emmrecs wrote on 02/11/2019, 20:17

@rraud

I think the IZotope Elements plugs that came with SF Pro 12 & 13 will run on any PC VST host app

I'm almost 100% certain that is correct. As I wrote in an earlier post, manufacturers of plugins want their products to be usable in as many host DAWs as possible.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

Trensharo wrote on 04/11/2019, 10:51

Jeff,

@ZoltanG

Welcome to the Magix forums. THANKS!!

I'm not sure I fully understand what you are saying but I think you are asking why certain Magix plugins do not work in other DAWs. Is that correct? THAT IS CORRECT!!

If so, the answer is quite simple: Magix design and build their plugins to work with one or more of their own software products; they are not intended to be used in software other than that for which they were designed.

The fact that earlier versions did work with other software is clearly a bonus but the current versions apparently do not offer this facility.

Jeff

Well, first of all MAGIX took over the exact same programs as was originally Sonic Foundry and SONY as in VEGAS, and Sound Forge, and if I am not mistaking whenever I start either of those programs it does a slew of folder checks for ALL and EVERY MANUFACTURERS' PLUG-INS that WORK with both software irregardless of who's! Why would MAGIX discriminate and not allow another DAW to use the SAME plug-ins from the same manufacturers and from it's OWN from previous providers that MAGIX took over and continued to expand or (maybe) improve on? That is purely ridiculous.

Zoltan


Even in earlier versions of Sound FOrge, many of those plugins only functioned in DEMO MODE in other software. Everything "ExpressFX" falls into that category, for example. Accoustic Mirror has never worked properly. It will freeze in Cakewalk if you browse for an IR file.

Cakewalk has its own set of basic mixing plugins, and then some. You don't need these in that DAW.

If you want some Additional Plugins for Cakewalk, and don't want to pay, go download the free REAPER VSTs and put them in the Cakewalk VSTPlugin Folder (if you don't want them showing up everywhere).

Plugin Boutique has free plugins in every category. Why would anyone even want to use those old-as-dirt mediocre DirectX plugins, when you can get so much better out there?

ZoltanG wrote on 04/11/2019, 16:46
@Trensharo
Plugin Boutique has free plugins in every category. Why would anyone even want to use those old-as-dirt mediocre DirectX plugins, when you can get so much better out there?

Well, as we are all creatures of habit, and we have a hard time of letting of things go that we are accustomed to and have proven to work well in the past, they might be considered 'old-as-dirt mediocre' but if it did the job it was intended for, and a more 'elaborate' substitute was not needed, then, yes they are used, especially in older projects that need to be resurrected sometimes, and then one does not expect a 'bleeping' sound in place of what used to work a year ago!