Plugin Scanner Issues: Please list plugins

I noticed several people are having issues with plugins not scanning. Please list the plugins that are failing to scan in this thread so the devs can look at them.

***BEFORE YOU LIST PLUGINS, PLEASE DO THE FOLLOWING:

1. Ensure that you have the most current version of the plugin installed
2. Scan both 32 and 64 bit versions of MPC
3. List the version of the plugin you have installed

Are they listed in a log file in the MPC directories? A bunch of old plug which worked with 1.6 no longer work with 1.7 on my system. These are free VST plugins which will most likely never be updated ever again but were running good in 1.6 and below.

WAVES v9.20 August 2014 release Win 7
The Waves 9.3 Waveshell crashes under 1.7 but Waveshell scans fine under 1.6.

If the Waveshell crashes it kills all my various Waves bundles.

I had some plugins which crashed a lot of time but finally worked after a scan spam... #strangeIssue

About Waveshell.dll from Waves.

There are Issues with some 5.1 Waves plugins making the whole bundle unusable.

I experienced the same Issue and fixed it with the Shell2vst.exe workaround. It extract each single *.dll from the Shell. Then If a single *.dll fail to load, others will work.

1 - Download Shell2vst.exe here ... http://www.xlutop.com/buzz/zip/shell2vst.zip
2 - Copy Shell2vst.exe to your plugin folder where the WaveShell is located.
3 - Drag and drop each "xxxdll WaveShell-VST" onto the shell2vst.exe (But not WaveShell-Direct X. .. dll or the WaveShell-Direct X. .. dll) If prompted to overwrite, choose "no"
4 -.'s "Waves" new folder will be created that contains all the waves plugins ( individual *.dll files)
5 - Copy the newly created "Waves" folder into your Vstplugins shared folder (Example: C: \ Program Files (x86) \ MPCplugins \ Vst_plugins)
6 - Remove the WaveShells from your shared folder Vstplugins or rename it Waveshell9.2.dllBKP.
7 - Scan for new plugins on the MPC software.

You will see which plugins pass and wich fails to load.

Et voilà.

comtox wrote:I had some plugins which crashed a lot of time but finally worked after a scan spam... #strangeIssue

About Waveshell.dll from Waves.

There are Issues with some 5.1 Waves plugins making the whole bundle unusable.

I experienced the same Issue and fixed it with the Shell2vst.exe workaround. It extract each single *.dll from the Shell. Then If a single *.dll fail to load, others will work.

1 - Download Shell2vst.exe here ... http://www.xlutop.com/buzz/zip/shell2vst.zip
2 - Copy Shell2vst.exe to your plugin folder where the WaveShell is located.
3 - Drag and drop each "xxxdll WaveShell-VST" onto the shell2vst.exe (But not WaveShell-Direct X. .. dll or the WaveShell-Direct X. .. dll) If prompted to overwrite, choose "no"
4 -.'s "Waves" new folder will be created that contains all the waves plugins ( individual *.dll files)
5 - Copy the newly created "Waves" folder into your Vstplugins shared folder (Example: C: \ Program Files (x86) \ MPCplugins \ Vst_plugins)
6 - Remove the WaveShells from your shared folder Vstplugins or rename it Waveshell9.2.dllBKP.
7 - Scan for new plugins on the MPC software.

You will see which plugins pass and wich fails to load.

Et voilà.

The Waveshell was crashing as soon as the BS 1.7 scanner would look at it.
NO OTHER software has a problem with it and it runs fine if you scan it in 1.6 instead of 1.7.

The problem is the newly designed scanner not the plugs.
Why would a person hack around their Waves plugs because of a problem with the MPC software?

Me... I'm just sharing some help. Hoping that will help somebody.

comtox wrote:Me... I'm just sharing some help. Hoping that will help somebody.

We are trying to share info to get things fixed not hack our setups to circumvent a problem.

Waves plugs are designed to run from the Waveshell not as a converted i.e. hacked VST, so there is no reason why you should have to do such.

I guess the willingness to do such depends on your true investment in the plugs.

Akai needs to fix the scanner or take it back to the previous scanner.

It's kinda surprising how often you see using Shell2VST as a suggested solution to making Wave plugs like it's a normal procedure instead of what it really is.

THE ADVERSARY wrote:It's kinda surprising how often you see using Shell2VST as a suggested solution to making Wave plugs like it's a normal procedure instead of what it really is.

That is because Waves Bundles are a monumental pain in the ass from the get-go!

Mike Boogie wrote:

THE ADVERSARY wrote:It's kinda surprising how often you see using Shell2VST as a suggested solution to making Wave plugs like it's a normal procedure instead of what it really is.

That is because Waves Bundles are a monumental pain in the ass from the get-go!

Been using Legit Waves since the days of the white HASP printer port dongle and I disagree.

That's long before they had enough plugs to make even a small bundle just to help you understand how far back we are talking.

i can dig it

I had the same problems when I updated to 1.7. It took me two days to get them reinstalled. It doesn't make sense but the shellvst.exe fixes the problem. The installation of 1.7 in my opinion was the problem because it seems like it removed waves completely or corrupted it during the installation. ALOT of waves plugins are not compatable on windows 7 and up. Version 9 is the only solution which is a headache when already having working plugins. But everything worked fine on windows xp. But I got them reinstalled. Be sure to make a backup copy of your dlls. Just in case this same problem happens when 1.7.1 is released. I talked to PETE from akai via twitter and he said they still don't know why it's crashing. But I'm good again for now

DJ Hellfire wrote:I noticed several people are having issues with plugins not scanning. Please list the plugins that are failing to scan in this thread so the devs can look at them.

***BEFORE YOU LIST PLUGINS, PLEASE DO THE FOLLOWING:

1. Ensure that you have the most current version of the plugin installed
2. Scan both 32 and 64 bit versions of MPC
3. List the version of the plugin you have installed

It happened to me but I got them up and running again. Had to reinstall them. I talked to PETE about via twitter. He said they still don't know why this happening.

i havent scanned mine..for fear that i iwll have this problem

I'm having this issue but with mac. is there any solution to this??

I could be wrong but I don't think it's the scanner. I think it has something to do with the installation of 1.7. It's the same as the vintage hack...after the update it no longer works. Something is kicking them completely out. I had to reinstall my waves 9 bundle. They are working fine again