@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 said in Couple of handy (free) Mac apps for checking code signs and notarisation:

@Oli-Ullmann said in Couple of handy (free) Mac apps for checking code signs and notarisation:

That's interesting—so you have to notarize your plug-in files, too? I just signed mine and haven't received any reports of problems from my beta testers so far. However, my installer is also notarized and stapled.

You notarize the installer (or zip file) and staple it and that also attached the notarization ticket to the plugins.

I notarize the plugins too, but Im not using any sort of installer - so Im notarizing the zip they are in...

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

@Oli-Ullmann Ok,

Thank you 🙏

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

@paper_lung Check this thread: https://forum.hise.audio/topic/5499/audiowaveform-laf

@dannytaurus Yeah, keeping the colours tidy in your code is easier in the end. Then you can set the component colours from script when needed and everything updates automatically if you adjust something instead of copy/paste in all components...

I tend to to everything I can in paint routines, the less components in the tree, the happier I am!
That being said... In order to reduce CPU load, I still tend to keep fixed drawing (bg, mask, etc...) in separate panels so the LAF function job is only constrained to what is really necessary. I also keep all the math constants externally, unlike the example...

Other issue with the "multiple panel masking technique" is that when you want to move it, it can be very annoying, unless adding them all in an holder panel, which is one more component... 😬

@Felix-W Break it down. Make a minimal project with one sampler where notes only trigger during legato transitions. Once you get that working you can start to incorporate it into your project.

@David-Healey Ok,

Is it possible to discuss in private?

@dannytaurus said in Stop pruning default values from XML?:

because I'm setting some values in script that happen to be default values.

Hmm this might be the source of an issue I was having too, I might try it.

@dannytaurus Good job detective!
I agree to the WTF, seems that developing new protocols of all sorts but there's still no agreement whatsoever in the way DAWs handle such a simple task... Shame...

@dannytaurus said in Anyone doing factory presets only, with no Save button?:

power-user feature

It for sure is a power-move and not as intuitive as a user preset.

@zachhealy1005 said in Linux:

so compiling hise on my laptop is in fact impossible.

If you reduce the number of compile threads to 1 or 2 it might still compile.
make CONFIG=Release -j 2