4 ms·
So I remember reading some early EME specs that seemed to indicate that EME encrypted content could be decoded and played by the browser's standard decoder and
by problems 10y ago
So I remember reading some early EME specs that seemed to indicate that EME encrypted content could be decoded and played by the browser's standard decoder and player - in the case of an open source browser like Firefox - hooking these decoding functions is quite trivial. Is this the means they've gone with or does this EME blob include their own decoder and player?
EDIT: This little image here: https://www.w3.org/TR/2016/CR-encrypted-media-20160705/stack_overview.svg https://www.w3.org/TR/2016/CR-encrypted-media-20160705/stack... in the bottom right indicates that "CDM implementations may return decrypted frames or render them directly".
Would be very interesting to see a generic CDM hook which could dump all the in-and-out calls to a given CDM.
- pornel 10y agoThis diagram and most of non-normative parts of the spec are a deliberate red herring. The purpose of these is to derail discussion about DRM restrictions by saying that any restrictions are optional. However, during discussions at W3C Netflix representatives confirmed that their implementation doesn't work like this. They are only interested in "strong" DRM model in which the player is not trusted and has no ability to see decrypted data, so it can't even use its regular HTML5 codec to decode it.
- problems 10y agoOn Android they feed it directly to the OS codecs except for 4K video so they can't really care that much.
- thomastjeffery 10y agoThanks for the clarification! Can I upvote you twice?