Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shaka Error DRM.FAILED_TO_GENERATE_LICENSE_REQUEST when trying to play Playready encoded content #1837

Closed
cristioltean opened this issue Mar 12, 2019 · 19 comments
Assignees
Labels
status: archived Archived and locked; will not be updated

Comments

@cristioltean
Copy link

cristioltean commented Mar 12, 2019

Have you read the FAQ and checked for duplicate open issues?

What version of Shaka Player are you using?

v2.4.7-uncompiled
Can you reproduce the issue with our latest release version?
yes

Can you reproduce the issue with the latest code from master?

Are you using the demo app or your own custom app?
yes

If custom app, can you reproduce the issue using our demo app?

What browser and OS are you using?
Edge , Windows 10

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?

What did you do?

Tried to played the dash content with playready encryption but it fails.

What did you expect to happen?
Playback to be normal

What actually happened?

I receive this message when trying to play the content .

Shaka Error DRM.FAILED_TO_GENERATE_LICENSE_REQUEST (SystemCode:0x80041301,TypeError: SystemCode:0x80041301,)

If I click the link I am sent to this message:

FAILED_TO_GENERATE_LICENSE_REQUEST 6006 number The CDM was unable to generate a license request for the init data it was given. The init data may be malformed or in an unsupported format. error.data[0] is an error message string from the browser. error.data[1] is the error object from the browser. error.data[2] is a string with the extended error code, if available.
@avelad
Copy link
Member

avelad commented Mar 12, 2019

I can reproduce the issue with v2.5.0-beta3
According the drm provider in v2.0.3 the issue doesn't happen due to changes in the pssh.

@johnsim
Copy link

johnsim commented Mar 13, 2019

@avelad I would be interested in knowing more about the pssh changes you mention. Could you reach out to me? [email protected]

@avelad
Copy link
Member

avelad commented Mar 13, 2019

I just tested with Edge 18 in v2.02, v2.0.3 and v2.5.0-beta3 and It doesn't work.
With Edge 15 works in 2.02, v2.0.3 but not in v2.5.0-beta3
It a bit curious...

@avelad
Copy link
Member

avelad commented Mar 13, 2019

Note: the same manifest with Widevine in Chrome/Firefox/Opera work without problem.

@avelad
Copy link
Member

avelad commented Mar 13, 2019

The stream works with http://reference.dashif.org/dash.js/v2.9.3/samples/dash-if-reference-player/index.html

So, I think that is not a browser error

@cristioltean
Copy link
Author

Hello ,

I have sent an email to [email protected] with more data : mpd link , license serve url.
Also a screenshot with the decode initData used when doing a session.generateRequest call.
It will help us allot if you can provide some information of how this initData is generated , I believe that the player crashes because it cannot get exact structure it needs to create it.
Regards,

Cristian

@johnsim
Copy link

johnsim commented Mar 18, 2019

@cristioltean - The error code indicates that the init data is incorect. If you could provide me with the information you sent to [email protected] we can help determine the root cause

@cristioltean
Copy link
Author

Hi @johnsim if you can provide me an email address or another way to send you the info I will do it ASAP.

@avelad
Copy link
Member

avelad commented Mar 19, 2019

@avelad I would be interested in knowing more about the pssh changes you mention. Could you reach out to me? [email protected]

@cristioltean ,in this comment you have the mail.

@cristioltean
Copy link
Author

@avelad Thanks Alvaro , I have forwarded the email to you @johnsim

@johnsim
Copy link

johnsim commented Mar 19, 2019

Thanks, @cristioltean, @avelad - the Microsoft PlayReady team is evaluating the data now. I will update this issue with our findings.

@avelad
Copy link
Member

avelad commented Mar 25, 2019

@johnsim , do you have any update?

@cristioltean
Copy link
Author

Hello Alvaro,

I was talking with John via email and currently we are trying to understand why the initData used to generate a license request is not compatible for Shaka.

Latest question from him was if this Star channel is working with Widevine , as far as I know in your tests Widevine is working fine.

@avelad
Copy link
Member

avelad commented Mar 25, 2019

@cristioltean , Yes, Widevine is working without problem in Chrome, Firefox and Opera.

@TheModMaker
Copy link
Contributor

The pssh data in the media is bad. It contains a valid Widevine pssh box, but the pssh box for PlayReady has an invalid System ID. The correct System ID is "9a04f079-9840-4286-ab92-e65be0885f95" but you have "9a04f079-9840-4286-ab92-e65be0889f95".

@avelad
Copy link
Member

avelad commented Mar 25, 2019

@TheModMaker, Would it be possible to add a more explicit error code for when the content does not have a valid system ID?

@cristioltean
Copy link
Author

Hi Alvaro , what I can see it's that the the System id in the init segment indeed is not 9a04f079-9840-4286-ab92-e65be0889f95

I will check this with R&D.

Thanks @TheModMaker

@TheModMaker
Copy link
Contributor

@avelad We don't like assuming init data formats or System IDs. That could be a valid System ID for some unknown key system, so we don't want to throw an error for it. We just give the data to the browser and let it handle it. But we could use the data in the manifest to validate the expected System IDs (at least for the ones we know about). You could file a feature request for that.

@cristioltean
Copy link
Author

Hello , indeed the system id was not correctly set in the init segment which was causing this , after fixing the typo playback is working ok .Closing ticket for now.
thanks for the help.

@shaka-project shaka-project locked and limited conversation to collaborators Jun 1, 2019
@TheModMaker TheModMaker self-assigned this Feb 27, 2020
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated
Projects
None yet
Development

No branches or pull requests

5 participants