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

[nouslou]

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 how to build Hise for that for Mac and for windows. Thank's

[Lindon]

@nouslou said in 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 how to build Hise for that for Mac and for windows. Thank's

The HISE you have already will build AAX plugins - first you must:

1. Download the AAX SDK (which it seems you've done)
2. Compile the AAX SDK - look for the Visual Studio or XCode project file..
3. Select AAX as a target environment for your build in HISE...

-- When you have an AAX plugin you then need to codesign it using the PACE EDEN tool set...

[nouslou]

@Lindon Thank you so much!!!

[lalalandsynth]

@Lindon " When you have an AAX plugin you then need to codesign it using the PACE EDEN tool set..."

I am using protools free, although I do also have a developer account.

Do I absolutely need the PACE EDEN for testing my aax export on a WIN machine ?
Can I bypass that requirement if I download protools via the dev account ?

If I codesign via PACE do I need an Ilok just to test plugins ?

[Lindon]

@lalalandsynth said in How to compile Hise properly before AAX export. Any Instructions?:

@Lindon " When you have an AAX plugin you then need to codesign it using the PACE EDEN tool set..."

I am using protools free, although I do also have a developer account.

Do I absolutely need the PACE EDEN for testing my aax export on a WIN machine ?
Can I bypass that requirement if I download protools via the dev account ?

If I codesign via PACE do I need an Ilok just to test plugins ?

Nope you dont need to do the EDEN stuff until you want to ship a product - testing using the Developer Version of ProTools (Not the free version) does not require EDEN signed plugins.

In order to codesign using PACE EDEN you will need an iLok anyway - to load the key to access the web site where you generate your signing code. ... but no your plugin itself is not "iLoked" when you do the codesigning - its just going to run in the commercial version of ProFools.

[lalalandsynth]

@Lindon
Ok So I installed the dev version of Protools but it asks for an Ilok , do I really need to apply for a code to run this Dev version of protools ? And do I need a physical Ilok ?

Seems weird that I can get the dev version but cannot run it ?

I have never done this before so if someone could explain the procedure, including any licensing and Ilok issues I might encounter.

@nouslou can you tell me something about the procedure ?

[DanH]

@lalalandsynth Generally you supply Avid with your iLok user account id (probably an email or username), and Avid then put the necessary licenses into your iLok account. I assume you have done this already if they gave you the dev version already. You may need to update your iLok with your new licenses, and possibly activate them in the iLok software.

Then when Pro Tools loads it checks the iLok for a license - if your iLok is plugged into your machine of course...

You might have the option to assign the licenses to your machine, you should check (means you don't need the iLok).