High Bandwidth via Direct Play on Windows 10

Server Version#: 1.19.4.2902
Player Version#: 1.12.0.1232-aacabe78

Plex Media Server Logs_2020-06-08_20-26-27.zip (5.2 MB)

The Plex for Windows app has been behaving very odd in terms of the network usage. Network send on the server and receive on the client player both show network usage of over 200Mbps when playing back any 1080p 8Mbps content. The playback buffers constantly and is unwatchable.

Switch to the Plex Media Player version 2.58.0.1076-38e019da on the same device and playback is flawless and barely uses any network bandwidth at all staying at a set limit of around 12Mbps for 1080p content.

image

New version released today to address stuttering video. Announcement below.

An initial burst of traffic is normal until the client buffer fills. The traffic should then settle down.

Direct Playing 10 Mbps video with Plex for Windows 1.12.1.1253.

Just updated to the Plex for Windows version above and still seeing constant network usage of over 200Mbps during playback.

Client player

Server dashboard

A test:
Get MKVtoolnixGUI
Drag your mp4 file into it and press “Start Multiplexing”
Add the resulting MKV file to your Plex library
play it

Is the faulty behaviour gone?
If it is, the original mp4 file has been incorrectly muxed by a broken software or script.

1 Like

On the advice above, I’ve tested other 1080p movies in the library in both MKV and MP4 formats and they all played back fine. I’m currently re-encoding the affected movie to MKV from the original media and will import and test.

Remuxing as instructed would have been much, much quicker, though.

I decided to re-encode as I noticed the file was also missing the 7.1 surround audio track.

Network usage is now normal for the affected title and only spiking briefly when buffering. Playback is now flawless and thank you for your guidance.

1 Like

Late to the party but in your logs in the OP, the logs are full of range requests for the same file. This is exactly what will happen when a file is badly multiplexed. Basically the client has to skip back and forth in the same file to read the video and audio because they aren’t located next to each other. The way this is done when a client is playing over HTTP is to abort the connection and create a new request starting at a different point in the file. Your logs have 10s of these per second which is responsible for your issues.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.