Re: Relation between a track's constraints/settings and how it is transmitted from Bernard Aboba on 2016-01-19 (public-webrtc@w3.org from January 2016)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Tue, 19 Jan 2016 15:16:28 +0000
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <BFF240C8-BB1E-4C34-A651-F784F11C7ACE@microsoft.com>

On Jan 19, 2016, at 1:49 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:
> 
> 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.

[BA] Constraints are applied to the track before it is input to the encoder. The encoder guidance is provided in RTCRtpEncodingParameters. This includes parameters.degradationPreference, parameters.encodings[j].resolutionScaleDownBy, maxFramerate, etc.

So I think you are asking about default values of the encoding parameters.

Received on Tuesday, 19 January 2016 15:16:58 UTC