9000/RNBO integration for the layman?

Hello taylor12k,

You may find that information in this thread: https://www.eventideaudio.com/forums/topic/h9000-rnbo-public-beta/

You will need a license for Max and RNBO to create patches and export them to the H9000 as algorithms. No H9000/Emote update is required.

The manual here shows the process for exporting RNBO patches to the H9000: https://cdn.eventideaudio.com/manuals/h9000/2.1.12/content/development/rnbo.html#content-development-rnbo–page-root

Users can then export these H9000 algorithms and share them to other users if they wish.

Let me know if that answers your questions.

The good news is you can use the trial version to try it out if you want.  You just can’t save the RNBO patch unless you buy. 🙁

The docs say that you can export the 9ka files that can be exported and shared.  Shouldn’t need a Max license.

Sharing RNBO Algorithms¶
If you would like to share your RNBO algorithm with other H9000 users, you may use the Dump Data feature to export a .9ka file that users can upload directly to their H9000 via Emote. To access the Dump Data feature, insert a FAT32-formatted USB drive into the H9000, then navigate to Emote’s Devices View, click UPDATES, then click DUMP DATA. The .9ka file will be exported to the USB drive.

My intention is to provide h9a files from my RNBO creations, which can be installed to the H9000 from emote or the USB slot, so people won’t need Max or RNBO to use my creations.

You only need Max/RNBO if you want to create your own algorithms.

The limitations on UI objects is a hurdle for me providing these at the moment, because complex algorithms can be a bit of a pain to drive as an end user.

Hey Puppeteer, do you happen to know if there’s a way to make a parameter something other than a knob?  I read through the docs but couldn’t find a way to do that.

Commenting on a couple of posts above:

First: It is important to note that RNBO is not Max, and hence RNBO patches are not Max patches. As it says right at the top of the main RNBO web page, https://rnbo.cycling74.com/ , RNBO is “A library and toolchain that can take Max-like patches [emphasis mine], export them as portable code, and directly compile that code to targets like a VST, a Max External, or a Raspberry Pi” and now the H9000. RNBO patches are similar to Max patches and are built inside Max, but you cannot take an existing Max patch and immediately export it to the H9000 without first translating it to a RNBO patch. RNBO has many, but not all, of the vast library of Max objects. Hence any given Max patch may or may not be able to be translated to RNBO.

Second: As Puppeteer said, currently RNBO is able to create only severely limited user interfaces on the H9000. I was initially excited to be invited to participate in the early testing of RNBO because I wanted to evaluate it as a possible means of creating 3rd-party effects (commercial and/or freeware) for the H9000. My enthusiasm waned rapidly when I found that it is not possible to create a user interface with RNBO that even approaches the expectations of H9000 users. IMHO the current situation is such that there’s little point in creating software of any complexity with RNBO because the resulting signal-processing system can’t be presented to the customer in a usable manner. My professional experience with audio software development and publication tells me that the user interface of a product is at least as important as how the product sounds, and right now I don’t think that I can produce a satisfactory user interface with RNBO. I hope that this situation will be improved with ongoing development of RNBO, but my brief investigation of RNBO’s capabilities with other targets (as described above) did not bolster my enthusiasm.

I’m sorry to rain on anyone’s parade, but there’s been a lot of speculation flying around about RNBO and not a lot of substance flying around with it.