I'm pretty sure HISE has shown up at some point on Audioz.net with a rapidshare download link. Fun times back then, no looming AI apocalypse, just good ol' copyright theft by script kiddies.

@pelle said in MacOS Parallels WIN build fail:

HISE generates 40 pop up windows

Can you make a screen recording?

@elemen8t
Please take a look on the scripting suggested above. Thanks

@griffinboy Yes, I am aware of that. But the question is: Is HISE using an internal sample rate, which is different from the host sample rate? It could use an internal sample rate, while still doing all the things you mentioned.
Maybe my question is mostly for @Christoph-Hart :-)
Or I should actually go and read the C++ code!

Might take a look at this now but I think it would be nice to have an option to draw the label on obj.clicked rather than auto appearing on hover. There is no .clicked option in getModulatorDragData currently, and my effort to implement one with Claude code hit a wall.

EDIT - Seemed to have got the clicked behaviour I wanted by drawing it .clicked in drawModulationDragBackground instead :). However, the issue of the label appearing when I don't want it to means that if I click in the label's area the label appears.

EDIT 2 - I've got it so the label won't appear on click but if the mouse is in the label zone it still activates the hover laf for the dragger, so there's no real workaround here. I think the dragger and label need to be decoupled. Everything I'm doing is pretty hacky....

@DanH said in Matrix Modulation System - Last Call for bugs fixes & changes!!:

@Christoph-Hart so with the singleDragger method the dragger knob's label will appear on hover when hovering in it's location, rather than the label only appearing when hovering over the dragger itself. I've drawn the label well away from the dragger in the example below but you can see the label appear on mouse hover:

ScreenRecording2026-01-16at10.37.46-ezgif.com-video-to-gif-converter.gif

@dannytaurus Correct

@duma I think something might have not gone correctly when you brought in the PR to your fork.

@NISHI_MUSIC I'm not 100% sure what you mean, could you give more detail?

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

@Christoph-Hart Style rules to follow strictly:

Tabs for indentation Allman braces 120 character line limit PascalCase for classes camelCase for methods. ???

@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