- From: Peter Thatcher <pthatcher@google.com>
- Date: Fri, 18 Jul 2014 12:09:16 -0700
- To: Robin Raymond <robin@hookflash.com>
- Cc: "public-ortc@w3.org" <public-ortc@w3.org>
Received on Friday, 18 July 2014 19:10:23 UTC
I think we can until we run into real implementation issues. I have a feeling it won't be a big deal. On Thu, Jul 17, 2014 at 12:37 PM, Robin Raymond <robin@hookflash.com> wrote: > > dictionary RTCRtpEncodingParameters { > //... > double resolutionScale; > double framerateScale; > } > > These are floats with relative values. The trouble is that there are fixed > geometric relations. It must be 1.0, 0.5, 0.25, 0.125, etc for resolution > scaling… > > Maybe this isn’t an issue but I’m a bit concerned that float rounding > issues might cause us problems. > > For example, if you start at a base scale of 0.3 (i.e. resolution is 0.3 > of source), are the layerings relative to 0.3, i.e. (1/1 * 0.3), (1/2 * > 0.3), (1/4 * 0.3) ? > > or would the scale be like this: > 0.3, 1/1, 1/2, 1/4, 1/8, etc? > > Also if people use dividers vs fixed value like: 1/8 vs 0.125, could we > end up in situations where the values almost match but don’t quite due to > float rounding problems? > > > Just a concern… > > Robin > >
Received on Friday, 18 July 2014 19:10:23 UTC