Can Nimble either integrate with existing DRM systems (e.g. playReady etc.) or handle streaming encrypted content? if so, can this be done using HLS protocol?
Thanks for your interest!
At the moment we handle DRM-encrypted content only in re-streaming mode: https://wmspanel.com/nimble/http_restreaming
We have customers who successfully re-streamed HLS, HDS and SmoothStreaming content via Nimble Streamer so I believe it will work for you as well.
As for DRM native support, it's a feature in our roadmap.
Feel free to sign up and install Nimble Streamer to see that in action: https://wmspanel.com/account/sign_up
You can also request installation by our team, it would be free of charge.
Thank you so much for the swift reply.
Making sure I got the scenario right - Nimble native DRM support is on the roadmap and in addition, the following scenario is currently working:
1. Nimble is used as edge server, re-streaming HLS from Wowza or IIS.
2. Wowza/IIS integrates with PlayReady so all content is encrypted on the disk ("in situ") - at the origin site and at the edge site.
3. The media player gets the encrypted data via HLS.
If the above works, would it be correct to state that the end user's player is doing the decryption by using Nimble to connect to the back end DRM system (e.g. the player calls Nimble; Nimble redirects the call to Wowza/IIS, which in turn interact with PlayReady server)?
You are absolutely right. You have an encrypted content; it's initially provided by some DRM-enabled media server like Wowza/IIS; you use Nimble as a re-streaming edge and it passes the requests from player to origin, then caches it and passes over to the player.
You may contact me via email@example.com for any further questions once you have them. I'm a co-founder of the service and I'm ready to help any time.
Thank you Yury. Certainly going to do that.
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the