Exported plugin fails to load (Windows ARM)
-
Just to reiterate, the plugins load fine on my Windows PC. It's only on my virtual machine on my Arm Mac where they instantly fail/don't load after this commit (the commit itself is fine, it's the ones after)
-
This is where stuff begins to break for me: https://github.com/christophhart/HISE/commit/d7b5a121a825bf9a3fb6153d5e81d3f6a5242420
-
@paper_lung Ah ok so it is the AVX commit that breaks, sorry I thought it was the other one.
Ok can you make a video showing the export process where you disable AVX so I can follow the exact steps?
-
@d-healey All I'm doing is removing the /arch:AVX flag in the Projucer extra compiler flags. Everything else I'm leaving as-is, but I have also tried changing the 'Use IPP Library' from 'Use Static Library' to 'no'.
-
Plugins exported with Hise don't work on Windows ARM, as far as I know. Only on x64. Or am I wrong?
-
@bendurso they used to - I have a few plugins from last year which worked no problem
-
@paper_lung said in Exported plugin fails to load (Windows ARM):
All I'm doing is removing the /arch:AVX flag in the Projucer extra compiler flags
So you remove that. Then you click save and open in IDE? Is that right?
-
@d-healey yeah, then build solution as normal
-
@paper_lung Ok so we can rule out AVX being the issue, and you've disabled IPP so that's not the problem either.
Free HISE Bootcamp Full Course for beginners.
YouTube Channel - Public HISE tutorials
My Patreon - HISE tutorials -
@paper_lung Have you tried an empty test project?
-
@d-healey No, I'll give that a try tomorrow
-
@d-healey I've tried compiling an empty test project but it's just exporting a 'shared code' folder, any idea why that would happen?
-
I also thought I'd throw one of my broken VST3 files into chatgpt to see if it can detect anything. Here's what it says (obviously to be taken with a pinch of salt):
Architecture: x64 (Machine = 0x8664)
️
VST3 entry: The binary contains GetPluginFactory️
Runtime linkage: No MSVC CRT DLLs are imported → looks statically linked (/MT)️
Side libs: No IPP/OpenMP/FFTW/etc. DLLs imported️
AVX/VEX footprint: The code section shows a high density of VEX prefixes (0xC4/0xC5), which strongly indicates AVX/AVX2 instructions are present.
I've disabled AVX via the Projucer like I've mentioned, and seeing as Hise commits previous to the AVX implementation compile working VST3's, I wonder if something is amiss with AVX?
-
@paper_lung said in Exported plugin fails to load (Windows ARM):
@d-healey I've tried compiling an empty test project but it's just exporting a 'shared code' folder, any idea why that would happen?
Did you save the xml? Did you set the plugin name/code and all the other usual project settings?
-
@d-healey yes to all of those
-
@paper_lung Can you send me the project and I'll try compiling it on my Windows VM, then you can test if it loads on your ARM system?
-
@d-healey Sure, thanks - here you go:
https://drive.google.com/file/d/1Nt0bmdkOrACbGAjoOLA8xDJ4RtPXmNBe/view?usp=sharingJust tried exporting again and it compiled, it still fails on ARM though
-
@paper_lung I've created standalone and VSTi with and without AVX.
-
@d-healey Thanks - with AVX fails, without AVX loads correctly.
-
@paper_lung said in Exported plugin fails to load (Windows ARM):
without AVX loads correctly.
So the question is what did you do different to me when you disabled AVX?
Time to make that video I asked for :)
