New issue
Advanced search Search tips

Issue 818743 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
hlundin@chromium.org
aleloi@chromium.org
rantonysamy@chromium.org
terelius@chromium.org
jansson@chromium.org
maxmorin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Audio gets muted when there are 3 or more peers in the webrtc call [Chrome only]

Project Member Reported by vasanthakumar@chromium.org, Mar 5 2018 
Chrome Version: 66.0.3356.0 /10443.0.0 Jaq, Squawks, Chell, Clapper 
OS: Chrome

What steps will reproduce the problem?
(1)Open hangouts or appear.in 
(2)Perform a group call [3 or more peers] -> [I used 2 chromebooks and a macbook]

What is the expected result?
Audio and video of the call is good. There should not be any audio/video related issues.

What happens instead?
As soon as the third peer joins the webrtc call, incoming audio to chrome books are muted. This happens instantly. 

Note: Similar tests are performed in Mac OS[M66 66.0.3355.0]. Mac device still can receive the incoming audio from chromebooks [peers]. 

Chromebooks does not receive any incoming sounds from its corresponding peers. [Tested in the devices: Jaq, Squawks, Chell, Clapper]. All four devices has this issue. 

Since this issue is related to the number of peers, this could be applicable for all webrtc apps that support multiple peers.

Comment 2 by vasanthakumar@chromium.org, Mar 5 2018 

These tests were performed with different headsets. Usage of headset does not impact with the results. It is because incoming audio is muted even after removing the headsets. 

Tested headsets:
Kingston HyperX Cloud II Gaming-headset
Corsair Gaming HS50 Headset 
Plantronics Audio 648 Stereo USB Headset
Logitech Stereo Headset H151
Steelseries Arctis 7 Wireless Gaming Heaset

Comment 3 by vasanthakumar@chromium.org, Mar 6 2018

Cc: terelius@chromium.org holmer@chromium.org sprang@chromium.org

Comment 4 by terelius@chromium.org, Mar 6 2018

Cc: -sprang@chromium.org -holmer@chromium.org hlundin@chromium.org aleloi@chromium.org maxmorin@chromium.org
Removing sprang@ and holmer@ as this is an audio issue. Adding some audio engineers instead.

Comment 5 by terelius@chromium.org, Mar 6 2018 

We suspect that this is a duplicate of a bug that has already been fixed. 

vasanthakumar@, could you add a link to the bug and mark this as a duplicate once it has been confirmed as fixed in the next dev/canary release.

Comment 6 by vasanthakumar@chromium.org, Mar 6 2018 

Thanks Terelius. I will close this as soon as I verify this in the later version.

b/73922571 (https://b.corp.google.com/issues/73922571).

Comment 7 by vasanthakumar@chromium.org, Mar 7 2018 

I just verified that this issue is not reproducible in 66.0.3359.10/10452.1.0 Jaq, Squawks, Chell, Clapper. 

Thus closing this ticket.

Comment 8 by vasanthakumar@chromium.org, Mar 7 2018

Status: WontFix (was: Untriaged)
►

Sign in to add a comment