search

balena-io-experimental / balena-sound

Build a single or multi-room streamer for an existing audio device using a Raspberry Pi! Supports Bluetooth, Airplay and Spotify Connect
https://balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/
MIT License
2.39k stars 427 forks source link

No audio from Raspberry pi 4 or Zero 2 W #647

Open audas opened 9 months ago

audas commented 9 months ago

No Audio from Raspberry Pi 4 through HDMI, Heaphones, or DAC board

No Audio from Raspberry Pi 2 Zero Wireless HDMI

I am using latest version flashed directly from cloud.

I have tested with HDMI output set to 2, I have removed DT overlay settings as advised, and tested with RPI_HEADPHONES, RPI_AUTO, RPI_HDMI0

I have tested with PI 4 b+ with IQaudIO Pi-DigiAMP+ BALENA_HOST_CONFIG_dtoverlay=iqaudio-dacplus,unmute_amp

This same problem had previously occurred and was claimed to have been fixed however is still returning.

 audio  W: [pulseaudio] module-loopback.c: Cannot set requested sink latency of 66.67 ms, adjusting to 99.95 ms
 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

It looks like this product is dead and no longer being updated? Mosat of the threads I am seeing now are showing people giving up on this project and it seems so strange that there has been nothing addressed on this issue now for almost 2 years.

audas commented 9 months ago

Ok - so the issue is that HDMI audio ONLY is not supported by many recievers without ARC (eARC) and so we must force the hdmi_force_edid_audio option. This really needs to be made clear as the number of requests for (NO AUDIO on HDMI) is related to this.

Perhaps just add this as an option in cloud as I struggled to get this into the vaiables as I was not aware we could do this using "RESIN_HOSTCONFIG" as a prefix - this should probably also be added as an asterixed addendum.

Now working.