so some plugins don't work within legit pro tools because their authorisation happens within the plugin whereas with other plugins, because the authorisation happens outside of pro tools, you actually can use cracked ones with a legit pro tools.

does anyone have a rough list or idea of which cracked plugins do work in a legit pro tools?

so far i've found these work:
waves
t-racks 5
baby audio
i think klevgrand works too?
revoice pro
denise audio stuff

anyone know anything else?

 

Any plugin which is registered with a serial number will work with Pro Tools. When a cracked plugin has its binary modified (i.e. the AAX file itself), Pro Tools will identify the mod and render it useless.

 

it doesn't matter how the plugin is authorized. the problem is that pro tools checks the integrity of the plugins and if they have been changed, pro tools ignores them. this means that none of the cracked/patched plugins can work with legal pro tools.

only pirated versions registered with a keygen / serial number or a license file can work with legal pro tools.

plugins that receive authorization information from other applications or libraries responsible for authorizing products can also work with legal pro tools. since cracking/patching of these applications/libraries does not modify plugins, and pro tools only checks the integrity of plugins, this allows plugins to be used with legal pro tools.

 

Some plugins are using custom wrapper like Izotope and Waves or Celemony Melodyne.

If such plugins wrapper doesn't check auth, it means that they are suppoosed not to be modified, so Pro Tools could load Waves and Izotope but Not Celemony Melodyne.

Other plugins with only key or without DRM, can pass PACE's AAX check.
E.g melda,overloud,etc.
The vast majority of problems occur in asymmetric encryption (RSA).

If the cracker can indeed factor the RSA private key, there are many ways to refuse home-calling, but the problem is that RSA-512 and higher-strength encryption cannot be processed at present, and it must be replaced with the public key generated by the cracker in the program flow.
Except for the leaked private keys like Overloud.

 

i appreciate the input guys, but i was more so just curious if anyone else knew of any other plugins that worked in pro tools aside from the ones i mentioned

 

- drumforge mixing plugins ("df" series) - don't requires any authorisation and sharing as original retail installers (unmodified plugins)
- audiority plugins that were relased with license files (unmodified plugins)
- hornet plugins (only unmodified purchased watermarked and shared retail products)

 

thanks man, really appreciate it

any more that people know would be great too!

 

Hi , do You have a better list ?
I succed with Waves, baby audio....
I maybe will have to buy fabfilter

 

if you are interested
i would suggest to write a small script with a scraper to download all nfos for example from upawg and then check the nfos for the words "untoched" or whatever is usually mentioned....
if you have no idea where to start just check youtube...

 

if it doesn't loaded aax natively, you can always use blue cat patch work to load the cracked vst version.

 

@plastictrees
sharing is caring!

So since you may be overwhelmed. I took time and wrote two small scripts with python in just 30min.

The first script is scraping all links to the NFOs of R2R:

Code:

from bs4 import BeautifulSoup
import pandas as pd
import os
import requests

page_no=1
links_ls=[]

while page_no < 486: #THIS IS NOT FUTUREPROOF (WITH NEW RELEASES MORE PAGES WILL BE ADDED)

    url = f'https://upawg.ca/index.php?Search=R2R&Page='+ str(page_no)
 
    page = requests.get(url)
    soup = BeautifulSoup(page.content, 'html.parser')
    table = soup.find('table',attrs={'class':'borderstyle'})
    rows = table.find_all('a')


    for links in rows:
        if 'href' in links.attrs:
            links_ls.append('https://upawg.ca/'+str(links.attrs['href']))
    
    print(page_no)
    page_no +=1

df = pd.DataFrame({'Links': links_ls})
df.to_csv(os.environ["HOMEPATH"] +r'\Desktop\upawk_links.csv', mode='a')
print('finished')

The second script checks if there is "AAX(MOD" in the string.
So every time it is specified that the AAX is modified the script detects it:

Code:

from bs4 import BeautifulSoup
import pandas as pd
import os
import requests
df1=pd.read_csv(os.environ["HOMEPATH"] +r'\Desktop\upawk_links.csv')
x=0
df1=df1.iloc[0:9699,1]
modified_ls=[]

while x!=9698: #THIS IS NOT FUTUREPROOF (NEW RELEASES WILL BE ADDED)
 
    url = str(df1.iloc[x])
    page = requests.get(url)
    soup = BeautifulSoup(page.content, 'html.parser')
    table = soup.find('pre')
    a=soup.select_one('pre:contains("AAX(MOD")')

    if a != None:
        modified_ls.append("Modified")
    else:
        modified_ls.append("Not_Modified")
    print(x)
    x+=1

df2 = pd.DataFrame({'Modified?': modified_ls})

df=pd.concat([df1, df2], axis=1)
df.to_csv(os.environ["HOMEPATH"] +r'\Desktop\upawk_links_result.csv', mode='a')

There is certainly need for optimization. I have not looked at whether R2R indicates if it is unmodified. If yes, you could add an extra case to check that. That way you would have less false positives for sure. I haven't checked the result, but surely there are some false positives (when it is not indicated that the AAX is modified or in case it is a library). But my scripts should be a good starting point.

My script is still running with all the releases R2R has made. As soon as it is ready I can upload the csv file.

UPDATE:
After about 2080 requests, upawg has blocked me for a short time. So, I recommend to add a timeout. Therefore I will not post a csv!

 

Last edited: Sep 22, 2021

i never got fabfilter to work

holy shit man, that's a ton of effort. i'll definitely try it out. the only thing is that sometimes the crack might not specify whether or not the aax is modified or not. i think @mercurysoto is right in saying that generally plugins that are authorised with a manager that isn't ilok and not within the plugin itself, the cracked version should work with pro tools

 

was not too much work. As far as I know R2R writes in their NFO which protection the plugin actually uses, so you can also search for that!