rnbo raspberry pi 3B+ no sound problem
Hi,
I exported a rnbo patch to raspberry pi but got no sound.
my environment:
raspberry pi 3B+
raspios-bullseye-armhf-rnbooscquery_1.0.0
Max 8.5.1
my rnbo test patch:
raspi-config shows there are 3 sound cards:
but AUDIO CONFIG shows there are only 2 sound cards:
hw:0 Dummy
hw2: vc4-hdmi
if set the umenu to "hw:0", I can export to pi successfully but no sound,
set the umenu to "hw:2" throws an error "rnbo cmd response error: {"code":5,"message":"cannot activate audio"}"
since I want to use pi's headphone as audio output but it is not listed in AUDIO CONFIG patch, I tried to set it manually: "hw:1", also get the error "rnbo cmd response error: {"code":5,"message":"cannot activate audio"}".
thanks for any help!
We've explicitly disabled the bcm2835 (rpi built in audio) because it had/has issues though I haven't checked back since we updated from buster to bullseye so I'll add a ticket to check into that. In the mean time, your best bet is to use a USB audio interface.
Thanks Alex! Replaced with a usb audio interface and it worked without a hitch.
Dear all,
Any update on this?
I aim to use the inbuilt headphone socket of the RPI 4B. I own already three USB Audio Interfaces and they are all not ALSA compliant. I would like to avoid needing to buy a fourth USB audio interface. Additionally, I plan to remain small in size too.
After some manual reviewing, I uncommented the
dtparam=audio=on
in the config.txt on the pi. But it seemed that it was already uncommented.
I also created a asoundrc file with
defaults.pcm.card 0
defaults.pcm.device 0
defaults.ctl.card 0
It showed the hw:1 in the max rpi-configure-audio patch but I still got the same error:
rnbo cmd response error: {"code":5,"message":"cannot activate audio"}
I am now thinking of getting a PI DAC+ but am a little worried with the connection compatibility, since I already have some sensors connected over a breakout cable and the DAC+ goes exactly on the same socket. I am sure the DAC+ will be compatible and have some pins left. Nevertheless, some advice would be helpful.
I run the latest 1.1.0 version of RNBO and I sudo upgrade + update the RPI.
Thoughts? Ideas? Directions?
Many thanks!
I've found that when exporting rnbo patches to the rPi, it's best to disconnect all usb devices except the usb audio interface. Because sometimes rPi also recognizes other usb devices as audio interfaces. And make sure to select the correct Audio: Interface under Configuration in rnbo export target settings.
Today I had the same {"code":5,"message":"cannot activate audio"}" problem, which I solved after selecting Audio Output in System Options /Audio, using sudo raspi-config command.
So far, I think this "cannot activate audio" issue is my biggest headache when exporting rnbo to rPi, sometimes it feels like it happens randomly.
Does anyone know if it's now possible to use the headphone output of the RaspberryPi rather than an interface? Any time I compile I receive the error 'cannot activate audio' despite having set it in raspi-config. Thank you!
Same situation here as well, was trying out monome's grid studies with my v3 model B and continually got errors when trying to export using the headphones interface.
Tried Ayrtbh's advice on matching up raspi-config to what was selected in the export interface in RNBO, and still get "Could not activate runner's audio, please check your audio configuration settings". Looks like USB interface may be the only route for now.
It looks like there is a bug in the export sidebar that isn't showing the "extra args" that you need to do this, but you can use the RNBO Web interface. Go to the audio settings and add this entry to "Extra Args" -i 0 -o 2
You'll want to select "hw:Headphones" for your interface (I don't have that here). I've found that you also need a relatively big "Period Frames" for the headphones, something like 512 or more.
