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

[bug] Microphone audio quality is worse in Windows vs. Chrome #576

Open
Unbreathable opened this issue Aug 17, 2024 · 2 comments
Open

[bug] Microphone audio quality is worse in Windows vs. Chrome #576

Unbreathable opened this issue Aug 17, 2024 · 2 comments

Comments

@Unbreathable
Copy link

Unbreathable commented Aug 17, 2024

Describe the bug

Hello, thanks for all your awesome work on LiveKit and making it available for Flutter. Today, I ran into quite the weird issue. Basically when I enter a call on Chrome the audio quality received by the other person sounds much better than when I use the Windows version of the example app provided in this repository. After some testing it seems that this problem mainly affects mono microphones since it doesn't happen with my web cam microphone.

To Reproduce

  1. Export the example app for both Windows and Chrome.
  2. Have someone else open either one and join the room.
  3. Join the room from Windows and try to speak with a mono (one channel) microphone.
  4. Now compare the audio quality to the audio quality you get when speaking through the Chrome version with the exact same microphone.

I've also recorded a video to illustrate the problem (because the video is over 100 MB, I couldn't upload it to GitHub):
https://www.youtube.com/watch?v=ngANWoGaAtA

Expected behavior

The audio should sound the same, no matter if I'm in Chrome or Windows.

Platform information

  • Flutter version: 3.24.0
  • Plugin version: 2.2.4
  • Flutter target OS: Windows, Chrome
  • Flutter target OS version: Windows 11
@cloudwebrtc
Copy link
Contributor

cloudwebrtc commented Sep 5, 2024

yeah, it sounds like the sampling rate is too low, will try to track that bug in native code.

@thameraltoimi
Copy link

Facing the same issue as well

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

3 participants