Wowza Streaming Engine 4.3 widevine live streaming problem on Shaka 1.6.5

[Nitimate Kasemsook]

Dear all,

I have been implementing Widevine Modular for our streaming service, it works nicely on our VOD, however I cannot make the drmed live streaming works on Shaka 1.6.5. 

Though I have no issue for live streaming without drm. When I monitored the network activity on Chrome, chunks were loaded, but for some reason it just did not play.

Have anybody encountered this problem before? Is there anything I need to check to find you guys more information on this issue?

I really appreciate any help you all can provide :)

Nitimate Kasemsook

P.S. I also attached the MPD and log into this thread, hope this may help.

[Joey Parrish]

Hi Nitimate,

Shaka fetches content independently of the availability of keys.  The content is fed to MSE, but MSE cannot decode until after EME has decrypted, which it cannot do without the keys.

I don't see anything obviously wrong in your log.  Can you provide some more details on what happens when your content does not play?  Are there any error events on the player?

What are the values of video.readyState, video.currentTime, video.buffered.start(0), video.buffered.end(0), video.buffered.length?

Can you also tell us the key IDs?  Run this in the JS console:

keys = player.emeManager_.sessions_[0].keyStatuses.keys();

do {

i = keys.next();

console.log(shaka.util.Uint8ArrayUtils.toHex(new Uint8Array(i.value)));

} while (!i.done);

Can you play the content on Shaka v2 beta?  http://shaka-player-demo.appspot.com/demo/

Thanks,

Joey

--
You received this message because you are subscribed to the Google Groups "Shaka Player Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to shaka-player-us...@googlegroups.com.
To post to this group, send email to shaka-pla...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/shaka-player-users/ebf29294-8ac3-4728-ac85-b4e91cc78de4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nitimate Kasemsook]

Hi Joey,

We switched from using our license proxy to "http://widevine-proxy.appspot.com/proxy" and also using UAT key and iv for retrieving content key to encrypt our test content. The result still the same though (VOD is good but no luck for live).

So I tried printing out the values and the snippet you provided in the console of the browser, which has our player opened I got the values as shown below, I also tried the demo player at "http://shaka-player-demo.appspot.com/demo/"  and put the result below too. Then I ran the snippet you provided on my players and the console gave me the message ''Uncaught TypeError: Cannot read property 'sessions_' of undefined(…)".

When I looked into the log I found messages like "Assertion failed: This should be an update of the last segment in a period" and "Assertion failed: SegmentReferences are incorrect", after start stream from a while.

If you do not mind I would like to send you the testing live and vod url to your email.

Thanks,

Nitimate K.

Debugging from my player page.

video.readyState: 1

VM247:2 video.currentTime: 88255.958999

VM247:3 video.buffered.start(0): 88241.813

VM247:4 video.buffered.end(0): 88270.122666

VM247:5 video.buffered.length: 1

Debugging from shaka demo player page.

video.readyState: 1

VM498:2 video.currentTime: 88076.030333

VM498:3 video.buffered.start(0): 88060.373

VM498:4 video.buffered.end(0): 88087.722666

VM498:5 video.buffered.length: 1

[Joey Parrish]

Yes, please send a manifest and license server URL so that we can try to reproduce.  Based on your description, my guess is that the CDM does not have the keys or has the wrong keys.

[Joey Parrish]

Using the manifest you sent me and the appspot license proxy, I tried playback in our latest nightly build of Shaka v2 beta.

What I'm seeing is not a DRM failure.  The license was acquired, and the browser seems to have keys.  The browser is complaining about the segments that it fetched being the wrong length. (net::ERR_CONTENT_LENGHT_MISMATCH errors in the JS console)  The network request for the segment therefore fails and triggers Shaka's NETWORK.HTTP_ERROR.

Please make sure your web servers are working correctly.  (They report themselves as "WowzaStreamingEngine/4.5.0", so you may want to report this upstream to Wowza.)