Exported plugin fails to load (Windows ARM)
-
@d-healey INot yet, but there's literally hundreds of commits since my last plugin exports which worked successfully. Do you know of any recent commits which may have affected Windows Arm plugins? I can't see anything other than the AVX changes, but I've disabled AVX anyway.
-
@paper_lung said in Exported plugin fails to load (Windows ARM):
but there's literally hundreds of commits
You don't need to test them all.
Go back 6 months, test a commit from then, if it works then you jump forward 3 months, try a commit, if that doesn't work you go back 1.5 months, etc. You can quickly narrow down which commit caused the issue.
It's a Binary Search: https://en.wikipedia.org/wiki/Binary_search
-
@d-healey Ok thanks for the tip. I'll have to give this another try next week.
-
@d-healey This commit is the last that exports a working windows VST3 on my virtual machine for me: https://github.com/christophhart/HISE/commit/b31195dcc43d84b17cd5de80ae3575a5c5e0c65e
There seems to be a lot of commits for IPP and adding the AVX flag immediately after this commit, so I wonder if something has happened there? None of my plugins that export after this commit work on my VM and instantly fail pluginval
-
@paper_lung Do all your projects use scriptnode?
-
@d-healey No they don't
-
@paper_lung That commit looks like it should only affect scriptnode stuff.
-
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?
