@ustk ok here is what I did:

downloaded aax-sdk-2-6-1.zip unzipped it and got aax-sdk-2-6-1 folder copied this folder to HISE/tools/SDK/ opened SDK/aax-sdk-2-6-1/Libs/AAXLibrary/MacBuild/AAXLibrary.xcodeproj in xcode ran Product>Build For/Profiling. xcode tells me this was a success... renamed aax-sdk-2-6-1. to AAX in the HISE/SDK folder opened my project in HISE ran Export>Export As Instrument and selected AAX as my target....

got this in the console window:

⚠️ ld: ignoring file '/Users/lindonparker/HISE/tools/SDK/AAX/Libs/Release/libAAXLibrary_libcpp.a[2](AAX_VDescriptionHost.o)': found architecture 'arm64', required architecture 'x86_64' Undefined symbols for architecture x86_64: "AAXStartup(IACFUnknown*)", referenced from: ❌ "AAXShutdown(IACFUnknown*)", referenced from: ❌ "AAXCanUnloadNow(IACFUnknown*)", referenced from: ❌ "AAXGetSDKVersion(unsigned long long*)", referenced from: ❌ "AAXRegisterPlugin(IACFUnknown*, IACFPluginDefinition**)", referenced from: ❌ "AAXGetClassFactory(IACFUnknown*, _acfUID const&, _acfUID const&, void**)", referenced from: ❌ "AAXRegisterComponent(IACFUnknown*, unsigned int, IACFComponentDefinition**)", referenced from: ❌ ld: symbol(s) not found for architecture x86_64 ❌ clang: error: linker command failed with exit code 1 (use -v to see invocation) [KeyEngine - AAX] Linking KeyEngine ** BUILD FAILED ** The following build commands failed: Ld /Volumes/Untitled/Nomad\ Sounds/KeyEngine/Binaries/Builds/MacOSX/build/KeyEngine.build/Release/KeyEngine\ -\ AAX.build/Objects-normal/x86_64/Binary/KeyEngine normal x86_64 (in target 'KeyEngine - AAX' from project 'KeyEngine') (1 failure) ⚠️ /Volumes/Untitled/Nomad Sounds/KeyEngine/Binaries/Builds/MacOSX/KeyEngine.xcodeproj: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.9, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'KeyEngine - All' from project 'KeyEngine')

so its something about this:

found architecture 'arm64', required architecture 'x86_64'.

for some reason its not set up to build properly on my M1 mac...

@David-Healey Please check your dms for me

@David-Healey
Looks like they are selling Plug-Ins and knives. :-)

@pratitghosh move all the xml files into the new project and then compile the DLL there

@observantsound You can use both references at the same time. Just use the one that works for the bypass, and the other for your sampler job

What I said might work, but do as @David-Healey said it's better implementation even if the reference are the same behind the scene 👍

I think you can probably do it using the MidiAutomationHandler: https://docs.hise.dev/scripting/scripting-api/midiautomationhandler/index.html

@David-Healey ok thank you

@JC Hey i actually got the moonbase module to work in juce 6..
took David's advice and messed around with Claude and got it to work.

little tricky for me but its working. I Havent shipped anything yet though--Hopefully soon.

@jeffd

So i got a notarized .pkg working of the .hr files. still need to test more but i got them into the plugin's own per-user app-data folder. Then when the plug-in opens and installs the samples it can also auto-delete the .hr files right after extracting. And no gatekeeper quarantine from macos. Ill have to do the same on pc and create .exe for the .hr files to match. but perhaps this will be best. less confusing for people i imagine?

@Oli-Ullmann Yes a vm is the way to go if you don't have a mac

@David-Healey payload is good.

Oh ok, I didn't know. I do it right now.

@David-Healey Thank you. It compiled and worked just fine.

@dannytaurus Oh nice one! 👍

@ustk very sexy!

@ulrik Thanks for clarifying that detail, I was able to export my practice projects.

@David-Healey No, because this is about persisting the file to the user's disk.

Although as I said earlier, I think the final best answer is to display the license directly in the plugin somewhere.

Then nobody could ever accuse the developer of not making the license easily available.

Website goes down - no problem
User moves the plugin to another machine - no problem
User wipes/moves/modifies their AppData folder - no problem

If the license is in the plugin itself, it can't be accidentally moved, deleted or overwritten, and it can't become unavailable because of server outage.

Probably going this route now...

@Lindon Yup that's because it needs to be thought more as "container" rather than strictly "installer". PKG or ZIP are containers so -> notarisation