|
|
|
|
|
by cpeterso
3808 days ago
|
|
EME commoditizes DRM, for better or worse. Like you said, a EME lowers the pain to adopt DRM. With a standard EME API and CENC (Common Encryption), services can easily support multiple DRM backends or switch DRM backends. I worry that increased competition between DRM providers will lead to an arms race of stronger DRM tech. |
|
EME Standardized the Plugin err "extension" API. It in no way standardizes DRM. The Stardardization is around the way Javascript will be used to call inside HTML5 the browsers CDM (content decryption module" which is a plugin by another name.
There are currently 3 competing technologies, with more to come, that are incompatible with FOSS, incompatible with open systems
For Chrome Browsers there is Google Widevine CDM
For MS Browsers there is MS PlayReady
For Firefox there is Adobe Video CDM (which is basiclly the video playback part of Flash)
This is the problem with EME, Netflix, Google, and Microsoft have been masterful at their marketing of this to people that should be able to see past the bullshit
EME/CDM is still a binary browser plugin, Sure we "eliminate" flash and the need for a "3rd party" plugin, but in many ways that it worse, Before we had a standard Plugin API that allowed non-supported browser to make use of Flash, so there where many many many browser that could call the 3rd party flash application to make use of that content. Now those browsers are completely locked out. You will only be able to Access content on the Big 2, Chrome and IE, and maybe Firefox is they finalize their agreement with Adobe to bring in a Binary Blob into the Firefox Browser
I do not call that a "WIN" for interoperablity.