look in the main forum “Streaming Devices” there’s 30 other posts about this same issue. Some of them have Plex Team Members already chiming in. Find one where a Plex Employee has chimed in, read their post, if it asks for logs, follow directions. They know of the issue, but all information to help them track it down is helpful.
I have shared logs with @sixones before on various other bugs, and I never get a response back from him so sharing with him has been pointless to resolve other outstanding issues. If @sixones is actually committing to look into it this time around, it may be a different story, but I want to ensure that the time I spend grabbing logs isn’t for naught like it has typically been,
@BigWheel asked for the reason and assumes the basic things like Speed Must not be fast enough, even though clearly the UPDATE HAS BROKEN SOMETHING as devices that were working fine, now don’t. The other thread is also related to FIRE TV CUBE, and mine was specifically for the FIRE TV 4K stick…
Seriously mind boggling that an update like this has been broken for NEARLY TWO WEEKS and they need logs to troubleshoot, rather than talk to their internal developpers to see who pushed out a pile of code without peer reviewing it… Just want it fixed… or rolled back.
Latest PMS server from yesterday also didn’t fix it…
People are also discussing pointless things like h264 levels (which has nothing to do with HEVC!)
the devs are looking into it. I’m sorry it is not as simple as go back to x version. Sorry I have no ETA for a fix. Creating a new thread is not going to make finding the cause and creating a fix any faster.
people are discussing other things like h264 because if multiple things went wrong at the same time and they are all related to detecting devices capabilities incorrectly it is possible the cause of one issue is the cause of another.