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

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

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Sep 2019 21:22:27 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-528092689-1567632145-sysbot+gh@w3.org>
This was [recently](https://github.com/w3c/mediacapture-main/pull/594) clarified by [this note](https://w3c.github.io/mediacapture-main/getusermedia.html#media-track-supported-constraints): *"The constraints specified in this specification apply only to instances of MediaStreamTrack generated by getUserMedia(), unless stated otherwise in other specifications."*

For example, [mediacapture-screen-share](https://w3c.github.io/mediacapture-screen-share/#constrainable-properties-for-captured-display-surfaces) specifies the constrainable properties of tracks from `getDisplayMedia()`, and [how](https://w3c.github.io/mediacapture-screen-share/#downscaling-and-frame-decimation) to implement them.

In other words, it is up to webrtc-pc to specify what constraints remote tracks have. This is being discussed in https://github.com/w3c/webrtc-pc/issues/2121.

> should we just ignore such members as latency or echoCancellation on remote audio tracks

FWIW, about those members specifically, [webrtc-pc](https://w3c.github.io/webrtc-pc/#mediatracksupportedconstraints-mediatrackcapabilities-mediatrackconstraints-and-mediatracksettings) already says: *"This means that certain members, such as facingMode, echoCancellation, latency, deviceId and groupId, will always be missing."*

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/619#issuecomment-528092689 using your GitHub account
Received on Wednesday, 4 September 2019 21:22:32 UTC

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