New issue
Advanced search Search tips

Issue 889487 link

Starred by 1 user
Status: Assigned
Owner:
hbos@chromium.org
Cc:
hbos@chromium.org
hta@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
WebRTC-1.0-Spec-Compliance


Sign in to add a comment

Remote MediaStreamTracks should be unmuted when the first RTP packet arrives

Project Member Reported by hbos@chromium.org, Sep 26 
"Whenever an RTCRtpReceiver receives data on an RTP source whose corresponding MediaStreamTrack is muted, and the [[Receptive]] slot of the RTCRtpTransceiver object the RTCRtpReceiver is a member of is true, it MUST queue a task to set the muted state of the corresponding MediaStreamTrack to false."
https://w3c.github.io/webrtc-pc/

Current strategies have involved being unmuted by default or immediately unmuting for the sake of firing an event.
It should truly be muted by default.

Comment 1 by hbos@chromium.org, Sep 26 

One concern with the spec is that there could be a race between RTP packets arriving and a setRemoteDescription() call. I filed https://github.com/w3c/webrtc-pc/issues/1994

Comment 2 by guidou@chromium.org, Sep 26

Cc: hta@chromium.org
Owner: hbos@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by hbos@chromium.org, Dec 19

Labels: -Pri-3 Pri-2

Comment 4 by hbos@chromium.org, Dec 19 

This is important for early media.
►

Sign in to add a comment