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

Re: A proposal for how we would use the SDP that comes out of the MMUSIC interm

From: Peter Thatcher <pthatcher@google.com>
Date: Tue, 13 Oct 2015 07:55:45 -0700
Message-ID: <CAJrXDUHwwORNn8niwCDYX2Dn8Xkbuv3WaeCujgOXN4gidVzb9Q@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: Byron Campen <docfaraday@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Tue, Oct 13, 2015 at 7:19 AM, Cullen Jennings (fluffy) <fluffy@cisco.com>
wrote:

>
> > On Oct 9, 2015, at 10:14 AM, Byron Campen <docfaraday@gmail.com> wrote:
> >
> >> dictionary RTCRtpEncodingParameters {
> >>   double scale;  // Resolution scale
> >>   unsigned long rsid;  // RTP Source Stream ID
> >>   // ... the rest as-is
> >> }
> >    I am skeptical that a resolution scale is the right tool for
> "full/postage stamp", which is the primary use case for simulcast. A
> conferencing service is probably going to want to define the postage stamp
> as a fixed resolution (and probably framerate), not a scale of the full
> resolution that can slide around.
>
> I Agree.
>
> And we also need to deal with the case where the small is not even the
> same aspect ratio as the large as that is a very common use case. I think
> we need max width, max height and do our usual thing of fixing it to
> landscape mode and then using other things to deal with rotation.
>

​If you think RTCRtpEncodingParameters​

​should have a .maxWidth and .maxHeight, then make a PR and propose it on
the list.
Received on Tuesday, 13 October 2015 14:56:52 UTC

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