Hi
I have a couple of files that are h.264 AC-3 in a MKV container. Pretty standard stuff.
The Plex server is pretty weak, too weak to do any transcoding. But with Direct Play the Xbox is supposed to do the groundwork, right?
Even though the server and the Xbox is connected to each other via a gigabit switch it lags and buffers almost constantly (plays for 10 sec, then buffers, repeat)
I could swear these files played flawlessly before. Could there be any settings that causes this?
The first place I would check is your Plex Media Server.log. This will tell you if there is anything causing an issue on the server side of things. (This support article will help you find the log)
When the file is direct play, it is basically a file transfer between the server and the xbox app. The only way a setting could be causing this is if there is setting set that is causing a transcode.
I see this alot. Only thing that really strikes me as an error
“Failed to stream media, client probably disconnected: 10054 - An existing connection was forcibly closed by the remote host”
This is not something i see around the time other Direct Play files were streaming.
That error simply means that the client (The Xbox One or another plex client) requested the server to stop sending data to it. This sometimes occurs in situations such as where the client simply gets shut off and the server is still expecting to be sending data to it.
I’ve come to the conclusion that the server might actually be too weak to deliver a steady file transfer at the required bitrate…
Ordered a Pentium G4500, boy those were cheap! The passmark score of the old one was around 600(Atom 330…) The G4500 is 3997. Nearly 7x the score. Should to the trick, even at transcoding.
