@Oli-Ullmann The --force flag overwrites any existing signature.

@David-Healey ill try it

@David-Healey payload is good.

Oh ok, I didn't know. I do it right now.

@David-Healey Thank you. It compiled and worked just fine.

@David-Healey Well so an SDK downgrade would be the best thing to test, at least to see if the process is the good one

@dannytaurus Oh nice one! 👍

@ustk very sexy!

@ulrik Thanks for clarifying that detail, I was able to export my practice projects.

@David-Healey No, because this is about persisting the file to the user's disk.

Although as I said earlier, I think the final best answer is to display the license directly in the plugin somewhere.

Then nobody could ever accuse the developer of not making the license easily available.

Website goes down - no problem
User moves the plugin to another machine - no problem
User wipes/moves/modifies their AppData folder - no problem

If the license is in the plugin itself, it can't be accidentally moved, deleted or overwritten, and it can't become unavailable because of server outage.

Probably going this route now...

@Lindon Yup that's because it needs to be thought more as "container" rather than strictly "installer". PKG or ZIP are containers so -> notarisation

@Lindon Yes you spotted both of the main issues:

JuceHeader collision. Previous versions used #include "../Binaries/JuceLibraryCode/JuceHeader.h" which was fine for the DLL, but exporting to VST3/AU caused the JuceHeaders (project info like companyName, versionString, etc.) to be pulled in twice. Solution is just to use #include <JuceHeader>

.cpp.inc is resolved on all Fx to just .cpp (it was a leftover from the batch compile I ran).

A handful of effects couldn't be compiled together — some of the amp/saturation nodes (the ones based on a shared __Gain_H template) and a few of the k-reverbs. Individually they were fine, but combining them caused build errors. It came down to a couple of effects accidentally reusing the same internal names behind the scenes, so they stepped on each other once everything compiled together. That's now sorted out, and the full set compiles as one.

The repo is up-to-date now and should be more stable.

@David-Healey Looks great! I kid ye not, I'm noodling on my website redesign now and used very similar colours and layout!

Total coincidence! 😂

CleanShot 2026-06-18 at 19.05.42@2x.png

CleanShot 2026-06-18 at 19.05.32@2x.png

@lijas90 Thanks!

4 over 4, that's enough stats for me 😎

I thought at one point the "full mod range representation" has been made available so it covers the full range of lastModValue (like in the above post)

Was I dreaming?

modvalue.gif

@David-Healey I added a dragThumbOnly property to Scriptslider

if enabled:

A left-click on the slider track no longer starts a drag or jumps the value.
HiSlider::mouseDown hit-tests the click against the drawn handle centre
and only forwards to Slider::mouseDown when the click lands on the
thumb (within dragThumbSize/2 + dragThumbPad). Right-clicks still pass
through for MIDI-learn / context menu. Snap-to-mouse is disabled, so dragging the thumb is relative and the
value does not snap to the cursor on click.

if anyone is interested it's on my fork
https://github.com/morphoice/HISE/commit/7b206d1951558381a2a38b2691a504d7542eec56

however the dimensions are currently hardcoded to my needs, so there will be further changes needed to make this a general feature. I therefor didn't make a PR

@David-Healey Thank you, kind sir.

@VybeCodeDSP StripKit looks really nice!

It seems you only support the Windows platform?
If so, are you planning to support MacOS?
If so, let me know if you need a beta tester!