search

raspberrypi / bookworm-feedback

13 stars 1 forks source link

No audio in Google Meet #211

Open mghadam opened 7 months ago

mghadam commented 7 months ago

Google Meet fails to output audio on Raspberry Pi running Bookworm. Despite successful speaker tests within Google Meet settings, no audio is heard through the TV speakers via HDMI. Interestingly, other platforms like Jitsi Meet provide audio output via HDMI, and VLC functions properly with audio playback.

The issue persists when using Firefox as well. Switching from the default Pipewire to PulseAudio in raspi-config does not resolve the problem.

Attempts to resolve the issue by changing the default args.AES3 parameter as suggested in https://github.com/raspberrypi/linux/issues/5525#issuecomment-1615922687 from 0x02 to 0x01 and rebooting proved unsuccessful.

Analog audio has been disabled via dtparam=audio=off, and the default audio device is set to HDMI by right clicking on the speaker icon on top right side of the desktop.

Interestingly, swapping the SD Card to Debian Bullseye and conducting the same Google Meet session on Debian 11 results in functional HDMI audio without any issue.

Steps to reproduce the behaviour

  1. Connect a Raspberry Pi running Bookworm to a TV via HDMI and attach a USB camera with a microphone.
  2. Open Google Meet in Chrome or Firefox on the Raspberry Pi.
  3. Add another participant to the meet session.
  4. The participant's audio cannot be heard on the Raspberry Pi.

Device Raspberry Pi 4 Mod. B

System Raspberry Pi reference 2023-12-05 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 70cd6f2a1e34d07f5cba7047aea5b92457372e05, stage5

version 30f0c5e4d076da3ab4f341d88e7d505760b93ad7 (clean) (release) (start)

Linux home.domain.local 6.1.0-rpi8-rpi-v8 https://github.com/raspberrypi/linux/issues/1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux

lurch commented 3 months ago

ping @cillian64 in case he has any ideas. Is this still a problem with a fully up-to-date Bookworm image @mghadam ?

cillian64 commented 3 months ago

Nothing obvious springs to mind. It's a pretty weird set of constraints, that it's not specific to a browser nor to pipewire/pulse, but only happens for Google Meet. But I've had some annoying camera breakages with Meet playing fast-and-loose with the MediaDevices API so it could be something similar.

Have you been able to test Google Meet with either the analog audio jack or bluetooth speaker/headphones? Would be interesting to know whether the problem is specific to HDMI.

Even though it's not specific to pipewire, it's worth checking if there are any obvious errors in the pipewire or wireplumber logs (journalctl --user -u pipewire --boot, journalctl --user -u wireplumber --boot). Also if there's anything in dmesg.