@DanH
Ha ha 😂 Good question! 🙂

I'm building a fairly extensive synth plug-in. It has 4 layers, each with 4 sound engines. Each layer has 4 insert and 4 send effects, a master effects section, 4 arpeggiators, and a main page.
Since I'm using the new HISE modulation system, each parameter really needs its own UI element, which is why there are so many.

@cassettedeath You can find a lot of brand vector logos on Wikimedia Commons:

https://commons.wikimedia.org/wiki/File:Cubase_6_logo.svg

CleanShot 2026-02-20 at 09.34.48@2x.png

You don't usually need permission to use the logos but you do sometimes need to attribute them and follow the brand's guidelines.

A blanket statement should be good: "DAW logos are trademarks of their respective owners." as long as you don't imply any sort of affiliation or link with the company.

Safest way is to just use text, no logos, like:

"VST3/AU/AAX versions. Works with Logic Pro, Ableton Live, Cubase, Reaper, Bitwig."

@DanH Got a snippet?

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