Gilles Boccon-Gibod

For Widevine, the value of the `content_id` parameter is something that must be understood by the Widevine server you use. If you use a server provided by a DRM service...

Looking at the ezdrm docs, it looks like the service provides you with a base-64 encoded widevine header, so with the Bento4 packager, you'd pass: `--widevine-header=#` where `` is the...

I'll work on an update to `mp4dash` so that it can support all the same options as `mp4hls`

I have just pushed some small modifications that should fix issues seen with Widevine/CBCS mode with HLS. So you should be able to use `mp4dash` with the `--hls` options to...

> I had same requirement DASH+HLS with DRM, so I had to modify the mp4dash.py script to merge mp4dash and mp4hls changes into one to avoid packaging twice (one for...

Issue #503 is something different (and unlikely to cause any practical issues, since cbc1 mode is probably never used in the field, and even then, the issue would probably not...

The `random` suffix here is for the IV, it uses a randomly generated IV. If you have a version that works, and one that doesn't, would it be possible to...

The issue here is that it looks like you passed the entire PSSH content as an argument to the `—widevine-header` (in the example you give here, you use the `--widevine-header`...

Indeed, I introduced a bug when adding support for passing a complete PSSH (and not just the payload) as input to the `--widevine-header` option. This is now fixed on the...

For a simple example with Widevine with `cbcs` mode in a way that's compatible with DASH and HLS: ``` # Key = 07551a633e47ebf903a2d81fd903b9fe # KID = 9d2f8cfe72e05c5ab895f8a030deb0a0 # PSSH =...