AAX on M1

[Dan Korneff]

@Lindon Are you talking about building the AAX Library? Or exporting from HISE?
I ditched my M1 machine, so maybe @orange can help.

[Lindon]

@Dan-Korneff well both really - I have my M1 humming along nicely - building standalones, VST and AU - but I'd like to be able to build AAX plugins - but I cant seem to get the AAX SDK to compile...or even start to compile....

I think 2.4.0 is announced as M1 compatible ....so its something I am (not) doing

[Dan Korneff]

@Lindon Looking at the AAX SDK docs, it looks like it's only compatible with Xcode 8.3.3 and Xcode 10.1
Are you using one of those?

[Lindon]

@Dan-Korneff said in AAX on M1:

@Lindon Looking at the AAX SDK docs, it looks like it's only compatible with Xcode 8.3.3 and Xcode 10.1
Are you using one of those?

Well its compiling on XCode 10.2.1 on intel.....

[Christoph Hart]

@Dan-Korneff I've just build the AAX library on my M1, and I'm currently testing the demo_project exporter. The latest SDK compiles fine on Xcode 14 (I guess they forgot to update readme file for a few years).

For now you have to change the Projucer file in the Binaries folder and add ARM as target manually, but if it works I'll change it so that AAX gets build as universal binary like the rest of the plugin formats.

Update: The compilation went through but I don't have a protools to check. I'll push a change that enables universal builds for AAX, then you can try it out for yourself.

[Lindon]

@Christoph-Hart said in AAX on M1:

@Dan-Korneff I've just build the AAX library on my M1, and I'm currently testing the demo_project exporter. The latest SDK compiles fine on Xcode 14 (I guess they forgot to update readme file for a few years).

For now you have to change the Projucer file in the Binaries folder and add ARM as target manually, but if it works I'll change it so that AAX gets build as universal binary like the rest of the plugin formats.

Update: The compilation went through but I don't have a protools to check. I'll push a change that enables universal builds for AAX, then you can try it out for yourself.

so assuming I dont want to add ARM as a target - becuase why would you if ProTools isnt M1 ready yet- and I only want to build intel AAX plugins on my M1 machine, do I need ot set any flags in the projucer?

[Christoph Hart]

@Lindon Protools will become M1 ready in a few weeks / months, so you can start building Universal binaries so you don't have to ship an update when Protools M1 is released.

I've just pushed a fix the enables ARM builds for AAX so you can now export it just like any other format.

[Dan Korneff]

@Christoph-Hart Protools has a free version you can use.
https://www.avid.com/pro-tools/whats-included-with-pro-tools-intro

[Christoph Hart]

I know I also have a Developer build available in my avid account, but I don't want to install it unless I really really have to.

The last time I installed it the Avid Manager created gigabytes of temporary cache files that ate up my free hard drive space :)

[Lindon]

@Christoph-Hart said in AAX on M1:

@Lindon Protools will become M1 ready in a few weeks / months, so you can start building Universal binaries so you don't have to ship an update when Protools M1 is released.

I've just pushed a fix the enables ARM builds for AAX so you can now export it just like any other format.

Okay yes good point -- therefore;

more details about this please?

"I've just build the AAX library on my M1, ..." I cant seem to get it to work, any quick pointers?

[Christoph Hart]

@Lindon Download the SDK from Avid, extract it in HISE/tools/SDK/AAX, Open the Xcode project in /Users/christophhart/HISE/tools/SDK/AAX/Libs/AAXLibrary then compile the Debug and Release configuration.

After this, just export your project as AAX (or now you can use All platforms as it doesn't make a separate build for AAX as before).

[Lindon]

@Christoph-Hart said in AAX on M1:

@Lindon Download the SDK from Avid, extract it in HISE/tools/SDK/AAX, Open the Xcode project in /Users/christophhart/HISE/tools/SDK/AAX/Libs/AAXLibrary then compile the Debug and Release configuration.

After this, just export your project as AAX (or now you can use All platforms as it doesn't make a separate build for AAX as before).

..hm thats what I've been trying to do... l will have another run at it - thanks.

[orange]

@Lindon said in AAX on M1:

I think 2.4.0 is announced as M1 compatible ....so its something I am (not) doing

AFAIK version 2.4.1 (which is the latest one) is Natively M1 compatible. Are you sure that 2.4.0 is M1 compatible too? I haven't built AAX on M1 yet, I've used Intel Xcode 10 for it.

[Lindon]

@orange well Im getting a ton of errors trying to build 2.4.0 on M1... let me try 2.4.1

[orange]

@Lindon Before using AAX SDK, don't forget to compile the static library on the M1 machine

[Lindon]

@orange you mean compile the SDK itself? Thats what was failing for me... but it was as you said - 2.4.0 = fail and 2.4.1 = success

[Lindon]

@Lindon right now to rebuild the latest HISE and I should be awaaaayyy,,,,

[orange]

@Lindon said in AAX on M1:

@orange you mean compile the SDK itself? Thats what was failing for me... but it was as you said - 2.4.0 = fail and 2.4.1 = success

Before compiling an AAX plugin from Hise, you need to open the below file in Xcode and build that binary. If this is what you're referring to, it's great.

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

[Lindon]

@orange yes that was failing as 2.4.0 , but works OK in 2.4.1...thanks

[Christoph Hart]

Yes I also built 2.4.1 - just the most recent one that can be downloaded as they announced a few weeks ago that the SDK is now M1 compatible.