I've been using Emby for quite a while without any issues that would prevent me from watching videos, etc. However, after updating the server to the latest version (126.96.36.199 on armv7 on Debian) there are some issues with video playback. Before the update, I was able to stream videos (H264 in MKV containers) without the need to transcode them. I am running the server on a RaspberryPi 3B, so transcoding would not be an option as it definitely can't happen in realtime (log attached). After the update, the videos somehow need to be transcoded in order to be played back properly.
Why is there a flag set for mkv not being supported?
Few lines higher:
2019-04-22 11:54:23.059 Info App: Profile: Unnamed, Path:*****.mkv, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
This would not be an issue if the transcoding was happening in realtime, but its not. I tried disabling hardware acceleration in the server settings, and yes, it did prevent the transcoding process from executing, the video did start, but it was choppy, it kept buffering after three seconds of playback, which I suppose was playing OK before updating. Note that I obviously tried playing different files, with similar results.
I have to note that I am using an app remotely, yes, connections both on the server and client side are an another variable in the process, but I highly doubt it could have such an impact, this wasn't happening before. I'll test it in a few days using local connection and post the result here.
Attaching emby and ffmpeg logs (I replaced my IP with some text for safety reasons).
Thanks for the help.
I've found some older logs from previous server version, the transcode flag was still set, but it wasn't transcoding the file but "StreamTranscode". I also attached the old logs.
Edited by Razrector, 22 April 2019 - 06:43 AM.