Roadmap concerning DRM handling

[dsilhavy]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

Discussions can be used to ask questions on the project which do not require a separate issue.

[BucherTomas]

Good idea!

This is a question for the core dev team. I'm curious about your roadmap concerning DRM handling.

Dash.js is still using Protection Model that is now 6 years old even though the industry has moved on in the meantime and some of the features that go hand-in-hand with new expected standards such as HDCP check, multikey stream support and track filtering based on given output protection key status returned from EME API are still not supported natively to my best knowledge.

Is this something that you keep in mind for the near future or does some kind soul need to provide a PR? :)

[dsilhavy]

Hi @BucherTomas , that are very good points. We are currently focusing on improving multiperiod support and rewriting the timing model in dash.js. These are major changes to the core functionality of dash.js. As soon as this is done your suggestions are valid points to be added to the release planing.

In general, dash.js supports switching between different AdaptationSet so the core functionality exists already. Moreover, adding new browser APIs like the MediaCapabilities API and MSE in webworkers are in our backlog as well.

To summarize, I can not give a concrete date for such changes but they are definitely on our agenda.