@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

@voxuer1 I hope one last question,

I successfully compiled my RNBO node with two outports (both using @tag mod).

In Scriptnode, I still only see one modulation target field. Right-clicking the icon also doesn't show the second port.

Any idea how to access both outputs? (See screenshots)

@Christoph-Hart yes that´s it Thanx!

@Christoph-Hart Hi Christoph,

Thanks a lot for the quick response and the info!

That explains it—I'll check out the outport with the @tag mod and I think I can take it from here.

Cheers!

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

yes global_cable is the best way, mod output => global_cable in scriptnode, then register the callback with AsyncNotification, then it's automatically polled and just updated when the value changes.

Hi Christoph,

I'm following your advice regarding the global_cable and AsyncNotification, but I'm stuck at the very first step: getting any kind of value to show up in HISE.

I have tried every possible connection method in RNBO to send my peak-meter data (conditioned to 0.0 - 1.0) to HISE, but none of them seem to work:

Audio Outputs (out~ 3 / out~ 4): I set CompileChannelAmount to 4 and used "Wrap into chain", but the RNBO node in Scriptnode remains strictly Stereo (2 pins). No additional pins appear to connect to a core.peak.

The outport Object: I used the outport object, which is specifically designed in RNBO to send messages to the host. However, HISE doesn't seem to create a corresponding "mod output" or pin for it.

Standard Outputs (out 3): Tried the non-signal outputs as well. No luck.

Parameters (param): The parameter appears in the list, but it is static. It doesn't reflect real-time changes from the internal RNBO signal, so the global_cable gets no update.

It feels like the RNBO-exported nodes are "isolated" from HISE's modulation system. No matter what I define as an output in Max/RNBO, Scriptnode only sees standard Stereo IO and static parameters.

My Question:
Is there a specific "handshake", attribute, or naming convention required in RNBO so that HISE recognizes an output as a "mod output"?

Thanks for your help!

@David-Healey

Hi everyone,

I'm trying to build a Peak Meter in HISE where the UI fader/progress bar is driven by dynamic values calculated inside an RNBO patch.

I've been stuck for hours trying to bridge the gap between the RNBO C++ engine and the HISE UI Designer. My goal is simple: Read a real-time amplitude/peak value from RNBO and use it to animate a HISE component.

I've explored these three avenues, but each seems to have a "dead end" in my current workflow:

The Audio Out Way: I added extra out~ ports in RNBO (Channels 3+4) for the peak signal. My plan was to route these to a to_global_cable node in Scriptnode and read them via Globals.getValue() in the UI. However, I keep hitting "Channel Mismatch" errors or the extra pins simply don't show up in the Scriptnode UI.

The Data Port Way: Has anyone successfully used RNBO outport messages to send data values directly to the HISE message stack?

The Parameter Way: Can an RNBO param be updated internally by the RNBO logic (like a follower) and "push" that change back to the HISE parameter system so the UI can listen to it?

If you have a working project with RNBO and a dancing VU-meter, could you please share the "Golden Path"? Is the to_global_cable via extra audio channels indeed the way to go, or is there a more efficient "scripting" way?

Thanks for your help!

@David-Healey

Hi everyone,
I have a question about the correct workflow for updating / recompiling an already working RNBO C++ export inside HISE 4.1.
My setup:
I exported an RNBO patch as C++
copied all generated RNBO files into:
DspNetworks/ThirdParty/src
then compiled the DSP network as DLL
everything worked correctly the first time
The problem starts when I want to update the RNBO code later.
Then I:
exported RNBO again
overwrote all files inside ThirdParty/src
opened HISE
used Compile DSP networks as dll
After that the build fails.
The compile log only shows:
Create files
Sorting include dependencies
Creating C++ file for Network Kanal42test_w
Copying third party files
Compiling dll plugin

Compiling test ...
** BUILD FAILED **

CompileC ... Main.cpp normal x86_64 c++
(1 failure)
The first compile of the project worked perfectly.
The problem only happens after replacing the RNBO export with an updated version.
I already tried:
overwriting all RNBO files
clean build directory
clean DSP network files
restarting HISE
creating a completely new project
A new project works again initially, but updating the RNBO export later breaks the compile again.
So my questions are:
What is the correct workflow in HISE 4.1 for updating RNBO exports?
Should the entire ThirdParty/src RNBO folder be deleted before copying the new export?
Does HISE cache generated RNBO files / DLLs somewhere?
Is there a safe/recommended way to update RNBO DSP code without rebuilding everything from scratch every time?
Would really appreciate any advice from people using RNBO with HISE 4.1.
Thanks!