is AAX support considered ready-for-production at this moment?
has anyone already released an AAX plugin succesfully?
For what it’s worth: this is for an effect plugin with the following configuration: (in: mono or stereo audio + MIDI, out: stereo audio), with a bank of factory presets to start with, and automatable parameters.
So, if anyone is in the loop on the current status, it’d be helpful to hear about your experiences.
Thanks,
afaik AAX support is currently stable, and maybe even complete. haven’t made a release yet but we are running a beta and there are currently no issues reported from our beta testers. cheers! Yair
I’ve been shipping 32-bit AAX for a while. There was a Juce fix (right around early February) that dealt with a plugin ID issue. Since then it’s been smooth sailing. The issue that nailed us on the 64-bit stuff (the one that was resolved around 2 weeks ago) didn’t show up in 32-bit.
It’s actually pretty cool. I’ve got a tester with AAX at one site and RTAS at the other. He can easily take jobs back and forth. PT10 just loads whichever is available.
I’ve been updating my plugin code to work with the latest Juce tip changes, figuring out which debug version of Pro Tools to use, struggling with iLok issues, all that fun stuff. Today, I tried one of my plugins in AAX for the first time, and it JUST WORKS.
Thanks to Jules for his work in creating the AAX wrapper, and thanks to all the other developers that have added your AAX code to Juce!