Alright I was able to get my plugin signed and Wrapped in AAX! This was a heck of a process but Im here to do what @Lindon said to me in this topic here: https://forum.hise.audio/topic/8151/help-with-aax-willing-to-pay/12 and "pay it forward"....I did share all this in that particular post. But I figured I'd do this as a separate new post so when someone is searching for AAX and how to codesign their plugin they will find this post directly and not have to sift through 100 other threads like I did....
These bullet notes are process as @Lindon laid out in the pervious post.. But I'll expound on these points as much as I can without compromising the confidentiality of the PACE agreement:
- Join the Avid Developer Program:
You'll need to follow the instructions here: https://www.avid.com/alliance-partner-program/how-to-apply
You'll need to do this even if you don't want to sell on the Avid Marketplace. Im not planning to at all
- When you're in download the Developer version of ProTools (so you cant test your unsigned AAX plugins):
Once your in you'll see a section in your Avid account for Developers like this:
This is where you'll be able to download the PT Dev Version/the Current AAX SDKs you'll need to export your project with.
- Email your Avid representative telling them you want to use the PACE EDEN tool kit:
It was a runaround to find this email but the official email to email is firstname.lastname@example.org
- When they send you and email for a pace person email them asking for the tool kit:
They will verify you as an Avid Dev and then you'll need to tell them that you need a license for PT Developer. You CAN'T run PT Dev without a license...it DOES NOT work even if you are already a PT Studio or Ultimate subscriber. They will connect you with the department to give you this and they will tell you the criteria for how to submit to them verification of your unsigned plugin running in PT Developer. Once you do this then they will connect you with the PACE person.
- Sign and return the NDA they send you:
This will be apart of the earlier step of signing up as a Dev.
- Install the license they send you onto your USB iLok:
You're gonna need a physical ilok to do this so pick one up if you don't have one...you can do it through ilok cloud...but it's going to cost $$$$...your gonna need this heavy for every step past this! They will email you all of the steps needed to access the PACE Central site and how to get the license on your iLok.
- Read the silly amount of documentation!
It really is a silly amount...probably about 80 or so pages. But everything you need is in there...it is a literal step by step walk though on how to sign the plugin. This is the part that is Confidential and covered under the NDA so I can't speak about the step by step. But I will say that it is a very detailed walkthrough and you'll be good if you follow the instructions to a "T" ...I didn't have to read through the full 80+ pages because not all of it is relative to signing. But I had to take my time and walk through each step. Took me a couple of hours, results may vary depending on how fast you read/are competent with implementing the steps...I took my time
- Use the iLok License to get to the web site:
As stated before you'll need a physical iLok to access the Pace site...there's no other way in
but once in there are explicit instructions on what to do. As long as you read everything you won't get lost.
- Generate your signing code:
Again I won't spoil too much of the process but you do need to be fairly comfortable with the command line/Terminal on Mac. The process was actually pretty simple cause they give you explicit instructions on how to do this in the manual. But I got into a tough spot cause I'm not as good with the command line...I did however email the support team at PACE and they were VERY responsive in helping me fix the issues in my terminal commands...so if you get stuck just email them and they will get you out of the mud!
- Sign your plugin with the pace EDEN tool kit and your signing code:
The biggest problem I ran into was the signing certificate...I tried my darnedest for about a day to get a Self-signed Certificate running and I kept failing...So I broke down and just bought the Dev account from Apple for $100...generated an official signing certificate from them and that worked. If you've got more ninja skills than me you probably can make the self-sign work...I didn't have the patience to keep banging my head...paid solution just worked...I did however get stuck one more time with it right at the LAST step because there were some permission issues with the Apple certificates. This is a common issue but the people at PACE support sent me to this forum:
And I literally just went down the page trying everything that people reported as "this worked for me" until it finally "Worked for me also" I can't tell you exactly which process worked...and It may have actually been combination of trying multiple solutions. But after that the signing process literally took 10 seconds and my signed plugin opened perfectly in the official version of PT Studio. No Issues! Hope this helps someone and saves them the 8-months it took me to figure all this out!