Releasing AAX plugin - no response from Avid. Tips?

General JUCE discussion
1

I have my plugin built and running with VST3 and AU, and now want to release the AAX plugin publicly.

I have followed the advice at AAX SDK to request the developer tools and license, but I have received zero response in over 2 weeks.

Does anybody have experience with this, or advice on how to get things moving?

Anyone got through to Avid recently? (Pro Tools Developer / AAX signing)
2

I also recall the process being a struggle and emails going nowhere. I think my solution was to start contacting Avid through other channels (like tech support) and finally somebody was able to forward me to somebody who delt with this stuff.

I always get the strong feeling that Avid don’t actually want people to develop AAX plugins because the system is that bad. I had issues with getting the Developer build of Pro Tools to run and their response was “oh yeah, sometimes it just doesn’t work, sorry”

Excuse the little rant, but I’m just letting you know this isn’t uncommon and it’s a problem with Avid, not you.

2 Likes
3

Thanks, I’ve actually started customer support now too for the same reason!

I’m amazed too at how hard they make it…

4

it took about 5 days to get my stuff, it seemed like it was an automated system, so it may be backlogged. but once you get it you shouldn’t need to contact them again for anything.

1 Like
5

Same here, went all smooth for me, but was ages ago, so YMMV.
Which email did you use? Try devauth@…

1 Like
6

Thanks @PluginDev97 and @daniel

It seems the email given at AAX SDK is incorrect! (audiosdk@avid.com)
I tried re-sending to devauth@avid.com and got an automated response straight away, mentioning a 5-day reply time. So it looks like I’m on track.

I’ll try and get them to correct their own documentation.

7

I also got confused last time (two years ago) when requesting this. The actual useful info is at the end of JUCE/README.md at master · juce-framework/JUCE · GitHub . Here is the exact instruction from the README (so I would assume this part is not under the NDA). I followed it and got reponse in about 2~3 days (though there still several steps after that). Good luck to you!

AAX Plug-Ins

AAX plug-ins need to be digitally signed using PACE Anti-Piracy’s signing tools
before they will run in commercially available versions of Pro Tools. These
tools are provided free of charge by Avid. Before obtaining the signing tools,
you will need to use a special build of Pro Tools, called Pro Tools Developer,
to test your unsigned plug-ins. The steps to obtain Pro Tools Developer are:

  1. Sign up as an AAX Developer here.
  2. Request a Pro Tools Developer Bundle activation code by sending an email to
    devauth@avid.com.
  3. Download the latest Pro Tools Developer build from your Avid Developer
    account.

When your plug-ins have been tested and debugged in Pro Tools Developer, and you
are ready to digitally sign them, please send an email to
audiosdk@avid.com with the subject “PACE Eden
Signing Tools Request”. You need to include an overview of each plug-in along
with a screen recording showing the plug-in running in Pro Tools Developer, with
audio if possible.

Please also include the following information:

  • Company name
  • Admin full name
  • Telephone number

Once the request is submitted, PACE Anti-Piracy will contact you directly with
information about signing your plug-ins. When the plug-ins have been signed, you
are free to sell and distribute them. If you are interested in selling your
plug-ins on the Avid Marketplace, please send an email to
audiosdk@avid.com.

1 Like
8

Thanks for this @zsliu98, it’s really helpful.

One question: when it comes to signing the plugins, do I have to use a physical iLok usb device, or is the iLok cloud service available? As a solo developer I’m trying to be as economical as possible and wondering if the iLok cloud service is actually affordable.

9

I use the physical device, a bit painful though … And I would guess the affordability of iLok cloud would be under a NDA :innocent:

1 Like
10

Hello @danryu,

Did you ever receive a response from Avid? I’m currently facing the same issue, so I’d really appreciate hearing whether you were able to get everything sorted out.

Thank you

11

Hi @fabimora12

A day after the automated response, I received a full email from Avid with the Pro Tools Developer NFR Bundle Activation Code and a list of instructions. I’m now testing with Pro Tools and waiting to receive the iLok hardware key.

I have not yet started the next process: send an email to audiosdk@avid.com with the subject “PACE Eden Signing Tools Request”.
I am going to follow the JUCE instructions for this stage within the next week.