UI in RNBO plugin

neuwirthe's icon

In plugdata I created the following interface.

I there a way to create a similar interface in RNBO?

Jean-Francois Charles's icon

Nope, RNBO is meant to create the sound processing part of a patch (that you can export to a web process, to a vst, to a max object, to a headless Raspberry Pi...) When in need of a UI, you use something else (depends on your export target - for instance you get help for UI with web export here: https://rnbo.cycling74.com/learn/the-web-export-target ). Inside of Max, your UI would be made in Max world, not in RNBO world.

Jan M's icon

Hello NEUWIRTHE,

If I am not mistaken, the concepts of creating plugins with Plugdata and RNBO are very different. To my knowledge Plugdata works - similar to how Pluggo used to work in Max - by executing the patch on the Plugdata sound engine and render engine and exposing that as VST/AU etc to a host application. In other words, a plugin created this way is Plugdata running inside a plugin. That's why you can create a UI using the Plugdata UI element.

RNBO is a tool to translate a patch into code (c++ or WebAssembly ) that can be integrated into other sound engines. This way the generated code doesn't have all the overhead and can potentially be integrated into any platform. That's why there is no UI in the exports from RNBO. Creating the UI is the responsibility of the program or device that will execute the exported code. An embedded board running the code for example won't even have graphic capabilities and couldn't execute a graphic renderer.
For convenience there are UI elements available when patching in RNBO but those are not exported as code.