Waves Mercury Bundle is a software program developed by Team AiR 2007. Upon being installed, the software adds a Windows Service which is designed to run continuously in the background. Manually stopping the service has been seen to cause the program to stop functing properly. It adds a background controller service that is set to automatically run. Delaying the start of this service is possible through the service manager. A scheduled task is added to Windows Task Scheduler in order to launch the program at various scheduled times (the schedule varies depending on the version).

The software is designed to connect to the Internet and adds a Windows Firewall exception in order to do so without being interfered with. The setup package is about 592.72 KB (606,944 bytes) when donwloaded. Relative to the overall usage of users who have this installed on their PCs, most are running Windows 7 (SP1) and Windows 8. While about 41% of users of Waves Mercury Bundle come from the United States, it is also popular in United Kingdom and France. Program details. Or, you can uninstall Waves Mercury Bundle from your computer by using the Add/Remove Program feature in the Window's Control Panel.

• On the Start menu (for Windows 8, right-click the screen's bottom-left corner), click Control Panel, and then, under Programs, do one of the following: • Windows Vista/7/8: Click Uninstall a Program. • Windows XP: Click Add or Remove Programs. • When you find the program Waves Mercury Bundle, click it, and then do one of the following: • Windows Vista/7/8: Click Uninstall. • Windows XP: Click the Remove or Change/Remove tab (to the right of the program).

If you are using Cubase 5 on Vista or on Windows 7, Trust me, your waves 5. (five point 0,1,2,3,4 etc. Versions) WONT WORK! Simply you have TWO choices 1.Switch to windows XP & (waves 5.0,5.2 etc.)IT IS WORKING.with. Cubase 5 2.Buy the waves version 7,You can work on any Operating System.

• Follow the prompts. A progress bar shows you how long it will take to remove Waves Mercury Bundle.

The advantage of Reaper x64 over Reaper x86 is that it's able to use more memory the x86 version. Where as the x86 might top off at 2.5-3GB of RAM, the x64 version (like anything x64) is able to use loads of RAM. Truthfully though, you will ONLY see this performance gain if you use a MASSIVE AMOUNT of synths, or a MASSIVE AMOUNT of audio tracks. The largest Reaper x86 project Ive had was 74 audio tracks large, 3 NI synths strong, and 30-40 VST's solid.and I still had no problem with stability. So there is no actual reason why you should have to go to x64 YET (assuming that you don't make massive productions, that is). And until some of the more important VST's (::cough:: Waves!!!) work flawlessly in a x64 DAW.I'll be sticking with Reaper x86. On a sidebar.why the hell hasn't Waves made 64-bit compatible plug-ins yet?

A lot of companies are doing it. Hell even iZotope has done it with their FAMOUS line of mastering plug-ins. When you install them, they install an x86 version and an x64 version. Get on the ball vendors. I had terribly annoying problems with Waves on Win7 64 Bit and I finally found a solution! - The user account control changes some things (coming from Win XP 32), but it's not that much: It's only relevant for older waveshells (5.0/5.2 etc, for all us Non-WUPers) which write their filter properties into the registry. These keys are located under HKEY_LOCAL_MACHINE/Software/Classes.

Whenever you encounter the famous 'could not find any Waves Plugins, reinstall.blabla' simply change the privileges of the 'Classes' registry key. Users need to have full access (right click on 'Classes' in regedit), at least during the plugin scan - otherwise C1, Q1, REQ etc. Won't appear at all. No need to install or run anything as an admin, just that single reg key ownership. UAC may be activated, no problems with that. - Things might be quirky GUI-wise when using the original WaveShells. I had much better stable results using the famous shell2vst converter.

Somehow I have to run shell2vst as admin to create the single wrappers. Move to vstplugins, clear cache and rescan plugin directory, done. - The BIGGEST issue for me was: newer WaveShell GUIs (SSL, API) didn't appear at all, just black. I found out that my graphic adapter (Macbook Pro with X1600, Boot Camp 3, Snow Leopard, Win7 x64) didn't run anything OpenGL-related. While desperately trying to find a driver version which would let me run it, I accidentally ACTIVATED Aero again (I always turn off any graphic stuff, so my Win7 looked like Win2000) - and suddenly OpenGL worked. Turning off Aero seems to entirely disable 3D-/OpenGL support for GUIs. So now I'm happily using Reaper x64 with Waves plugins!

These keys are located under HKEY_LOCAL_MACHINE/Software/Classes. Whenever you encounter the famous 'could not find any Waves Plugins, reinstall.blabla' simply change the privileges of the 'Classes' registry key. Users need to have full access (right click on 'Classes' in regedit), at least during the plugin scan - otherwise C1, Q1, REQ etc. Won't appear at all. No need to install or run anything as an admin, just that single reg key ownership. I've got the same problem with that waves - could not find any waves plug-ins.

And I tried to fix it with the registry. I am using a German version.:P So would you please tell me, what I accuratly have to do? Should I change the whole 'Classes'-folder? Or just parts of it? And what do I have to change? -->see my screenshot.

I'm just about to install Windows7 64bit. I have the impression that I can get nearly all plugins and standalone's to run even though they are 32bit. Is this correct?

I really need: Battery, Kontakt, Guru, SynthSquad and BFD2 to run. Oh, and a Line 6 audio interface.

Do you think there will be any problems? Most 32Bit apps/plugins work just fine under Win7 x64. You can get the Waves plugins to install. But it's a small PITA. If you have the latest version of Komplete 6, it has both 32Bit and 64Bit (code) versions of the plugins. The 32Bit (code) versions of the NI plugins work fine in Win7 x64. In general, if your software/hardware works well with Vista x64, it'll work with Win7 x64.

Jim Roseberry. You can use the benefits of x64 bts OS only if you: 1. Have x64-bits processor (assuming you have one) 2. I mean really EVERY hardware installed on you computer has x64-bits driver for your installed x64-bits OS. Otherwise tha device may not work properly and it won't work as expected. Every program you install is recomended to has x64-bits edition (otherwise you can't use more than 3 GB RAM addressing per application because 32-bits limmiting). Especially audio and video programs and raster/vector applications with real-time rendering and so on.

If you cover 1-3 you'd better have at least 4 GB of RAM. Otherwise it won't worth it. Recommended is 8, 12 or more for your needs.

With money you can purchase even custom 64-bits drivers for any x64-bits OS. I had terribly annoying problems with Waves on Win7 64 Bit and I finally found a solution! - The user account control changes some things (coming from Win XP 32), but it's not that much: It's only relevant for older waveshells (5.0/5.2 etc, for all us Non-WUPers) which write their filter properties into the registry. These keys are located under HKEY_LOCAL_MACHINE/Software/Classes.

Whenever you encounter the famous 'could not find any Waves Plugins, reinstall.blabla' simply change the privileges of the 'Classes' registry key. Users need to have full access (right click on 'Classes' in regedit), at least during the plugin scan - otherwise C1, Q1, REQ etc. Won't appear at all. No need to install or run anything as an admin, just that single reg key ownership.

UAC may be activated, no problems with that. - Things might be quirky GUI-wise when using the original WaveShells. I had much better stable results using the famous shell2vst converter. Somehow I have to run shell2vst as admin to create the single wrappers.

Move to vstplugins, clear cache and rescan plugin directory, done. - The BIGGEST issue for me was: newer WaveShell GUIs (SSL, API) didn't appear at all, just black. I found out that my graphic adapter (Macbook Pro with X1600, Boot Camp 3, Snow Leopard, Win7 x64) didn't run anything OpenGL-related.

While desperately trying to find a driver version which would let me run it, I accidentally ACTIVATED Aero again (I always turn off any graphic stuff, so my Win7 looked like Win2000) - and suddenly OpenGL worked. Turning off Aero seems to entirely disable 3D-/OpenGL support for GUIs. So now I'm happily using Reaper x64 with Waves plugins!

This is a great story, thanks a lot for this! Unfortunately I still can't get it working. I also have windows 7 64bit. Changing the permissions on the classes fixes the first part. Then I tried shell2vst, got some nice dll's now.

But still: when I open a c1 or anything else from murcery or diamond bundle, from the shell2vst dll or the shell itself, it crashes my host(both ableton live and max/msp same problem). The strange thing is that other wave bundle plugins work fine! My windows view is already set to aero. First I thought it had something to do with graphics, becouse I opened a set in ableton and everything was working fine I think but when I opened the wwindow of a c4->crash. But now I'm not sure becouse the same set causes a crash on the start since then. I'm working on this problem for the one whole day now, I'm out of idea's can anyone help me?

Thanks (also frustrating is, ableton live hangs in memory if it crashes so I have to reboot every time. Same problem with xp). Hi, I just want say, I figured it out.

I already changed the compatibility mode of ableton live to xp sp3, without succes, but I didn't try xp sp2. I thought it wasn't such a big difference.but that was the key, everything is working now! Using wave plugins on windows 7 64 bit in ableton. Please good sir im in diying to know how you changed the compatibility mode to sp2 i have the exact same problem and have searched every were but cant find the answer. Please please tell me. Thanks alot in advance.zz.

BTW for anyone (like myself who just switched to Reaper yesterday) who is wondering how to get WaveShell 5.7/5.9 (e.g. API/SSL) GUI working - just use shell2vst and it will show the GUI no problem. Without using shell2vst you just end up with a black screen for the gui. What I did was copy the two waveshell dll's and shell2vst.exe to c: (outside the vstplugins dir), drop the 2 dll's onto the shell2vst.exe, then copy back the contents of the waves dir into a vstplugins folder and clear cache and rescan. I had terribly annoying problems with Waves on Win7 64 Bit and I finally found a solution! - The user account control changes some things (coming from Win XP 32), but it's not that much: It's only relevant for older waveshells (5.0/5.2 etc, for all us Non-WUPers) which write their filter properties into the registry.

These keys are located under HKEY_LOCAL_MACHINE/Software/Classes. Whenever you encounter the famous 'could not find any Waves Plugins, reinstall.blabla' simply change the privileges of the 'Classes' registry key. Users need to have full access (right click on 'Classes' in regedit), at least during the plugin scan - otherwise C1, Q1, REQ etc.

Won't appear at all. No need to install or run anything as an admin, just that single reg key ownership. UAC may be activated, no problems with that. - Things might be quirky GUI-wise when using the original WaveShells.

I had much better stable results using the famous shell2vst converter. Somehow I have to run shell2vst as admin to create the single wrappers. Move to vstplugins, clear cache and rescan plugin directory, done.

- The BIGGEST issue for me was: newer WaveShell GUIs (SSL, API) didn't appear at all, just black. I found out that my graphic adapter (Macbook Pro with X1600, Boot Camp 3, Snow Leopard, Win7 x64) didn't run anything OpenGL-related. While desperately trying to find a driver version which would let me run it, I accidentally ACTIVATED Aero again (I always turn off any graphic stuff, so my Win7 looked like Win2000) - and suddenly OpenGL worked. Turning off Aero seems to entirely disable 3D-/OpenGL support for GUIs. So now I'm happily using Reaper x64 with Waves plugins! I've tried all this and I still get the API and SSL looking completely black.

Any other solutions? Hey guys If you have problems with Waves Millenium bundle not being picked up by Cubase 5 ( ie. Receiving error - 'Please reinstall Waves plug-ins in order to use Waveshell' ). Go to your system where you installed the Waves folder - c:/programfiles/waves Open the Millenium Read me file - it lists the name of every plug in dll that was installed into that same Waves folder. Create a folder called waves on your desktop and COPY everyone of those dll files into it (about 90) Then MOVE that folder into c:/programfiles/steinberg/cubase5/vstplugins Open Cubase 5 ( ignore any error msgs) and refresh your plug in information from the drop down tool bar All the waves plug ins should appear This worked for me on Windows 7 64 bit with Cubase 5 Good luck! I had terribly annoying problems with Waves on Win7 64 Bit and I finally found a solution!

- The user account control changes some things (coming from Win XP 32), but it's not that much: It's only relevant for older waveshells (5.0/5.2 etc, for all us Non-WUPers) which write their filter properties into the registry. These keys are located under HKEY_LOCAL_MACHINE/Software/Classes. Whenever you encounter the famous 'could not find any Waves Plugins, reinstall.blabla' simply change the privileges of the 'Classes' registry key.

Users need to have full access (right click on 'Classes' in regedit), at least during the plugin scan - otherwise C1, Q1, REQ etc. Won't appear at all. Install Endpoint Protection Sccm 2012 Manually.

No need to install or run anything as an admin, just that single reg key ownership. UAC may be activated, no problems with that. - Things might be quirky GUI-wise when using the original WaveShells. I had much better stable results using the famous shell2vst converter.

Somehow I have to run shell2vst as admin to create the single wrappers. Move to vstplugins, clear cache and rescan plugin directory, done.

- The BIGGEST issue for me was: newer WaveShell GUIs (SSL, API) didn't appear at all, just black. I found out that my graphic adapter (Macbook Pro with X1600, Boot Camp 3, Snow Leopard, Win7 x64) didn't run anything OpenGL-related. While desperately trying to find a driver version which would let me run it, I accidentally ACTIVATED Aero again (I always turn off any graphic stuff, so my Win7 looked like Win2000) - and suddenly OpenGL worked.

Turning off Aero seems to entirely disable 3D-/OpenGL support for GUIs. So now I'm happily using Reaper x64 with Waves plugins! I have been pulling my hair out for DAYS, trying to figure out how to get Waves to run on my new Windows 7 machine. You have just made my DAY. I seriously owe you one for this.

THANK YOUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BTW for anyone (like myself who just switched to Reaper yesterday) who is wondering how to get WaveShell 5.7/5.9 (e.g. API/SSL) GUI working - just use shell2vst and it will show the GUI no problem. Without using shell2vst you just end up with a black screen for the gui. What I did was copy the two waveshell dll's and shell2vst.exe to c: (outside the vstplugins dir), drop the 2 dll's onto the shell2vst.exe, then copy back the contents of the waves dir into a vstplugins folder and clear cache and rescan. I did the first half.drop the shells onto the shell2vst.exe, saw that it created the shells but now where and how do I drop those back into the vst folder???

I copied the shell2vst.exe into my vst folder but that didnt work.still getting the black screen for the gui thing??? I had terribly annoying problems with Waves on Win7 64 Bit and I finally found a solution! - The user account control changes some things (coming from Win XP 32), but it's not that much: It's only relevant for older waveshells (5.0/5.2 etc, for all us Non-WUPers) which write their filter properties into the registry. These keys are located under HKEY_LOCAL_MACHINE/Software/Classes. Whenever you encounter the famous 'could not find any Waves Plugins, reinstall.blabla' simply change the privileges of the 'Classes' registry key.

Users need to have full access (right click on 'Classes' in regedit), at least during the plugin scan - otherwise C1, Q1, REQ etc. Install Microsoft Forefront Endpoint Protection 2010 Without Sccm. Won't appear at all. No need to install or run anything as an admin, just that single reg key ownership.

UAC may be activated, no problems with that. - Things might be quirky GUI-wise when using the original WaveShells. I had much better stable results using the famous shell2vst converter. Somehow I have to run shell2vst as admin to create the single wrappers. Move to vstplugins, clear cache and rescan plugin directory, done. I managed to drag the WaveShell-VST.dll into shell2.exe and the Plugins were created. But when I move the new shell2.exe or WaveShell-VST.dll 's into my plugins folder Reaper still doesn't recognize the wave plugins.

Any suggestions? To all you guys who're still having trouble with installation, maybe this summary helps: 1. Follow the steps fuseburn posted (this admin and registry stuff) than: 1 - download and unzip this: 2 - copy the extracted shell2vst.exe into the C: Program Files Waves Waveshells folder (this just makes it easier to use) 3 - drag and drop each 'WaveShell-VST x.x.x.dll' onto the shell2vst.exe 4 - that will create a folder C: Program Files Waves Waveshells Waves that contains all the plugins as DLLs 5 - Cut and paste this new folder into your vstplugins folder. If there are already any waveshells in the vstplugins folder you should delete it/them. (NB delete the waveshells placed in vstplugins NOT the ones in Waves Waveshell otherwise there'll be a conflict).

First I didn't see that new Waves folder shell2.exe creates. But it is there! I don't know if its really necessary to uninstall and reinstall waves before all that. I did and it suddenly worked fine. Then some more dumb questions. If 32 bit work on a 64 bit OS. What are the advantages of running a reaper 64, instead if reaper 32?

Absolutely none except if you make monster projects that require a massive amount of RAM. In fact in many case it might even be slower than the 32bits versions unless the software is specifically written for 64 bits. The only softwares I know that are written like that are computational software like Matlab/Mathematica/Maple/Stata/etc. And VST wise your choice will be limited and bridging 32bits VSTs to 64bits host has always been less than satisfactory for me in terms of performance and stability.

CPU wise it is virtually the same as the 64bits version, at least that is what I am seeing on my machine, a core2duo T8600 (yes it's a laptop!). To all you guys who're still having trouble with installation, maybe this summary helps: 1. Follow the steps fuseburn posted (this admin and registry stuff) than: 1 - download and unzip this: 2 - copy the extracted shell2vst.exe into the C: Program Files Waves Waveshells folder (this just makes it easier to use) 3 - drag and drop each 'WaveShell-VST x.x.x.dll' onto the shell2vst.exe 4 - that will create a folder C: Program Files Waves Waveshells Waves that contains all the plugins as DLLs 5 - Cut and paste this new folder into your vstplugins folder. If there are already any waveshells in the vstplugins folder you should delete it/them. (NB delete the waveshells placed in vstplugins NOT the ones in Waves Waveshell otherwise there'll be a conflict). First I didn't see that new Waves folder shell2.exe creates. But it is there!

I don't know if its really necessary to uninstall and reinstall waves before all that. I did and it suddenly worked fine. Side note, if you use Windows 7 convert to DLL in a directory that is not under Program Files. If you do, you are asking for trouble because security to memory and disk writes in and from the Programs Files folder is very tight and at a very low level of the OS.