W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > September 2019

[mediacapture-main] non-applicable constraints must be ignored for remote tracks (#619)

From: Ruslan Burakov via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Sep 2019 15:26:31 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-489232597-1567610789-sysbot+gh@w3.org>
kuddai has just created a new issue for https://github.com/w3c/mediacapture-main:

== non-applicable constraints must be ignored for remote tracks ==
In the presence of  ["Clarify what happens to non-applicable constraints"](https://github.com/w3c/mediacapture-main/pull/542) and 

> The basics of MediaTrackSupportedConstraints, MediaTrackCapabilites, MediaTrackConstraints and MediaTrackSettings is outlined in [GETUSERMEDIA]. However, the MediaTrackSettings for a MediaStreamTrack sourced by an RTCPeerConnection will only be populated with members to the extent that data is supplied by means of the remote RTCSessionDescription applied via setRemoteDescription and the actual RTP data. This means that certain members, such as facingMode, echoCancellation, latency, deviceId and groupId, will always be missing.

in https://w3c.github.io/webrtc-pc/#mediatracksupportedconstraints-mediatrackcapabilities-mediatrackconstraints-and-mediatracksettings

Should we just ignore such members as latency or echoCancellation on remote audio tracks instead of throwing OverconstrainedError? By remote audio tracks I mean track which is produced by [RTCRtpReceiver](https://w3c.github.io/webrtc-pc/#dom-rtcrtpreceiver). 

The issue is equally applicable to [w3c.github.io/webrtc-pc](https://w3c.github.io/webrtc-pc/) as it occurs on spec intersection. 

Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/619 using your GitHub account
Received on Wednesday, 4 September 2019 15:26:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:28 UTC