- This topic has 12 replies, 6 voices, and was last updated 8 months ago by studionebula.
-
AuthorPosts
-
-
April 3, 2024 at 3:15 pm #180448taylor12kParticipant
for those of us who don’t use Max/MSP, will there be some instructions about how to take advantage of this new funcitionality? i haven’t seen anything yet about what we need to do to use it.
– does it require an h9000 update?
– does it require an emote update?
– how do we load RNBO patches?
—- do we simply download patches that others make and load them in?
—- are the patches just, at that point, h9000 algorithms?basically looking for info about how the average h9000 user can use this great new feature.
thanks
-
April 3, 2024 at 3:17 pm #180449
Hello taylor12k,
You may find that information in this thread: https://www.eventideaudio.com/forums/topic/h9000-rnbo-public-beta/
-
April 3, 2024 at 3:23 pm #180450
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.
-
April 3, 2024 at 3:56 pm #180452vpajerskiParticipant
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. 🙁
-
April 3, 2024 at 5:49 pm #180460taylor12kParticipant
thanks! yeah, not interested in programming RNBO patches but hoping to be able to take part in trying out patches that others create and share. to do that do we still need a Max license? to simply load exported patches into the 9000? (that is, if there ends up being banks/libraries for share/sale)
or, likewise, does getting a Max license open us up to an already existing RNBO library that we can then open and export to our 9000?
basically, i’m looking for where we can find RNBO patches that others have made and how we get them into our 9000s. i’m totally happy to pay or get a license for what’s required.
-
April 3, 2024 at 6:07 pm #180461vpajerskiParticipant
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. -
April 3, 2024 at 11:19 pm #180463PuppeteerParticipant
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.
-
April 4, 2024 at 8:34 am #180467taylor12kParticipant
yes, thanks, this is what i was wondering. if non max users will be able to load patches into their h9000s from programmers willing to share them.
that being said, i wonder if there’s still any advantage to for a non max user (like myself) to get a max/rnbo license so we can possibly convert community max patches (of which there are a lot!) into usable H9000 algos…. tho, as you alluded to, it may not be as easy due to needed tweaks of UI or non-supported objects.
-
April 4, 2024 at 8:19 pm #180549PuppeteerParticipant
taylor12k,
I think at best the conversion of community patches to the H9K will be hit and miss. I’m not a Max/RNBO expert, but my impression is that most will require work get them to work on the H9000.
-
-
April 4, 2024 at 8:07 am #180465vpajerskiParticipant
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.
-
April 4, 2024 at 8:18 am #180466
Sorry, this is not included in the documentation yet, but parameters with range 0-1 with a stepsize of 1 will be displayed as a toggle. Besides that, the UI is currently limited to all knobs. We’d be happy to hear any suggestions you may have for UI improvements.
-
April 4, 2024 at 8:16 pm #180548PuppeteerParticipant
As tbskoglund alluded to, currently only knobs and toggles are available, which I find to be a hurdle to releasing RNBO creations, particularly anything with complexity. For example even a selector of filter type lowpass, highpass, bandpass will be represented as a knob labelled 0, 1, 2, which is not the ideal user experience. Hopefully the UI integration will be improved in future releases.
-
-
April 10, 2024 at 12:09 am #180819studionebulaParticipant
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.
-
-
AuthorPosts
- You must be logged in to reply to this topic.