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

Issue 800712 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

[Minnie] Audio of the user is not clear and partially mute

Project Member Reported by vasanthakumar@chromium.org, Jan 10 2018

Issue description

Chrome Version: 10176.41.0 / 64.0.3282.79
OS: Chrome
Not reproducible in other chrome devices like Pit, Falco, Yuna. 

What steps will reproduce the problem?
1. Browse to https://webrtc.github.io/samples/src/content/peerconnection/webaudio-input/
2. Open the javascript console (alt+cmd+j or ctr+shift+j) and watch for any errors
3. Press Start
4. Start speaking, verify that you can hear yourself

What is the expected result?
Audio of the speaker should be clear. Upon enabling "Add local audio to output" audio of the speaker should enhance a bit. 

What happens instead?
Audio of my voice is not clearly heard. It does seem like partially muted while speaking. This kind of behavior happens when AEC3 is enabled but in this case flags are restore to default. It should not be like this. 


Tested with the following headphones.

Kingston HyperX Cloud II Gaming-headset
Corsair Gaming HS50 HeadsetĀ 
Plantronics Audio 648 Stereo USB Headset
Logitech Stereo Headset H151



 
This issue is reproducible in Gnawty when following the steps below.


0. Browse to https://webrtc.github.io/samples/src/content/peerconnection/pc1/
1. Open the javascript console (alt+cmd+j or ctr+shift+j) and watch for any errors
2. Press Start
3. Press Call
4. Verify that you see the same video in the local preview (left pane) and remote video (right pane)
5. Verify that you don't see any errors in the javascript console


same issue of muting partially. 
Owner: cychiang@chromium.org
Cc: maxmorin@chromium.org olka@chromium.org
Hi vasanthakumar, could you get the webrtc debug dump like 

https://bugs.chromium.org/p/chromium/issues/detail?id=747450#c7 ?

Also, this might be related to https://bugs.chromium.org/p/chromium/issues/detail?id=797272&desc=5

So, please be sure to test on an image that is late enough on R64 to include the fix

https://bugs.chromium.org/p/chromium/issues/detail?id=797272#c7

Thanks!
Owner: vasanthakumar@chromium.org
Owner: cychiang@chromium.org
Hi I have uploaded the logs and the audio files as requested (with a new folder Gnawty). Kindly have a look.

If you need any help feel free to ask me. 
@ Cychiang: 10176.41.0 / 64.0.3282.79
This issue is reproducible in Snappy device on both the weblinks 

(1. https://webrtc.github.io/samples/src/content/peerconnection/webaudio-input/)
(2. https://webrtc.github.io/samples/src/content/peerconnection/pc1/ )

Logs are attached in the same weblink provided at comment 1.

The same tests performed yesterday with the exactly same Chrome Os and build. It was working just fine. Today I am facing issues. There are possibility for a state bug. 
Labels: M-64
Partially muting issue seem to be available in Stout device as well. Follow the steps shown in the description of the bug. 

logs are attached in the same link with different folder. 

10176.41.0 / 64.0.3282.79 
In stout same issue while using this link as well. 

https://appr.tc/r/010198215?debug=loopback&audio=true&video=false

Comment 13 by peah@chromium.org, Jan 18 2018

Hi,
Looking at the aecdumps provided in #1 and #7 I get the feeling that you have both devices in the call in the same room. Is that correct? 

The reason why I think so is that I clearly hear the echo twice in the microphone signal. Or is there anything special in the setup that causes this?


Comment 14 by peah@chromium.org, Jan 18 2018

Owner: vasanthakumar@chromium.org
vasanthakumar@: I'm reassigning to the issue to you. Please describe how the setup was for the recording.


Hi@ Peah:

These testcases that I have provided are all performed in only one device and doesn't need two devices to perform. Its like a loop back call scenario. 

There is no special setup required. I used headphones in all scenarios and I have observed this behavior only in few device families and not all chromebooks. Just to avoid maybe headphones are causing this issue. Thus, I have repeated the same test with as many headphones I have. Thus headphones can be ruled out. 

When you make a call using any of the weblink, we should be able to hear our voice clearly. This is the expected behavior. 


Issue is in Minnie, Gnawty, Snappy, Stout as commented above. 

Regarding the voice heard clearly twice: This is the expected behavior if using the weblink in the description. Upon enabling "Add local audio to output" check box, audio of the speaker should enhance a bit. (if noticed well we can hear twice). This is not the issue I meant. We can clearly observe our voice is partially mute while speaking continuously. 


If you need any other assitance feel free to ask me anytime. 
This issue is reproduced in Pyro.


0. Browse to https://webrtc.github.io/samples/src/content/peerconnection/pc1/
1. Open the javascript console (alt+cmd+j or ctr+shift+j) and watch for any errors
2. Press Start
3. Press Call
4. Verify that you see the same video in the local preview (left pane) and remote video (right pane)


64.0.3282.101 / 10176.54.0  Pyro

Comment 17 Deleted

Comment #16, is that really related to this bug?
Vasan, could you retry on a Mac or Windows machine? The test page https://webrtc.github.io/samples/src/content/peerconnection/webaudio-input/ clearly states that Linux (ChromeOS is linux based) is not supported (not sure if that's true anymore though).
Yes thats the same issue of partially muted audio. If following the steps mentioned in comment 16, we can observe the audio issue quite clearly. 


Also I'm not sure what to expect in terms of audio on that test page, it applies a filter "HP filter with fc=1500 Hz" which probably explains why it sounds like this. 

Keep in mind this is a demo page for feeding a media stream into Webaudio and process it using Webaudio effects. 

Also adding local input to the output bypasses the filter hence why it sounds clearer: https://github.com/webrtc/samples/blob/gh-pages/src/content/peerconnection/webaudio-input/js/webaudioextended.js#L34-L41.

I think you can close this bug.
Status: WontFix (was: Assigned)
Ok Chris!

Sign in to add a comment