@d-healey said in Problem compiling with AAX:

So that's good

Yeah indeed

For 3D GUI stuff; I use Cinema 4D (with Octane Renderer) + After Effects (with Sheetah - Spritesheet Tools) + Photoshop & Illustrator. Sometimes not Sheetah, WavesFactory StripGenerator instead.

For Vectoral GUI stuff: Hise has cool features for it.

@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

@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)

@dustbro Yeah you are right.

My version: AAX SDK 2.3.1

@Lindon hmm, it looks something different.

@Lindon I wrote it above, again:

64 bit: SDK KIT\AAX\Libs\Release\AAXLibrary_x64.lib
32 bit (if you use): SDK KIT\AAX\Libs\Release\AAXLibrary.lib

@Lindon The aim for compiling the source file is .lib files. Are you sure it is not located different folder? If you compile it, it should be there.

@Lindon Just compile the solution file and don't change anything, leave the files in the AAX SDK folder.

So the files should be like this:

64 bit: SDK KIT\AAX\Libs\Release\AAXLibrary_x64.lib
32 bit (if you use): SDK KIT\AAX\Libs\Release\AAXLibrary.lib

While building AAX plugins, Hise will use this files that are already in SDK folder. After compiling your plugin, you need to digitally sign the compiled plugin in order to use it in Pro Tools. If you have Pro Tools Developer License, you can preview your plugins without signing. But for normal Pro Tools versions, you must sign.

For that, just contact the Avid, all of the AAX plugin information is in the Avid's NDA

@Lindon
You need to create .lib files on your own using the AAX SDK Solution file for Mac and Windows separately.