RNBO randomly goes blank on Raspberry Pi 3
Hi,
I've been testing a setup on a Raspberry Pi 3 during the last two months with RNBO. Everything works great but I have a major issue.
At first, I noticed that after a few reboots or power-offs during the night time, RNBO goes empty. The sound isn't processed anymore, and when I type the RPi's IP on port 3000, the page is blank and no parameter/presets/inports/outports is shown. The only way to get it back is to push the RNBO patch from Max on my Mac again.
Today, for the first time, that happened when the RPi was powered and on (no sound was coming through at this time so I didn't notice the exact moment it happened).
It runs the Raspbian with RNBO OS provided by Cycling'74, and the RPiis only used for this purpose.
Does anyone have a clue on what it could be due to ?
Thanks in advance
Update:
I updated the RPi and Max/RNBO to the latest versions. I then put a time counter in my patch, sending an OSC message every second.
When the problem happens (it still does), I receive the OSC message on my client interface, so RNBO is up and running, but it appears that the sound processing part and the 3000 port are "empty".
Side question: when exporting from a RNBO subpatch, does it only export the subpatch, or the whole patch ?
Any would be appreciated, thanks !
Hi,
I'm wondering, when you say "goes empty" do you mean that you reboot your RPi and your patch isn't running as you expect? Or is something else going on? Does this behavior always happen after turning the power on or would it happen after the patch is running correctly for a long time as well?
What audio interface(s) are you using? Are you running your pi attached to a screen or "headless"?
RE exporting subpatch vs whole patch.. i'm actually not sure, I should look into that.
-Alex
Hi Alex,
I mean that no sound is coming from RNBO (for instance with only two in~ objects straight to two out~ objects, it would not output any sound). Plus when I go to the 3000 port, there is no parameter or inport displayed.
Sometimes upon reboot, it works again, some other times I would have to export the patch from Max again.
When the patch runs, it runs correctly, but it can suddenly go to this "blank state", though it happens most of the time after some reboots (but not every).
I’m using a Focusrite Scarlett 18i20, and yes the RPi is headless to maximize the ressources allocated to RNBO.
I'm curious, are you able to ssh to the pi when this happens and run: journalctl -u rnbooscquery
I wonder if anything interesting is showing up there?
I also wonder, in this case, can you see what the runner thinks it is using for an audio interface? If you look at the JSON in a web browser? For instance, my pi is called 'c74bull32' so I go here:
http://c74bull32.local:5678/rnbo/jack/config
the "VALUE" for /rnbo/jack/config/card , for me, is "hw:USB"
If you're using something like "hw:0" or "hw:1" (indexed and not named) I'd recommend that you use the named values "hw:Focusrite" or whatever it is, as the indexes can change between boots.
Yes I can ssh to the RPi when it happens. I'll try that command whenever it does it again and post the output.
I configured RNBO to use "hw:USB", which is the hardware device ALSA sees when connected to the Focusrite interface (same as the output of the "aplay -l" command").
sounds good, hopefully we can get to the bottom of this!
Happened a few times again today.
I set up a midiout inside my RNBO patch that lights up keys on my Launchpad Mini.
So, as previously said, no sound nor OSC is processed by RNBO, but midi is working.
Here is the result of "journalctl -u rnbooscquery"-- Journal begins at Sun 2023-03-05 00:43:37 CET, ends at Sat 2023-03-11 17:50:54 CET. --
Mar 05 00:43:48 audioproc systemd[1]: Started RNBO OSCQuery Service.
Mar 05 00:43:50 audioproc rnbooscquery[698]: Cannot connect to server socket err = No such file or directory
Mar 05 00:43:50 audioproc rnbooscquery[698]: Cannot connect to server request channel
Mar 05 00:43:50 audioproc rnbooscquery[698]: jack server is not running or cannot be started
Mar 05 00:43:50 audioproc rnbooscquery[698]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 05 00:43:50 audioproc rnbooscquery[698]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 05 00:44:25 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:44:25 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:44:26 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:44:26 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:44:33 audioproc rnbooscquery[698]: [2023-03-05 00:44:33] [error] handle_read_frame error: websocketpp.transport:7 (End of File)
Mar 05 00:44:33 audioproc rnbooscquery[698]: [2023-03-05 00:44:33.678] [ossia] [error] Node not found: / ==> /rnbo/inst/0
Mar 05 00:44:35 audioproc rnbooscquery[698]: [2023-03-05 00:44:35] [error] handle_read_frame error: websocketpp.transport:7 (End of File)
Mar 05 00:44:35 audioproc rnbooscquery[698]: [2023-03-05 00:44:35.953] [ossia] [error] Node not found: / ==> /rnbo/inst/0
Mar 05 00:45:05 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:45:05 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:47:35 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:47:35 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:54:12 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:54:12 audioproc rnbooscquery[698]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:54:15 audioproc rnbooscquery[698]: [2023-03-05 00:54:15] [error] handle_read_frame error: websocketpp.transport:7 (End of File)
Mar 05 00:54:16 audioproc rnbooscquery[698]: [2023-03-05 00:54:16.454] [ossia] [error] Node not found: / ==> /rnbo/inst/0
Mar 05 00:54:26 audioproc systemd[1]: Stopping RNBO OSCQuery Service...
Mar 05 00:54:27 audioproc systemd[1]: rnbooscquery.service: Succeeded.
Mar 05 00:54:27 audioproc systemd[1]: Stopped RNBO OSCQuery Service.
Mar 05 00:54:27 audioproc systemd[1]: rnbooscquery.service: Consumed 3.882s CPU time.
-- Boot 516e01771d2d42c29d0ff3fede1da02e --
Mar 05 00:54:39 audioproc systemd[1]: Started RNBO OSCQuery Service.
Mar 05 00:54:41 audioproc rnbooscquery[686]: Cannot connect to server socket err = No such file or directory
Mar 05 00:54:41 audioproc rnbooscquery[686]: Cannot connect to server request channel
Mar 05 00:54:41 audioproc rnbooscquery[686]: jack server is not running or cannot be started
Mar 05 00:54:41 audioproc rnbooscquery[686]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 05 00:54:41 audioproc rnbooscquery[686]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 05 00:55:16 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:55:16 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:55:16 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:55:16 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:55:28 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:55:28 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:56:23 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:56:23 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:56:32 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:56:32 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:57:11 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:57:11 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:57:17 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":0,"message":"received","progress":1}}
Mar 05 00:57:17 audioproc rnbooscquery[686]: {"id":"internal","jsonrpc":"2.0","result":{"code":1,"message":"created","progress":100}}
Mar 05 00:57:25 audioproc rnbooscquery[686]: JACK server starting in realtime mode with priority 10
Mar 05 00:57:25 audioproc rnbooscquery[686]: self-connect-mode is "Don't restrict self connect requests"
Hmm, nothing here jumps out as a problem, are you able to check/share the HTTP/json data when this happens?
Are you also willing to share your patcher?
I have a similar problem. Suddenly the RPI4 with RNBO stop working without any reason and the only possible solution seems to be upload again the patch from MAX.