"Following up on my previous question about exposing RNBO outports as blue pins:
I’ve found a workaround, but I’d like to know if this is the recommended 'HISE way.' Since I can't get the internal outport data to show up as signal pins on the Scriptnode wrapper, I'm now doing this:
Inside RNBO: I capture the peak, apply a slide~ for ballistics, and send it to a standard output parameter (control rate).
In Scriptnode: I connect that RNBO parameter directly to a Global Cable.
In Interface: I use a Timer to poll the cable value and update my UI components.
This seems much lighter on the CPU than streaming high-rate audio data to the UI, and it bypasses the need for specific C++ flags or JSON edits. Does the community agree that using Global Cables as a 'data tap' for RNBO parameters is the most efficient method, or is there a more direct way to expose the outports that I'm overlooking?"
