@David-Healey Solved! I've simply moved the font outside the font folder and removed the "Font/".

@Christoph-Hart PR sent, I'm not being precious about it so feel free to close again, good to get the practice in 😆

@pelle There is no decompressor, so always keep your original files.

@griffinboy

Solved, it was me being silly. I checked and it was only certain projects that had the issue.
After investigation I found what I had done wrong:

#include <Windows.h>

^ I had used this line in my c++ nodes,
And it happens that Windows.h has methods with the same naming as some of the Hise files, creating a conflict.

The include was actually in a dsp file that I wasn't even using, which is how I missed it.
But when Hise goes to compile as VST it runs every c++ dsp file, and so the error flagged.

@Christoph-Hart fixed thanks!

Oh, but this style sheet should correctly assign the label selector to the outer UI component - I assume you don't use it with nested UI components? Can you make a minimal example?

Hi David, sorry for the late response, I just got my internet back up today. Just wanted to let you know the export is working perfectly now, even with that warning popping up. Thanks for the help!

@David-Healey That's what I initially suspected too. But no I haven't changed architectures.

Edit: Actually it seems to do with my authorization/licensing system, it's triggering HISE's activate system. I left the RSA.xml in the project folder so just removing it clears up the error.

Solution here: https://forum.hise.audio/topic/12825/errors-when-exporting-to-vst3/3

By the power of Claude I've added drawThumbnailMarkers and extended drawThumbnailRange to include sample start, loop crossfade, and release ranges.

This is quite a big PR in terms of number of lines of code changed. I started this before Christoph added the new workflow documentation so it hasn't been through that checking process.

Here's the PR. To pull this into your own fork:

Add Christoph's repo as a remote called upstream (if you haven't already) git remote add upstream https://github.com/christophhart/HISE.git Run git fetch upstream pull/885/merge:pr-885-merge Checkout the branch of your fork you want to merge to Run git merge pr-885

61b25f76-c83d-41ed-a69e-63e58801ad53-image.png

@Lindon Looks like the JUCE sub module was added on the 8th of January, so try end of December.

@David-Healey It compiled and builds successfully now both with App & VST. Thanks for your support have compiled it with VS 2026 didn't face file path specification error as well.

@David-Healey it worked, thanks for your help

@David-Healey said in Custom Halloween Boxes Packaging by BoxesGen:

@hiraboxesgen it's February!

..but mate, these are "high quality materials" we are talking about here.....

@Christoph-Hart

Maybe the 32GB RAM on my MacBook Air means there's enough to go around so it's not like typing through syrup.

I interact with Xcode, and now Visual Studio, as little as possible anyway. Launch, press Build keyboard shortcut, wait, quit.

@username1234 this is a thing that I vibecoded last week - it‘s super fresh but yes once that is tested a bit it will definitely be recommended as the preferred way of getting hise setup for development. Just be a bit more patient my friend.

@dezertaudio I think it will read flac, have you tested? It might not work with multi-mics and might cause issues during conversion to monolith, I'm not sure.

@dannytaurus said in What minimum Mac & Win OS are you supporting?:

Does this mean if I use VS2022/26 to export Windows VST3, I can only support Win 10.0+

I've been using VS22 since ?2022? for Rhapsody builds, so unlikely.

Regarding Debian version, you need to build on a sufficiently old version of Linux otherwise there will be library incompatibilities for users on older distros.