Remote WebRTC MediaStream does not work with WebAudio
Reported by
ulti...@gmail.com,
Jan 22 2017
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36
Example URL:
Steps to reproduce the problem:
1. Create a WebRTC connection with an audio stream from microphone i.e. getUserMedia({audio: true}), that goes to a remote tab/page context on the same machine (i.e. do not just simulate WebRTC connection on the same page, it needs to connect to a different page)
2. Create a web audio context, do context.createMediaStreamSource(remoteMediaStream), connect it to destination.
3. No output, the remoteMediaStream seems to be all zeros if you analyze it
What is the expected behavior?
The remoteMediaStream should be output to web audio as if it were local. It should not analyze as all zeroes.
What went wrong?
I think this is related to https://bugs.chromium.org/p/chromium/issues/detail?id=121673, but it's a bit different: the audio stream works if you simulate WebRTC within the same page. So you will not reproduce it with https://webrtc.github.io/samples/src/content/peerconnection/webaudio-output/. It seems to only be broken when you are actually routing the WebRTC media stream through the network.
I was able to get the remote media stream playing via URL.createObjectUrl(), so I know it's not a WebRTC problem. Also, playing a local mic MediaStream via WebAudio also works just fine. It seems to be a bad interaction between remote WebRTC and WebAudio.
Did this work before? No
Is it a problem with Flash or HTML5? N/A
Does this work in other browsers? N/A
Chrome version: 55.0.2883.95 Channel: stable
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0
Contents of chrome://gpu:
,
Jan 23 2017
Could you please help with sample url/jsfiddle to triage from Chrome TE side along with the detailed steps.
,
Jan 24 2017
,
Jan 25 2017
,
Feb 27 2017
No feedback was received in the last 30 days from reporter "ultimus@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ulti...@gmail.com
, Jan 22 2017