The EME page is an excellent resource for basic EME - downloading a WebM file with an encrypted stream (Chrome_44-enc_av.webm) and decoding it in the browser.
But, how was that encrypted WebM file created? ffmpeg? openssl? MP4Box? It's left quite a mystery, and Googling this only leads to encryption-as-a-service companies, and other confused idiots.
So, what is the secret sauce?
It would be convenient to embed some guidance in inline HTML:
<video autoplay controls>
<!-- ffmpeg -i Chrome_44.webm -eme-key ebdd62f16814d27b68ef122afce4ae3c \
Chrome_44-enc_av.webm -->
<source src="../video/Chrome_44-enc_av.webm" type="video/webm" />
<p>This browser does not support the video element.</p>
</video>
The EME page is an excellent resource for basic EME - downloading a WebM file with an encrypted stream (Chrome_44-enc_av.webm) and decoding it in the browser.
But, how was that encrypted WebM file created?
ffmpeg
?openssl
?MP4Box
? It's left quite a mystery, and Googling this only leads to encryption-as-a-service companies, and other confused idiots.So, what is the secret sauce?
It would be convenient to embed some guidance in inline HTML: