Is the RNBO runner 1.4.1 for the Raspberry PI Zero 2 W limited to 48kHz?
Hello,
is the RNBO runner 1.4.1 for the Raspberry PI Zero 2 W limited to 48kHz?
I know I could probably use
sendosc c74rpi.local 1234 /rnbo/jack/config/sample_rate i 96000
but then I get connectivity-flapping true/ false in the export window and can't select it in the web interface (I don't know if it changes to 96kHz in the background). Is there a better way?
I know it will probably end in XRUNS, but I would like give it a try.
I appreciate your help.
Thanks,
Jasper
It may be a limitation of your sound interface. Which one are you using?
I have written a driver and an overlay for the TAC5242 codec which is connected via I2S.
So far everything is working fine. I just tested and I can start jack manually with 96kHz. But when I try to use it in RNBO with 96kHz I can't select it in the export window or the web interface. So I guess the runner doesn't like 96kHz on a Raspberry Pi Zero 2 W?
That could be. It’s probably best to write to support directly.
It seems 48khz is the maximum sample rate available from the export side bar or from within the runner. If you want to set a higher sample rate you need to use OSC, as described here:
when you set the SR to 96k via OSC, can you then SSH over and share the logs?
journalctl -u rnbooscquery
The export sidebar might list 48k as the max but if your soundcard can handle 96k that OSC should work, you'll just then have to restart jack via OSC:
/rnbo/jack/restart
Thanks for all the answers!
96kHz is working fine via OSC. It just doesn't show in the export and the web interface. I wrote to the support and got the answer that this is expected behavior. I wrote a python skript that sends the OSC message after booting, so it's always automatically set to 96kHz now.
localhost works if you're on the RPI communicating locally, c74rpi.local should work if your device is called c74rpi and you're on some other computer and your router supports the .local domain.
Your audio settings should be saved between boots so I don't think you should have to run this post boot script once you've successfully setup your audio but it also shouldn't hurt.