Smooth Streaming with Playready not working with latest firmware

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Play a stream with Smooth Streaming and Playready DRM. If you are not able 
to reproduce, please ask for a test stream.

What is the expected output? What do you see instead?
With the latest firmware update (19084) none of our protected streams play. 
Fails with "Uncaught InvalidStateError: Failed to read the 'buffered' property 
from 'SourceBuffer': This SourceBuffer has been removed from the parent media 
source."

Both VOD and live with DRM fails. Streams without DRM still plays.

We have not changed our streams or receiver, and everything plays perfectly on 
a device that has not received the firmware update (running version 17977).

We are using media player library 0.9.0

Original issue reported on code.google.com by glenn.hi...@tv2.no on 9 Sep 2014 at 3:39

[GoogleCodeExporter]

Yes, please give us a test stream we can use to reproduce.  Thank you!

Original comment by vadi...@google.com on 9 Sep 2014 at 7:35

[GoogleCodeExporter]

Original comment by anad...@google.com on 9 Sep 2014 at 9:38

• Changed state: NeedInfo

[GoogleCodeExporter]

Hi

We have a test stream here: 
http://hls.akamai.tv2.no/wzlive/_definst_/smil:Wza04_chromecast_live_test_001.sm
il.ism/Manifest

License URL: 
https://sumo.tv2.no/api/web/asset/840305/license?timeStamp=2014-10-01T12:20:07+0
200&contract=a283f43cfe5d129d95036f09284b4894&account=source

We currently do not have CORS enabled on the license server, so you will have 
to do some kind of proxying, or use a receiver hosted by us.
One of the following receiver URLs can be used:
https://sumo.tv2.no/CastMediaPlayerStreamingDRM/mpl.html
https://sumo.tv2.no/sumo_test_receiver/

The first one is a fresh copy from 
https://github.com/googlecast/CastMediaPlayerStreamingDRM
The latter is our own receiver.

I see that I get a different error from mpl.html than our own receiver, but 
both fails on startup.
I have verified that the stream works on both silverlight and a chromecast 
device with older firmware.

Original comment by glenn.hi...@tv2.no on 10 Sep 2014 at 1:42

[GoogleCodeExporter]

Thank you, we will investigate.  At first glance, it doesn't appear to be a DRM 
issue.  It's failing in this code in Chrome:

https://code.google.com/p/chromium/codesearch#chromium/src/media/formats/mp4/avc
.cc&q=%22first_subsample_size%20!=%20(config_insert_point%20-%20buffer-%3Ebegin(
))%22&sq=package:chromium&type=cs&l=101

so it's possible that there was a change in Chrome M37 which the current 
Chromecast firmware is using that impacted this.

Original comment by vadi...@google.com on 10 Sep 2014 at 5:04

[GoogleCodeExporter]

Thank you. Streams from the same setup without DRM plays fine. That's why I 
figured it would be DRM related.

Original comment by glenn.hi...@gmail.com on 10 Sep 2014 at 5:43

[GoogleCodeExporter]

Any updates on this?

Original comment by glenn.hi...@tv2.no on 19 Sep 2014 at 12:32

[GoogleCodeExporter]

We are looking into this. We have identified one issue on our side (Chrome has 
an issue with inserting SPS/PPS params into keyframes that start with AUD NALU 
and contain one or more unencrypted NALUs after that). I have tried fixing this 
locally and I'm now able to play the video stream, but playback starts with 
about 10-15 second delay and I've seen it pausing occasionally without my 
intervention, so my fix might be incomplete.

Original comment by serv...@google.com on 19 Sep 2014 at 11:17

[GoogleCodeExporter]

Thank you for the info. I guess the fix is for the Chrome code, so a firmware 
update is required for it to go into production?

Do you know if there is anything we can do on our end to make our streams work 
on the current firmware? We use Wowza for our streaming server.

Original comment by glenn.hi...@gmail.com on 24 Sep 2014 at 7:07

[GoogleCodeExporter]

Just to let you know that we have tested with MediaPlayerLibrary 1.0 as the 
release notes mentioned a Source Buffer fix. Didn't seem to make any difference.

Original comment by glenn.hi...@tv2.no on 25 Sep 2014 at 8:39

[GoogleCodeExporter]

Yes, this fix will require a Chromecast update, so it will take some time 
before end-users get it. In the meantime, how much control do you have over the 
generated bitstream? The problem here is that Chrome 37 doesn't handle properly 
bit streams where key frames start with AUD NALU followed by one or more other 
NALUs in the clear text part of the first subsample of the key frame. In your 
case looks like most key frames start with AUD + SEI NALUs. Could you try 
removing the SEI NALU and leave just AUD NALU at the beginning of key frames?

Original comment by serv...@google.com on 25 Sep 2014 at 5:54

[GoogleCodeExporter]

Not sure how much control we have. I will have our streaming guys look into it. 
Hopefully they will be able to do some adjustments.

Original comment by glenn.hi...@gmail.com on 25 Sep 2014 at 6:08

[GoogleCodeExporter]

The fix for this issue landed in Chromecast firmware build 20957. Although I 
can't play the original stream anymore, but looks like it's due to some other 
issue, perhaps expired key or license.

Original comment by serv...@google.com on 9 Oct 2014 at 11:16

[GoogleCodeExporter]

Thanks. Do you have a release date for 20957? The license URL for the stream 
has expired. If needed I can find a new stream for you to try.

Original comment by glenn.hi...@tv2.no on 13 Oct 2014 at 3:00

[GoogleCodeExporter]

I'm seeing something very similar to this but with audio only streams. Could it 
be the exact same issue? All our VOD (AOD?!) fail with the exact same error 
message.

Example audio stream (no DRM): 
http://nordond17a-f.akamaihd.net/i/wo/open/af/af9a44b198071e699f23d291e208a4b544
e1ff09/92437d0c-20d8-49ea-b2cb-ea1f8dae96cd_,64,192,.mp4.csmil/master.m3u8

Original comment by tobias.lundin on 3 Nov 2014 at 12:42

[GoogleCodeExporter]

is there an release date for: 20957 ?

Original comment by anders.o...@gmail.com on 8 Nov 2014 at 11:03

[GoogleCodeExporter]

This should be fixed and available for public.

Original comment by and...@google.com on 10 Nov 2014 at 11:22

• Changed state: Fixed