hi, i'm having problems with some plugins that when i've installed them pt then wants to send them to the unused plugin list because they're not valid. they are indeed cracked plugins. is there a way to work around this problem ?

by the way i'm on a windows 10 64bit. pro tools 2019 legit version.

 

The majority of cracked AAX don't & won't work in legit Pro Tools. That's why the AudioUTOPiA version of PT12 exists.

 

What are those plugins? I have PT 2019 on a W 10 and PT 12 on a W 7 and every 64bit non-legit plugin that I have is working. They also work with the non-legit version of PT 12, too. A blanket statement saying that the majority of non-legit AAX do not work and would not work in legit Pro Tools is incorrect. If anything, I would say that the majority of non legit AAX do work in a legit PT.

 

I always understood it as 'modified' AAX were always rejected by legit PT...?

 

Let me rephrase my answer. You are mentioning modified, the OP is mentioning cracked. I will refer to them as non-legit. What a lot of people were having problems when it came to non legit plugins was with the Audiotopia plugins and other some patched plugins. That is the reason why I asked him which plugins were not working as there is a couple of things that can be done about that.

 

Last edited: Jul 16, 2019

They're not valid to Pro Tools because they haven't been properly signed.

 

As well as ProTools just being Pro Tools. Even with legit properly signed plugins "third party" plugins you get that message, sometimes.

 

Last edited: Jul 16, 2019

Here's an overview of the code signing procedure:
The AAX build process is depending on access to Avid, and the signing process is depending on access to PACE's tools when you create the AAX bundle you use a code signing certificate. This is in combination with PACE's Eden which in turn connects to the PACE servers during the signing process and does some magic. The code signing certificate can be self-created. There isn't much more to it.

 

well autotune 8 doesn't work, soundstoys 5, black box by plugin alliance (the one i recently installed),fabfilter, massive X. that's all i know for now. because i work with both a laptop and pc. so that what i mention is all that doesn't work on my laptop. and both my laptop and pc have the same OS. and i know by experience that they both react the same. whatever doesn't work on my laptop won't work on my pc. i'd be happy if there is a solution to this or anything i can do or try.

 

Let us do this. How about compiling a proper list of the ones that are not working. Not just the name but the full release name. Once I get the list I can double check at my end. As I said, Pro Tools is very fickle even with legit plugins. Usually the non legit ones that do not work have been patched, yet there are some that do as well as a couple of things that can be done to make some work.

 

Ok cool.

Pluginlist:
Black.Box.Analog.Design.HG-2.v1.3.Incl.Patched.and.Keygen-R2R,
FabFilter Total Bundle 2018,
this is what i have left from the autotune dont know if it's acually going to help - Auto-tune-8.1-vst3-Phucthai, Valhalla.DSP.Valhalla.VintageVerb.v1.7.1.Incl.Patched.and.Keygen-R2R,
Valhalla DSP Valhalla Plate v1.5.0.25 Win & MacOSX,
from this valhalla i copied the installation drivers name - ValhallaRoomWin_V1_5_1.

This is all i have for now. I do feel like there is some missing but i'm ok with the list right now. I also wanted to see if native instruments Guitar rig 5 worked but i'm having issues installing it because the setup don't wants to start up. but for now thats my list of non-legit not working vst.

 

Without wanting to step on anyone's toes, here is my experience...

Ive been a "legit" Pro Tools user since 1998 (old now... I know). The vast majority of r2r aax releases will say... aax (modified). And they will further state that those require AudioUTOPiA Avid Pro Tools HD v12.5.0.395 to run... and they do. That's the nature of the beast... and what makes that release so special (for now).

I work in any of the latest versions of PT, but if I want to test things out beyond "demo time" in a current version, I have to use a vst through a legit version of Blue Cat's Patchwork. Fantastic solution, but sometimes lacks a few bells and whistles to a (native) aax format within Pro Tools.

Legit Pro Tools with legit Patchwork gets me within 90% of where I want to be. I can test at my leisure... and purchase (or delete)... when I'm ready.

Maybe something has changed, and I didn't get the memo, but... PT is finicky with the aax format. I'll give it a shot after I submit this post. I'll try a release (aax) in a PT 2019.6 build and see what happens.

Anyway... that's my experience... be well.

 

Tank You alot for sharing your experience. It's much appreciated here.

Well i need to say that it sounds pretty logical indeed and eventhough it's painfull to admit i still want to maintain stubborn and believe there is a way around it. But if not i've at least given it a try and eventually need to buy these plugins earlier that i intented to.

Thanks once more and take care. I'd also liked to know what the results are of your test!!

 

Same problem here. Which are these couple of things I could try? Thank you

 

if the aax is cracked using keygen, then works 100% with legit pro tools, if you need to replace the original aax with a cracked one, then it won't work on legit PT.

 

exactly as rockhard says, any release asking you to replace the .aax or saying in the nfo that the .aax file was cracked WILL NOT WORK! Keygen releases or releases where main exe's/dll's are cracked and in turn makes hte plugins work cracked will work fine.