androidx
Is there a way in content protection which allows L1 content to decrypt with non secure decoder?
I encountered a scenario where L1 content was successfully decoded on a non-secure decoder, contrary to expectations.
When I tried using the Media3 sample app to test "HW secure decode" asset, I found crypto failure when forced the software decoder and encountered an expected failure. However, when testing with my specific asset, I did not receive a crypto error, and the decoder was able to decrypt the content successfully.
So I assume output protection rule can cause this difference. I want to achieve the same behavior like media3 sample where L1 content is only decrypted on secure decoders. Could you suggest suitable license protection rules to achieve this? Specifically, my L1 track fails to decrypt on an L3 CDM, but it decrypts successfully on an L1 CDM. However, it's also being decoded by a software decoder, which contradicts the expected secure decoding behavior of L1 content.
Showing below warnings, but the playback continues without any widevine error.
2024-09-26 15:47:45.191 3597-4605 MediaCodecRenderer androidx.media3.demo.main W Drm session requires secure decoder for video/avc, but no secure decoder available. Trying to proceed with [c2.android.avc.decoder].
Output protection rule query: In which condition we can decode DRM protected video which has L1 key with device designated as widevine L1 (CDM) but decoded as part of software decoder ?
This is a question about widevine license policies, not about ExoPlayer. If you're a Widevine partner you can get support directly from them: https://www.widevine.com/contact.
If your company is not a Widevine partner, you can sign up through https://www.widevine.com/contact at no cost. We can answer some of your questions there or guide you in case they are more complex.
Hey @akhilesh-dubey. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Since there haven't been any recent updates here, I am going to close this issue.
@akhilesh-dubey if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.