transcode reason: recovering from playback error

[TeamB 2438]

playback in a browser was causing transcoding when it should not be and the reason given in the dashboard was

recovering from a playback error

what does this mean?

Edited October 8, 2023 by TeamB

[Luke 42083]

Hi, it means the browser video player raised an error and so we automatically switched to transcoding in order to keep playing.

[rbjtech 5284]

Is there any more detail available on these 'Recovering from a playback error'  messages - maybe a dump on the standard I/O to a debug log or something to assist with WHY ?   

I've notice a lot more of these creeping in on what I thought were perectly good files that play fine on all platforms manually, but still give the error from emby.

Edited October 8, 2023 by rbjtech

[TeamB 2438]

it is weird because the media file in question actually plays fine all the way though on all the clients I have tested on. I have been trying to reproduce this all day and can not.

this happened on a play session my wife had earlier today, the only thing she did out of the ordanary was left the web client paused (in firefox) for a while (10 to 20 min) and then came back and unpaused it play the rest of the file. This is normal for her and how she uses the system.

In the log I see a reference

2023-10-08 13:54:20.082 Info EncodingManager: Transcoding kill timer stopped for JobId f47ac549-9213-409d-bf56-956ad66eb226 PlaySessionId b3d208bfa16649a0add2f7190e0d29bd. Killing transcoding
2023-10-08 13:54:20.082 Info App: ProcessRun 'StreamTranscode f47ac5': Stopping ffmpeg process with q command for C:\Users\user\AppData\Roaming\Emby-Server\programdata\transcoding-temp\2A702D\2A702D_0.ts
2023-10-08 13:54:20.113 Info App: AppendExtraLogData - Read graph file: C:\Users\user\AppData\Roaming\Emby-Server\programdata\logs\ffmpeg-remux-f47ac549-9213-409d-bf56-956ad66eb226_1graph.txt
2023-10-08 13:54:20.115 Info App: AppendExtraLogData - Deserialized GraphData fileStream: 6,712.00 bytes Graph Count: 1
2023-10-08 13:54:20.116 Info App: AppendExtraLogData - File Deleted
2023-10-08 13:54:20.122 Info App: ProcessRun 'StreamTranscode f47ac5' Process exited with code 0 - Succeeded
2023-10-08 13:54:21.090 Info SessionManager: Session 5badf6d548efaaf3baa1b39837dc55eb has gone idle while playing
2023-10-08 13:54:21.090 Info SessionManager: Playback stopped reported by app Emby Web 4.7.14.0 playing Crete. Stopped at 305217 ms

and that lines up with the weird message and double finish message in the dashboard

Its like being paused too long casued the session to time out and triggered an error that then caused the rest of the play session to be transcoded.

 

Edited October 8, 2023 by TeamB

[Luke 42083]

It’s possible there are some quirks related to this yes. There are areas we need to improve on related to pausing something and then just leaving it paused indefinitely.