26 replies to this topic

[Luke]

Chromecast is designed to be a casting protocol from one device to the chromecast. Whoever initiates the casting session becomes the primary controller.

 

Is it possible to come up with something proprietary and control it from the server? Yes but it would take a bit of work, and it would all be chromecast specific, meaning, it wouldn't necessarily be able to help us in other areas.

[Jdiesel]

Bump for visibility.

 

I currently have a Chromecast with paused playback outside my local network that I can't get rid of and has been pasued for over 24 hours now. Is there a technical reason we can not kill active streams from the server side?

[Luke]

The client may interpret it as an error and just retry, so we'd need to build specific support for doing that.

[Jdiesel]

What type of connection recovery is in place? I just tried disabling remote connections to the user with the Chromecast for 25 minutes but as soon as I enabled remote connections for the user again the Chromecast reconnected to the server and playback continued. At what point will the client give up trying to connect? 

[Luke]

A lot of times it is just the way the video player on a particular platform will work, that it will keep playing until you stop it.

[Jdiesel]

How can I prevent users from being able to cast to Chromecast devices? I already disabled the Remote Control settings for the user but they are still able to cast to their local devices. 

[Luke]

You can't. You'd have to just cut them off entirely.