@David-Healey Haha yeah, guilty as charged — Grok helped polish the post a bit since English isn't my first language, but the questions are all mine :)

Thanks for the update! So the AVX stuff got removed in a recent commit — that's awesome news. Does that mean exported plugins from the latest master now load fine on Windows ARM (real hardware or VM)? Or are there still issues?

Anyone tested the newest build on Snapdragon X / Win11 ARM? Would love to hear if native compilation is closer now too (or Linux ARM/Pi side).

Appreciate the heads-up!

Hey folks,

I'm curious about Windows ARM support (Snapdragon X stuff, Surface Pro X on Win11 ARM, that kind of thing).

I saw the thread about exported plugins failing to load on Windows ARM (the one from last October that's still going), and it sounds like most recent builds are x64-only and just crash or don't load at all on ARM hardware/VMs

Has anyone actually managed to:

• Compile HISE itself natively on Windows ARM64? (like with VS ARM toolchain)
• Export plugins that are native ARM64 .vst3 / .dll (not just x64 emulated)?
• Or even get reliable x64 emulation working with newer HISE versions?

If you have, what did you do? Like:

• Any special Projucer settings, CMake flags, or build tweaks?
• Which HISE commit/version worked best? (someone mentioned a specific commit from last year in that thread)
• Any custom changes to the project templates or JUCE?

Bonus question: What about Linux on ARM setups like Raspberry Pi 4/5 (aarch64)? Has anyone compiled HISE there or exported actual plugins? (There's an old 2017 thread about Pi ideas, and some mentions of RockPro64 compiling HISE, but nothing recent on plugin export/loading.) Same questions apply — flags, disabling stuff, or is it just not feasible yet?

I'm mostly building on x64 Windows right now, but I'd love to target ARM devices properly if possible (Windows or Linux). Native ARM64 would be awesome for portable stuff, but even a solid emulation workaround would be great.

If you've got it running (even if it's hacky), screenshots of your setup or a quick step-by-step would be super useful!

Thanks a bunch — really appreciate any real-world experience here :)

I'm working on a “high-end” guitar processing plugin and I need to implement an EQ Match function to allow users to capture a reference tone.

Since HISE doesn't have a native "EQ Match" module, I'm considering the following approach:

Using FFT to analyze both the "Source" and "Reference" signals.

Calculating the magnitude difference to generate a compensation curve.

Applying that curve via a high-resolution FIR filter or a series of peak filters.

Does the current Scriptnode API support efficient buffer handling for this kind of FFT analysis? Or is it mandatory to write a custom C++ node for the matching logic?

If anyone has experience with FFT-based DSP in HISE, I’d love to hear your thoughts on the best workflow to achieve a "finished product" sound without killing the CPU.

Best regards,

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

Hello,

is there any way in HISE to make some ComboBox items act as non-selectable category headers (e.g. display "hh" and "we" as bold/separator items that cannot be chosen)?

I would like to group IR files by subfolders without flattening everything.

Any examples, snippets or forum threads that show how to do this would be very appreciated!

Thanks in advance!

HiseSnippet 1268.3ocuW0saiSDEdbSMr0.R6h1aQZHW4.sgjzz1EspPa9iMr8mnjrKf.T0D6IMC0dFK6wcazpJwk7LwU7NvKBuAvYFamX2lcopB1bQZlyuey4b72wcPnvgFEIBQFVimGPQFen4n4b4r1yHLNpeGjwCLYgXG+InVyCHQQTWjgQouQo0Xi0Q5O+0W2h3Q3NzkhPnWJXNziX9L4RoCN34LOudDW5XleNqadPeGAusvSDCHojYMT.w4Bx4zSHJyVyD8LRzLjwmY53Now1tMcZzj9kaSm17I6UuwdSq2Xm8Z1fraylfN5d6RZfLduttLoHbjjHoQHi0aIbmOZl3U7jD7RVDahGUcnNZDj4Dw8DdtpqnRJp8Llm6frRTDBhxfkErRIErGadLyksP9xB2C0JvK8HeAzXshvqTA3UOO7pkCdq.RF4fz5IP5QlibBYAxkZT34CL6ykzvoDnOkGJI1hV62KY1V.VvkU8IWP6EBGV3g8N0psItYsZUdpkkEzrhj3KIgXeRDXQ+gCoWRCmf2GqmdpdNUdXrKSLh3G3QWfC6xEsu7MhFKLBBwOVdqsvi5dT21iw8Gh2Zqx+7SwVVSEgXaBlwwDUn6w7nQUrrvvG1TPSUF2kd0oSsKyB+hxUve593spWAqM305uw3z+fSvNkGOfHmAojTMJdRjLjwO+1A5ywauIXgG.89YZpVtBf8rnA3tZPbzL6rPlp6Zqqye8fmhf6y93rxLTkZK7CDb3fcYsVUEQ+ipQTPFSR8iJuoNA+hfwsK+SbclsrXbOFmhmFycjLAGK3Z+TwNT3Y6jE3MgT6ESqXkTCVTuzRweEtdkBUnb0HOgCwCGQ8nNRpaZkZQbUnuO.uwzqj14pEV2NLD29CsyGmaYdV0BtXKt8o2j1DOuI.afcwK3JqAooZJLZnSSxcVG7hCdp3qFfrK+5ACO8agIsy5c5Qc5N7ZUKG53Yg.9Y4puhbopubctZ8IBI8TtsJCa.MY7MUMc5J0kBdOZ3JUqXECeaNZyi8mPCy0S0FBO4WjNw7MSmjmsyIYPLmgBdeNSdZ.k+l3.QoSuJpmTTAlJ0DOOLk3AlpmHZItBw.Fl22T22PZHujy+wGfdQ+NDIIKPPLg7DPCkL0UvnC8RXCRBi1FlcnQWHEAZaSm.AN96PZuZQJ+0dGLeY9O4.8CWHiMMuAciU8F0aYsydssN73A3C0e2BOZ7gseNxm.wyzvTuM6VDu.kuvM1iHKtGPssLUAzMKP9pHX4QL477aS+Oa4vcEhOxb.S5La0XbsUfQnm8+AFSWo9QlcmNEHKVBv0M688uC1e9wY4GlGuT3EqKEI8vh7GEvRmv4Eeene3O9NprnHD5H.nbmB0v99AwdQzin7ykyxO.jBo97fXYd4uHh1BnBOOTDycGOKjRbyGuAgTWpGoPNdFqctX7a+4AcfUxvZt71zq23zGyVJB3+Rd4qOwbETjpmPTzhHe0kzzP4R5iFnGhPdBQ.zYBkY5TB5xcyzaT5N28p+1GdFJflD+7iIvtaU5OI1eD7RjNTX1gyodJtPi0TrVImqkgnQTtq9veCeRUVWc1HUY8LkuSxgOwITblSBepZr7AZIv8lq6BaXdr5Lt9MoQg5N7Vlm43TLT2xwF2WG2995Xy6qi6becb26qi6cec7I+6Np9m.NLVJ7SHVQniGzUu1yvnKm.S4ZNDz+.zW7o5.

@iamlamprey Awesome! Could you please update the libraries in "src" folder? I can't open the project without those libraries. So sad

Hey everyone, I’ve noticed that a lot of plugins online don’t seem to support the latest macOS version. I haven’t updated yet, so I’m wondering if anyone here has upgraded and successfully tested whether HISE-exported plugins work? Both VST and AU formats.

@HISEnberg Hi, finally I've gotten back to you now. Thanks so much!

1. I don't know if I need to change something inside the HISE or JUCE project first.
   After testing it again, I found that I got some errors about "MD_DynamicRelease" issues as I exported the AAX directly from HISE. So I re-exported it by opening the autogenerated project from Juce. I fixed from "MD_DynamicRelease" to "MT_StaticRelease" in Visual Studio 2022. Then it seemed to build successfully. Now the Pro Tools DEV detected the plugin.

But I wonder if there's a way I can directly export AAX from HISE.

2. When I do it on my MacBook, I find I meet the other problem. (AAX SDK 2.4.1, HISE 4.1.0, M4, Xcode 16.1, sequoia)
   I can only compile the ARM version for the AAX plugin in Xcode, which warned me I could not compile the universal AAX for both Intel and ARM MAC.

Big thanks again, I believe that you must have experience with it.

@HISEnberg It's really nice of you.

@d-healey thanks a lot, I will watch it tomorrow!

@d-healey yes, this is for the user to load their IRS instead of right click the convolution "waveform".

Hi everyone. I dont know how to add a load button for convolution reverb to load custom IRs. could you help me?
thanks a lot!

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

@d-healey so i need to recompile HISE so i can directly export as the Universal Binary AU plugin from HISE. Am I right? Thanks so much!

@HISEnberg Thanks Mate! Do you use the Hise 4.1.0 on Windows? I'm sure I'm having a hardtime compiling an AAX plugin, including getting it signed.

Hi Everyone.
I'm currently using an M4 Macbook to compile an AU plugin for the ARM version.
Since I don't have access to an Intel Mac, I'm wondering if I need to recompile the Intel Mac version of the AU plugin in Hise.
Any advice would be greatly appreciated!