Emby playback stops/stutters entirely after long playback

[Grouse 0]

To clarify: After a long period of time playing a video directly to a remote client successfully, Emby playback just fails. This has happened on two seperate types of client, both a Tizen Samsung TV, and an Android TV 9 client. Switching over to a Plex instance immediately works (on the same type of client), where Emby was still broken. S.M.A.R.T Status of the HDD which the content is stored on reports good health, Emby Server and its encoding temp files are stored on an NVME Gen4 SSD. Found 'System.IO.FileNotFoundException: Could not find file' (in embyserver) around the time it started to break after a couple of hours of successful playback, also included is the ffmpeg transcode log of the missing video fragment (ffmpeg-transcode-de2358bb-f7d7-4c05-9b1c-0532ed1d845a_1.txt). Also of note is that around this time there are a huge amount of ffmpeg logs, in the space of one minute there are twelve seperate logs. Those are also attached if needs be.

 

Thanks! 

embyserver-63857018761.txt ffmpeg-transcode-de2358bb-f7d7-4c05-9b1c-0532ed1d845a_1.txt

ffmpeg-transcode-00ddf921-eddc-4b92-a7c1-bc0515d4cd8f_1.txt ffmpeg-transcode-0f10960a-58c6-4bdf-918a-2af51703ef10_1.txt ffmpeg-transcode-3b6f9f8b-e9dd-4a87-ae22-722a9cbb7888_1.txt ffmpeg-transcode-05edb48b-4695-4c9a-9d15-57c5ba847289_1.txt ffmpeg-transcode-7d592a45-6994-4a76-9bd8-ba1fa9ec737e_1.txt ffmpeg-transcode-8c72372f-8056-4fbc-a667-6bd51ca7d5b0_1.txt ffmpeg-transcode-75d387b6-41f7-42bc-b900-afb9b36db369_1.txt ffmpeg-transcode-abbd8a4c-b9eb-447a-aa3d-008685a4eb9f_1.txt ffmpeg-transcode-b4a81873-63e7-4877-bb39-ab9442185b55_1.txt ffmpeg-transcode-d6652b78-189e-41ff-a66c-026bceffefd3_1.txt ffmpeg-transcode-ec5c683d-bc43-4cc6-b082-2e9c3b7f0a93_1.txt ffmpeg-transcode-eebfe3ae-92c5-4fbf-b548-178632404634_1.txt ffmpeg-transcode-fe822aa8-3a78-4ffb-ae12-f7a6056523a8_1.txt ffmpeg-transcode-461991bd-8a5e-41bc-a92c-df17ddde8828_1.txt

Edited July 20, 2024 by Grouse
Added additional ffmpeg logs

[Abobader 3464]

Hello Grouse,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Grouse 0]

Decided to move back to Plex because despite troubleshooting, upgrading to beta, changing transcode location (in case PATH or permissions were the issue), nothing has worked.

[Luke 42079]

4 hours ago, Grouse said:

Decided to move back to Plex because despite troubleshooting, upgrading to beta, changing transcode location (in case PATH or permissions were the issue), nothing has worked.

Hi @Grousebut don't you want a personal media server and not one that puts all of your information into the cloud?
We're happy to help you resolve your issue.

[Grouse 0]

  

11 hours ago, Luke said:

Hi @Grousebut don't you want a personal media server and not one that puts all of your information into the cloud?
We're happy to help you resolve your issue.

I'd love to. Extremely appreciate of the fact that I don't have to use an account for Emby, and to get remote access working it requires a far simpler VPN Policy Routing as compared to Plex. I'm just absolutely stumped at what could possibly be causing issues. I experienced similar issues on the Samsung Plex app, but was subsequently resolved in switching to Android TV. If it were local only I'd stick with Emby, but providing remote access to my library is a requirement.

Edited July 27, 2024 by Grouse

[Luke 42079]

@Grouse

Hi.  Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares?

Thanks.