3 ms·

So the open source wrapper can receive unencrypted audio/video frames. Does that mean it does the video decoding too or does it get the compressed stream back?

So the open source wrapper can receive unencrypted audio/video frames. Does that mean it does the video decoding too or does it get the compressed stream back? Either way it doesn't sound like a very strong protection of the content as you can access it with at most a single generation compression loss. Is it me or are the content providers and the DRM providers realising the limits of DRM and loosening their requirements?

higherpurpose 12y ago
No, it just means they were ignorant enough about the technology to allow Mozilla to do it this way - for now. Also, Mozilla gets to say now that "look, we're implementing DRM, but it's not so bad". However, once the content owners see how useless this method is (they all are, but this in particular), they will demand heavily proprietary closed source down to the metal software to protect their content. And since Mozilla has "already" kind of agreed to do this, they'll have no choice but to implement that much worse version of DRM.