Windows 7 64 bit + Waves plugins

gregerlindberg · 09-22-2009, 12:23 AM

Installed Windows 7 64 bit on my new computor. When i open uper Reaper 64 and the SSL plugins its not the SSL gui. Its the rea plugins GUI in it instead. Kind of different when u learned to tweak it as it normally look.
My question, is it suppose to be like this? can i get it to look the way it is suppose to do? Or is it due to that it originally is a 32bit plugin running in a 64bit OS?

ThePulse · 09-22-2009, 01:04 AM

Has nothing to do with the OS. It's that you're using the 64-bit version of Reaper and the x86 (32-bit) bridge can't account for all of the coding of the 32-bit plug-ins in that x64 environment.

Everything shows up fine in the x86 version of Reaper...even on a x64 OS.

gregerlindberg · 09-22-2009, 01:17 AM

Quote:

Originally Posted by ThePulse

Has nothing to do with the OS. It's that you're using the 64-bit version of Reaper and the x86 (32-bit) bridge can't account for all of the coding of the 32-bit plug-ins in that x64 environment.

Everything shows up fine in the x86 version of Reaper...even on a x64 OS.

So is it possible to use the 32 bit Reaper in 64bit OS and it will work or will it not run? So i can get the Gui?
Thank you for the answer. =)
/Greger

Edwood · 09-22-2009, 03:29 AM

Yep, I'm Running Reaper 32 on a 64 bit system. Only way I can get Addictive Drums to show, Ed

gregerlindberg · 09-22-2009, 04:36 AM

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?

ThePulse · 09-22-2009, 08:41 AM

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.

fuseburn · 10-09-2009, 04:45 AM

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 !

Mortis · 10-20-2009, 01:05 AM

Hi @ all.

Quote:

Originally Posted by fuseburn

... 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.

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 http://www.youscreen.de/Classes.jpg <--
Just the access (1) or even the ownership (2)?

Greetz
Mortis

fuseburn · 10-22-2009, 03:21 PM

Just one single checkbox: Users need to have full access to the entire "Classes" key.
Nothing else to do, no change of ownership.
After that shell2vst should be working.

Mortis · 10-25-2009, 05:49 AM

Ok, thank you very much! That helped! Great!

drillbit · 10-29-2009, 05:43 AM

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?

Jim Roseberry · 10-29-2009, 08:32 AM

Quote:

Originally Posted by drillbit

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
www.studiocat.com
jim@studiocat.com

Cableaddict · 10-29-2009, 11:48 AM

Jim,

A few folks have suggested that running Win-64 and WOW gives no appreciable cpu hit. That in fact it may be more efficient than the same apps & plugins under XP32.

Does you experience back this up?

Jim Roseberry · 10-29-2009, 12:44 PM

Quote:

Originally Posted by Cableaddict

Jim,

A few folks have suggested that running Win-64 and WOW gives no appreciable cpu hit. That in fact it may be more efficient than the same apps & plugins under XP32.

Does you experience back this up?

Yes
32Bit apps run very well under x64...
Performance is typically just a smidge better than running them under x86.

Jim Roseberry
www.studiocat.com
jim@studiocat.com

adXok · 10-29-2009, 01:04 PM

You can use the benefits of x64 bts OS only if you:
1. Have x64-bits processor (assuming you have one)
2. Every... 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.
3. 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...
4. 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.
5. Money... of course. With money you can purchase even custom 64-bits drivers for any x64-bits OS.

yurki · 11-02-2009, 03:37 PM

Quote:

Originally Posted by fuseburn

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)

yurki · 11-03-2009, 04:49 PM

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.