This thread:
https://forum.hise.audio/topic/9788/hise-filter-display-inconsistencies/20?_=1750768491529

And Claude, helped quite a bit. Got it working!

The essential bits I'm calling in my c++ node are:

void setExternalData(const ExternalData& d, int index) override { SNEX_INIT_FILTER(d, index); } // HISE calls this (message thread, on repaint) for each frequency point. // freqNorm is normalised to the sample rate (1.0 == fs); return linear gain. double getPlotValue(int /*getMagnitude*/, double freqNorm) override { return (double) magnitudeLinear((float)(freqNorm * fs)); } // == Parameters ========================================================== template <int P> void setParameter(double v) { if constexpr (P == 0) { pFreq = (float)v; sendCoefficientUpdateMessage(); } else if constexpr (P == 1) { pReso = (float)v; sendCoefficientUpdateMessage(); } else if constexpr (P == 2) { pGain = (float)v; sendCoefficientUpdateMessage(); } else if constexpr (P == 3) { pDrive = (float)v; sendCoefficientUpdateMessage(); } else if constexpr (P == 4) { pType = (float)v; sendCoefficientUpdateMessage(); } else if constexpr (P == 5) { pMode = (float)v; sendCoefficientUpdateMessage(); } }

@David-Healey What errors do you mean?

@David-Healey Of course! Silly me.....

@justinfitzmusic have you added a velocity modulator to the Gain of the Sampler?

@David-Healey so there's no way my server could be faster, especially since it is actually very slow...

@David-Healey yeah that seems more comprehensive, its more or less doing under the hood what Im doing in HISEScript... so both approaches have the advantage of getting a result back for the plugin itself (no matter how the user has set up to run it..)

Thanks for looking and confirming what I'd found.

@dannytaurus It working soo fine, I had to put engine.loadaudiofilesintopool earlier

@ustk Thanks for your hard work!

@Orvillain ill give that a try thanks. I don't have claude code though. I cant afford paid services at the moment

Very cool man!

@David-Healey It was already default to 500 mb in 4.1

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.

I'm not sure whether MIDI tempo information messages makes it through to the Faust node, but the tempo sync node is definitely the way to go. just build your Faust node with a absolute delay time parameter and then connect it to the tempo sync node - it automatically sends the correct time value matching the tempo and reacts to tempo changes etc.

upcoming docs:

Tempo Sync (control.tempo_sync)

Converts a musical tempo value to a duration in milliseconds and sends it as a modulation signal.
Tempo Sync converts a musical time value (such as 1/4 note or 1/8 triplet) to a duration in milliseconds based on the current DAW tempo. The output updates whenever the host tempo changes or any parameter is adjusted, making it suitable for driving time-based effects that need to lock to the beat.

The output is an unnormalised modulation signal carrying the raw millisecond value. If the target parameter expects a different unit (such as frequency in Hz), place a control.converter between this node and the target. When Enabled is set to Off, the node outputs the manual UnsyncedTime value instead, allowing a smooth fallback for standalone operation or manual control.

CPU: negligible, polyphonic.

Signal Path

Pseudo-code - hover highlighted terms for details // control.tempo_sync - musical time to milliseconds // BPM + parameters -> ms out (unnormalised) onParameterChange() { if Enabled: output = tempoToMs(bpm, Tempo) * Multiplier else: output = UnsyncedTime } onTempoChange(newBpm) { bpm = newBpm if Enabled: output = tempoToMs(bpm, Tempo) * Multiplier }

@Orvillain Nice work

@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

@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

@David-Healey There might be a bad parsing at some point. Without really knowing, the hex might be first parsed as string by the property editor...

@Lurch Not sure if it affects compiling networks

@Christoph-Hart I can breathe again....and move much faster now lol