Now playing still shows on file that's finished playing

[sa2000 674]

6 minutes ago, Neminem said:

What happens if you leave the stream running and just turn off your TV ?

Just switching off the TV that the roku is connected to was detected by the Emby for Roku app and it sent a playback/stopped status to the server.

[bandit8623 213]

36 minutes ago, sa2000 said:

Just switching off the TV that the roku is connected to was detected by the Emby for Roku app and it sent a playback/stopped status to the server.

just a fyi this one is a roku tv.  so not sure if that makes a diff.  old and slow roku tv.  

[sa2000 674]

1 hour ago, bandit8623 said:

just a fyi this one is a roku tv.  so not sure if that makes a diff.  old and slow roku tv.

Thanks. My tests were on a roku 3 which pre-dates roku tv. I only had one session not detected as idle in my tests of several playbacks.

[speechles 2055]

@bandit8623

They pressed home during playback? Either that or they just turned off the Roku TV during playback. Both have the same effect on a Roku TV making it so the Roku app cannot tell the Emby server to stop playback. Using the Home button or turning off the Roku TV will immediately exit the running application. Since nothing can be done after that we then depend upon the server to then kill the active session of video playback. The transcoding is completed. The TS segments are not being deleted nor is the m3u8 playlist.

Do you have a server log from that time period? The server might have tried to end the abandoned session but something (an error or something similar) kept it from doing so. I know it is hard to have a log from 3 days ago and how massive that might become. So maybe next time you see this happen try to catch logs right away and share those and we can probably find some kind of circumstance that would cause the issue and how we might react in that instance. Because something is slipping through the cracks here. Quite literally. There are safe-guards in place that are supposed to catch these things but this one is proving elusive.

Edited November 18, 2025 by speechles

[sa2000 674]

I think it might be when paused because the Roku app does not appear to send the periodic time updates whilst paused and I would presume because of that the server would not have the means of detecting an idle session through lack of time updates

roku 3 behaviour may be different from Roku TV when home button pressed 

[bandit8623 213]

11 minutes ago, speechles said:

@bandit8623

They pressed home during playback? Either that or they just turned off the Roku TV during playback. Both have the same effect on a Roku TV making it so the Roku app cannot tell the Emby server to stop playback. Using the Home button or turning off the Roku TV will immediately exit the running application. Since nothing can be done after that we then depend upon the server to then kill the active session of video playback. The transcoding is completed. The TS segments are not being deleted nor is the m3u8 playlist.

Do you have a server log from that time period? The server might have tried to end the abandoned session but something (an error or something similar) kept it from doing so. I know it is hard to have a log from 3 days ago and how massive that might become. So maybe next time you see this happen try to catch logs right away and share those and we can probably find some kind of circumstance that would cause the issue and how we might react in that instance. Because something is slipping through the cracks here. Quite literally. There are safe-guards in place that are supposed to catch these things but this one is proving elusive.

I'll grab those when I see it. The users don't use that TV very often.

 

Thx for the help

[bandit8623 213]

9 minutes ago, sa2000 said:

I think it might be when paused because the Roku app does not appear to send the periodic time updates whilst paused and I would presume because of that the server would not have the means of detecting an idle session through lack of time updates

roku 3 behaviour may be different from Roku TV when home button pressed 

i just asked the user.  they power off the tv.

[speechles 2055]

5 minutes ago, bandit8623 said:

i just asked the user.  they power off the tv.

The TV might not include an HDMI-CEC handshake the Roku could interpret when the TV has lost the active input device signal. The older Roku 3 might not even include full HDMI-CEC detection. I no longer have one of those older devices to test with since Roku updated the models they require us to test with. They require we test on Roku stick and Roku express as the lowest end. If something misbehaves on the Roku 3 it is expected they tell us. Apologies this is happening. If you train them to always exit video playback before power off the TV it would help. Otherwise the Roku continues to play even when the TV isn't the active input source or the TV is turned off. Tell them it isn't their fault, your fault, or the apps fault. It is just the Roku 3 is getting up there in years and starting to show its age.

[bandit8623 213]

24 minutes ago, speechles said:

The TV might not include an HDMI-CEC handshake the Roku could interpret when the TV has lost the active input device signal. The older Roku 3 might not even include full HDMI-CEC detection. I no longer have one of those older devices to test with since Roku updated the models they require us to test with. They require we test on Roku stick and Roku express as the lowest end. If something misbehaves on the Roku 3 it is expected they tell us. Apologies this is happening. If you train them to always exit video playback before power off the TV it would help. Otherwise the Roku continues to play even when the TV isn't the active input source or the TV is turned off. Tell them it isn't their fault, your fault, or the apps fault. It is just the Roku 3 is getting up there in years and starting to show its age.

its a roku tv. so all in one. cec shouldnt really be involved?

really no issues for them.  just annoying for me the server admin

Edited November 18, 2025 by bandit8623

[speechles 2055]

1 hour ago, bandit8623 said:

its a roku tv. so all in one. cec shouldnt really be involved?

really no issues for them.  just annoying for me the server admin

If it is a RokuTV there are two things users of those devices should not (read this to them as can never) do. They should never press HOME or turn of the TV while playing anything in the video player. Press back to exit the video player then turn off the TV or press Home. This prevents them from losing their resume spots. It also prevents runaway playback. Explain the loss of resume point to them as why they should not so they see a personal benefit to doing it and reinforces the correct behavior. This is specific to the RokuTV line for the most part. Because when they do the app is then rudely terminated with no way to call home and tell the server to stop playing. The app is forcefully terminated on the spot the moment that happens. The server must "guess" the Roku isn't there anymore.

The server is expected to clean this up. But there may be cases where something is holding up that process. We would need to see server logs where the server did try to clean up and end the session. But something is in the way preventing that from happening. That is likely what is happening. Because when I try to replicate with my RokuTV the session isn't stranded. It exists for a few minutes after and then it disappears from the dashboard as the server cleans up and removes the session.

If you see it there 3 days later something definitely is causing the streams to stick as sessions. I am very very curious what that is as it isn't just something happening to the Roku. It is just more users experience it with Roku than other clients. But other clients occasionally see this same sort of thing. Seeing the server logs from those times would definitely help pinpoint where the issue is happening.

Edited November 18, 2025 by speechles

[bandit8623 213]

1 hour ago, speechles said:

If it is a RokuTV there are two things users of those devices should not (read this to them as can never) do. They should never press HOME or turn of the TV while playing anything in the video player. Press back to exit the video player then turn off the TV or press Home. This prevents them from losing their resume spots. It also prevents runaway playback. Explain the loss of resume point to them as why they should not so they see a personal benefit to doing it and reinforces the correct behavior. This is specific to the RokuTV line for the most part. Because when they do the app is then rudely terminated with no way to call home and tell the server to stop playing. The app is forcefully terminated on the spot the moment that happens. The server must "guess" the Roku isn't there anymore.

The server is expected to clean this up. But there may be cases where something is holding up that process. We would need to see server logs where the server did try to clean up and end the session. But something is in the way preventing that from happening. That is likely what is happening. Because when I try to replicate with my RokuTV the session isn't stranded. It exists for a few minutes after and then it disappears from the dashboard as the server cleans up and removes the session.

If you see it there 3 days later something definitely is causing the streams to stick as sessions. I am very very curious what that is as it isn't just something happening to the Roku. It is just more users experience it with Roku than other clients. But other clients occasionally see this same sort of thing. Seeing the server logs from those times would definitely help pinpoint where the issue is happening.

they dont care about resume as this is typically a live tv stream.  Thats not their goal to resume. even when watching a show they dont really care if it comes back to where it was.  they just want the tv off.  so when they are done watching they turn the tv off.

how about code a diff way of heartbeat from client to server?  if the client doesnt send a special heartbeat every 5 min  disconnect the client?  Just an idea.

or let us as admins clear the dashboard manually without having to reboot the entire emby instance?  For live tv there isnt even a stop playback button on the admin dashboard

  if i can get logs i will.

 

 

Edited November 18, 2025 by bandit8623

[speechles 2055]

2 hours ago, bandit8623 said:

how about code a diff way of heartbeat from client to server?  if the client doesnt send a special heartbeat every 5 min  disconnect the client?  Just an idea.

That is what should already be happening. In your case because this is a livestream other variables come into play. The server might try to kill the session and something is holding up that process. The logs would show what that is.

2 hours ago, bandit8623 said:

or let us as admins clear the dashboard manually without having to reboot the entire emby instance?  For live tv there isnt even a stop playback button on the admin dashboard

The server believes the session is still attached to an active encoding. If this was transcoding and you just remove the session it doesn't stop the active encoding that is still eating up one of your tuner slots and dumping TS slices into your temporary transcoding folder. Whatever is hanging up the logic that removes the session needs to be understood what that is. I am sure in the logs it will show the attempts to remove that session are failing.

Since you have experienced this and can replicate it the next time you can discover this if you can submit logs from as close to that time as possible. Then we should be able to deduce how or why this is happening and figure it out.

NOTE: You cannot stop a session on the Roku being watched remotely. The Roku does not allow an external IP address to access the ECP (https://developer.roku.com/docs/developer-program/dev-tools/external-control-api.md) port. This means you cannot cast or remote control that Roku. I do agree some kind of "bouncer" needs to be implemented that would stop their session and force their playback to stop. Like, you don't want to rudely throw them off your server, but you want whatever it is they are playing to stop right now. I understand the issue entirely. We are working towards a better solution.

Edited November 19, 2025 by speechles

[Luke 42077]

Hi, has this helped?

[bandit8623 213]

47 minutes ago, Luke said:

Hi, has this helped?

i havent had a chance to grab logs.  as its hard to know when it locks up.   i dont want to send in random server logs for 3 days of data that has to be sifted through.

Edited November 25, 2025 by bandit8623

[bandit8623 213]

Hi there,

@sa2000

So think i have an example. this has been sitting here for the day.

 

  ffmpeg-transcode-f3ca136e-ef5a-4df3-9dca-c05877b22e5b_1.txtembyserver (20).txt

[sa2000 674]

11 hours ago, bandit8623 said:

So think i have an example. this has been sitting here for the day

Thanks. I have added this example to the issue that is with the development team

I see it shows playback got to the end. There is no indication of that in the log other than it started at 07:39 at offset of 29 min 33 seconds

 

[bandit8623 213]

3 hours ago, sa2000 said:

Thanks. I have added this example to the issue that is with the development team

I see it shows playback got to the end. There is no indication of that in the log other than it started at 07:39 at offset of 29 min 33 seconds

 

user says the show was not over when they shut of the roku.  was around the middle point of the show

[sa2000 674]

24 minutes ago, bandit8623 said:

User says the show was not over when they shut of the roku.  was around the middle point of the show

The log confirms that - actually it was only played for about a minute and a half from 07:39 starting at offset 29 minutes into the 55 minute episode and last successful request from the roku was for an offset that was only 80 seconds beyond that. The 32' TCL Roku TV must have got switched off about a minute after start - and the server did not notice it