Jump to content

Server - Kill current transcode/streaming sessions from the server


Florux

Recommended Posts

Hi,

 

On the Server you can currently see active devices on the dashboard, and consequently which users are watching what on what media.

 

However, there's no way to abort these active devices to either conserve bandwidth, conserve server CPU, or simply to stop a renegade process.

 

One use case that would be particularly helpful is when you're casting from the phone app to ChromeCast. If the phone gets interrupted, you lose control over the stream so that the TV stops showing whatever you were watching, and there's no way to stop it or regain control over it.

 

Instead of having to stop and start the entire server, it would be nice to just click on that particular activity on the dashboard and press KILL (or perhaps a less dramatic word - cancel?)

 

Food for thought?

 

 -Florux

  • Like 15
Link to comment
Share on other sites

  • 2 weeks later...

Yea, it's a good idea

 

Not quite sure how this works around here - does this mean the request made a roadmap somewhere, or how are these requests managed? Not really super important - just curious on how this is done here :-)

 

 -Florux

Link to comment
Share on other sites

I think this functionality already exists on the server. In the web interface you can Select Player and then remotely stop the stream.

 

Should be pretty easy to add a button in the dashboard under Active Devices that sends the same call.

 

@@Florux as another solution to get this functionality, does clicking the cast icon in the top right, selecting the player you want to stop, and clicking stop do the same thing you are looking to do?

Link to comment
Share on other sites

Florux

I think this functionality already exists on the server. In the web interface you can Select Player and then remotely stop the stream.

 

Should be pretty easy to add a button in the dashboard under Active Devices that sends the same call.

 

@@Florux as another solution to get this functionality, does clicking the cast icon in the top right, selecting the player you want to stop, and clicking stop do the same thing you are looking to do?

 

This is good for local players, but does not cut it for guests / remote people watching. At least I'm not able to do, and in best case it'd be cumbersome.

 

What I believe to be the most user-friendly end-game would be to be able to abort resource intensive jobs (CPU, bandwidth etc) from the dashboard under active devices. Ultimately it could even, as a mouse-over, show the bandwidth and CPU resources associated with that particular device, allowing the operator to cut either hanging processes or remote users over-using.

 

 -Florux

Link to comment
Share on other sites

@@Luke is there a reason this isn't as simple as adding a button to send a POST to:

 

/Sessions/{Id}/Playing/Stop

 

Are there any clients which can't be remotely stopped? Or is that all it would take?

Link to comment
Share on other sites

Maybe but I would like to redesign remote control to be in a flyout that we can slide up/slide down, rather than redirecting to a page for it. that will be better for mobile so that you don't lose context of where you are. so once we have that, we can add a remote control button to each one to bring up the remote control panel.

  • Like 1
Link to comment
Share on other sites

denethor

@@Luke is there a reason this isn't as simple as adding a button to send a POST to:

 

/Sessions/{Id}/Playing/Stop

 

Are there any clients which can't be remotely stopped? Or is that all it would take?

I think this may not be good enough. Player should understand the kill command from server and display friendly message to that particular user. Like: "server owner stopped your stream for personal reasons please text him/her to ask what going on" :) Edited by denethor
  • Like 1
Link to comment
Share on other sites

Ah, if that remote redesign is planned then that should solve this use case nicely, instead of just adding stop buttons.

Link to comment
Share on other sites

I think this may not be good enough. Player should understand the kill command from server and display friendly message to that particular user. Like "server owner stopped your stream for personal reasons please text him/her to ask what going on" :)

 

I can see wanting to display a message so another person knows why their stream stopped, and doesn't just hit play and then report a bug on the forums that their stream is randomly stopping  :rolleyes:

Link to comment
Share on other sites

  • 1 year later...
  • 1 year later...
Jdiesel

Any updates on this. There has been some progress in a few app to prevent runaway playback but a need to kill streams on demand is still needed.

 

I have a remote Chromecast that has been playing for over a day with no way to stop it. Playback continued even after the server has been restarted. This is a must have feature than Plex has had for years.

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

Any updates on this. There has been some progress in a few app to prevent runaway playback but a need to kill streams on demand is still needed.

 

I have a remote Chromecast that has been playing for over a day with no way to stop it. Playback continued even after the server has been restarted. This is a must have feature than Plex has had for years.

Yeah, I'm seeing the same thing, except far more than a single day. I have a remote stream that's been running for weeks, and yeah a restart of emby does nothing.

Link to comment
Share on other sites

Jdiesel

I ended up having to block Chromecasts from being used on my server. It was causing way too many issues.

Link to comment
Share on other sites

  • 3 months later...
runtimesandbox

Agree, still struggling with chromecast feeds endlessly running in the dashboard. 

Is it not possible to have a stop button like the other devices / streams do?

Link to comment
Share on other sites

horizonbrave

is Google getting the blame that we can't have this feature because of some locked-down APIs?

Edited by horizonbrave
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • 2 weeks later...
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?

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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? 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...