Relation between a track's constraints/settings and how it is transmitted from Stefan Håkansson LK on 2016-01-19 (public-webrtc@w3.org from January 2016)

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 19 Jan 2016 09:46:53 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B3744CE00@ESESSMB209.ericsson.se>

Hi,

reading the webrtc-pc spec, I can't find any text on the relation 
between a MediaStreamTrack's applied constraints/settings and how that 
track would be transmitted if added to a PeerConnection.

Is this an oversight or intentional?

It seems to me that it would be logical for a web author to expect, if a 
video track is constrained to e.g. a certain width, height and 
framerate, the UA to try (of course there are situations when it is not 
possible to fulfill the constraints - there may be network congestion or 
CPU limitations for example) to honor this if the track is transmitted 
to a peer using PeerConnection. But as I read the spec the UA is free to 
completely disregard the constraints that have been applied.

Stefan

Received on Tuesday, 19 January 2016 09:47:24 UTC