AAX SDK - compiled

[Lindon]

• hang on , dont worry - turned out to be a lot easier than I remembered... ignore me. "I'm being Stupid" (c) 2022

[lalalandsynth]

@Lindon I wouldnt mind you could upload yours ;)

[Lindon]

@lalalandsynth as I say its easy enough to build.

[lalalandsynth]

@Lindon ok, will do

[Lindon]

@lalalandsynth said in AAX SDK - compiled:

@Lindon ok, will do

check the instructions I gave in the other current AAX thread - where you posted recently...

How to compile Hise properly before AAX export. Any Instructions?

Hi! How to compile Hise properly before AAX export? Any Instructions? I downloaded AAX sdk and I have all tools for signing AAX plugins, but can't understand...

Forum (forum.hise.audio)

[DanH]

@lalalandsynth I've just been through it all for the first time, let me know if you need help, it's reasonably fresh in my mind

[Lindon]

@DanH said in AAX SDK - compiled:

@lalalandsynth I've just been through it all for the first time, let me know if you need help, it's reasonably fresh in my mind

I for one can never remember where in the PACE web site I'm supposed to go to generate the id, if you recall then I'd find that useful to document.

[DanH]

@Lindon yeah I haven't got that far yet, waiting on Avid to send me the Pace signing toolkit, but no replies to two emails so far...

[lalalandsynth]

@DanH After building the sdk , what do I do with it ? Where do I place it?
Anything I need to be aware before building the sdk ?

[orange]

@lalalandsynth

Before compiling an AAX plugin from Hise, you need to open the below file in Xcode and build that binary. For Windows, you need to repeat the process for the Windows build. After compiling, you don't need to do anything, now you can compile the AAX plugin.

/SDK/AAX/Libs/AAXLibrary/MacBuild/AAXLibrary.xcodeproj

After compiling AAX, then you'll need to sign the plugin with EDEN tools.

[lalalandsynth]

@orange This is what I built.
Dont I have to then bring the built sdk into the HISE SDK folder ? That is what I did, before that it said that the SDK was missing.

SO now I have the AAXSDK in the SDK folder but get errors on build. I had to rename the AAXLibrary to AAX to get hise to see it.

In my case I have a dev version of protools so I do not need to sign them.

[orange]

@lalalandsynth

[lalalandsynth]

@orange I see, so I build the SDK then copy the whole folder including the SDK into the HISE SDK folder ? Correct ?

[lalalandsynth]

@orange Fixed the "use IPP" issue.
Now getting this error.

Following this, looks similar.
https://forum.hise.audio/topic/901/aax-compile-error-develop-branch/3?_=1673020664965

WORKS ! :)

[DanH]

@lalalandsynth I got this too. You need to rebuild the AAX library but this time with MT Static release instead of whatever the other option is. You change this setting in the project settings (I'm not at my windows machine right now)... I can't remember exactly where it is now, config / compile perhaps. Its a few options down the list.

I found a stackoverflow thread which pointed me in the general direction - I can't find it now. Search the error in google.

Wish I could help more but literally running out the door. Good luck!

(Or wait until tomorrow and I can show you exactly what to do!)

[lalalandsynth]

@DanH I figured it out and am now building aax , thanks for the help.
We now have a working AAX plugin with CC output !

[lalalandsynth]

@orange The signing with pace eden tools , can you elaborate on that a bit ? Do all AAX plugins have to be signed by that or is that only if you plan on using Pace ?

I am assuming you can buy a license from Pace and then do your copy protection via Pace ?
And also assuming that you can just use your own copy protection and not use Pace at all ?

Can someone explain the process to me as I have no experience with protools or pace?

[Lindon]

@lalalandsynth nope.

All AAX plugins - whether they use PACE protection or not - must be signed with the PACE EDEN tool kit. If they are not signed they will not run in ProTools commercial products.

The PACE EDEN tool kit is codesigning ONLY - it offers no protection, and is required by Avid. Your copy protection is up to you.

[orange]

@lalalandsynth

If you want to release an AAX plugin, you have to code sign it with Pace EDEN Tools. This code signing procedure is not for copy protection of your software, this is only for your plugin to run in Pro Tools.

If you only use Pace for code signing your plugins, you don't need to buy a Pace license. If you register to Avid as a developer (you need to contact them), they will assign a Pace EDEN Tools license (for signing purpose only) for you for free. But if you want extra copy protection from Pace, then you'll need to buy extra license for this, that is a different story.

So, for releasing AAX plugins, follow the instructions below:

• First, get an iLok USB.
• After getting your iLok, contact to Avid, tell about your company and register your company as a developer. And they will assign a Pace Eden Tools license to your iLok, so you won't have to pay $500 per year for signing your AAX plugin.
• Then code sign your plugin with using your iLok & EDEN Tools.
• After code signing, test your AAX plugin in a non-developer Pro Tools version. You can download free version of Pro Tools that also supports 3rd party plugins from here: https://www.avid.com/pro-tools/intro

[lalalandsynth]

@orange I already have a dev account and I am running a dev version of Protools.
Currently my PACE license to run the DEV PT version is on the cloud.
Should I now have access to these EDEN tools or do I still need to apply for them specifically ?