@JulesV which files are you copying into the Juce folder?

@David-Healey Ah yes I've got it. So encode to .hxi > export HR1, then I need to use installExpansionFromPackage that's accessible from a button or something in the UI that'll unpack the HXI and samples. thanks!

Hi all, I'm currently exploring expansions (never really explored it before) and I'm a little confused on HXI files and how they should work. In the docs when describing HXI, it mentions: 'the entire expansion is included in one file which makes it much more convenient to distribute.'

So, after encoding an expansion, do I then only ship the .hxi file? After encoding one of my expansions into an HXI, it's incredibly small (only a few kilobytes) so I'm not sure if I'm missing something or misunderstanding the above statement from the docs.

@paper_lung Hmm I've just re-compiled both hise and the plugin and it's worked this time, so I'm going to keep testing to see if this now works

@d-healey here's where I'm removing arch in the autogenerated Projucer. then I build solution in visual studio as normal. https://drive.google.com/file/d/1yqu2D1OLFPgXUt_V6JVTu_aAY5-MEqnz/view?usp=sharing

@d-healey I'll send one over tomorrow - thanks for your help so far, appreciate it.

that's not worked either...

@d-healey Ok thanks, I'll give that a go and let you know if that's the issue (likely is!)

@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.

@d-healey there aren't any AVX flags in the hise project settings?

@d-healey Here you go, hopefully I've not missed anything haha. https://drive.google.com/file/d/1_5Vi0pO6ta6hNzu3Su4CESh2IJ4MHTnQ/view

@d-healey Thanks - with AVX fails, without AVX loads correctly.

@d-healey Sure, thanks - here you go:
https://drive.google.com/file/d/1Nt0bmdkOrACbGAjoOLA8xDJ4RtPXmNBe/view?usp=sharing

Just tried exporting again and it compiled, it still fails on ARM though

@d-healey yes to all of those

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?

@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?

@d-healey No, I'll give that a try tomorrow

@d-healey yeah, then build solution as normal

@bendurso they used to - I have a few plugins from last year which worked no problem