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

Issue 822762 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

[Regression] WebAudio fails in Chromebooks

Project Member Reported by rantonysamy@chromium.org, Mar 16 2018

Issue description

Chrome Version: 66.0.3359.31
OS: 10452.11.0
Connect a Headphones

What steps will reproduce the problem?
(1) Go to https://webrtc.github.io/samples/src/content/peerconnection/webaudio-input/ 
(2) Click on add local audio to output

What is the expected result?
Local audio has been played in the headset 

What happens instead?
Nothing has been played.

also, test.webrtc.org - fails in audio. Looks like a regression in M66.
 
Summary: [Regression] WebAudio fails in Chrmebooks (was: WebAudio fails in Chrmebooks )
Cc: maxmorin@chromium.org
Summary: [Regression] WebAudio fails in Chromebooks (was: [Regression] WebAudio fails in Chrmebooks )
Could you attach chrome:media-internals info? Copy all from the "Players" and "Audio" tabs.
Players tab added in the Link at #1, and audio tab is just empty. also attached a screenshot.
Cc: ossu@chromium.org grunell@chromium.org
+some people from the "no audio" team. Do you know how to get those neat text logs we get with customer feedback?
You'd have to do a Hangouts call. Maybe some basic tests here is in place. Have you checked the console output for example? Could this be the gesture requirement?
Uploaded both the logs during an hangout call, In-fact, during a hangout call there this problem does not raises. (we already have a user-input in the view, so call goes successful, there is audio).

If you use webaudio without an active user input, It fails (ex: test.webrtc.org) or the sample page given in the initial description. 
I think the root cause is because of the javascript error in few test pages. 

Javascript error: The AudioContext was not allowed to start. It must be resume (or created) after a user gesture on the page. https://goo.gl/7K7WLu

As Ravi mentioned it is not affecting any other webrtc apps.
  
Fix for this https://github.com/webrtc/samples/issues/1028 ticket should resolve it. This github issue has all the three sample pages which are affected by this issue. 
Tested in 66.0.3359.48 beta and works fine. Closing.
and I can't close the issue (unable to change the status)
Status: WontFix (was: Untriaged)
66.0.3359.67 (Beta M66) the issue present again. can you please check Its backported into the upstream ? 
#12 Same in Windows as well. 

Beta 66.0.3359.46 /10452.19.0 Windows 7 (Thinkpad lenovo), Windows 10 (Asus UX430x)

Sign in to add a comment