@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

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

@ustk Good call. Claude suggested I update to this:

UserPresetHandler.setPostCallback(function(presetFile) { // On first launch the default preset loads with no file (frontend leaves // currentlyLoadedFile empty), so getCurrentUserPresetName() is "". Fall back // to the default preset name. (Editor returns the real name, so it's unaffected.) var name = Engine.getCurrentUserPresetName(); btnShowPresetBrowser.set("text", name != "" ? name : "00 INIT"); });

I'll try it and make sure it works on first launch, and doesn't interfere with reloading DAW sessions.

It depends whether you want it to be a static connection or a dynamic modulation routing.

If static, then a control.pma node would be the best candidate - connect the UI knob to the value and the envelope output (either from an extra_mod or an inbuilt scriptnode AHDSR) to the add output, this will combine the two with unipolar modulation mode.

Scales and offsets a normalised modulation signal using a multiply-add formula with clamped output.
The PMA node (Parameter Multiply Add) scales and offsets a normalised modulation signal. It takes a 0-1 input value, multiplies it by a configurable factor, adds a constant offset, and clamps the result to the 0-1 range. This is one of the most commonly used control nodes for adjusting modulation depth, inverting signals, or combining parameters.

Each parameter change triggers an independent output update. If Value, Multiply, and Add all change in sequence, three separate output values are sent to connected targets.

@HISEnberg @Christoph-Hart I hit a problem with controlling a ScriptNode macro with a UI knob AND an envelope.

New post here: https://forum.hise.audio/topic/14793/control-scriptnode-from-ui-knob-and-envelope

@dannytaurus Thanks for sharing this! If anyone has questions about the data going into this, or suggestions for the next survey, please let us know! :)

@David-Healey cool cool
I did make just a licensing system with traditional serial keys...so Ill probably just use that for now, and then update.
and I finally actually fininshed making this instrument😁

now just working on some vids and demos and final testing. but ill include some screenshots here.
Its just a sample based synth, where i sampled the f-k out of a LYRA 8 synthesizer..
recorded through some amps and speaker cab impulse responses etc.
Screenshot 2026-05-29 at 2.41.06 PM.png Screenshot 2026-05-29 at 2.41.18 PM.png

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?

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

The OOG would recommend not a hidden slider but a LAF that paint the three buttons on a linear slider in vertical mode. Or a scriptPanel if you dont want the drag between values behaviour.

I never use the radio group for non UI, saveInPreset components for this very reason.

@Bart Wow, that interface is wild! 😮 😂

The synth I'm building is the start of a series, so I'm designing a layout that will work with all of them. Each one will have a couple of unique controls, so they all look slightly different but obviously from the same family.

@dannytaurus I'm using Scriptnode. This issue was reported earlier here https://forum.hise.audio/topic/10321/scriptnode-synth-smoothes-transients

@Christoph-Hart said in How to control Flex AHDSR Decay time with Velocity?:

@HISEnberg I've added a few customization options to the mouse behaviour for HISE tables last month, this should all be doable.

Well as long (as Dave say) it loops in the sustain potion and thats where the multiple segments are then we get "kontakt like" MSEGs,,,

@David-Healey said in Code feedback on this custom envelope panel:

For paint routines and mouse callbacks I'm not sure it makes a difference since the paint routine or mouse callback is still a regular function.

Yes but the way I understand it (might be wrong though) is that it's faster to execute even if the outside part isn't inlined. The inline part containing locals, the code execution inside it seems faster especially for long paint routines or mouseCB. Then what happens after this isn't affected but at least the script part might be improved.

@dannytaurus Just my experience, in my case if the device is still on then closing and reopening Hise keeps the connection working. But it's lost when I switching the device off and starting hise again. (haven't tested the PR yet)