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

Issue 640286 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Audio channels get merged when sent over WebRTC PeerConnection

Reported by kylepetr...@gmail.com, Aug 23 2016

Issue description

Chrome Version       : 52.0.2743.116
OS Version: OS X 10.11.6
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Create a multi channel audio track.
2. Send audio track through PeerConnection via MediaStream
3. Receive stream, playback audio.

What is the expected result?
Channels on audio track remain intact.

What happens instead of that?
Channels on audio track have been merged.

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

A demo of this can be found here: https://kpetrovi.ch/samples/src/content/peerconnection/webaudio-channels/

Toggle the source audio to hear what I'm trying to send. Toggle the received audio to hear what I'm getting. Headphones recommended for greatest effect.

 
FWIW: I was able to get the expected results in FF v49 (currently beta).
Components: Blink>WebRTC>Audio
Labels: -OS-Mac OS-All

Comment 3 by ajha@chromium.org, Aug 25 2016

Cc: perkj@chromium.org ajha@chromium.org
Labels: -Type-Bug -Pri-3 M-54 hasbisect Pri-1 Type-Bug-Regression
Owner: tommi@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this on the latest canary(54.0.2839.0) and the latest stable(52.0.2743.116) on Mac OS 10.11.6 as per the attached Demo.

This is regressed in M-49.

Last good build: 49.0.2589.0
First bad build: 49.0.2590.0

Changelog:
==========
https://chromium.googlesource.com/chromium/src/+log/2c35494313065bb6d07ef80bb5c4dbf319cc109f..9c249ae0e2b69e5bed744e958e08cb0adbb82e6f

Webrtc changelog:
=================
https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/1961b16..387e90b

Suspected change: https://codereview.webrtc.org/1505253004

tommi@: Could you please take a look at this.

Thank you!
tommi@ this sounds like it's a caveat of the current implementation as you describe in https://bugs.chromium.org/p/chromium/issues/detail?id=121673#c102, is that right?
ping
Just checking on the status of this. Is this still scheduled for release 54? Thanks so much.

Comment 7 by tommi@chromium.org, Oct 2 2016

kylepetrovich: Are you turning off audio processing in your call to getUserMedia?  If no, try setting echoCancellation=false.  With audio processing turned on, stereo will be down mixed to mono.
Labels: -M-54 Needs-Feedback

Comment 9 by tommi@chromium.org, Jan 16 2017

Status: WontFix (was: Assigned)
Closing due to no feedback. I assume that this was because of using audio processing.

Comment 10 by goo...@imeus.com, Apr 5 2018

I have the same issue. The issue doesn't seem resolve even echoCancellation=false

Sign in to add a comment