New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2013
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

switching audio devices results in garbage audio with webrtc

Reported by tmiss...@gmail.com, May 7 2013

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31

Example URL:

Steps to reproduce the problem:
1. Launch Chrome, make a webrtc audio call
2. Switch output using system preferences sound applet to another source, usb based or bluetooth
3. make another webrtc call and audio will sound like garbage

What is the expected behavior?
Audio should switch without degrading 

What went wrong?
After switch audio output source without restarted Chrome, audio is degraded to the point of being unusable

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes Chrome stable, dev and canary versions on 5/6/2013

Chrome version: 26.0.1410.65  Channel: stable
OS Version: OS X 10.8.4

This works both ways, ie: if Chrome is launched with external audio source, usb based or bluetooth then the output is switched to the built in speakers ( macbook pro ) the sound from the built in speakers will then be degraded to an unusable state.
 
Labels: -Cr-Internals-Media Cr-Internals-WebRTC
Cc: tnakamura@chromium.org henrika@chromium.org vikasmarwaha@chromium.org braveyao@chromium.org
Labels: Needs-Feedback
@tmiss - can you try this again with the latest canary version? I'm not able to reproduce this with 29.0.1510.0, and I suspect that some recently submitted audio fixes might have helped improve this flow.
Project Member

Comment 3 by bugdroid1@chromium.org, May 24 2013

Labels: -Cr-Internals-WebRTC Cr-Blink-WebRTC
Status: WontFix
I'm closing this bug because there hasn't been an update in more than 2 weeks. @tmiss, you're welcome to reopen this issue, but please include results from the current dev channel build.

Comment 5 by ethan...@gmail.com, Apr 30 2015

Still happening: was playing a music video on youtube via bluetooth — sounded great. Then opened up a WebRTC app (appear.in) and quality immediately downgraded to crap status.

Changing the plist value to 100 didn't solve the problem.
defaults write com.apple.BluetoothAudioAgent "Apple Bitpool Min (editable)" -int 40

Chrome: 42.0.2311.90 (64-bit) on 10.10.3
#5 - can you file a new bug? This bug hasn't been touched in nearly 2 years, so what you're experiencing may have a different root cause. Thanks!
I don't think a new issue is needed since the described behavior is expected. Switching to a WebRTC client will change the audio mode to VoIP/Comm mode and it will reduce the audio quality to ensure that the BT profile can support full duplex audio. The volume icon will also change to a phone icon. It is the same QoS as for a phone call using BT on Android. Close the call and the volume icon will change to a media icon and the BT QoS will be improved back to normal again. And yes, the audio quality of the BT SCO audio profile is really bad.

Comment 8 by ethan...@gmail.com, May 13 2015

Thanks Henrika—is there are workaround? I have a brand new Bluetooth 4.0 device. Doesn't it have enough bandwidth for high quality full duplex?
So far as I know, OSX would force the BT headset working at 8kHz sampling rate for communication, which is one of the reason that it doesn't sound as good as wired sound devices. Unless you can see that BT device can work at higher sampling rate in AudioMIDISetup(in Utilities) on OSX, you won't expect anything much better.
My comment in #7 assumed Android. I missed that it was for Mac OS X. As is stated in #9, the full-duplex performance differs between BT devices but it will most likely switch to a much lower bandwidth in full-duplex compared with playout only. However, it should not "sound very bad" with glitches etc.

But to summarize: if you have perfect quality using a normal USB headset and bad quality using a BT headset, then the issue is not in Chrome but either in your audio settings or in the actual USB headset.
This is a really old and annoying problem.  Is it ever going to get fixed???
jerry@: could you please elaborate? Do you refer to a crash or a bad quality when using a BT headset? As mentioned, full duplex audio using BT will limit the quality compared to using BT for audio playout only.
This issue continues.  I go to use Uberconference on my Mac with Chrome.  I test the audio quality, it does not pick up my mic.  I have close Chrome completely, fiddle with my mic settings, and then open Chrome again.  Huge hassle.

Sign in to add a comment