link to the thread?
My entire library is HEVC, it’s playing fine. It’s 4K HDR that is transcoding for me, nothing else. All SDR HEVC (1080p, 720p, 480p) etc is working just fine. So it’s not HEVC that’s messed up. The Transcode Reason for the 4K HDR content is “Either Resolution or Bitrate not supported”. In the Streaming Devices category of the forums, there’s a bunch of posts with varying levels of Plex support involved and working on the issue.
i stand corrected, 4K HDR is not working HEVC appears to not be the culprit.
1 Like
I can’t find the exact thread right now, since there are several reports of issues with the Fire devices. It’s also likely that having one of these confirmed didn’t relay the information properly that these other reports are related. To summarize, here are the issues we are aware of and either investigating internally or already working on a fix.
- default h264 level set to 1.0
- h264 profile support not being detected correctly, you’ll see a message like “high profile not supported”
- 10-bit HDR not working
- New Cube TV specifically will not play anything
There is also a generic issue with all Android TV, not just Fire devices, where the refresh rate or automatic resolution switching can cause issues.
4 Likes
awesome, this makes me feel better. I honestly think that announcements should be expanded to include information like this when problems arise. This would go a long way I think.
1 Like
When you’ve got 100 Threads about a sweeping issue - an announcement and directions to ‘The Working-On-It Thread’ would go a long way - to quelling user hate that builds, and builds, and builds…
1 Like
exactly, you can look at my recent post history (even the mod deleted ones, lol) i’ve been an asshole the last few days because this really pissed me off. Now? I feel fine.
In the first few minutes after a ‘China Syndrome’ is detected, Staff should make an announcement with directions to the ‘Working-On-It’ thread.
Volunteers can direct traffic and moderators can close threads and maintain order.
Meltdowns happen.
Deal with it.
Plex’s name is being dragged through the mud a lot, on major forums. I guarantee if they did this one simple thing right here, a lot of that would stop. I understand problems happen and it’s to be expected when they try to support a plethora of devices. But when you jump on this forum, and you can’t find a post right away like @anon18523487 's explaining they are completely aware of this and all other issues, and are working on it, it is beyond frustrating. This would pacify the user base, and not only that, it would lower duplicate threads significantly.
1 Like
True, but often times users are not able to express the problem appropriately to know if a known issue is the same as what they are experiencing. Or users may think they have the same issue and it turns out to be something else. That’s why it’s best if users report problems following our guide and providing as much info as possible, including logs. That’s the only way we can verify if the issue is the same.
I still think there should be a way for them to stop that bad client from getting loaded…
1 Like
ya but at least pinning a running list of issues at the top of a device’s thread would work wonders.
Moderators/Volunteers would be there to grill (ask) users for the correct info - or interrogate (explore) more deeply for what the issue may be - splitting off threads as required.
User Benefits:
They don’t waste time acting like Savag… Native Americans preparing for a re-enactment of The Little Bighorn - with Plex playing Custer. They get what they’re looking for. Help. They’re part of the process - even if they’re just reading.
Plex Benefits:
(See Above) Everything they need is being gathered efficiently. The area is under control, a curfew has been announced, but order remains while the problem is being worked… and progress reported… if any…
1 Like
I have to agree. IMO the moment i started losing faith in plex was when they switched the forum design to this one. That was the turning point for me. You say the information is here, I say fine, but why does that information need to be buried?
Does this list include whatever is causing the playback issues we’ve talked about over private messages?
finally the 7.29.1 update has fixed this for me.
Odd. 7.29.1.15972 still sets H264 to 1 for me. I mean, sure, I can manually fix this, but trying to talk family and friends through this as they ask me why their videos look so bad, while my server wants to die under all the pointless transcode load over what seems like an incredibly simple bug to fix is kind of annoying.
well, i did a fresh install of it, maybe try to clear data from applications settings?
how did you get that update? its not available according to amazon?
Motherf*: NOTE: We are performing a staged rollout, which means the update may take a day or two before it becomes available.
SERIOUSLY?! NOW YOU ARE DOING A STAGED ROLLOUT?!?!?!?
Why didnt you do it with the old update?!
That’s the Plex client 7.29.1.15972 that is released by Plex and has to be side loaded…
I had problems with that release and also with
kepler-armv7a-amazon-fireExo-7.29.2.16071-71e4f554
because of issues with both I had to roll back to
kepler-armv7a-amazon-stdExo-7.27.1.15203-5c57babb
only one that seems to play everything without problem for me…
1 Like
