So i got the new r2r patch + keygen release for 9r25. VST patch works fine, and I decided to use the license patcher for the AXX module (protools), because all the AAX plugins that i have used keygens for have worked fine and authorized, but for some reason, I generate a license, waves ceneter finds the license for hte complete package, but pro tools is telling me when i lpoad that waves cannot find any licenses? It's showing up right in the waves license center teh generated license. Anyone have issues with hte license generator? Is it not working correctly?

Every license generator/keygen i have used for other aax plugins have worked flawlessly, something must be going wrong

 

have you tried the 9r24 licence gen?

 

It's not a true keygen. Waves plugins have an embedded cert and inside that cert is a 1024 bit RSA public key. They have simply replaced this with an ASN editor with their own public key and signed the license file using their own public/private key pair. This means the AAX plugins have been altered which means they don't checksum correctly when loaded into PT.

 

As you said in your first few words, it is a patch. The R2r waves thing modifies the plugins, and (as you all _should_ now) you can't modify AAX files, they will never work, it has to be a clean unmodified keygen to let AAX work.

Please note, that from Waves r23 and up Waves changed their protection system which requires different things in the r2r releases / patches. So if releases _before_ r23 worked, that says nothing about anything after it.. waves caught up.
The VST 2/3 stuff still work ok (and I guess AudioUnit).

 

Question regarding the r2r (dada) recent waves releases (r22-r26). The info always say "Bad Protections, just annoy the users. Bad Watermarks, just leak personal info when it is stolen".

Does that mean that these cracked waves releases cannot watermark your audio (as many suspected before) with personal info of the original buyer?

Hope someone knows the answer for this!
Thank you.