Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No HDMI audio in Google Meet via Pipewire/PulseAudio on Bookworm #5950

Closed
mghadam opened this issue Feb 13, 2024 · 4 comments
Closed

No HDMI audio in Google Meet via Pipewire/PulseAudio on Bookworm #5950

mghadam opened this issue Feb 13, 2024 · 4 comments

Comments

@mghadam
Copy link

mghadam commented Feb 13, 2024

Describe the bug

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 this GitHub thread 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 (s)

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 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux

Logs

No response

Additional context

No response

@popcornmix
Copy link
Collaborator

This doesn't sound like a kernel issue to me, but we'll leave it here until more information is found.
@cillian64 any thoughts?

@qrp73
Copy link

qrp73 commented Feb 16, 2024

here is the same issue: raspberrypi/bookworm-feedback#205

@pelwell
Copy link
Contributor

pelwell commented Feb 16, 2024

Discussion can continue on the new thread.

@pelwell pelwell closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2024
@mghadam
Copy link
Author

mghadam commented Feb 16, 2024

here is the same issue: raspberrypi/bookworm-feedback#205

It is not the same issue, here we do not have any output audio in Google meet while other programs or websites have outgoing audio.

I opened a new feedback at raspberrypi/bookworm-feedback#211 to see if we get more information on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants