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

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

@Phelan-Kane Hi Meta Function,

I’m encountering a compatibility issue between Max 9 / RNBO 1.4.2 and HISE 4.1 (Developer Branch).

Current Status:

RNBO 1.3.3 patches (Max 8) work and show up in the Scriptnode project list.

RNBO 1.4.2 patches (Max 9) are created by the HISE wizard but stay invisible in the workspace.

Individual compilation in Xcode fails with 23 errors.

Errors indicate missing members in the C++ class: createParameters, prepare, process, and reset.

It seems the HISE C++ wrapper doesn't recognize the new RNBO 1.4.2 class structure. Have you found a workaround for Max 9, or are you still using RNBO 1.3.3 for HISE integration?