RNBO error (since Max update?)

robinfoster

Whenever I try and build anything made with RNBO, I get the following error:

no member named 'scheduleParameterBang' in 'RNBO::EngineInterface' column: 28, line: 693

It does it with any .cpp generated by RNBO, even empty patches and unchanged patches that have worked previously, and persists with the dev-1.2.1 repo that I found on a previous forum post.

I think it might be since updating Max - I can't think what else has changed. I'm on Max 8.6.2 and RNBO 1.2.6.

giuliomoro

Can you post the full set of files generated by rnbo somewhere and send me a link?

robinfoster

Sure - https://www.dropbox.com/scl/fo/q9of7rl0ehmaip38ub08x/h?rlkey=abcbbyjq1cpuqfom91k431r2a&dl=0

This is just an empty rnbo patcher...

Thanks!

robinfoster

I've posted a link but it's awaiting approval... 🙂

giuliomoro

try the dev-1.2.6 branch now

robinfoster

Sorted 😃 Nice one!

Thanks so much

giuliomoro

for posterity, anyone finding themselves in having a different rnbo version from the one supported by the branches on the rnbo.example.bela repo should try the following:

get the non working exported files on the board (e.g.: in /root/export)
cd to the rnbo.example.bela folder
run ./update_rnbo.sh /root/export
hope everything goes fine

background:
the rnbo-generated cpp files in the rnbo folder are normally built by including them all from the RNBO.cpp file. That's pretty unorthodox, and on a small embedded computer like Bela it would mean extremely long compile times - assuming it would actually compile at all before it runs out of memory. I am not here to judge, it's an approach that works for them so they can keep using it, but on Bela we have to build each one of those files individually. Unfortunately those cpp files are missing some critical includes that need to be added in when building them individually, so this is the reason why we cannot just use the files generated by rnbo but actually need to do some processing on them. The annoying thing is that these changes could be applied upstream at zero build- or runtime- cost to them, but even though I reported this the day after the relase of rnbo, it hasn't been applied yet.

robin

giuliomoro

Hi there,

The RNBO currently in Max is quite a different version than the dev. Can you elaborate on this process a bit?

I tried following but get:
root@bela ~/Bela/projects/rnbo.example.bela-main# ./update_rnbo.sh /root/export bash: line 56: ./update_rnbo.sh: Permission denied

I also tried creating a zip file similar to your zip on GitHub from the Max export folder although this was missing some files.

I'm not familiar with this process so appreciate your patience.

Thank you,

robinfoster

I would much rather be using Pd for Bela stuff in all honesty, but I'm just not familiar enough with it compared to Max 🙁 - thanks for your speedy work here though

giuliomoro

robin bash: line 56: ./update_rnbo.sh: Permission denied

whenever you get that, make sure the permissions on the file are appropriate: chmod +x ./update_rnbo.sh and then it should run. I just updated to 1.3.2 and the automated update failed because the patches don't apply cleanly. So I made a new main-1.3.2 branch for you. Try this out: https://github.com/giuliomoro/rnbo.example.bela/tree/main-1.3.2

I also updated the update_rnbo.sh script hoping it will work again next time.

robin

Thanks for the updated branch. No errors now, so should be working fine. I still have issues on my end so currently working through those. Will report back.

Appreciated!

robin

All working great now, thank you.

For future RNBO updates, is there an easy method for me to update the package myself? I.e. replace files from the RNBO export into a prior BELA package?

giuliomoro

robin For future RNBO updates, is there an easy method for me to update the package myself?

I use the update_rnbo.h file in the project. If it fails, I fix it and try again, as I did this time.