3 ms·
EME spec covers only a JS API for metadata exchange with unspecified magical CDM plugins. The spec deliberately doesn't cover how CDM gets integrated with the
by pornel 14y ago
EME spec covers only a JS API for metadata exchange with unspecified magical CDM plugins.
The spec deliberately doesn't cover how CDM gets integrated with the browser (currently: you're Google and you make a deal with Netflix privately and get binary to bake into closed version of ChromeOS).
* It might be that CDMs will be shipped with the OS (Widevine in Android/ChromeOS, WMDRM in Windows, FairPlay in OS X) and you'll have to rent licensing servers from each vendor.
* It might be that browser vendors will allow ActiveX-like download or allow regular .exe installers add components to the system and you'll have convince viewers that you're not giving them a virus.
* Or it might be that major browser vendors will license Netflix DRM, Hulu DRM, Amazon DRM and that's it.
In either case if you're a small player, you probably won't be able to use the DRM. The only option for you will be the default ClearKey which is as pathetic as the name implies. It can be broken with:
javascript:MediaKeys.prototype.update = function(key){alert("game over " + key)}