@mrrob@me.com said:
Thanks for your response BigWheel. I did attached the Plex Server Log in my post. I enabled it in Xbox Settings, then played the file for awhile with it pausing periodically, and then attached the Server Log as instructed. Is there something else I’m supposed to be providing? Xbox doesn’t have an app log does it?
The app has a setting in the options to log to the server log. So if you enable logging in the xbox one app additional log entries will be created in your Plex Media Server.log The log you provided actually takes affect after the transcoding has already started so all we can see is the progress of the transcode and not the initial calls (With your processor though it really shouldn’t matter if you’re transcoding video/audio or both though).
The file itself is in an MKV container and used a H.264 codec for the video. Full codec shows as H264 - MPEG-4 AVC (part 10)(avc1) when viewed in VLC. It is a DTS audio file, so I guess the audio is having to be transcoded, but not the video.
Any DTS audio will have to be transcoded on the Xbox One until Microsoft releases a DTS decoder for 3rd Party developers. The video should direct play or stream, but without the transcoder calls when you start playback we can’t be sure that is what is happening.
I’m starting to think Plex is just not all it’s cracked up to be. I also have it on my Apple TV gen 4, and just went to play a standard HD 1080p file. It played for 5mins then said the network wasn’t fast enough to stream it. Switch apps to Infuse and Infuse played it immediately with no issues at any time. If Infuse can stream the file just fine via Apple TV, if the WD Live device never had a problem streaming these files, then when Plex has issues, it’s not hard to determine where the problem lies.
Unfortunately, it looks like your server is struggling to keep up with the transcode. Your log has a lot of speed values of less than 0. What this speed value actually means is how fast your server transcodes in realtime. So anything less than 0 means it is taking longer than 1 second to transcode 1 second of video. The tricky part here is because your speed value occasionally bounces above 1 into around 1.5-1.7. This has the effect that you are seeing where it will play for a bit, buffer, play, buffer. From the logs there isn’t a way to tell what is actually causing the slow transcode. (IE hard drive speed, slow CPU, Other things using the CPU, network congestion, etc).
The first thing I would try is setting up a temporary folder on your Mac with the problem file, add that folder to a test library, and then playback the file in your test library. This will help you eliminate network congestion from the process. Typically, when you have an above average CPU and low transcoding speed values the main cause is disk speed or network congestion. With your media all setup on network storage and a transcode happening the server has to pull the file from the storage location, transcode the file, and then send the file to the xbox one. Because the speed values are bouncing between 0 and 1.7 the problem isn’t with sending the file to the xbox and has to be with either pulling the file from storage or transcoding. This is why the above test is helpful in narrowing it down.
The other thing I would check is to make sure that everything is negotiating at proper speeds. IE is your iMac and network drive bothing reporting a 1Gbs connection. If you’re negotiating at 100Mbs you may be running into a lot of network congestion.