mmeitine / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
1 stars 0 forks source link

Casting HLS adaptive stream(multiple bit-rate) fails with democastplayer Sample using MediaPlayer Library. #243

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
We are trying to stream HLS adaptive stream master playlist on Chrome-cast. 
In accordance to use Media Player Library for cast, We are using the receiver 
app from a sample in git-hub 
(https://github.com/googlecast/Cast-Media-Player-Library-Sample).

MediaPlayer Library version updated to 0.5.0.
We have registered the chrome-cast device and also registered the receiver app.

We are working with the democastplayer sample with-in the 
android-sdk/extras/google_play_services/..
Our stream does not play in the sample we are using. The streams are tested 
over a variety of player and are confirmed to be fine. But same are not able to 
be cast, though the sample streams play/cast as expected.

A sample stream in question:
http://mavshackhdvod-vh.akamaihd.net/i/IND-DVD-02-011--Inkaar--F--HQ21_512.mp4.c
smil/master.m3u8?{AKAMAI_TOKEN}

To access the video, add AKAMAI_TOKEN in the above url generated using 
following call in your browser:
https://appsapi.mavshack.com/MediaSystem.Core.Frontend.WcfService.Web/WcfService
Web.svc/GenerateAkamaiToken

Original issue reported on code.google.com by pratibha...@gmail.com on 24 Apr 2014 at 3:04

GoogleCodeExporter commented 8 years ago
Have you tried our default or styled receiver?

Original comment by anad...@google.com on 25 Apr 2014 at 2:03

GoogleCodeExporter commented 8 years ago
Yes, I did try them. It dint work with them as well.

Original comment by pratibha...@gmail.com on 25 Apr 2014 at 6:08

GoogleCodeExporter commented 8 years ago
Hi, can you please let me know whats the issue???

Original comment by pratibha...@gmail.com on 28 Apr 2014 at 5:36

GoogleCodeExporter commented 8 years ago
On debugging the receiver (using cast default receiver) I got following error.

GET 
http://mavshackhdvod-vh.akamaihd.net/i/IND-DVD-02-011--Inkaar--F--HQ21_,950,512,
320,.mp4.csmil/index_0_av.m3u8?null= 403 (Forbidden) media_player.js:52

[162.072s] [cast.receiver.MediaManager] Load metadata error
 cast_receiver.js:18
ib cast_receiver.js:18
gb.Gb cast_receiver.js:18
B.log cast_receiver.js:13
E cast_receiver.js:15
Z.pa cast_receiver.js:71
Eb cast_receiver.js:23
Cb cast_receiver.js:24
(anonymous function) cast_receiver.js:21
e.onError player.js:55
h.gb media_player.js:157
Q.W media_player.js:76
Gc media_player.js:48
h.dispatchEvent media_player.js:47
Yc media_player.js:53
$c media_player.js:56
H.Ef media_player.js:54
H.ce

Original comment by pratibha...@gmail.com on 28 Apr 2014 at 1:21

GoogleCodeExporter commented 8 years ago
The log shows you have "?null=403", is that correct?

Original comment by anad...@google.com on 4 May 2014 at 7:49

GoogleCodeExporter commented 8 years ago
No, the stream link is only 
"http://mavshackhdvod-vh.akamaihd.net/i/IND-DVD-02-011--Inkaar--F--HQ21_,950,512
,320,.mp4.csmil/index_0_av.m3u8?null=". Remaining "403 (Forbidden) 
media_player.js:52" is the error message.

Original comment by pratibha...@gmail.com on 5 May 2014 at 8:31

GoogleCodeExporter commented 8 years ago
You need to retest this and use our Default or Styled receivers. Also, the 403 
that you were getting is something that you need to resolve on your side.

Original comment by anad...@google.com on 1 Aug 2014 at 11:00

GoogleCodeExporter commented 8 years ago
Closing the issue due to lack of response

Original comment by anad...@google.com on 11 Aug 2014 at 4:43

GoogleCodeExporter commented 8 years ago
As already mentioned in the same thread earlier, we have tested with both 
Default and Styled receivers. Also we are using google's sample custom receiver 
code for our receiver. Still we get same issue. 

The 403 we are getting is because the links are tokenized. Once the master 
playlist is validated with the token, the token is further saved in the cookies 
to validate each segment. But as we checked with the chromecast debug resources 
with 9222 port on device ip, we dont see any cookies getting saved. 

Any help on this will be really helpful.

Original comment by pratibha...@gmail.com on 12 Aug 2014 at 2:50