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

Issue 591842 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Cannot mute the remote audio stream using WebRTC API

Reported by pan.dev....@gmail.com, Mar 3 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Example URL:
https://thinclient13.webex.com/meet/beshe

Steps to reproduce the problem:
1. Join WebEx meeting through Chrome browser.
2. Join Audio.
3. Click the icon (3 dots icon in menu bar) to mute the local speaker. 

What is the expected behavior?
You should not not hear remote audio

What went wrong?
You can still hear remote audio even when local speaker is muted. Even when the Audio track which is WebRTC audio object "enabled" property is false.

Did this work before? Yes version 47 Chrome Stable worked fine

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 49.0.2623.75  Channel: stable
OS Version: 7
Flash Version: Shockwave Flash 20.0 r0

In order to reproduce this problem, one need to join first as host though a regular WebEx PC client, and then the participant can join as browser client. 

please reach out either to beshe@cisco.com(Benrui She) or tusingh@cisco.com(Tushar Singh) in order to reproduce this issue. You can also reach out to niklase@google.com(Niklas Enbom) at Google regarding this issue.
 
chrome_mute_speaker.png
29.9 KB View Download
Cc: niklase@chromium.org hta@chromium.org tommi@chromium.org
Components: -Internals>Media Blink>Webrtc>GetUserMedia

Comment 2 by tommi@google.com, Mar 3 2016

If I understand correctly, this doesn't work as expected in 48 and later.  Can someone confirm?
Cc: jansson@chromium.org
I can't seem to figure out how to sign up for an account in a way that lets me host meetings. I went through the signup flow at https://thinclient13.webex.com/mw3100/mywebex/register.do, but I saw some message about requiring admin approval before my account could be created.

Does anyone have a more isolated test/sample page (e.g. jsfiddle) we can use to reproduce and debug this issue?
Hi Tommi,

That's correct , it works on chrome bersion 47 and below but not on 48 and above. We got to test the older version from here - https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/352221/

Hi Ted,

We got your account request. We are in the process of updating our Conference servers. Once that is done, we will get you an account on the site for you to test it. Thanks for holding on and apologies for delay

-Tushar


Cc: tnakamura@chromium.org guidou@chromium.org srnarayanan@chromium.org
Labels: Needs-Feedback
tnakamura: please share your account with srnarayanan when you've received it, so this can be tested.

guidou: is this a test that we can add?

Comment 6 by hta@chromium.org, Mar 7 2016

By accident, I found a number of tests that do muting in content_browsertests:

content/browser/media/webrtc/webrtc_browsertests.cc

EstablishAudioVideoCallAndVerifyRemoteMutingWorks
EnsureLocalVideoMuteDoesntMuteAudio

and so on. These pass in bots.
Check that we agree on what "remote mute" means.



tnakamura, I have a test account you can use.
tnakamura: We have added your account on the site. You should receive the mail regarding this.

1. If you can access and login, you should be able to join as host to the site (click on Log In button on far right and enter credentials). 

2. Once you do that, go to Meeting Center tab and join your personal room from Mac or Windows. This will launch the Webex PC client Enable audio and video.

3. Now from another machine go to https://thinclient13.webex.com

4. Enter your user name for account and click Join

5. Join WebEx meeting through Chrome browser (it should say Beta).

6. Join Audio.

7. Click the icon (3 dots icon in menu bar) to mute the local speaker. from Webex PC client.

Expected result - You should not hear remote audio
Actual result - You can still hear remote audio

It works on chrome version 47 and below but not on 48 and above
Project Member

Comment 9 by sheriffbot@chromium.org, Mar 10 2016

Labels: -Needs-Feedback Needs-Review
Owner: kjellander@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "kjellander@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Hi,

Has there been any update on this? 
Owner: ----
Status: Unconfirmed (was: Assigned)
Oh, it's unfortunate this was assigned to me (that's not how our WebRTC triage process works) since I've been busy (and missed following up on this).

Ted: can you take a look? 
Labels: -Needs-Review Needs-Feedback
I think we need a clearer repro case. I did a simple test page by modifying https://webrtc.github.io/samples/src/content/peerconnection/audio/. I extract the audiotrack from the remote stream, set enabled to false, and it mutes correctly in Chrome 51. Attaching sample code (you need  --disable-web-security --allow-file-access-from-files to run locally)
audio.zip
5.7 KB Download
Here's another example of remote working, this time with https://appr.tc:

1) Join a two party AppRTC call
2) Open the js console
3) Enter this command to mute remote (aka incoming) audio:
document.querySelector('#remote-video').srcObject.getAudioTracks()[0].enabled = false;

4) and to unmute:
document.querySelector('#remote-video').srcObject.getAudioTracks()[0].enabled = true;

Those steps work for me - the remote audio is muted (and unmuted) as expected.

(separately, kjellander@ asked for webex credentials. I've shared those internally; please search for "webex" in valentine)
Status: WontFix (was: Unconfirmed)
It's been nearly a month since niklase@ posted his follow up, and there hasn't been any replies from the original bug reporter. Because of that, and the fact that this doesn't repro with apprtc (comment #13), I'm going to close this issue.

I'm willing to reopen it, though, if a smaller/isolated test page is presented that demonstrates the bug. :)
Components: -Blink>Webrtc>GetUserMedia Blink>GetUserMedia

Sign in to add a comment