admant

Hello there,
would it make sense to make a tutorial on how to encapsulate a rnbo patch in a html page at a very basic level? Something like a "bare minimum" with a single JS onclick event. I know there is the JavaScript Webpage Template but it is not clear to me how to connect - i.e. - a single toggle (play/pause) button to an oscillator without using the template sliders.  There are too many functions in the template to get oriented, at least for me, and modifying the index or the app.js by deleting lines of code many often gives me JS errors.

Hello there,
would it make sense to make a tutorial on how to encapsulate a rnbo patch in a html page at a very basic level? Something like ... 

web-page-bare-minimum

I recently made something like that: https://github.com/ersheff/simple-rnbo-web-template 
Feel free to use and/or offer suggestions.

No pressure of course, but I'd be interested in gaining a bit more insight into what parts were unclear or seemed too complex in the existing template in order to see if we can further simplify or split things up in a way that reduces the complexity and hurdle of getting started with the template or if an additional walk through / tutorial would be helpful.

Thanks again for sharing, appreciated!
Florian

Hello Florian,
to me it's the functions that calls the parameters in the js file that is a step ahead: 

makeSliders(device);
makeInportForm(device);

etc..

also a toggle button along with the sliders would be useful (the sliders shows a float range 0. to 1.  and not 0/1)

I think an example with a single parameter that I directly assign to a html IU object would be useful for beginners (like me :)

This template works great - bare minimum!

I added a parameter to the cycle~.
But this does not work??
I added param @name freq @min 20 @max 20000 @value 400 to RNBO (then export and replace files in "export" folder)

In the app.js I added getElementById=slider, parametersById = freq
In the html I added id="slider" + min, max, value etc


When I export and open in localhost, volume slider works, and if I change @value of the freq param to a different number (400 -> 45 or anything) this updates to the new freq. 
***But the frequency slider that I made doesn't do anything??
Can anyone see what is wrong in these screen shots??

(also, I tried using different names for the parameter in RNBO and the corresponding app.js and html-- nothing :(

Also... It would be great if there was a link to all the different UI input types available. (On c74 and Ableton sites they are using pictsliders).


Also, it would great to see an example of {outport} converted to an  html number box (or float) so I can see the numbers change on the website (for testing and cute aesthetics!)

Ok. This works.
Moving the "vol-slider" to control the frequency works on web page.
So something must be wrong when adding a second param and connecting everything in js and html.

web page bare minimum

Cephas Teom

Super excited about RNBO. Found it ridiculously simple to build a synth, build it the integrate into a web page. So many possibilities!

I've built a basic FM patch that sounds as you would expect when played in MAX. However, when I export it and included it in my webpage it sounds completely different - almost like the modulation is not happening and, instead we're hearing two tones.

Here's my RNBO patch:

import { createDevice, MIDIEvent } from '@rnbo/js'

let rawPatcher, patcher;
let device, modi, harm;
let WAContext = window.AudioContext || window.webkitAudioContext;
let context = new WAContext();

window.addEventListener('click', () => context.resume() );

function playNote(pitch) {
    let midiChannel = 0;

    let noteOnMessage = [ 144 + midiChannel, pitch, 100];

    let noteOffMessage = [ 128 + midiChannel, pitch, 0 ];

    let midiPort = 0;
    let noteDurationMs = 250;

    let noteOnEvent = new MIDIEvent(context.currentTime, midiPort, noteOnMessage);
    let noteOffEvent = new MIDIEvent(context.currentTime * 1000 + noteDurationMs, midiPort, noteOffMessage);

    device.scheduleEvent(noteOnEvent);
    device.scheduleEvent(noteOffEvent);
}

const fm = async () => {
    rawPatcher = await fetch("/json/fm2.export.json");
    patcher = await rawPatcher.json();
    
    device = await createDevice({ context, patcher });
    modi = device.parametersById.get("modi");
    harm = device.parametersById.get("harm");

    device.node.connect(context.destination);
};

fm()

window.addEventListener('click', () => {
    harm.value = 2
    modi.value = 1
    playNote(60)
});

In Max, the same synth with a harmonicity of 2 and a mod index of 1 create an open, concordant tone. The web export sounds like a bell, as if you're hearing both the carrier and the modulator and they are not multiples of each other.

This may not be a bug - there may be something obvious that I'm doing wrong - but it's odd that the same synth behaves differently when compiled.

Screenshot 2022-11-10 at 18.11.10.png

Hi there!
Super excited about RNBO. Found it ridiculously simple to build a synth, build it the integrate into a web page. 

rnbo-fm-patch-export-to-web-results-in-a-different-sounding-synth

Hi there. Would you mind copying the patcher  content compressed? (Select all the objects and then select copy compressed from the edit menu). 

This way it’s easier to reproduce without having to duplicate the patch from your screenshot.  

One debugging step would be to check the values of all of the parameters using for exampleconsole.log(device.parametersById.get("harm").value);
for each of your parameters, just to check that they are all set correctly.  

Florian - alas, I'm just trying out RNBO and haven't bought a license yet. So, it doesn't let me copy the code. If I do, I'll paste it here...

Is the synth polyphonic? Maybe there is a param that is not initialized correctly in some voices?

It is polyphonic yes. I've rebuild it as simple as possible to illustrate the issue - sorry I can't export more easily:

But when exported to web, same values sound completely different - unharmonious, despite the modulator being at the same frequency as the carrier!

One thing I notice is that you have an [out~ 0] (which I am surprised compiles). Does it change anything if you use [out~ 1] and [out~ 2] instead?

Changed and exported. Still the same issue. I wonder if the harm and modi inputs in JS are getting scaled somehow?

Even simpler - have removed any parameter inputs and just left the internal calculation:

import { createDevice, MIDIEvent } from '@rnbo/js'

let device;
let WAContext = window.AudioContext || window.webkitAudioContext;
let context = new WAContext();

window.addEventListener('click', () => context.resume() );

function playNote(pitch) {
	let midiChannel = 0;

	let noteOnMessage = [ 144 + midiChannel, pitch, 100];

	let noteOffMessage = [ 128 + midiChannel, pitch, 0 ];

	let midiPort = 0;
	let noteDurationMs = 250;

	let noteOnEvent = new MIDIEvent(context.currentTime, midiPort, noteOnMessage);
	let noteOffEvent = new MIDIEvent(context.currentTime * 1000 + noteDurationMs, midiPort, noteOffMessage);

	device.scheduleEvent(noteOnEvent);
	device.scheduleEvent(noteOffEvent);
}

const fmSimple = async () => {
    const rawPatcher = await fetch("/json/fm-simple.export.json");
    const patcher = await rawPatcher.json();
    device = await createDevice({ context, patcher });
    device.node.connect(context.destination);
};

fmSimple()

window.addEventListener('click', () => {
    playNote(48)
});

It's as if the math being applied to the signal is incorrect.

Just experimented with the Synth Building Blocks package and it behaves in the same way:
https://rnbo.cycling74.com/explore/synth-building-blocks-intro 

Here's the exported FM Synth JSON file - no changes made to the patch:

import { createDevice, MIDIEvent } from '@rnbo/js'

let device;
let WAContext = window.AudioContext || window.webkitAudioContext;
let context = new WAContext();

window.addEventListener('click', () => context.resume() );

function playNote(pitch) {
	let midiChannel = 0;

	let noteOnMessage = [ 144 + midiChannel, pitch, 100];

	let noteOffMessage = [ 128 + midiChannel, pitch, 0 ];

	let midiPort = 0;
	let noteDurationMs = 250;

	let noteOnEvent = new MIDIEvent(context.currentTime, midiPort, noteOnMessage);
	let noteOffEvent = new MIDIEvent(context.currentTime * 1000 + noteDurationMs, midiPort, noteOffMessage);

	device.scheduleEvent(noteOnEvent);
	device.scheduleEvent(noteOffEvent);
}

const fmSimple = async () => {
    const rawPatcher = await fetch("/json/ssb-fm.export.json");
    const patcher = await rawPatcher.json();
    device = await createDevice({ context, patcher });
    device.node.connect(context.destination);
};

fmSimple()

window.addEventListener('click', () => {
    device.parametersById.get("ratio").value = 3;
    device.parametersById.get("index").value = 5;
    playNote(48)
});

Again, odd behaviour when changing the values. For example, if you change the modulation index value, the pitch changes, rather than just the timbre.

if you look at the json, you can see it looks like you have some kind of per voice parameters setup 

"paramId": "poly/1/index",
 "paramId": "poly/2/index",
 "paramId": "poly/3/index",
 "paramId": "poly/4/index",

as well as ..
"paramId": "index",
"paramId": "poly/index"


it'd be interesting to see the source code to see how this is actually being used...


have you tried exporting as max externals/vst... do you get a similar behaviour?
it would be useful to know if this is solely web export related issue or a more general code generation rnbo issue.
(it'd also be easier to 'debug' if it exists in the c++ code export) 


(Ive been focusing on monophonic rnbo suff at the moment, so haven't been looking at much poly c++ code... though I did see one oddity early on when I tried the poly code export)

Still looking into this but as an aside - I assume you are exporting with per-voice parameters enabled either on the [rnbo~] object or in the export configuration?

Yes, that is correct. I've done it with and without to the same effect. Going to have a go exporting some even simpler patches with isolated operators and see if I can find the one that's at fault.

So, it's not to do with the polyphony or any of the parameter inputs. Here's a patch with a constant carrier frequency, harmonicity and mod index.

I just recreated the patch in max/rnbo, and in Max, mine sounds exactly like the second example (which. you label web ) .. not the first.

I also exported the c++ code, and ran against my template/host , and it sounded identical.


so, from what I hear, your first example in max is the issue, not the second.


edit for those that want to try the rnbo patch... 


Thank you for sharing this with us. I think there's at least a few things here that are worth greater investigation.  
In my local testing related to your minimal example with audio recording, a Max (not RNBO version) sounds like your first audio recording. A RNBO version running in Max sounds like your second audio recording (I believe the same as @technobear). I haven't had a chance to dig into the RNBO in Max vs RNBO as wasm in web browser yet, but there are some interesting things to note here, which may also relate to the RNBO in Max vs RNBO as wasm in browser. 

First, there are possibilities of differing sounds with this type of dsp based on where the phase of the two oscillators are with respect to one another. The way in which that might work out might be dependent on a variety of factors like vector size, the ways in which various parameters might update differing parts of the graph (e.g. if multiple parameters are meant to be set simultaneously, but perhaps happen in two different vectors for some reason), the way in which phase is initialized, and or drift across differing oscillators. 

Second, the cycle~ oscillator in gen and RNBO uses a combination of floating point and fixed point arithmetic in a different way than Max, and there could be aspects of this implementation that relates to these issues, especially when multiplying the output of these oscillators with very large numbers as you are doing in your patch. I've isolated a very simple example this is difference between RNBO and Max below. When initially turning on dsp there is minimal difference which noticeably grows over time when scaling with a large factor like 6600 or more like your example does. It could be that this is really pushing some of the boundaries of RNBO cycle's 32bit fixed point phase increment (as opposed to Max cycle's double precision floating point phase increment).

I can do some deeper investigations, but likely won't get much further until sometime later this week. In the meantime, perhaps it gives you and others some additional starting points to scrutinize. I would suggest further analysis by elimination, paying close attention phase, math precision and what results you are expecting. There of course could be other issues at play here, and only now that RNBO is released some very subtle issues for us to improve may come to light. Thank you for helping us track them down. 

ah, indeed... I assumed the OP was testing the rnbo patch, not a 'similar' patch written as max.

(thats comparing apple's n' oranges in my mind)


yes, if I use Max/MSP objects, I hear the first example.
but, if its Max RNBO or C++ RNBO then I hear the second example.

so it not web related at all (which was my suspicion) , rather  RNBO vs Max.

in this case, as @Joshua says, either 32bit vs 64bit , 
or perhaps order of evaluation of initialisation or processing... this could cause phase differences.


Thanks so much for your considered replies here. Interesting that I only hear the unwanted outcome once I've exported the RNBO patch. Sounds fine when I'm using a RNBO patch within Max - which points to some additional environmental factors that could be affecting the signal processing. 

It also makes sense that the multiplication by large values inherent in FM synthesis would expose small phase artefacts. I'll carry on investigating based on the suggestions here, and if I have any further insight, I'll share it.

Once again, thanks so much for your contributions and time.

just a quick note that after further debugging we identified an issue with modulating cycle~ that led to the discrepancies you are experiencing between the Web / WASM Export and running the patch inside rnbo~ in Max or within other exports targets.

We have a fix for this that will be released with the next update to RNBO.
Thanks again for your report and helping us to track this down.

That's great news. I'll look forward to the update. I've been enjoying RNBO in the meantime. Thanks for such an excellent piece of technology.

If you haven't already, it may be worth checking the other oscillators in the same context. I swapped out cycle for 'saw', 'tri', and 'pulse'. Saw appeared to work as expected, whilst tri and pulse exhibited similar behaviour to cycle.

RNBO FM patch export to Web results in a different sounding synth

RNASound

Hi, I'm trying to use codebox inside RNBO to parse a list and format some numbers to be sent to a midiout to output midi notes. In the RNBO codebox help file, under the "MIDI" tab, there is an example that uses 

// midiparse is a stateful operator
@state midiparser = new midiparse();

// we process the next message and assign it
let parsed : list = midiparser.next(in1);

I see that the midiparser operator that is created in the first line calls a funcion "next(in1)".
Is there a list of all the functions supported by the operators in Codebox? The reference docs for midiformat and midiparse only specifies input and output. 

In my case I need to use a "midiformat" operator, but I can't find the list of member functions for any of the codebox operators. I imagine there's a "format" or "pack" function that I'd need, but I don't know where to look. 

I'm gonna hunt for solutions in the source code, but it would be nice to see these functions included in the docs for quick reference. (Unless I missed it anywhere!)

Hi, I'm trying to use codebox inside RNBO to parse a list and format some numbers to be sent to a midiout to output midi notes. 

rnbo-codebox-operator-functions

@rnasound, if you look inside of the RNBO package's source/operators folder, you will find the source for the midiformat and midiparse operators which should be of help for what you're looking to do. We'll work on advanced codebox useage documentation over time, but  in the meantime, the operator source code will be the most helpful. It also will provide some examples of value for codebox in general (even though an operator definition is a little different than the lighterweight expression behavior of codebox). 

On Mac, the bundled RNBO package is located at /Applications/Max.app/Contents/Resources/C74/packages/RNBO.

RNBO Codebox Operator Functions

Ernest

My question on that disappeared on the announcement thread, so I am asking it again. 

It appears, from the announcement, that one can pass variables into JavaScript which are used to control a displayed image from a multi-image GIF. But there is nothing in the online documentation about what can actually do.  

what-ui-is-possible-with-rnbo-besides-sliders-and-knobs

it depends how deep you want to go down the rabbit hole!


rnbo patches have no UI, they expose everything as parameters 
(k, simplification, actually we also have external buffers and io too, and a few other things) 


code is generated (which we have no control over) and then 'hosted' inside a template.

what does this mean?
well the rnbo patch generates rnbo_source.cpp, that is 'platform agnostic', its the save regardless if its going to be vst, a max external etc.

to make it into something we can use directly (so assuming we dont just use the raw c++ code), it is then combined with a 'template'


so in the case of the javascript side, its this template that maps the rnbo onto sliders etc., that is all that this **template** supports. (currently?!)

this template, can only be generic... but C74 provide (in GitHub) the templates that are used.

so we can modify them to our hearts content.


in particular the javascript one is based on.


https://github.com/Cycling74/rnbo.example.webpage

tl;dr;  if you want to get your hands dirty, you can modify/create your own templates to do what ever you want... (you can see Ive done this with the Percussa SSP running RNBO patches) 


Regarding 'getting ny hands dirty' I have been waiting for 12 years now for copy protection, and I have to say at this point, Ive rather given up hope, having paid for upgrades to Live and Max during that time, it just seems unworthwhile to spend more money and more time on what appears to be an eternal toy.  To me. But others with less experience with what I am talking about will probably find it new and exciting ) 

What UI is possible with RNBO besides sliders and knobs?

schlam

Hello
Sorry if it's a dumb question, I use MaxMsp since a long time but I know nothing about Raspberry and RNBO.

RNBO seems very interesting for a project I have to do, but I need to use a very small card (Raspberry Pico).

The FAQ says that RNBO is compatible with Rspi3 and Rspi4, I don't manage to know if the Raspberry Pico is one of them or if it's compatible with RNBO..

Hello
Sorry if it's a dumb question, I use MaxMsp since a long time but I know nothing about Raspberry and RNBO.

RNBO seems very ... 

raspberry-pico-and-rnbo

Hi Schlam,
The raspberry pi and the pico are very different boards. the pi is a complete computer on a single board running Linux. The pico is a microprocessor only without all the other parts that would make a full computer.  Think of it as a much more powerful version of an Arduino.
in short, RNBO won’t run on a pico.

Hello Jan, 
I was quite sure that I will have this response... :(


There is something I don't understand very well.
Maybe you can help me to understand..


I understand that the Pico is quite the same that an arduino.
Arduino works with a language close to C, If I understand well.
With Arduino you can use max with Maxuino to program the arduino...
...>BUT it's only working while the USB cable is connected between the microcontroller and the computer.

You cannot "compile" your max patch with maxuino in your microcontroller to make it standalone.

When I learned the outing of RNBO and its capability to compile patchs in C, I really believed that finally I will be able to program microcontrollers with visual language.

So, even if RNBO is a kind of revolution, there is still no way to program a microcontroller with it ??

Arduino language seems very close to C, RNBO can compile patchs in C, but still no way to program an Arduino or a Pico with that...

it's a quite vast topic. I try to give a brief overview. 
Yes, an Arduino board as well as the Pico can be programmed via C. But this is merely the programming language a program is written in and does not take into account the platform it is written for.

A book written in English could be a manual for a CD player or a novel. The novel won't be of any use to understand how the CD player works - though they are both written in English.

In computer terms:

A C program written for a Mac won't run on Windows, or a Gameboy...  A C program always has to target a specific platform and/or operating system. 

RNBO generates programs/C code that can be understood by a Linux operating system that has the RNBO host program  running (with is included in the RNBO/Pi image C74 provides). It requires various aspects of the the RNBO host program and the underlying Linux operating system.

On a Pico or an Arduino there is no operating system running. A C program that targets these platforms works by manipulating the processor directly. One step at a time. RNBO for example needs the multi threading scheduler part of Linux in order to run (among many other things).
I haven't worked with Maxuino yet so I can't say anything about how/if this framework generate Arduino C code.

Does that help a little to understand more?

Best Jan


Yes! thank you. I understand more !

I am so a noob with those kind of question that I don't understand why it's so complicated to program an arduino directly with Max while Maxuino allows to control an Arduino.

I hope there will be a way to compile Max very simple patchs for an arduino/Pico one day..
Maybe I have to ask in the Maxuino forum, it seems to be the closest way to achieve that.

Of course that would be nice, but I think it’s probably not feasible. There is so much underly stuff in Max that’s far beyond the capability of an Arduino or even a Pico that I don’t see how this could result in anything that’s less complicated than writing an Arduino sketch directly. And it would be limited to very basic max algorithms (no msp or jitter, no timed events etc…) 
it seems more feasible to write an entirely new patching environment for Arduino from scratch as the platforms are based on very different paradigms.

I haven't tested it yet, but maybe a Raspberry Pi Zero 2 could handle a simple RNBO patch?

@LSKA I'd say yes it should but haven't tested it either. 

The pico and raspberry pi are two very different boards. The Raspberry Pi is an all-in-one computer running Linux. The pico is a microprocessor that lacks all the other components of a complete computer. Imagine it as a significantly more potent Arduino.

Raspberry Pico and RNBO

TobyAM

I've been trying to recreate some of Tim's (?) great FFT guides re: use of poly to handle the processing of discrete bins (e.g. https://youtu.be/gIZoyT380KQ) and I'm running into a CPU load wall. I realize this may be a case of expectations not matching capabilities, but I'm wondering a few things:

1) Is there or will there be multiprocessor support a la poly object? Polyphonic RNBO patchers obviously aren't, so while I can use a polyphonic RNBO subpatcher in a hacky way to process discreet small FFT bins, increasing the polyphony count to high numbers like 2048 just crushes my Ryzen 9 5090X, and I see it's all processed on a single core. In Reaper the plugin registers as taking 3c, or 3 cycles of a CPU core, which is unusable even at an audio buffer of 2048.

2) Any tips on effectively, and neatly, processing 2048 bins of an FFT discreetly in RNBO? Will there be any use-case examples of FFT processing in RNBO? Is this simply not a good use of RNBO? I'm unsure if splitting out the processing of 2048 bins out of a polyphonic subpatcher into 2048 individual subpatchers would yeild better results and be worth the insane-seeming effort and mess. Perhaps I need to learn codebox better, but if this is all being done on one CPU core I don't know if it will improve performance.

3) The windowing documentation is pretty sparse, but I think I figured it out. Is it correct that all that's needed is to split an input into multiple FFTstreams~, each successively being offset by the phase attribute, and corresponding IFFTstreams~ added successively back together? This seems to work on my end as expected, but to have a group of 4 windowed 2048 FFTstream~s the necessary phase offset seemed to be multiples of 512, which I figured out by trial and error. This seems odd, am I off base? 


If anyone can help me achieve my Max-driven FFT plugin prototyping dreams I would be very grateful.
Thank you, RNBO is awesome!

I've been trying to recreate some of Tim's (?) great FFT guides re: use of poly to handle the processing of discrete bins (e.g. 

p-polyphonic-fft~-and-too-high-cpu-load-multithreading

Looking into codebox, it doesn't seem poosible to create an array of stateful operators, so I'm not sure that's a good option for operating on many FFT bins in a state-based way...

Any chance on anyone having any CodeBox~ fftstream @state examples? I can't figure out how to create this object properly.

Will there be any use-case examples of FFT processing in RNBO?

i read in the announcement thread, i think it was Josh Clayton, mentioned to someone asking about fft, that there will be some examps eventually(just need to be patient, i bet the rollout requires some care in working out immediate kinks here and there, first).


it’s difficult to give FFT advice without seeing the patch, and i don’t recommend sharing your RNBO commercial product here, either, but going by what i’m reading, it seems you might be reaching too hard:
-there’s rarely any need to process each bin discretely at all(if you have 2048 bins, that would be an intense amount of detail you’re trying to work over the spectrum going bin-by-bin(maybe you get an AI to do this instead, haha), plus with an FFT size of 2048, there’s 1024 bins(upper-half) that might be redundant for you depending on what you‘re doing)
-instead of going through this and running the risk of confusing you with the way i barely understand the semantics, i’d recommend you go through these tutorials if you haven’t yet:
PhaseVocoder-Part1 
PhaseVocoder-Part2 

-you’re not off base with that one part you mentioned(for an FFT-size of 2048, and a desired ‘overlap’ of 4, you need a ‘hop-size’ of 512), i’m just not sure how you’re doing it, there’s many ways(see the phasevocoder-part1 article i linked above), you don’t necessarily need multiple ‘ifft~’/‘ifftstream~’ objects, depending on how you’re processing the data you get from the input/analysis stage(again, see the part1 article linked above, notice they have multiple fft~, but only one fftout~… but also, for that article, you’ll need to remember it’s within a pfft~… there will be things that you’ll need to figure out on your own from there specific to fftstream~ in rnbo~, hopefully with help of incoming examps c74 might give us(?))

-for your codebox question, first off, codebox is not necessarily easier nor more-efficient(you don’t necessarily need it at all, but it’s good to learn to have more options/techniques)
with that in mind, your specific answer is one i’m wondering about myself: we don’t have a way to create visual objects in rnbo~ and then click to see the codebox equivalent(and that probably means they need to create better docs for rnbo~ codebox, otherwise, most of us will be flying in the dark as to what we can or can’t do - i don’t see how it registers ‘fftstream’ as an op at all, nor even just ‘fft’?)

but if you want to study codebox in general, try within gen~ first, try this: create a gen~ object(maybe outside of rnbo~ to start), then go into the gen~ object, create a [buffer wut what] op, and a [sample wut @interp cubic] op, then connect the [in 1] op to the input of the [sample] op and [out 1] to the output of the [sample] op, now with everything connected, click the ‘C’ icon in the right-hand toolbar, and you’ll see an equivalent code for codebox(this is how you can learn the more advanced/detailed parts of how to codebox, for example, how to codebox the “@interp cubic” part of the sample op and what order all the arguments go in, etc.).


that said, i don’t see how to get help for using ‘fftstream’ in a codebox within rnbo~-naked(my word for it), perhaps it just means codebox in rnbo~-naked will be different than in gen~(you’ll just need to use it for the specific uses documented only?)

anyways, that’s my 2cents, it’s Thanksgiving weekend, too, so if you’re still lost on your codebox question about fft in rnbo after you give some time for folks to come back from the holiday here, maybe bump this thread again(it‘s definitely an interesting/worthwhile question about using fftstream in codebox, i‘m curious too :) hope this helps.

Thank you very much for the reply. I'll check out those tutorials for a refresher.

This plugin design rather specifically relies on state-based manipulation of individual bins. I've managed to accomplish this with using a fixed array within CodeBox~ and it seems to be working pretty well, though now I'm working on navigating the awkward mix of sample-stream and buffer processing in CodeBox~. At least I can say I've accomplished the main goal roughly.

Yeah, it's perhaps an excessive bin count in total, but it's ideal for the lower-frequency resolution. I might do an overlap with a lower-count FFT for higher frequencies to save some processing, but I'm not sure if that will be necessary.

While doing it all within CodeBox~ is likely excessive, it would be nice, but I'll avoid that for now.

I have tried looking at Gen~ code panel for objects, but in my experience so far it doesn't translate to Rnbo CodeBox~ operators in a helpful way.
On one hand the current Rnbo~ CodeBox documentation seems great and an improvement over past CodeBox documentation, for which I'm very thankful, but it still seems to be only a confusing glimpse into the potential that's leaving me a bit frustrated.
What would be rather ideal for them to include is at least one basic code example per operator, at least the stateful operators that seem to be more tricky.

oh no, i didn't mean the bin count is excessive, just that attempting to have discrete-processing for each bin(as if each bin is processed in a very different way individually) is very specific, but these things are just hard to describe in text so i'm probably not really understanding what you're doing or what the words, 'discrete objects for each bin' means(2048 with overlap of 4(hopsize of 512) seems a good resolution for most things). 

it sounds like you've made good headway(i have to read up on rnbo~ more, didn't even realize the difference between codebox and codebox~ til you wrote it here, haha... thank you for that!). 

big FFT~, multicore processing?

I've tried many variations on :
@state fftleft = new fftstream();
in CodeBox~ to try and create a new fftstream state object, but I get an error every time.

Can anybody throw me a bone on how to use this?

I've tried many variations on :
@state fftleft = new fftstream();
in CodeBox~ to try and create a new fftstream state object, but I get an ... 

error-compiling-codebox~-fftstream

No matter what arguments I enter into fftstream() I get the same compile errors:
I've been trying this for hours so I would love just a simple example of this CodeBox FFT.

oh, i see now, you tried it as a ‘stateful operator’… maybe it isn’t one? and maybe codebox doesn’t actually do audio in rnbo-naked(?)… the helpfile for codebox in rnbo-naked doesn’t show any audio processing, it shows utilizing ‘peek’/‘poke’/‘interp’ ops as though they’re already proper ‘ops’ within the codebox system, but the example still translates out to events only(no audio in that example coming out of the codebox itself, the comment says ‘this codebox is event rate’ …but then that confuses me some more as i go looking into its inspector to see how to turn an rnbo-naked codebox into an audio-rate codebox(?))... think they just need to add a bit to those rnbo-naked docs.

not sure it’s a stateful-operator to begin with 🤔 (?) …good tries, tho! you got me curious :)

i saw your other thread's reply, now i get it:
codebox~(with the tilde) is where you do it! ha, i still have much to learn about rnbo~. will try it some more, thank you!

error compiling Codebox~ fftstream

dwingus

Hi . .  Looking into how to recall snapshots/presets on a Raspberry Pi. The docs say the Pi will load the first snapshot in the presets file that is sent to the Pi which is fine. How does one access other snapshots in the preset file via OSC messages? I see the docs mention using rnbo.remote so I poked through that to see if there is an obvious OSC path to use but i didn't find it. Thanks!  

Hi . .  Looking into how to recall snapshots/presets on a Raspberry Pi. 

rnbo-presets-on-raspberry-pi

https://github.com/Cycling74/rnbo.oscquery.runner#osc-namespace

"presets":{
                  "FULL_PATH":"/rnbo/inst/0/presets",
                  "CONTENTS":{
                    "entries":{
                      "FULL_PATH":"/rnbo/inst/0/presets/entries",
                      "TYPE":"s",
                      "VALUE":[
                        "untitled 1"
                      ],
                      "ACCESS":1,
                      "CLIPMODE":"none",
                      "EXTENDED_TYPE":"list",
                      "DESCRIPTION":"A list of presets that can be loaded"
                    },
                    "save":{
                      "FULL_PATH":"/rnbo/inst/0/presets/save",
                      "TYPE":"s",
                      "VALUE":"",
                      "ACCESS":2,
                      "CLIPMODE":"none",
                      "DESCRIPTION":"Save the current settings as a preset with the given name"
                    },
                    "load":{
                      "FULL_PATH":"/rnbo/inst/0/presets/load",
                      "TYPE":"s",
                      "VALUE":"",
                      "ACCESS":2,
                      "CLIPMODE":"none",
                      "DESCRIPTION":"Load a preset with the given name"
                    },
                    "initial":{
                      "FULL_PATH":"/rnbo/inst/0/presets/initial",
                      "TYPE":"s",
                      "VALUE":"",
                      "ACCESS":3,
                      "CLIPMODE":"none",
                      "DESCRIPTION":"Indicate a preset, by name, that should be loaded every time this patch is reloaded. Set to an empty string to load the loaded preset instead"
                    }
                  }
                },

so....  something like 

oscsend osc.udp://c74rpi.local:1234 /rnbo/inst/0/presets/load  s "presetname"


not tried it... so Id double check the namespace as shown on readme, in case its changed etc.

(also check that rnbo.remote is working... Ive noticed a few things in RNBO that are not yet implemented ;) ) 

As mentioned you can access the list of available OSC paths via a web-browser. More info on that can be found on these two pages in the RNBO Docs:

Raspberry Pi Export FAQ - List of Available OSC Messages 

If you are looking for a quick and simple way to change and save presets - the web interface hosted on the provided Raspberry Pi image provides that functionality as well via the WebSocket interface of the OSCQueryRunner.

RNBO presets on Raspberry Pi

John Goldsmith

I feel like I am missing something here, but I have tried exporting a drum sequencer to VST that syncs to the temp of the DAW. I have tried using the metro object with @lock set to 1 but it does not sync. I can get it to work with selectable tempo in the device, but can't seem to lock it to the DAWs transport. Is this possible using the default VST/AU out or would I need to export the code to JUCE and use that to handle the sync?

Apologies if I missed something very obvious in the tutorials. The ones I have been using are https://rnbo.cycling74.com/learn/sync-in-rnbo and https://rnbo.cycling74.com/learn/midi-sequencer 

Screenshot 2022-11-17 at 11.42.12.png

Hi,
I feel like I am missing something here, but I have tried exporting a drum sequencer to VST that syncs to the temp of the DAW. 

sync-to-daw-tempo-for-vst-export

Hi John,
We don't have transport sync implemented for the plugin exports (yet).. I'll create a ticket for this.


Thanks! I will work on getting it working in JUCE for now. Very interested in the feature.

I actually just got it working, it is in the next release candidate for RNBO 1.0.2

I'd really like to have this feature too please!

Sync to DAW tempo for VST export

thetechnobear

see this test patch, works fine in max, but rnbo seems to ignoring begin, and screwed up entirely when you connect to end.


also checking some functionality (for both rnbo and max) of record...

begin/end only seem to work when loop = 1?

Id hoped they would also work for 'one shot' recording.

(also theres some quirkyness with rnbo using external buffers, I noticed when writingthe above example, rnbo record~ only worked after saving/loading patch...
(perhaps max is not setting the external buffer into the rnbo patch without reloading?)



see this test patch, works fine in max, but rnbo seems to ignoring begin, and screwed up entirely when you connect to end.

 

also ... 

Cycling '74 Forums

web page bare minimum

Ok.

RNBO FM patch export to Web results in a different sounding synth

Hi Florian, If you haven't already, it may be worth checking the other oscillators in the same context.

RNBO Codebox Operator Functions

@rnasound, if you look inside of the RNBO package's source/operators folder, you will find the source for the midiformat and midiparse ...

What UI is possible with RNBO besides sliders and knobs?

Well thanks for answering the question ) Regarding 'getting ny hands dirty' I have been waiting for 12 years now for copy protection, and I ...

Raspberry Pico and RNBO

@LSKA I'd say yes it should but haven't tested it either.

big FFT~, multicore processing?

excessive bin count in total oh no, i didn't mean the bin count is excessive, just that attempting to have discrete-processing for each ...

error compiling Codebox~ fftstream

i saw your other thread's reply, now i get it: codebox~(with the tilde) is where you do it! ha, i still have much to learn about rnbo~.

RNBO presets on Raspberry Pi

As mentioned you can access the list of available OSC paths via a web-browser.

Sync to DAW tempo for VST export

I'd really like to have this feature too please!

record~ begin/end not working?

see this test patch, works fine in max, but rnbo seems to ignoring begin, and screwed up entirely when you connect to end. also ...

Cycling '74 Forums

.css-lq0bf2{font-size:18px;line-height:24px;font-weight:700;color:var(--theme-ui-colors-accent);-webkit-text-decoration:none;text-decoration:none;}.css-lq0bf2:visited{color:var(--theme-ui-colors-dark30);}.css-lq0bf2:hover{color:var(--theme-ui-colors-accent);}web page bare minimum

Ok.

Hi Florian, If you haven't already, it may be worth checking the other oscillators in the same context.

@rnasound, if you look inside of the RNBO package's source/operators folder, you will find the source for the midiformat and midiparse ...

Well thanks for answering the question ) Regarding 'getting ny hands dirty' I have been waiting for 12 years now for copy protection, and I ...

@LSKA I'd say yes it should but haven't tested it either.

excessive bin count in total oh no, i didn't mean the bin count is excessive, just that attempting to have discrete-processing for each ...

i saw your other thread's reply, now i get it: codebox~(with the tilde) is where you do it! ha, i still have much to learn about rnbo~.

As mentioned you can access the list of available OSC paths via a web-browser.

I'd really like to have this feature too please!

see this test patch, works fine in max, but rnbo seems to ignoring begin, and screwed up entirely when you connect to end. also ...

web page bare minimum