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

[mediacapture-main] Width and height of MediaStreamTrack (#647)

From: guest271314 via GitHub <sysbot+gh@w3.org>
Date: Sun, 01 Dec 2019 18:03:39 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-530769615-1575223417-sysbot+gh@w3.org>
guest271314 has just created a new issue for https://github.com/w3c/mediacapture-main:

== Width and height of MediaStreamTrack ==
**Question**

> [5. The model: sources, sinks, constraints, and settings ](https://w3c.github.io/mediacapture-main/#the-model-sources-sinks-constraints-and-settings)
> 
> Note that `MediaStream` sinks (such as `<video>`, `<audio>`, and even `RTCPeerConnection`) will continue to have mechanisms to further transform the source stream beyond that which the `Settings`, `Capabilities`, and `Constraints` described in this specification offer. (The sink transformation options, including those of `RTCPeerConnection`, are outside the scope of this specification.)

Occasionally the first frames of a `MediaStreamTrack` set as `srcObject` of an HTML `<video>` element can have `width` and `height` displayed that is less than the underlying encoded frame `width` and `height` (https://github.com/web-platform-tests/wpt/pull/19030#discussion_r344963902). Does that case fall under "are outside the scope of this specification"?





Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/647 using your GitHub account
Received on Sunday, 1 December 2019 18:03:40 UTC

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