no such thing as 100%, but pretty sure R2R job is atleast 99.9% for me since 2019 (minus the repack, it happens). Had to re-register before but aware that it's error on my side by merging them with other group's releases and another being plugin-in USB on different port than the one I register the plugin with, or whenever the USB disconnected, I plug in straight back without clearing the cache, that will "create" a new MACHINE/DEVICE ID and will fuckup the PA license. There are releases from other group that randomize the DEVICE/MACHINE ID too in the past, can't say for sure now since I stopped using them. If the internal DEVICE/MACHINE ID randomized, all R2R PA's (and legit) release will de-register itself, everytime you use that group releases same thing will happens again, will stuck in that loop forever. The protection scheme is kinda sensitive.

Other than that, activation, new PA's plugin (released after the big bundle) by R2R needed to be done carefully. Only one pa.lic license can be used on a single device. All R2R PA plugin share one pa.lic, can't use different pa.lic for older and newer one. When you activate the new plugin, delete the old one and create a new "pa.lic" and make sure to activate all the older ones together (that, "Activate All my Plugin" option) with new one, pick the right MACHINE/DEVICE and Drive to store them too. Keep that file in a folder and don't move/delete them, then register, not the other way around. Don't overwrite "pa.lic" file too, manually delete, and generate/create a new one, it's known to create problem. Keygen is not a reliable app to rewrite file. Also make sure no DAW running (I mean no plugin with older activation running, you kinda need the DAW to active, lol) check the Task Manager too, sometimes, the DAW is closed but the "pluginscanner" still running. If you didn't properly do this, whenever you use the old plugin (that was registered with different pa.lic file at different location/drive), the new one will de-register, and vice-versa and you will stuck in another loop. It's even trickier if you're using the legit ones together, which is another story. Don't install the new FREE retail copy ever, it is the same as using the legit together.

Not to mention the other windows file signature/permission stuff for the wrapper dll to work (forgot what it is called, having to do it only once made me forgot what it is called). Check that the file signing works perfectly (also forgot how, lol). Yeah, also leftovers from previous installation, clear that shit up, every single one of them manually, check and verify.

Once I'm being careful with those mentioned above, 0 problem with having to re-register for say 2, 3 years now ? Something like that.

 

Last edited: Jun 6, 2023

So in essence, if I were to install a R2R pa plugin from say, 2021, today and created a license file for it, installing another R2R pa plugin from 2023 tomorrow would require deleting the old pa.lic file and creating a whole new one for BOTH plugins, yes?

 

Technically that's the idea, but I can't fully 100% confirm it, since all the plugins already updated earlier this year, I moved on and I don't have any 2021 installation anymore. Never been in that situation. There's a possibility the protection scheme (and cracking method) changed too since 2021, newer pa.lic might won't work for the older ones. If that's the case, you probably will have to use a different Device with different Machine ID (USB stick) to store the second pa.lic file and be mindful with the "activate all my plugin" option.

 

So even better idea;
- make certain not to mix PA releases from other groups with R2R releases
- make certain all R2R PA plugins being installed going forward are NEW (2023) updated versions
- wherever adding to your PA plugin arsenal make certain to nuke the existing pa.lic file manually and create
a new one via "activate all plugins" option

 

that's what I did, and it works for me.

also the latest (v. 2.0.1) R2R PA Wrapper Core installed. I think it needs the TEAM.R2R.Root.Certificate-R2R properly installed in your system so the antivirus won't delete the dll file. Many didn't get the installation right. Confused whether it's just for the Cubase or PA too. Shit, I totally forgot the details, only did it once, sorry. Hope someone can confirm this.

 

@Stevie
You were very helpful indeed!!!

 

Kind of moot really. It's a dick move to be running A/V on a production system in the first place. This just proves that point.