Encrypted Media Extensions
Encrypted Media Extensions (EME) is a W3C draft specification for providing a communication channel between web browsers and digital rights management (DRM) agent software.[1] This allows the use of HTML5 video to play back DRM-wrapped content such as streaming video services without the need for third-party media plugins like Adobe Flash or Microsoft Silverlight. The use of a third-party key management system may be required, depending on whether the publisher chooses to scramble the keys.
EME is based on the HTML5 Media Source Extensions specification,[2] which enables adaptive bitrate streaming in HTML5 using e.g. MPEG-DASH with MPEG-CENC (Common Encryption) protected content.[3][4]
EME has been highly controversial within the W3C, because it places a necessarily proprietary, closed component into what might otherwise be an entirely open and free software ecosystem.[5]
Support
In April 2013, on the Samsung Chromebook, Netflix became the first company to offer HTML5 video using EME.[6]
As of 2016[update], the Encrypted Media Extensions interface has been implemented in the Google Chrome,[7] Internet Explorer,[8] Safari,[9] Firefox,[10] and Microsoft Edge[1] browsers.
While backers and the developers of the Firefox browser were hesitant in implementing the protocol for ethical reasons due to its dependency on proprietary code,[11] Firefox introduced EME support on Windows platforms in May 2015. Firefox's implementation of EME uses an open-source sandbox for the Adobe Primetime CDM, which is treated as a plug-in that is downloaded when EME-protected content is requested. The sandbox was also designed to frustrate the ability for services and the DRM to uniquely track and identify devices.[10][12]
Netflix supports HTML5 video using EME with a supported browser: Chrome, Firefox,[13] Microsoft Edge, Internet Explorer (on Windows 8.1 or newer[14]), or Safari (on OS X Yosemite or newer).[15]). YouTube supports the HTML5 MSE.[16] Available players supporting MPEG-DASH using the HTML5 MSE and EME are THEOplayer[17] by OpenTelly, the bitdash MPEG-DASH player,[18][19] dash.js[20] by DASH-IF or rx-player.[21]
Version 4.3 and subsequent versions of Android support EME.[22]
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references> tag; parameter "group" is allowed only.
<references />, or <references group="..." />See also
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ HTML5 MSE
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.dash-player.com/blog/2015/02/the-status-of-mpeg-dash-today-and-why-youtube-and-netflix-use-it-in-html5/ THE STATUS OF MPEG-DASH TODAY, AND WHY YOUTUBE & NETFLIX USE IT IN HTML5 & BEYOND
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Mozilla begrudgingly brings Netflix support to Linux with DRM in Firefox
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Netflix system requirements for HTML5 Player and Silverlight
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ THEOplayer by OpenTelly: HLS and MPEG-DASH player for HTML5 MSE and EME
- ↑ bitdash MPEG-DASH player for HTML5 MSE and EME
- ↑ bitdash HTML5 EME DRM demo area
- ↑ dash.js
- ↑ rx-player
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
