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

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

From: Jan-Ivar Bruaroey <jib@mozilla.com>
Date: Wed, 26 Aug 2015 18:03:15 -0400
To: Peter Thatcher <pthatcher@google.com>, Randell Jesup <randell-ietf@jesup.org>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <55DE37A3.301@mozilla.com>
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 
> <mailto: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() ?

.: Jan-Ivar :.
Received on Wednesday, 26 August 2015 22:03:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:08 UTC