So when it’s acting up with buffering or won’t connect to the server I restart wifi on my shield, quit Plex client, open Plex client again and it works fine for a while.
(I know I should be using ethernet but this bug seems worse for me over a wired connection.)
I agree, it does seem worse over a wired connection. It is just baffling!
As a matter of fact when I stream a show over 250 miles away to my brothers house they play with no issue what so over but over gigabit ethernet connection in my house with my server just a few feet away I encounter this damn problem.
I am seeing the same error when I try to stream a movie from my nVidia Shield Pro 2019. The movie is stored on a USB disk connected to the nVidia. No network involved. It only happens for a few of the 100 or so Movies I have.
I too have these issues. I’m running Plex 1.19.1.2645 on an AppleTV 4K.
Both wired as wireless I have this issues. I have a Gigabit network, and Plex is running on a 12 Core i9 10920 with an NVidia RTX 2060 graphics card, so I refuse to believe that this setup is not able to stream at the required network speeds.
What works most of the times is “close” the Plex app (swipe up) and reboot the AppleTV, but it sometimes takes 2-4 tries. However, when it works, it usually works the entire evening.
I have two AppleTV 4K’s and both have the same issue. Reconfigure (reset and reinstall) only worked once, but I guess it would be similar to restarting.
From the various threads I see that this issues is existing for quite some time now. Are the Plex developers reading this forum?
Downgrading the stream quality is not an option for me. That is just ridiculous.
plexlog.txt (573.1 KB)
Having this issue. I tried using Kodi as the player too. It’s a new PC, ryzen 3900x, WD RED RAID 1 serving the video. Wired connection to new Nvidia Shield TV.
After about 10 minutes the error pops up. Nothing else is using that hard drive. I’m at a loss, things should be stoopid fast. If anyone can check the log above and point me in a direction i’d be very thankful.
To clarify, I also have it hang using Kodi and Plex add-on
I sat there, watching the HDD in task manager. It just stops transferring, and then about 20 seconds later the video cuts out with the connection error. Could this actually be a server side bug?
I’ve noticed, if I’m downloading (to a completely different hard drive) the issue presents itself much more often.
Has anyone else had the issue with Kodi as well? All my content is 4k, HDR, DTS, Atmos, etc. That’s the whole point to me as I’m driving a 10 speaker home theatre.
Any work arounds? Other software options? Plex has been rendered completely unable to me, and as such so has my home theatre. I’m desperate for options.
This clearly is an Nvidia shield and PMS compatibility issues. Other Android clients play everything just fine. I just sold my 2017 Shield and upgrading to the 2019 version. I really hope the 2019 solves this stupid issue but I swear I’ve read some people having the same problem with the 2019.
Side note, I’ve discovered that there’s a connection to download. I download to a 500gb SSD, then upload to the raid array after to avoid slowing down the HHDs while playing back. So downloading and playback are on completely separate drives.
If i’m downloading, the error happens every ten minutes. Not downloading? Never-to-every 2 hours.
Definitely connected somehow, even though completely separate drives…
I wonder, is the SATA getting overwhelmed? it is old tech…
That’s possible but I doubt SATA3 is being saturated, unless of course you have a lot of users. I use a Debian NAS myself and when I encountered this issue in the past it was as random as it can be.
I don’t think the throughput is the issue, it’s rated for 6gb/sec. But when you’ve got 20 torrents going, that’s a lot of connections writing data at complex timings. I think the performance of data is suffering due to amount of read and write requests, not the bandwidth. I’m no expert though, but it seems that if I’m not downloading (again, to a completely different drive but still SATA), then the issue dissappears.