How To Install Cracked Waves Bundle

Posted in: admin23/12/17Coments are closed

This domain name is for sale (100,000 USD): uploading.com Write us for more information @. Feb 10, 2015. Install Waves, run patch, copy patched files from waveshell dir to: Common Files; VST Plugins; Digidesign; VST3 and replace originals. 9.3.aaxplugin' isn't cracked (no crack for AAX files yet I guess) and I have no clue what format 'WaveShell-WPAPI_1 9.3.bundle' and 'WaveShell-DAE 9.3.dpm' are in.

Since the few latest there is something different in the installer. You have to manually copy the cracked WaveShell files to the right VST path of your PC. If you don't do that, you leave the original WaveShell files in there and those will pop up with the license message. So far I never had to install 'on purpose' the license center. Just followed the steps in the. Silent Hunter 4 Patch 1.5 Crack more. txt file (basically, picking Mercury + the few extra separate plugs).

Although different results and opinions are around, I always run the (official) waves installer twice. Bennetts Cosmetics Formulary Pdf Free. The 2nd time, it asks if you want to 'modify, repair or uninstall' the installation. I choose repair. This extra step overwrites some older cracked files sometimes that otherwise wouldn't be upgraded. Only after that I run the crack / patcher.

After running the crack / patcher, you have to copy some files to the right location (since R23 or something? Some recent release anyway, it's in the.txt file). On my x64 Windows machine, Waves installed some files in C: Program Files (x86) Waves Waveshells. The patcher cracked those files, but left them there.

You need to copy the one you want (or multiple) to the right place. WaveShell-VST 9.3.dll = 32bit VST2 plugin = (on my machine) C: Program files (x86) VstPlugins WaveShell-VST 9.3_x64.dll = 64bit VST2 plugin = (on my machine) C: Program Files VstPlugins WaveShell-VST3 9.3.vst3 = 32bit VST3 plugin = (on all PCs) C: Program Files (x86) Common Files VST3 WaveShell-VST3 9.3_x64.vst3 = 64bit VST3 plugin = (on all PCs) C: Program Files Common Files VST3 I'm assuming the 'WaveShell-AAX 9.3.aaxplugin' isn't cracked (no crack for AAX files yet I guess) and I have no clue what format 'WaveShell-WPAPI_1 9.3.bundle' and 'WaveShell-DAE 9.3.dpm' are in.

I don't need them, that's for sure. That single 'Waveshell' DLL file contains _all_ the waves plugins you have installed (this is why it is called a 'shell'). Most recent DAWs support this just fine (one dll file with multiple plugins in it). Just to add that 'WaveShell-DAE 9.3.dpm' goes to 'C: Program Files (x86) Common Files DigiDesign DAE Plug-ins' and it's a Waves waveshell for 32bit ProTools 10 and lower. Not needed for Nuendo, of course.

You don't need VST3 waveshell either for Nuendo 4.3. A common mistake that people do is they forget to replace the VST3 waveshell for newer Cubendo, they just replace the VST2 waveshell and then you get problems. You have to replace both in order for Cubendo to work with Waves properly. Maybe your VST paths are different, so it's best to open Cubendo and check the VST paths that it loads the plugins from. A VST2 path that Nuendo 4.3 creates is usually 'C: Program Files Steinberg VSTPlugins' or 'C: Program Files (x86) Steinberg VSTPlugins' on Windows 7. I still don't get why those stupid MS programmers insist on using 'Program Files' instead of just simple 'Programs'.

Bloody corporate idiots. Just to add that 'WaveShell-DAE 9.3.dpm' goes to 'C: Program Files (x86) Common Files DigiDesign DAE Plug-ins' and it's a Waves waveshell for 32bit ProTools 10 and lower. Not needed for Nuendo, of course.

You don't need VST3 waveshell either for Nuendo 4.3. A common mistake that people do is they forget to replace the VST3 waveshell for newer Cubendo, they just replace the VST2 waveshell and then you get problems. You have to replace both in order for Cubendo to work with Waves properly. Maybe your VST paths are different, so it's best to open Cubendo and check the VST paths that it loads the plugins from. A VST2 path that Nuendo 4.3 creates is usually 'C: Program Files Steinberg VSTPlugins' or 'C: Program Files (x86) Steinberg VSTPlugins' on Windows 7. I still don't get why those stupid MS programmers insist on using 'Program Files' instead of just simple 'Programs'. Bloody corporate idiots.

Can't afford the whole bundle but could possibly go a piece at a time. Besides that I have no qualms that I don't buy everything I try. There are some plug-ins in that bundle that are my go-to like the API but can't afford it right now. I put in too much time here, need to start finding some balance so I can focus on making some extra dough. So I look at it like I help people all day every day and get a little bonus sometimes by having some plug-ins that are outside of my price range at the moment. I definitely don't live with my parents though.

One thing to note is if you are running a 32bit DAW on a 64bit OS, you will still end up with a VST3 in your 64bit program files hierarchy aswell. 32bit VST2 plugin - WaveShell-VST 9.3.dll..= C: Program files (x86) VstPlugins (or wherever you installed it) 64bit VST2 plugin - WaveShell-VST 9.3_x64.dll.= C: Program Files VstPlugins (or wherever you installed it) 32bit VST3 plugin - WaveShell-VST3 9.3.vst3..= C: Program Files (x86) Common Files VST3 64bit VST3 plugin - WaveShell-VST3 9.3_x64.vst3.= C: Program Files Common Files VST3 no need to copy the whole folder either, just the right file. Don't miss any of these locations & it should work just fine.

The VST3 paths were the most confusing to me at first because you have 0 control during the installation process whether to skip or install VST3 as it automatically installs & there is no information in the logs stating that VST3 has been installed, its like ninja & the nfo mentions nothing about it. Its a bit stupid.

Click to expand.But isn't that kind of the whole point? People buy what they CAN afford, but aren't left in the dust because they don't have 10s of thousands of dollars to spend on plug-ins?? Sure companies give you months to try products out, but it's not just about TRYING for many of us. It's about LEARNING too! That's the way I've always justified it. I've spent somewhere around ~4000 grand on software over the last few years, and I don't make a dime for any of my music!!

I can't afford to pay for everything. I'm not good enough to make that kinda money (yet!). How am I supposed to get better though if I don't have the same tools to use as everyone else? That's what I understood one of the main point of warez was for! You'd obviously know best Mykal.

But that's just how I understood things around here.

Popular Articles: