RPI3B or RPI4 -> No sound whatsoever

[Mehrdadg]

Hi I am new to this BalenaSound but I have been trying for the past many hours to get BalenaSound working on multiple RPIs without any success. I have tried all the trick that was able to find googling (forcing audio to HDMI, 3.5mm jack, deleting vc4-fkms-v3d on Rpi3, ...) and none so far fixed my issue.

I use the cloud app to create an image (for both RPI3 and 4) and go through installing without any issues. I can use my ipad and see the newly configured BalenaSound in my Airplay menus and when I select it, it connects without any issues but there is no sound (yes I even tried increasing the sound on IPAD to max as someone had suggested).

not sure what these warning mean but I figure I post them as it may give rise to some clue on the issue: airplay warning: could not acquire a Shairport Sync native D-Bus interface "org.gnome.ShairportSync.i7" on the system bus. airplay warning: could not acquire an MPRIS interface named "org.mpris.MediaPlayer2.ShairportSync.i7" on the system bus.

audio Setting audio routing rules... audio Routing 'balena-sound.input' to 'snapcast'. audio Routing 'balena-sound.output' to 'alsa_output.bcm2835-jack.stereo-fallback'. audio W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). audio W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 audio W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 172.30.6.117:4317 sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 172.30.6.117:4317 sound-supervisor Connected to PulseAudio at 172.30.6.117:4317 sound-supervisor Server protocol version: 35 sound-supervisor Client protocol version: 33 sound-supervisor Playback started, announcing 172.30.6.117 as multi-room master! sound-supervisor Joining the fleet, requesting master info with fleet-sync...

Anyhow, it looks like a pretty good software but for the life of me I can't get it to work as I get no sound either from HDMI port or 3.5mm jack. By the way I tried the following as well:

open a terminal to the ‘spotify’ container and run install_packages alsa-utils. After that completes you can run speaker-test -c2 -t wav to test the output ----> Results is that I hear audio from the HDMI port

Any help is greatly appreciated. thanks

[achochia]

Can confirm same warnings on 2 fresh 32Bit BalenaSound installs on Raspberry Pi 3b+, and on a Raspberry Pi ZeroW with a supported DAC, and no audio on any of the devices. Been having these issues with the newest version and even using the older 2.38.0 rev1 on my 3B+. Attempts with a 64Bit OS had the same issues, and no fixes specified online helped.

[Mehrdadg]

Achochia- The error messages I posted earlier are from fresh install on RPI3B+. I don't have RPI ZeroW to try and don't have DAC. I am just relying on the Headphone Jack from the RPIs and/or HDMI outputs. one issue that was raised along ago was related to 64b OS on RPI3 which the recommendation was to remove "vc4-fkms-v3d" from the device which did nothing for me.

Also below is a new message from the audio container:

audio Routing 'balena-sound.input' to 'snapcast'. audio Routing 'balena-sound.output' to 'alsa_output.bcm2835-hdmi0.stereo-fallback'

Wondering if I should go back in many revisions to see if this clears things up!

[achochia]

Im just adding more devices and variations to the mix. I had used BalenaSound for years now and this is the first time a fresh install gives me this much headache. I had a working version from a build in September, which correspond to tag ca96642. I think ill try to fork that revision and attempt from there.

[TurtleRad]

I would suggest merging this with #543 and #542 … Seems some update here or elsewhere is breaking the audio outputs on RPi.

[Maximus48p]

Confirm no sound output 3.5mm jack on Pi3b+ with AUDIO_OUTPUT on RPI_HEADPHONES. version 2.83.21+rev1 and 12.11.30.

Starting audio service with settings: audio - pulseaudio 15.0 audio - Pulse log level: NOTICE audio - Default output: RPI_HEADPHONES audio - Default volume: 75% audio
audio Detected audio cards: audio 0 bcm2835-jack bcm2835_headpho-bcm2835Headphones audio
audio
audio Setting audio routing rules... audio Routing 'balena-sound.input' to 'balena-sound.output'. audio Routing 'balena-sound.output' to 'alsa_output.bcm2835-jack.stereo-fallback'. audio W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). audio W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 audio W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[Patrick114]

Having this issue as well, rolling back to 3.6.19 fixed it

[Mehrdadg]

Stupid question... I looked everywhere to see how I can downgrade to version 3.6.19 but I don't see this option available to me. this is what I see...

HOST OS VERSION balenaOS 2.83.21+rev1

production SUPERVISOR VERSION 12.10.3

Any hint is greatly appreciated. thanks

[tmigone]

Should be fixed by https://github.com/balenalabs/balena-sound/pull/547, update to v3.8.4 to get the fix!

[jellyfish-bot]

[tmigone] This issue has attached support thread https://jel.ly.fish/7802acc7-97a3-403e-80a8-3b04ba4b5640

[jellyfish-bot]

[tmigone] This issue has attached support thread https://jel.ly.fish/a3ebe05e-5cb6-4bf9-b565-08dcdb8f52c9

[jellyfish-bot]

[tmigone] This issue has attached support thread https://jel.ly.fish/afe98d55-077b-4900-a513-0be544ba4fa2

[jellyfish-bot]

[tmigone] This issue has attached support thread https://jel.ly.fish/9f909c7b-fc11-41b3-a885-2dfbf9e33d18