TobyAM

I've been using the rnbo.example.juce project for my plugin for months.
In an earlier version of Max the GUI would update when parameters in RNBO would have their values change programmatically without user input. RNBO would generate a new parameter value, and it would be reflected in the JUCE GUI. Great.
In the current Max version I noticed that's not happening. Parameter changes from within RNBO are not reflected in the JUCE GUI until the plugin instance window is closed and opened again. The parameter change is not updated in the DAW host either.

I spent a whole day trying to debug C++ code for the JUCE example, only to find that rolling back the Max version and exporting and rebuilding fixed it. Perhaps it's a problem with updateSliderForParam

So this seems like an unintended change if not a bug! I'll be using version 8.5.4 in the meantime!

I've been using the rnbo.example.juce project for my plugin for months.
In an earlier version of Max the GUI would update when parameters ... 

parameter-changes-in-rnbo-not-reflected-in-juce-gui

The latest version of RNBO attempts to fix some issues with automation that previous plugin exports have. We've changed the default for a parameter notifications and added metadata to allow for altering those defaults: https://github.com/Cycling74/rnbo.adapter.juce/blob/dd233609adc495828fa9efcf756ab2a155a3bd1d/RNBO_JuceAudioProcessor.cpp#L144C5-L148 

I believe you should get your old behavior if you define RNBO_JUCE_PARAM_DEFAULT_NOTIFY in your build process.

Here is some more information about the metadata: https://rnbo.cycling74.com/learn/using-the-vst-audiounit-target 

Well, that's pretty cool! I missed the memo :) 
I just added the metadata to the parameter I needed and I'm good to go, thank you!

edit: But now presets don't recall until the window is reopened... well, more to do.

As the plugin is no longer recalling save states or presets properly, I would like to follow your advice and "define RNBO_JUCE_PARAM_DEFAULT_NOTIFY in your build process."  I haven't figured out how to make that work yet. I tried putting "set(RNBO_JUCE_PARAM_DEFAULT_NOTIFY TRUE)" in the CMakeLists.txt file, but that's not working... Any tips?

In the meantime I've added the metadata to each object individually, but with this global change, was there any other change I should know about that would allow saves and presets to be recalled?

But now presets don't recall until the window is reopened...
well, more to do.

As the plugin is no longer recalling save states or presets properly, I would like to follow your advice and "define RNBO_JUCE_PARAM_DEFAULT_NOTIFY in your build process."

I haven't figured out how to make that work yet. I tried putting "set(RNBO_JUCE_PARAM_DEFAULT_NOTIFY TRUE)" in the CMakeLists.txt file, but that's not working... Any tips?

Here is an example compile definition:
https://github.com/Cycling74/rnbo.example.juce/blob/cab65fd46cc1398152f088c82f0ac4cc61388c95/CMakeLists.txt#L54 

What you did only sets a definition within the cmake build setup, it doesn't actually become a `#define`

add_compile_definitions(JUCE_VST3_EMULATE_MIDI_CC_WITH_PARAMETERS=0 RNBO_JUCE_PARAM_DEFAULT_NOTIFY)

I'm curious to know how presets behave after you do this. There is something going on with presets in the latest rnbo code that I haven't quite figured out yet, I'd like to know if you're still having issues after this or not.

Thanks! I've implemented that as above, which works as expected which is great!

EDIT: I had to delete and rebuild builds and exports, but it's all working as expected now.

Yeah, re-exporting the source code is expected, some of the codegen/interface likely changed between your previous rnbo version and the latest.

I'm happy to hear that this new setup is working for you. So, presets work okay too?


BTW, this thread was a good reminder that I hadn't actually merged the juce template develop back into main for this release.

I have a cmake cache variable already set up to do all this there now: https://github.com/Cycling74/rnbo.example.juce/blob/299823760bdd28f2f73d525479844b2b306b4bd7/CMakeLists.txt#L26

So, for future readers, you can simply change the value of that instead of augmenting the build as suggested above.


Yes, presets seem to be working as expected, thanks again Alex!

So there are no other changes in the latest juce template I should look out for? Any straightforward way to get a buffer from RNBO to JUCE for analysis GUI? I know there's a workaround that's still slightly over my head. That's the next step for me.

Happy to hear that this is all working for you!

I don't think there are significant differences in the template.. you're probably good with what you have.

RE buffer output, I'd start a new thread with that topic and see if anyone has something to say about it?

rolling back Max to 8.5.4 resolved an issue with JUCE not seeing RNBO parameter updates.

ShelLuser

Hi gang!

First if all: huge compliments for RNBO~... I'm still very much a newbie at the time of writing but I already managed to build, and use, a very crude VST3 plugin and... it's just amazing. See: I use both Live (suite) & FL Studio side by side and while I have M4l in Live I always fantasized about what might happen if you could use Max with DAW's like 'FLS'. Now I can!

Question... everything works as expected but I'm wondering if it would be possible to 'overrule' the cloud compiler and instead use a locally set up compiler & framework? Or is this approach fully hardcoded into RNBO?
 
Note: I'm not necessarily asking how it can be done, merely if...


(edit): Thanks for the feedback!  I overlooked that option and I can easily imagine that this will make it much easier for people to filter stuff. Not gonna respond because we don't need a "ping", so... figured I'd just edit.

Hi gang!

First if all: huge compliments for RNBO~... 

would-it-be-possible-to-use-a-local-compiler-for-vst3-targets

So, yah, in hindsight this was a bit of an obvious question I suppose... 

First things first: the export sidebar features 2 options for "Source code" where the 1st option is C++ source code export. That's an obvious approach.

Second... having already experimented with VST exports (and being very impressed with it) you'll quickly learn that VST builds are powered by Juce; a "framework for audio applications and plug-in development". Best part is obvious: it can be downloaded and used for free, which is something that Cycling '74 is doing.

And there's my answer. Of course I still need a compiler for all this, but that's something which Visual Studio can handle for me.

Thanks for answering you own questions so that others with the same question can have a quick hint on what to to.
Instead of editing the title als ‚(solved)‘ there is a resolved tag you can give to the topic instead. ;)

Here is the JUCE adapter code that we bundle with the RNBO source code: https://github.com/Cycling74/rnbo.adapter.juce 
and here is a template project that we provide for creating your own customized JUCE/RNBO based projects: https://github.com/cycling74/rnbo.example.juce


Would it be possible to use a local compiler for VST3 targets?

Thestral Sound

I've made an FFT based plugin in rnbo~ that uses a hanning window, but the hanning function disappears when I export to vst3 and try it use it in my DAW. There is an option to load a function into the plugin for use, but the problem is that I have no idea what file type it is expecting, or where to even find such a file which contains a hanning function in the first place.

Any help solving this would be much appreciated.

Hello folks,
I've made an FFT based plugin in rnbo~ that uses a hanning window, but the hanning function disappears when I export to vst3 ... 

rnbo~-fft-plugin-function-windows-missing

no idea about RNBO here, but i would not trust samples for windowing functions, it seems better to always calculate the function live.

hanning is nothing more but a cosine (i.e. the first half of it), that´s what you use by default for FFT, granular delays, frequency shifters and many more tasks.

Hire mobile app, custom web app team & digital marketers on hourly, fixed price, monthly retainers.
Online Marketplace App 

Casino org is the world’s leading independent online gaming authority, providing trusted online casino news, guides, reviews and information since 1995.
casino

I'm confused by "the hanning function disappears when I export", how does it 'disappear'?

RNBO has the [hann] object that you can use to compute the window.
If you want to load buffers in a vst, you can load any of the audio file formats that JUCE supports as of Juce 7.0.3.

There is an option when you export, if you're using the cloud compiler, to "Package Sample Dependencies" as well. In this case, if you use a buffer like:  [buffer foo @file blah.wav], and max can find and load 'blah.wav', you should get that file data automatically loaded in your VST, if you've selected that option.


What I meant by it disappearing was that once the patch was exported it seemed as though the vst no longer knew where to find the hanning function. This has been disproven by myself while reviewing the patch and finding a mistake I'd made. It essentially was applying the hanning window, but then outputting the version of the signal that was not yet windowed.

Providing unlimited, fast & reliable broadband connectivity to homes and businesses at affordable price.
Internet rates


RNBO~ FFT Plugin Function Windows Missing

Peter Nyboer

I'm posting this because I'm sure someone will search the forum for multichannel out RNBO plugins before they find it in the manual!

It took me a bit to find this, but I did, and met with some success.
I have a RNBO patch with 6 audio outs. I initally tried to export as a VST3, but the outputs did not show up in Bitwig 4.4.8 or in Live 11.2.10. 
I then found this bit in the RNBO manual about exporting, where you label the outputs with the "@meta bus <name>" tag. Once I exported with unique bus names on the [out~] objects, the DAWs recognized the plugin as multi-out. Yay!

Here's how you get the individual outs from Live and from Bitwig.

multiple channels output
multiout plugin


I'm posting this because I'm sure someone will search the forum for multichannel out RNBO plugins before they find it in the manual!

It ... 

-you-may-need-this-multichannel-output-plugin-export

Thanks for sharing this! I know I eventually will run into that problem as well :) 

Sure thing. For additional reference, here's what this looks like in a patch:


[you may need this] Multichannel output plugin export

Cephas Teom

Good evening all.
I'm creating synths for a web application, so building them in RNBO then exporting them to web assembly.

I've created a simple synth in RNBO and configured it to have 16 voice polyphony. I've also exposed the voice parameters which allows me to target individual voices using a path, such as:
poly/<id>/<param>

Using the attriui object, I can see all of the individual voice parameters formatted in this way. When I export to web assembly,  logging out the individual parameters also confirms to me that these individual voice parameters exist:

console.log(device.parametersById.get('poly/16/amp'))

However, when I trigger notes using a MidiEvent, I can't see any way of knowing what voice I am triggering, so I'm unable to effectively target the individual parameters. What I would really like to be able to do is something like:

- Query the device to get the next available voice id
- Target the voice, setting the desired parameters
- Schedule an event for that voice

The other option would be that I export a monophonic synth and, in JS, create a new synth instance for each note event, then dispose of it after it has finished. Not sure on the performance overhead of spinning up so many audio worklets, but as a concept, does anyone know if this is possible? Can I dispose of devices?


Many thanks in advance for everyone's time.

Cephas.

Good evening all.
I'm creating synths for a web application, so building them in RNBO then exporting them to web assembly.
I've created a ... 

voice-targeting-andor-synth-disposal

I'd recommend looking at the documentation for User Voice Control which gives you far more control on how to use and interact with voices within your RNBO patch.

Cycling '74 Forums

Happy to hear that this is all working for you! I don't think there are significant differences in the template..

Here is the JUCE adapter code that we bundle with the RNBO source code: https://github.com/Cycling74/rnbo.adapter.juce and here is a ...

Happy to hear that you figured it out!

Sure thing. For additional reference, here's what this looks like in a patch:

Hi Florian, That's exactly what I'm looking for. Thanks very much! Cephas.