DASH Live cannot transition from completely unencrypted content to encrypted content later in the live presentation

[TheJohnBowers]

Have you read the FAQ and checked for duplicate open issues?
Yes - Nothing open, but this looks like a regression: #1360, I don't think I can re-open an issue this old. In 2.4.7, this bug doesn't exist.

What version of Shaka Player are you using?
3.0.10

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?
Demo App

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

What browser and OS are you using?
Chrome on Macos

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

What are the manifest and license server URIs?
https://content.uplynk.com/playlist/4f1a9815a1af43d5ba64465d85bf11cf.mpd?ad=sintelads
https://content.uplynk.com/wv

What configuration are you using? What is the output of player.getConfiguration()?
No special config -- I mean I can easily reproduce with the public appspot demo. So whatever config is default for the demo:

https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://content.uplynk.com/playlist/4f1a9815a1af43d5ba64465d85bf11cf.mpd?ad=sintelads;panel=CUSTOM%20CONTENT;build=uncompiled

What did you do?

The demo url is specifically designed to reproduce the issue quickly (honestly this would be a good sample stream for the demo app)-- You just start playback, it will always start in unencrypted ads. It will run through roughly 45 seconds of ads, and then try to transition into content which is encrypted

What did you expect to happen?
I would like it to work as well as it does on shaka 2.4.7

What actually happened?

The transition into content after 45 seconds fails with: Shaka Error MEDIA.VIDEO_ERROR (3,,PIPELINE_ERROR_DECODE: audio error during playing, status: PIPELINE_ERROR_DECODE) every time. It works on shaka 2.4.7

[TheModMaker]

You need to configure the license server before playback starts if you expect to see encrypted content later. The following works fine for me:

https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://content.uplynk.com/playlist/4f1a9815a1af43d5ba64465d85bf11cf.mpd?ad=sintelads;license=https://content.uplynk.com/wv;panel=HOME;build=uncompiled

[TheJohnBowers]

Ah, ok. I don't need to configure the license url normally because shaka will read it out of the mslaurl attribute (ms:laurl xmlns:ms="urn:microsoft" licenseUrl="https://content…..’) in the manifest.

As an example without a license server configured:
https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://content.uplynk.com/playlist/6c526d97954b41deb90fe64328647a71.mpd?ad=bbbads&delay=25;panel=CUSTOM%20CONTENT;build=uncompiled

I guess I expected that laurl to get picked up and add the license server when a new period shows up with it for the first time. Perhaps this can be a feature request?

[TheModMaker]

Unfortunately we can't initialize EME after playback has started. We need to setup EME before playback starts, so it either needs to be in the first manifest or the configuration. The browser sets up special media pipelines for protected content and many/most browsers don't allow switching while content is playing.

[TheModMaker]

Also, I think you can just change the license server URL after playback has started. So you could add a dummy value to the configuration and change it later. I guess we could add support for a dummy value that gets filled from the manifest later.

[avelad]

Unfortunately we can't initialize EME after playback has started. We need to setup EME before playback starts, so it either needs to be in the first manifest or the configuration. The browser sets up special media pipelines for protected content and many/most browsers don't allow switching while content is playing.

@TheModMaker I know you're no longer involved with Shaka, but do you remember that browsers don't support initializing EME when playing clear content?

[shaka-bot]

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.