Problem compiling with AAX
-
@Lindon cool you've done it!
I just did on macOS yesterday and it works with no complication... Except that I didn't know the folder should be renamed "AAX", not "AAX SDK"... -
@ustk great, so just rename the folder AAX and select the xcode project - load it - build it and its done yes?
HISE Development for hire.
www.channelrobot.com -
@Lindon That worked for me ;)
-
@Lindon yay!!!!!
-
I'm just exploring AAX now. Do I understand correctly that you get the SDK for evaluation purposes only and you have to ask AVID for approval before you're allowed to release anything commercially?
They want a decent amount of info! I don't think I'd be approved given that I license everything under GNU GPL.
Your name, title and contact information
Executive summary, including brief commentary on expected mutual benefits offered by the Alliance Partner program
Schedule of proposed products for inclusion with retail pricing
Weblinks to corporate web site and related products
Overview of past experience with Avid customer base
Description of prior collaborations with Avid and participation in developer programs, where applicable
Narrative on market size and revenue potential for solutions proposed for program
Overview of your testing and customer support capabilities
Any additional data you wish to add, or questions you have for the Alliance Partner Team -
@d-healey its WAAAAY more complicated than that.
You have to sign up to Avid - yes you have to tell them everything they want.
You have to become an approved developer, then you can use the SDK to build AAX plug-ins, BUT...
they wont load in the commercial release of Pro-tools, you will need to digitally sign them (on each platform, and then get teem licensed thru PACE - you will need an iLok and you will need to sign up with them and it will take time .. are you sure you want to do this?
HISE Development for hire.
www.channelrobot.com -
@Lindon I have no desire to do any of that :p I have an iLok already, it's about 10 years old though so I don't know if that would be usable any more. I've had two customers who have bought my products only to discover they can't load them in pro-tools. So if I can supply AAX I'd like to. I can't find any information though on if I can license my plugin as GPL. I don't think I can technically for VST2 either for that matter...
-
All these questions? seriously? just all that I hate from a company... Love Pro Tools though, but avid...
-
@Lindon said in Problem compiling with AAX:
You have to become an approved developer, then you can use the SDK to build AAX plug-ins
I had questioned this directly to AVID and they directed me to some FAQ in their forum. From what I read, this is only necessary if you want to sell your product in the AVID Marketplace. I couldn't find any documentation saying otherwise to the commercial sales of your product.
do you have a link to share?Dan Korneff - Producer / Mixer / Audio Nerd
-
@dustbro said in Problem compiling with AAX:
@Lindon said in Problem compiling with AAX:
You have to become an approved developer, then you can use the SDK to build AAX plug-ins
I had questioned this directly to AVID and they directed me to some FAQ in their forum. From what I read, this is only necessary if you want to sell your product in the AVID Marketplace. I couldn't find any documentation saying otherwise to the commercial sales of your product.
do you have a link to share?For creating AAX plugins, you must be approved developer by Avid. And also they will give you a PACE license (which costs $500 annually) free and you can sign your plugins. The Avid don't want to see any un-approved developers and AAX plugins from un-approved developers. Also nobody can publish your plugins, because every plugin will have unique wrapped GUID. (Dİgitally signing plugins is different from iLok license protection)
For Avid Marketplace, afaik (1 year ago) you must pass the developer exams :) I am not kidding. When you pass the developer knowledge level exams, then you can be a partner of the Avid Marketplace. (This is not required for building and selling AAX plugins in your store)
develop Branch / XCode 13.1
macOS Monterey / M1 Max -
@orange said in Problem compiling with AAX:
@dustbro said in Problem compiling with AAX:
@Lindon said in Problem compiling with AAX:
You have to become an approved developer, then you can use the SDK to build AAX plug-ins
I had questioned this directly to AVID and they directed me to some FAQ in their forum. From what I read, this is only necessary if you want to sell your product in the AVID Marketplace. I couldn't find any documentation saying otherwise to the commercial sales of your product.
do you have a link to share?For creating AAX plugins, you must be approved developer by Avid. And also they will give you a PACE license (which costs $500 annually) free and you can sign your plugins. The Avid don't want to see any un-approved developers and AAX plugins from un-approved developers. Also nobody can publish your plugins, because every plugin will have unique wrapped GUID. (Dİgitally signing plugins is different from iLok license protection)
For Avid Marketplace, afaik (1 year ago) you must pass the developer exams :) I am not kidding. When you pass the developer knowledge level exams, then you can be a partner of the Avid Marketplace. (This is not required for building and selling AAX plugins in your store)
That's what I read too. So that part about guid would prevent me creating AAX plugins under a free license.
-
@d-healey said in Problem compiling with AAX:
@orange said in Problem compiling with AAX:
@dustbro said in Problem compiling with AAX:
@Lindon said in Problem compiling with AAX:
You have to become an approved developer, then you can use the SDK to build AAX plug-ins
I had questioned this directly to AVID and they directed me to some FAQ in their forum. From what I read, this is only necessary if you want to sell your product in the AVID Marketplace. I couldn't find any documentation saying otherwise to the commercial sales of your product.
do you have a link to share?For creating AAX plugins, you must be approved developer by Avid. And also they will give you a PACE license (which costs $500 annually) free and you can sign your plugins. The Avid don't want to see any un-approved developers and AAX plugins from un-approved developers. Also nobody can publish your plugins, because every plugin will have unique wrapped GUID. (Dİgitally signing plugins is different from iLok license protection)
For Avid Marketplace, afaik (1 year ago) you must pass the developer exams :) I am not kidding. When you pass the developer knowledge level exams, then you can be a partner of the Avid Marketplace. (This is not required for building and selling AAX plugins in your store)
That's what I read too. So that part about guid would prevent me creating AAX plugins under a free license.
You can talk this with Avid. And also the number of Pro Tools users are considerably much for a developer ;) You should think AAX ;)
-
@orange said in Problem compiling with AAX:
For creating AAX plugins, you must be approved developer by Avid. And also they will give you a PACE license (which costs $500 annually) free and you can sign your plugins. The Avid don't want to see any un-approved developers and AAX plugins from un-approved developers.
I already have that, so I guess I'm good to go? Maybe @Christoph-Hart has some insite ?
-
Yes, that's basically it. PACE doesn't cost anything to code sign AAX plugins (but you don't get iLok protection). Just signup on Avid, download the SDK, get in touch with PACE for the Eden Tools stuff, buy an iLok, and you're set.
Procedure was much more tedious in the past, now it got better. It's still bad, but once you've set it up it works.
EDIT: I wouldn't know whether a pure GPL plugin can be published on AAX since you're basically required to publish anything that was needed to build the product under the GPL license and I am sure that Avid wouldn't like that for their precious AAX thingie :)
-
I'll send Avid an email and report back.
-
This post is deleted! -
yeah, in short : Nightmare.
Still I am considering how to go about generally signing my binaries - especially the installers/packagers, to stop all that "unknown developer" stuff on both win 10 and MacOs.
Has anyone any insights on that?
As far as I have read I could join the Apple Developer Program, and use my Apple ID on MacOS to sign stuff, and apparently with some jiggery-pokery use it on windows too - but as Apple are not a recognised authority on Windows(yeah go figure..) you may as well use a recognised signing authority. Cheapest I can find is about $65.00 per year.
Any actual experiences anyone?
-
I got a very quick answer from AVID.
You are welcome to sell your products as AAX plugins independently
So that's good :)
-
-
You are welcome to sell your products as AAX plugins independently
I don't want to nag around, but that's not how it works. Avid is not in the position to "allow" selling a product based on a GPL codebase, unless they have no problem if the AAX SDK is included in the public repository (and I would be surprised if this is the case).
If one part is closed-source, then the entire thing is closed-source, and the only solution to this problem is this:
So basically, it would require me and the JUCE team to add an exception to the default GPL license.
