Exported plugin fails to load (Windows ARM)
-
@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 :)
-
@d-healey Here you go, hopefully I've not missed anything haha. https://drive.google.com/file/d/1_5Vi0pO6ta6hNzu3Su4CESh2IJ4MHTnQ/view
-
@paper_lung You need to do that for your project, not for HISE.
-
@d-healey there aren't any AVX flags in the hise project settings?
-
@paper_lung You have to open the autogenerated juicer file in Projucer.
-
@d-healey Right ok, is that the autogenerated file that gets output when I compile? so I have to compile > edit the autogenerated Projucer file to remove the arch flag > recompile? Hopefully this is what I've been missing - when you mentioned Project Projucer, I thought you meant the Hise Project Projucer file, not a plugin project Projucer file.
-
@paper_lung Yeah when you select export/compile from inside HISE it will create a juicer file and start compiling it in the terminal window. Press ctrl+c in the terminal to cancel it. Then open the juicer file (from the binaries folder) inside Projucer and from there it's just like compiling HISE.
@Christoph-Hart AVX checkbox in project preferences still looks like a good idea :)
-
@d-healey Ok thanks, I'll give that a go and let you know if that's the issue (likely is!)
-
that's not worked either...
-
@paper_lung Video
-
@d-healey I'll send one over tomorrow - thanks for your help so far, appreciate it.
