Tried this — native HISE on Win ARM64 is a pain. VS ARM toolchain works if you patch JUCE and tweak CMake, but VST3s crash unless you strip x64-only intrinsics. x64 emulation on Win11 ARM is way more stable. Linux ARM / Pi is basically DIY hell for plugins, engine only.

@Sawatakashi I can't get you a far advanced response, but basically yes, you'll have to go C++ and probably a SIMD integration regarding the efficiency.

But yeah that's probably how I'd do it, not knowing if there's a better (and accessible) method.

Since a C++ node gives you access to Hise API, Juce API, and any third party library you'll want to import, Hise won't be the bottleneck.

@dannytaurus THANKS so much! I will figure it out!

@Dan-Korneff I haven't tried. The most recent I tried was Sonoma but couldn't get it to work so I'm still on Ventura.

@HISEnberg It's really nice of you.

@d-healey Thanks again, i will give it a try.

@Sawatakashi Lol not really I only set this up last week but I had similar issues.

For the first issue on Windows you have basically solved it. When you build the AAX in Visual Studio (so the one that is in HISE's SDK folder), set it to static release. Each time you build your HISE project it will build against this version and you will be good to go. There is a post about this on the forum somewhere.

When building the AAX SDK on Xcode it was a bit more trial and error for me but I think what happens is HISE is only designed to build for arm64 or Intel slice  x86_64 (depending on what you set in your Projucer). I ended up asking chat gpt for the solution to the universal binary and it gave me the right response. I found the terminal command (option 2) to be more efficient:

Option 1 – Re‑build in Xcode (GUI)

Open the project again
Libs/AAXLibrary/MacBuild/AAXLibrary.xcodeproj

Target & Build Settings

Select the AAXLibrary_libcpp target.

In Build Settings

Architectures → Standard Architectures (arm64, x86_64)
(don’t choose “arm64 only”).

Build Active Architecture Only → No (Debug and Release).

Excluded Architectures → (leave empty)

Choose a universal build destination
In the scheme selector (the drop‑down next to the ▶︎ button) pick
Any Mac (My Mac) or Any Mac (Mac Catalyst) – not “My Mac (Apple Silicon)”.
That generic destination tells Xcode to build all valid slices.

Build (⌘B)
When it finishes, run:

lipo -info "$HOME/HISE/tools/SDK/AAX/Libs/Release/libAAXLibrary_libcpp.a"

Expected output:

Architectures in the fat file: libAAXLibrary_libcpp.a are: arm64 x86_64 Option 2 – One‑liner with xcodebuild (CLI)

From Terminal inside Libs/AAXLibrary/MacBuild/:

xcodebuild -project AAXLibrary.xcodeproj \ -target AAXLibrary_libcpp \ -configuration Release \ -sdk macosx \ ARCHS="arm64 x86_64" \ BUILD_LIBRARY_FOR_DISTRIBUTION=YES \ BUILD_ACTIVE_ARCH_ONLY=NO

This explicitly asks Xcode to build both slices and drops the fat libAAXLibrary_libcpp.a in:

Libs/Release/libAAXLibrary_libcpp.a
Check it with lipo -info as above.

@Sawatakashi

You can use Engine.loadUserPreset() to load a preset, if you combine this with the on controller callback you can create the behaviour you want.

@dannytaurus 50mb, it includes whatever you put in the audio files folder. Loops usually go in the Samples folder I think.

+1, I thought this was already possible

@Christoph-Hart would this be a nightmare to implement? it's a pretty critical feature for any sort of guitar amp software (most guitarists don't want to wait for a DAW to load lol)