- From: Jean-Yves Avenard <jya@mozilla.com>
- Date: Wed, 12 Apr 2017 20:35:58 +0200
- To: Mark Watson <watsonm@netflix.com>
- Cc: Harry Halpin <hhalpin@ibiblio.org>, "public-html-media@w3.org" <public-html-media@w3.org>
On Wed, Apr 12, 2017 at 12:39 AM, Mark Watson <watsonm@netflix.com> wrote: > Just for for the record, as one of the organizations driving this effort, > our rationale for this has nothing at all to do with the DMCA and everything > to do with improving the user experience: specifically plug-in free access > to our service and access to hardware decoders to improve battery life and > video quality. Improvement in security and privacy vs Silverlight is also a > benefit. That's really it: hardware decoders enabling 4K and soon HDR are a > big deal for us. This has been a lot of work for a technical refactoring > exercise. You got me curious... This may be off-topic but now that you've mentioned it. How is EME helping with the use of hardware decoder, 4K and/or support for HDR? The requirements for secure path after all limit Chrome and Firefox to a maximum of 720p resolution. And hardware decoding capabilities had to be removed precisely because of EME and vendor requirements. Note that I do not wish to participate in the current debate about EME. It would be rather inappropriate for me to do so.
Received on Wednesday, 12 April 2017 18:36:31 UTC