AAX SDK
-
@TNTHM - theres a butotn at the top right "How to Apply"
-
@Lindon That's what I was missing. Thank you!
-
@Lindon I heard rumors from a 2017 Juice forum post that you need iLoc to work with the AAX SDK. Is that true?
-
@Lindon I heard rumors from a 2017 Juice forum post that you need iLoc to work with the AAX SDK. Is that true?
- as far as I am aware no you dont. The AAX SDK is just like any other plug-in SDK - it lets you build AAX plug-ins.
Those plugins however are useless - as they will ONLY run in the developer version of ProTools - which is available to you as part of the Avid Partner program, but is NOT available to any of your customers (who would be using the commercial version of ProFools (sorry Tools) :-)
So once you've built your AAX plug-in you must work with Avid's codesigning and noterization partner - which is PACE (the iLok people). They will provide you with a set of tools to codesign and noterize your AAX plug-in so it will work on the commercial version of ProTools...
-
@TNTHM An AAX plugin has to be code-signed if you want it to work (at least, outside pro tools dev version). For that, you have to join the PACE program (it's done through avid). The PACE code-signing tool works with an iLok. This means you don't need an iLok for the plugin to launch, but you need one for code signing...
-
@ustk To reiterate, in order to build AAX plugins with hise I will need to buy an iLok fob? Is code signing a separate process from building the plugin with hise?
One of the questions on the form is:
Executive summary, including brief commentary on expected mutual benefits offered by the Alliance Partner program.
I'm not sure what this means. Could you reword this for me in simpler English by any chance?
-
@TNTHM Yes, you'll need an iLok for code signing.
Yes, code-signing as nothing to do with Hise. You build the plugin in Hise, then you code-sign it using the PACE tool. I cannot enter in the details because it's simply forbidden to do so once you have a "contract" with them. But no worries, they are cool and they will assist you.What you need to provide to Avid is anything that can prove you're "serious" about plugin development... Provide examples if you have so, website, a brief summary of what you are doing, etc... This will be asked the first time you contact them.
-
AAX plugins can't be released under the GNU GPL HISE license, so you'll need a commercial proprietary license for HISE.
-
@d-healey Ahh I wasn't aware of that. They can't be released for free under GNU GPL? Can they be built for personal use without a commercial proprietary license for Hise?
-
@TNTHM Well, if it is for personal use, you're not making money so I don't see where it can be a problem.
But AAX is not compatible with GNU GPL anyway dixit Avid. -
@ustk That makes sense.
To reiterate:
"But AAX is not compatible with GNU GPL anyway dixit Avid" means that it is not possible to build AAX plugins unless you have a commercial license for Hise to sell your plugins for profit because the developer of the AAX SDK will not issue authorization to people developing AAX plugins for free?
-
@TNTHM If you have a Hise license, then you can release a commercial or a free AAX plugin if you wish.
What you can't do is to release it under a GNU GPL license. Because in such a case, you have to provide the source code, wish is forbidden by Avid. Hence the non-compatibility between GNU GPL and AAX.
But nothing stops you to release free AAX plugins if you get a Hise commercial license. In this case, they will be in close source anyway, not open source... -
To add to what @ustk said.
The GNU GPL doesn't care if you are making commercial software or not, the only thing that matters is what the user gets when they obtain a copy of your software. If they don't get the 4 freedoms then you can't release your software under the GNU GPL, and AVID doesn't let you release the source code so that rules out freedoms 0, and 1.
-
@d-healey So if I understand correctly: GNU GPL comes into affect once the user has received a copy of your software, however what they must do to obtain the software is not explicitly stated in or protected by the license? Therefore it is legal under GNU GPL to require customers to sign up for a mailing list before obtaining a copy of my plugin. Correct?
-
Therefore it is legal under GNU GPL to require customers to sign up for a mailing list before obtaining a copy of my plugin. Correct?
I don't see why not.
