Subject:Problems with Waves plugins in SF10 BatchConverter

Posted by: jeffjams

Date:1/9/2010 8:19:37 PM

First, let me say...the Batch Converter loads a bit faster in SF10 than it did in SF9. That's good.

However, there are two problems with Waves plugins in SF10's BC that I do not have in SF9. I still have SF9 loaded on the same computer...and my Waves plugins continue to function properly in SF9's Batch Converter.

Problem #1 -- I cannot distinguish between VST and DirectX versions of my Waves plugins in SF10's BC. I simply see duplicate entries of each plugin. Example: I see two entries of "Waves Enigma." In SF9, the DirectX version shows as "Waves Enigma," while the VST version shows simply as "Enigma." At least I could tell the difference in SF9.

Why is this a problem? That leads to...

Problem #2 -- The VST version of Waves plugins don't work in Batch Converter...nor in FX Favorites...both in SF9 and 10. I get the error message: "You are unauthorized to use this plug-in component."

Fortunately, the DirectX version of Waves has always worked properly in FX Favorites, including SF10.

However, in SF10's Batch Converter, not only can I not tell the difference between DirectX and VST, some plugins don't even load what appears to be the DirectX version. For example: the L3 Ultramaximizer shows up twice as "Waves L3 Ultramaximizer." Both give me the error message, and neither instance will load any presets.

It's really weird. Some DirectX versions of Waves plugins seem to be there (with presets), though I can't tell them apart from VST's without loading them. Other Waves plugins simply don't work at all in Batch Converter

Sony...what have you done differently in Sound Forge 10's Batch Converter in the way you organize plugins?

It's awful...AWFUL!!! Please fix it.

Or, if someone can enlighten me on how I might correct something in SF10, I'm open to suggestions.

As I said earlier, my Waves plugins (DirectX version) continue to work fine in Sound Forge 9's Batch Converter...on the same computer.

Subject:RE: Problems with Waves plugins in SF10 BatchConverter

Reply by: jackn2mpu

Date:1/11/2010 4:37:17 AM

I don't have SF10, but do have SF 7, 8, and 9. What I do to be able to tell what plugs are vst and what are dx, especially when I have both versions on my computer, is to use the organize plugins feature. This allows you to create custom menu layouts of your plugs, with folders and subfolders; it also allows you to rename plugins as you want to. It takes a while to do so if you have a lot of plugs, but well worth it. That way, when you go to add/use plugs in any operation in Soundforge you know what's what. What you have to do is to pay attention to the extensions used for each plug version.

BTW, this isn't done in the Batch Converter but the main part of the program.

Jack

Subject:RE: Problems with Waves plugins in SF10 BatchConverter

Reply by: jeffjams

Date:1/11/2010 11:30:39 AM

Thanks Jack. Organizing the Favorites is something I've always done since Sonic Foundry first introduced that menu years ago (SF5 ?).

You're right. It seems a user's manual reorganization of the plugin folders has no effect on the Batch Converter.

It's also why I've left SF9 installed on the same computer. My semi-educated logic tells me that if third party plugins work in one version of a host...on the same computer...the reason it doesn't work in the upgrade is likely due to something changed in the upgrade.

...Unless there's something I've missed in a setting someplace.

--Jeff

Subject:RE: Problems with Waves plugins in SF10 BatchConverter

Reply by: jeffjams

Date:1/11/2010 11:55:10 AM

One additional note -- I went to Wavesupport.net and tried their suggestion of going into my registry to...

"Delete the DX Cache folder from under:

Using SF 7.0 or higher - HKEY_CURRENT_USER > Software > Sony Media Software > Sound Forge > 7.0 (or the current version)."

The folks at Waves have some updating to do in their answer base as SF10 is in a different folder:
HKEY_CURRENT_USER > Software > Sony Creative Software > Sound Forge Pro > 10.0

The result? Deleting the DXCache folder did not work.