IE11: error 6006 (FAILED TO GENERATE LICENSE REQUEST) when playing video with separate video and audio keys

[gigon]

Have you read the FAQ and checked for duplicate open issues?: yes
What version of Shaka Player are you using?: v2.4.5

Can you reproduce the issue with our latest release version?: yes

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

Are you using the demo app or your own custom app?: both

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

What browser and OS are you using?: IE11 (11.1387) on Windows 10 (1703)

What are the manifest and license server URIs?: Will send by email

What did you do?
Play my DASH video with separate keys for video and audio on your Demo app, on IE11.
Notice in order to play the video you have to turn off CORS restriction in IE Security Settings
(Internet Options - Security - Custom Level- Misc. - Access Data Sources across domains (Enable this.)

What did you expect to happen? Play without issues

What actually happened?
The video plays ok (with audio), but after 10-15 seconds I get Shaka error 6006
(FAILED_TO_GENERATE_LICENSE_REQUEST), and this repeats every 10-15 seconds.

• The same video plays without issues on Edge browser.
• The same video plays without issues on IE11 with DASHJS player.
• A similar video with a single playready key for video and audio plays well on IE11.

--

[TheModMaker]

This is usually caused by the platform rejecting the content, and there is often nothing we can do about it. I can't reproduce this on our Windows machine. I get a different error and the video doesn't play at all. Could you try with verbose logging and post those logs? Did you try with the nightly site? Can you also look at the error object to get extended error codes, I think it will be in error.data[0].errorCode. You could also look at lib/polyfill/patchedmediakeys_ms.js and look at the onMsKeyError_ function to see if there is any more info in the native error object.

[gigon]

Sorry but someone modified the license proxy after I posted the bug (as it was many days ago...). I am sending now the correct urls to shaka-player-issues@google.com. With these urls I can reproduce it also on the nightly build. Notice: it does play! you have to let it play for 5-10 seconds until you see the shaka error message on top of the playing video.

…

On Tue, 27 Nov 2018 at 23:33 Jacob Trimble ***@***.***> wrote: This is usually caused by the platform rejecting the content, and there is often nothing we can do about it. I can't reproduce this on our Windows machine. I get a different error and the video doesn't play at all. Could you try with verbose logging and post those logs? Did you try with the nightly site <https://nightly-dot-shaka-player-demo.appspot.com/>? Can you also look at the error object to get extended error codes, I think it will be in error.data[0].errorCode. You could also look at lib/polyfill/patchedmediakeys_ms.js and look at the onMsKeyError_ function to see if there is any more info in the native error object. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1689 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABv9wYCizBaH4VuuNZ_9AJVTl3C7Bwqkks5uza_FgaJpZM4Yq-CC> .

[TheModMaker]

When this happens, we get an error from the browser with a code of 0x8004b8ad, which I can't find any reference to this anywhere. This appears to be some internal COM error with an undocumented error code. Oddly enough, the video plays fine and I don't get the error if I reload the video in the same tab.

It looks like your audio init segment contains invalid data. The pssh box isn't the correct size and probably results in parsing errors in PlayReady (somehow it doesn't cause video errors).

[joeyparrish]

I found a reference to this. It's not documented by MS, but it seems to be a PlayReady-related error:

/*
*    MessageId:    MSPR_E_INVALID_CDMSESSION
*    Message Meaning:
*       Only one reactive CDM Session can be attached to a playback session at a time.
*    Hex Value:    0x8004B8AD
*/
#define MSPR_E_INVALID_CDMSESSION                                   MAKE_DRM_RESULT(DRM_SEVERITY_ERROR,  DRM_FACILITY_ITF, DRM_E_MSPRSDK_BASECODE+0x00AD)

https://github.com/tpn/winsdk-10/blob/master/Include/10.0.16299.0/winrt/Windows.Media.Protection.PlayReadyErrors.h

Could our IE11 EME polyfill have a race condition? That might explain the inconsistency in repro.

[TheModMaker]

I'm not sure, but it is hard to diagnose because we are getting invalid data from the media, which will cause errors either way. I tried doing a similar path with our own assets and the version @gigon sent us that works, and both work fine. So I don't think it is a race unless we get it with non-broken content.

[gigon]

@TheModMaker, please explain how come the same asset works fine, including audio, on Edge browser,
if it has a bad PSSH box?
And: do you have any reference Playready content with separate keys for video and audio?

[TheModMaker]

@TheModMaker, please explain how come the same asset works fine, including audio, on Edge browser,
if it has a bad PSSH box?

My guess would be Edge either more resilient against errors or has a different parser so it ignores the parts that are wrong.

And: do you have any reference Playready content with separate keys for video and audio?

I just tried the Axinom Multi-DRM, multi-key asset and I get the same error, so maybe there is a platform bug or something the IE EME polyfill is doing. See #959.

[joeyparrish]

Extended error code and work so far cherry-picked for v2.4.6.

[joeyparrish]

I just tried the Axinom Multi-DRM, multi-key asset and I get the same error, so maybe there is a platform bug or something the IE EME polyfill is doing.

Axinom has stated that they simply don't support IE with their content, so that is not going to be fixed. It's still unclear if the content in this issue is encoded in the same way as Axinom's. If that is the case, then there's nothing we can do.

[joeyparrish]

Unlikely to get fixed given that Axinom doesn't support IE and our support for IE ends after v2.6.