AAX SDK - compiled
-
-
@orange I see, so I build the SDK then copy the whole folder including the SDK into the HISE SDK folder ? Correct ?
-
@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?_=1673020664965WORKS ! :)
-
@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!)
-
@DanH I figured it out and am now building aax , thanks for the help.
We now have a working AAX plugin with CC output ! -
@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?
-
@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.
-
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
-
@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 ? -
@lalalandsynth I was told to apply to a specific email address for the eden tool set. Sent two emails last week. Haven't heard back...
-
@lalalandsynth EDEN Tools license has to be assigned to your iLok. If you've already been registered as developer to Avid, contact Pace for EDEN Tools license with an email that also CC'd to Avid too.
-
@lalalandsynth said in AAX SDK - compiled:
@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 ?Once you have an Avid developer account there should be an Avid employee contacting you, ask him/her for the email address of the PACE person you need to contact.
Once you have the email contact PACE, telling them you are an Avid Developer Program member and they will send you an NDA to sign. Sign it and return it and they will send you the EDEN tool kit.
This tool kit is only any use to you if you have a signing ID (that's not its name but I cant remember what its actually called), so once you have the tool kit you need to go generate IDs for each of your plugins.
You do this on a PACE web site. But you cant access the PACE web site without the relevant license downloaded into your iLok. So you need to get your license into your iLok, how to do this should be in the (copious) documentation Avid and PACE send you.
So to sign your plugin you will need:
- The PACE EDEN tool kit
- a unique ID for each plugin
-
@Lindon Thanks, this is very helpful.
I wonder how you guys deal with multiple developers on a single product? Does each dev need their own Dev account and EDEN toolkit on an Ilok or is there a way to share this stuff ? -
This post is deleted! -
@lalalandsynth said in AAX SDK - compiled:
@Lindon Thanks, this is very helpful.
I wonder how you guys deal with multiple developers on a single product? Does each dev need their own Dev account and EDEN toolkit on an Ilok or is there a way to share this stuff ?one of you takes the lead and does the iLok work?
-
@Lindon Yes, I am doing that part, I guess one of us has to make do with using the dev pt to test and one has to do the pace signing work :)
-
@lalalandsynth said in AAX SDK - compiled:
@Lindon Yes, I am doing that part, I guess one of us has to make do with using the dev pt to test and one has to do the pace signing work :)
if you are both on the program you can both do the PT testing.
-
@lalalandsynth said in AAX SDK - compiled:
@Lindon Yes, I am doing that part, I guess one of us has to make do with using the dev pt to test and one has to do the pace signing work :)
For the free Pro Tools Intro, each person has his own account, no need to use iLok for this, so everybody can test the plugin separately (of course that version requires code signing :) )
-
@Lindon Indeed :)
