Issue metadata
Sign in to add a comment
|
WebRTC uses wrong audio device to output audio
Reported by
ateyh...@skorozvon.ru,
Dec 5 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: I fill this issue as continuation of issue https://bugs.chromium.org/p/chromium/issues/detail?id=604523 which was fixed in the past year but appears again What is the expected behavior? Chrome should use default audio playback device. What went wrong? Chrome uses non default audio playback devices in webrtc sites. In my case default device is "Logitech USB Headset H340", but chrome choose "Realtek digital output". Did this work before? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 28.0 r0
,
Dec 5 2017
Thank you for reply. Communication device is also same as default. I added screenshot with my settings.
,
Dec 5 2017
In previously mentioned issue new comments also show same trouble.
,
Dec 5 2017
Could you share your audio recording settings as well - how the mic is configured?
,
Dec 5 2017
Anything which will help to solve the issue. Hm, may be this is the cause - I use different input and output devices (because mic on my logitech is broken), and chrome selects corresponding output device for my recording device?
,
Dec 5 2017
,
Dec 5 2017
Are you able to reproduce the issue using appr.tc? If not, which webrtc site do you experience a problem with? Could you start a webrtc call there, then open chrome://webrtc-internals/ and capture GetUserMedia info from there?
,
Dec 5 2017
guidou@ - could you PTAL?
,
Dec 6 2017
Yes, it's absolutelly reproducable using appr.tc. Here is screenshot.
,
Dec 6 2017
Unable to reproduce the issue on Win-10 using chrome reported version #62.0.3202.94 and latest canary #65.0.3286.0. Attached a screenshot for reference. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to https://appr.tc/ and joined to enter a session. 2. Opened sound settings on windows. 3. Observed that chrome used default audio playback device as expected. ateyhrib@ - Could you please check this issue on latest canary #65.0.3286.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. The latest chrome builds can be downloaded from the below URL: https://www.chromium.org/getting-involved/dev-channel Thanks...!!
,
Dec 6 2017
On latest canary everything is ok. Also I've noticed that after chrome restart everything become ok in stable release. And I thinked about usb devices and tried to plug different devices, but everything works as expected. Looks strange.
,
Dec 6 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 6 2017
Hm, appr.tc is now working, but our service skorozvon.ru isn't. How can I debug the issue?
,
Dec 7 2017
Tried testing the issue by navigating to https://skorozvon.ru/ but it seems the site accepts only regional(russian) numbers. ateyhrib@ - Could you please provide test credentials/number to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Dec 7 2017
Sent login/pass in pm. Strange, but our service now is also working correctly on the same machine - nothing changed from the previous test, even I didn't restart chrome.
,
Dec 7 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 7 2017
,
Dec 8 2017
Ok, thanks for investigation, will look further in the mentioned issue |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by olka@chromium.org
, Dec 5 2017