AAX on M1

[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.

[Lindon]

@Christoph-Hart damn it now its telling me..

AAX SDK is missing

so not working...

[Lindon]

@Lindon heres the contents of my SDK folder:

-- the other(well VST3) builds are working...

[orange]

@Lindon

[Lindon]

@orange ok let me try the rename...

[Lindon]

@orange - yep that was it - my you've been my hero today mate - thanks.

[Lindon]

@Lindon damn it again - spoke too soon now I'm getting these errors:

❌  error: unable to create directory '/Library/Application Support/Avid/Audio/Plug-Ins/Grand Piano Suite.aaxplugin/Contents/Resources' (in target 'Grand Piano Suite - AAX' from project 'Grand Piano Suite')



❌  error: unable to create directory '/Library/Application Support/Avid/Audio/Plug-Ins/Grand Piano Suite.aaxplugin/Contents/MacOS' (in target 'Grand Piano Suite - AAX' from project 'Grand Piano Suite')



❌  error: unable to create directory '/Library/Application Support/Avid/Audio/Plug-Ins/Grand Piano Suite.aaxplugin' (in target 'Grand Piano Suite - AAX' from project 'Grand Piano Suite')



❌  error: unable to create directory '/Library/Application Support/Avid/Audio/Plug-Ins/Grand Piano Suite.aaxplugin/Contents' (in target 'Grand Piano Suite - AAX' from project 'Grand Piano Suite')

[orange]

@Lindon Have you installed Pro Tools on your computer? Pro Tools creates this folder automatically. You can create that folder manually, but in the end you'll need a Pro Tools to open the plugin anyway.

/Library/Application Support/Avid/Audio/Plug-Ins/

As @Dan-Korneff sugegsted, you can use this free Pro Tools version which supports 3rd party plugins:
https://www.avid.com/pro-tools/whats-included-with-pro-tools-intro

[Lindon]

@orange said in AAX on M1:

@Lindon Have you installed Pro Tools on your computer? Pro Tools creates this folder automatically. You can create that folder manually, but in the end you'll need a Pro Tools to open the plugin anyway.

/Library/Application Support/Avid/Audio/Plug-Ins/

As @Dan-Korneff sugegsted, you can use this free Pro Tools version which supports 3rd party plugins:
https://www.avid.com/pro-tools/whats-included-with-pro-tools-intro

nope I'm like @Christoph-Hart trying hard not to install ProTools at the moment...

[orange]

@Lindon Then you'll have to create it yourself manually. The compiled plugin will be created in that folder.

But I'd install PT first.

[Lindon]

@Lindon -yep eventually...this worked. For those arriving here with the same problem

• creating this:
  Macintosh HD/users/yourname/Library/Application Support/Avid/Audio/Plug-Ins

does NOT work, it has to be the one at the system level:

Macintosh HD/Library/Application Support/Avid/Audio/Plug-Ins

[optimistic]

Just want to chime in and say I was able to build and get running an arm64 AAX plugin first try. Not what I was expecting but very much appreciated. Thanks to everyone for the great information shared here.

[Matt_SF]

I stumbled upon this one after having reset my mac. Since I've installed ProTools beforehand, the folder @Lindon was talking about was already there, but I was still facing the unable to create directory error.

I used the

chmod 777 Macintosh\ HD/Library/Application\ Support/Avid/Audio/Plug-Ins

command to grant this folder writing permissions and it solved the issue.

I'm leaving this here in case someone stumbles upon this one too.