Mad love on this post man, for real, I didn't come here to be mr big shot or anything like that, the Warez community has supported me just as I have supported them. There was a point in time when I was directing people to warez sites to download my records ya dig? Hell, you can find my whole labels discography on multiple torrents, and I am all for it. I'm not a greedy dude by any means, I am just someone chasing their dreams like so many of us are, so I thought it was horseshit when dude came at me like that without knowing jack SHIT. Anyway, thanks for the love my dude I appreciate it!

 

I totally get where to put them my dude, that is why this situation is fucking with me, prior to the incident in my OG post I had never had one problem except for the "networking" issue (network card) which figured out on my own. I really hate to even bother the people on this board, but because I know how to properly do it, and it isn't working, I didn't know what else to do lol. I wish there was a way I could like broadcast it so ya'll can watch me and correct me as needed.

 

Hell yeah my dude keep that shit up! Maybe sometime we can switch some stems off or something and kill a mix!

 

What an07her said, make sure that the license file you generate with the R2R keygen gets placed in ProgramData\Waves Audio\Licenses.That one even confuses me at times when I'm tired, even though it's quite trivial to do it. It's also one of the most important steps, aside from copying the patched Waveshell dlls to your VST folders.

That could definitely also be a problem here. Waves put their *unpatched* waveshell dlls into your VST folders, both x86 and x64, so you have to *overwrite* their unpatched waveshell dlls with the patched ones from Program Files (x86)\Waves\Waveshells.

So if your VST folders reside in Program Files\VSTPlugins and Program Files (x86)\VSTPlugins make sure that the Waveshell dlls there get overwritten with the patched ones. You have to do it manually, no way around it.

Adrianus Antonius you have some kind of a problem with this mate? :/ Maybe you should let the adults talk in peace.

 

Last edited: Jan 23, 2016

I

He

Hello awesome people I have returned from my slumber! Ok. Real quick, I know for SURE i am putting the license in the right directory no doubt 10000000 percent %. Now here is where you confused me kind of, ok, so say my default VST directory is : Z:/sick/vstplugins (32)/
and then for x64 it was : Z:/sick/svstplugins (64)/ now... when i install waves by default the PATCHES go to the C: yaada yadda correct? So when install is done I copy and paste them from the C: to the Z: thereby replacing the legit plugs with the patched plugs. I just wanna makse sure conceptually I have it correct as to where the patches are instaled and go from there. Also one more thought, could this issue I am having (since you said my log file looked just fine) have anything to do with the fact that I wam 100% offline on that system? I have a network card so the mac address DOES pop up, but is there a chance sometthing else is going on that would require me to BE online or anything? Just a curiosity, process of elimination.
Z:/sick/vstplugins (32)
Z:/sick/vstplugins (32)

 

The default installation for the waveshells (the one you don't want, from waves) is C/\program files\steinberg and c:\prg files\common\vst3. You have to over write these (if it is the place your DAW scans for vst, it often is by default, it always is for vst3, that's why I told you in my post earlier so if you don't use these folders in your daw as a location for your vst you should supress the waves vst in it, because sometimes some DAWS always scan these folders and if you still have the unpatched shells there, waves tells you during scanning that you have no licence on your computer) with the patched wave shells which are in the folder C/\Program Files(x86)\Waves\ (the default installation folder for waves where the R2R patch puts the patched wavesshell)

 

What you say about the default Waveshells location Talmi is true, but interestingly, when I install Waves Complete unpatched Waveshells always end up in both [normal and (x86)] Program Files\VSTPlugins somehow. Possibly because one of the first things I do on a freshly installed system is make new "VSTPlugins" folders in both Program Files. Maybe Waves installation scans both Program Files folders for VSTPlugins folders and install the Waveshells there if it finds them.

 

Actually you're probably right, by default the vst's either go in the steinberg folder or the vstplugins folder (sometimes they even create a vstplugins folder inside the steinberg folder ! to make things easier !)...I'm not sure which one it is for waves since I don't keep any vst in this folder. Sicktanic should definitly check all of them.
When I installe new vsts I always check all of these folders and if there are vst's dlls I either overwrite them, paste them to my vst folder which is elsewhere or delete them if I don't use them, it depends on the patch/crack method (or if I own the plugs)...When I started using and installing vst's, I was really confused by that, then you get use to it. Some companies like iZotope copy their vsts all over the place (same with FXPansion), some put them where you tell them, it's all weird.

 

From what you're saying it sounds like you're moving them from the default VST folder locations in "C" over to your "Z" drive. If that is what you've been doing it is incorrect and not in line with the instructions I referred you to. After you run the v9r27 and v9r24 patches the patched Waveshells are inside this folder.. C:\Program Files (x86)\Waves\Waveshells. You only need to copy the Waveshells you need to use from this folder. One pair of Waveshells is equal to the whole collection of plugins. For example, if you use a 64bit DAW and want the VST2 version of the bundle you'd need to copy (WaveShell-VST 9.3_x64.dll and WaveShell-VST 9.61_x64.dll) and paste them in the VST folder on your "Z" drive. And this is important: The Waveshells that install by default to VST folders on your "C" drive are not patched at all during the patching process. And since you don't use the VST locations they are in they don't need to be overwritten with the patched ones, or moved.. they need to be "deleted" from all these folders..

C:\Program Files (x86)\VstPlugins
C:\Program Files (x86)\Common Files\VST3
C:\Program Files (x86)\Common Files\Digidesign\DAE\Plug-Ins

C:\Program Files\VstPlugins
C:\Program Files\Common Files\VST3
C:\Program Files\Common Files\Avid\Audio\Plug-Ins

 

Last edited: Jan 24, 2016

Bashing/off topic rant from any member in this/any thread will be banned & left with a warning from this/all thread. First & final Warning!!! Cmon guys, It's love baby, ColeTrain
Thank you for understanding

 

Hey everyone! Please excuse my belatedness on a status update, I was playing catch up and doing the old man thing the last 2 days, but guess what, thanks to Daz my issue is SOLVED! I still don't know where I was going wrong, but I followed his video step by step and BOOM! I'm good to go! BUT! I appreciate EVERYONE who took time out to try and help me, so to all of you who gave suggestions I am offering a free leased instrumental off my website, or a free engineering consultation or actual mixing job to say thanks. All of you are great stand up people forreal and I will deff be a regular on this board, so thank you for your help! Throw me a DM if you are interested in claiming any of my offers! Much love and respect to all you kick ass people!

 

No problem! My pleasure. I'm glad you've solved the problem.

 

Happy it all worked out for you Sictanick
Words ... don't come easy to me, but a picture paints a thousand words.....Cheers guys

 

Last edited by a moderator: Jan 26, 2016