Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When content ends and new playback is requested sender player is loosing control for remote player #1

Closed
radiantmediaplayer opened this issue Nov 18, 2016 · 4 comments

Comments

@radiantmediaplayer
Copy link

radiantmediaplayer commented Nov 18, 2016

I am able to reproduce this issue with the sample Chrome sender app (v3) here on GitHub and our own implementation. Tested with Chrome Version 54.0.2840.99 m on Windows 10 and an up-to-date Chromecast device.
To reproduce:

  • install app from GitHub on local server and open index.html in Chrome (this also happens on a real site like http://www.staging-rmp.com/cast/)
  • play first item (BBB) on sender device. Cast.
  • wait or seek for content to end.
  • Cast device enters IDLE mode once content has finished
  • Request a new play after content has ended and cast device is in IDLE mode
  • LOADING of same media happens and player then go to PLAYING and then IDLE mode again. A this point sender device cannot control remote player anymore.
  • Requesting a new play cause a new LOADING of media process which ends in correct and expected behaviour (e.g. sender can control remote).

Can you please provide guidelines on how to properly handle end of content when the same media is reloaded?
Thanks
Arnaud

@neckaros
Copy link

I have the same issue. This is an issue with the SDK more than this demo.

With the default receiver:
if you switch media before the end you don't have any issue.
But if you wait untill play end and then change video the remotePlayer will note fire events nor be able to control the newly casted video.
But if during this video you switchagain before the end you are again able to control/receive events.
When having the issue casting an image and then a video also solve the issue.
it seems that when a video end you enter a problematic state

Where can we report this issue to Chrome cast sdk?

@radiantmediaplayer
Copy link
Author

Hi @neckaros The google-cast-sdk issue tracker is at https://code.google.com/p/google-cast-sdk/issues/list. Can you open a bug over there?

@NoRulesJustFeels
Copy link
Contributor

Not a sample issue.

@neckaros
Copy link

Done and has been accepted.

For reference:
https://code.google.com/p/google-cast-sdk/issues/detail?id=1104&start=100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants