Client would parse the element mentioning the location in the file for the cue element (which is going to be at the end).Client would read and parse the file from the beginning by making an HTTP request to read the file from beginning to the end.This caused slow playback start because of how the client would play an MKV (similar occurs with MP4): The bug manifested in that a single file opened multiple times would cause the second to not be able to read any data for a long period of time (on the order of 30s). In case it helps to find the real issue, I’ll describe the old bug: I thought they had fixed it but maybe it regressed (again). The media was made accessible to the Shield via SMB (but not SMB 3)Īssuming that the above is true, then you may have encountered a bug in the kernel on the Shield.The Plex Media Server was running on the Shield.

The client was on the Shield and was direct playing.

It’s hard to glean the information from this thread but if I understand this correctly you were experiencing the issue when:

Using nvidia shield as plex server