Closed GoogleCodeExporter closed 8 years ago
There used to an issue for message from receiver to get to sender app but it
has been fixed. See this:
http://stackoverflow.com/questions/21566190/chrome-google-cast-sender-not-receiv
ing-media-status-updates-on-original-media-l.
To verify that you have this issue, you can check that your message actually gets to Cast extension but not your sender app. See Cast extension console log from it's background.html.
If this is the case, you need to get the latest Cast extension. Otherwise
please provide more info.
Original comment by shawns...@google.com
on 18 Feb 2014 at 1:37
Original comment by anad...@google.com
on 18 Feb 2014 at 7:01
Hi folks,
I checked my extension, and it's at version 14.123.1.5.
The way to reproduce this is to check out the CastHelloVideo-chrome project,
and play a video. The media update listener never gets called as the video
plays. It is only called when the video is played/paused.
To double check that it wasn't a bug with the example, I ran the line on the
console:
currentMediaSession.addUpdateListener( function(){ console.log("media session update"); } )
and I only ever got a message when I clicked pause/play, and never just as the
video was playing.
Am I not registering the right callback? What's the right way to get updated on
the progress through the video as it's playing on the chromecast?
Thanks again.
Original comment by cra...@gmail.com
on 19 Feb 2014 at 2:29
Hi Craiig,
This is the correct behavior for now. Currently receiver won't send status
update during playing only when there is some event like pause/play.
For continuous update like progress bar, you'd have to keep a timer in your
sender app. An example of this is provided in the CastVideos-chrome app.
We'll revisit this in next release and provide more hooks potentially.
Original comment by shawns...@google.com
on 20 Feb 2014 at 6:55
Ok! Thanks for the response! :)
Original comment by cra...@gmail.com
on 20 Feb 2014 at 6:56
Just a heads up. There is a beta release of Cast extension, freshly released,
which will provide a way to get current estimated time. There will be more
discussion on this in coming days on stackoverflow, github, G+ community, etc.
:-)
Original comment by shawns...@google.com
on 20 Feb 2014 at 8:29
Original issue reported on code.google.com by
cra...@gmail.com
on 17 Feb 2014 at 11:33