@d-healey After hours of watching YouTube tutorials, I've found a solution to link a label value to a slider, yeh, but there's just a small problem left that I can't fix. I want to round the value to 2 decimal places, which works, but sometimes I get values with more than 10 decimal places. Hmm, can you tell me what's wrong with my script?

const var Speed = Content.getComponent("Speed");
const var SpeedValue = Content.getComponent("SpeedValue");

inline function onSpeedControl(component, value)
{
local roundedValue = Math.floor(value * 100 + 0.5) / 100;
SpeedValue.set("text", roundedValue);
Console.print("Slider Value: " + roundedValue);
};

Content.getComponent("Speed").setControlCallback(onSpeedControl);

@d-healey I did it, broadcaster was the right tool!

@HISEnberg Yes, it works now
Thank you very, very much!

@HISEnberg Yes, if I compile the simple gain network with Export -> Compile DSP networks as DLL and load it into the HardcodedMasterFX, then the DSP works correctly after export.

But with my RNBO setup I lose the outport / modulation connection in Hardcoded mode, which I need for the peak meter communication.

@HISEnberg tested it with a completely simple core.gain ScriptFX network (no RNBO at all) and the same thing happens: works inside HISE, but after export the plugin passes audio through dry. So it seems the issue is not RNBO-specific but Scriptnode/ScriptFX export related on my setup (HISE 4.1 macOS).

@Oli-Ullmann no no success

@HISEnberg export as custom Cpp?

@HISEnberg Yeah, that’s the frustrating part — as a hardcoded master FX everything works perfectly, including the exported VST/AU.

But I need RNBO outports for my peak meter / UI data, and I can only access those through Script FX / Scriptnode runtime. In hardcoded mode I lose the outport communication completely.

Has anyone successfully exported an RNBO patch running inside a Script FX in HISE as a working VST3 or AU plugin?

@Oli-Ullmann already tried all of that exactly as you suggested, but unfortunately no success yet — neither as AU nor as VST3.
Current setup:
Project Type = FX Plugin
Force Stereo Output = enabled
Enable Sound Generator FX = enabled
Dry/Wet default is set to Wet
I even added an extra global bypass button for testing
The GUI works, but the audio signal just passes through unchanged in the exported plugin.
The reason I’m not using a hardcoded effect is because I need to read data back from RNBO via outports for my peak meter. That only works for me through Global Cables / Script FX. As soon as I hardcode the network, I lose the outport communication.
So currently the RNBO patch is loaded directly inside a Script FX on purpose.
Inside HISE everything works perfectly, including:
RNBO processing
Global Cable communication
Peak meter
parameter control
Only the exported plugin loses the DSP processing.

Hi everyone,
I'm having a strange issue with a exported VST3 plugin containing a Max RNBO patch inside a scriptnode network.
My Setup & What works:
Previously, I always compiled my RNBO patches successfully as a Hardcoded Master FX, and everything worked flawlessly upon export.
In my current project, I moved the RNBO patch into a Script FX (using a scriptnode workspace) because I wanted to implement a peak meter.
I successfully set up a global_cable inside the scriptnode network called peak to send the meter data back to the main UI.
Inside the HISE editor, everything works 100% perfectly: If I put a noise generator in front of it, the RNBO effect processes the audio correctly, the parameters react, and the peak meter in the UI shows the data via the global cable.
The Problem:
After exporting the project as a VST3 plugin and loading it into my DAW:
The audio signal passes through the plugin (it is not silent!).
However, the RNBO effect itself does not engage at all. The audio signal remains completely dry/unprocessed.
"Allow Compilation" is Enabled on the network. The DSP networks compiled successfully before exporting the VST3.
It seems like the exported VST3 completely bypasses or ignores the internal RNBO processing node within the Script FX wrapper, even though the audio path itself is open.
What am I missing here? Why does the compiled C++ version of the scriptnode network lose its processing inside the exported VST, while working perfectly inside HISE?
Any help or pointing me to the right forum thread would be highly appreciated!
Thanks in advance!

@Christoph-Hart said in Best practice for Real-Time Metering: How to pass dynamic peak values from RNBO to HISE UI?:

ah here you hit a real limitation - multiple modulation outputs are not supported for RNBO at the moment.

According to your screenshot the second one is just a peak hold - if you replicate this in scriptnode you should be able to get by with a single output.

Ah, ok, yes that´s a good idea, thanx