W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2015

Re: Al PR for adding various fields to RtpParameters and RtpEncodingParameters

From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 26 Aug 2015 15:14:11 -0700
Message-ID: <CAJrXDUHtTdXfkWDBBbBPvNcRK=RB1o5ySrQaC0qUo=xrCznZBA@mail.gmail.com>
To: Jan-Ivar Bruaroey <jib@mozilla.com>
Cc: Randell Jesup <randell-ietf@jesup.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Wed, Aug 26, 2015 at 3:03 PM, Jan-Ivar Bruaroey <jib@mozilla.com> wrote:

> On 8/25/15 9:43 PM, Peter Thatcher wrote:
>
> On Tue, Aug 25, 2015 at 6:34 PM, Randell Jesup <randell-ietf@jesup.org>
> wrote:
>
>> On 8/24/2015 6:01 PM, Peter Thatcher wrote:
>>
>> maxFramerate can be accomplished with a gUM constraint, so I don't think
>> it's needed on the RtpSender.
>>
>>
>> Not all sources come from gUM (video.captureStream() for example, or
>> canvas.captureStream(), or even another PeerConnection, etc).  Also, a
>> stream may have more than one consumer with different needs.  (On a side
>> note, I was surprised looking at some stats that show a non-trivial number
>> of peerconnections are carrying 60fps video.)
>>
>>
> I
> ​ t still seems like it's a transformation on the track we really want to
> have.  Tell the track to control its framerate.  It's probably more
> efficient that way anyway for things like canvas.
>
>
> In other words, use track.applyConstraints() on a track from
> video.captureStream() and canvas.captureStream() ?
>
>
​Yes



> .: Jan-Ivar :.
>
>
Received on Wednesday, 26 August 2015 22:15:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:45 UTC