Thanks for investigating my issue.
I disabled Tone Mapping today and also tested two 4K HDR TrueHD clips with a 1080P TCL Roku TV and it also did not work, as expected given your explanation (assuming that TV also does not support 10-bit video).
More findings:
In fact, it seems that ALL 4K HDR clips (not just TrueHD audio ones, but even clips with EAC3 5.1 audio e.g.) NOW no longer play on 1080P devices that (presumably) do not support 10-bit video either, so the Tone Mapping issue being the culprit makes sense.
The majority of my TVs are 4K (all the main areas / rooms), so I do not use the 1080P ones (except the small one on the porch) and cannot pinpoint timing, but I guess this all started with my āforcedā (see why below) upgrade from PMS 1.23 to 1.25.
I say āforcedā because that was when that early April PlexTV (client) update āborked TrueHDā even on 4K HDR TVs (per another long thread).
At that time, since no TrueHD clips played anymore after that PlexTV client update (in conjunction with the PMS version I had at the time - 1.23), like other users, I was forced to finally upgrade to PMS 1.25 (knowing transcoding was broken, but I balanced that with knowing the TrueHD fix was necessary to be able to keep playing TrueHD clips on 4K TVs).
So my assumption is none of my 4K HDR clips would have played with Plex on my 1080P devices since April upgrade to PMS 1.25 ā¦
Its been well over a month, and having worked with two mods to replicate the issue, both have confirmed the issue exists and forwarded it to the development team. Since then, over a dozen updates have come out, none to address this transcoding crashing failureā¦
How long does it typically take to fix issues?
Literally plex is currently unusable for most transcoding because of this bug (a bug which the mods have reproduced by working with me on their end, indepedant of my server!)
Any news regarding addressing the Tone Mapping issue which is preventing 4K clips from working on 1080P Plex clients (devices such as Roku TVs or Roku 3) that do not have 10-bit video support?
(Most of my TVs and Plex clients support 4K HDR / DV, but I still have 2 or 3 exceptions (1080P devices without 10-bit video support).
The fix will be out in the next release. To be clear, the fix is to play the files again as-is, so it may look horrible on a TV that doesnāt support 10-bit.
Thanks, understood / noted. We wonāt set our expectations too high then.
Luckily at home this is a non issue: Other than the guest room TV (which we do no use ourselves), the only other 1080P TV is in an area we do not watch Plex anyway (workout area).
For us it may be more relevant when watching Plex content remotely where the only available TVs may be non-4K sets without 10 bit support.
FYI ā I needed to do this āoptimisationā because while this will work perfectly from the iOS Plex app on my iPhone (even when then cast to my Sony TV running Android), it wont work directly on the Android TV app on either the nVidia Shield or the Sony TV)
Not the same issue. It does appear to not use hardware transcoding for that optimization, but I canāt say why. Iāll need the logs from the start of that.
Edit - Can you post the entire xml info for that video? I canāt tell why it wouldnāt direct play in the first place based on that image.
The only thing I see in that info is that the aspect ratio is wrong. According to the resolution, it is 2.39 but the file lists it as 2.35. I would need to see the server logs to check what it is doing but itās possible itās transcoding to get the aspect ratio to match the 2.35.
Another thing to check in your client settings is to make sure Automatically Adjust Bitrate is turned off. That option forces a transcode.
Your TV is not on the same network as your server so itās treating the connection as remote and using the remote quality setting. The remote quality setting on the client is set to 2 Mbps. Your file is 14 Mbps, so that is why it is being transcoded.
This is the public IP of your TV. Your server shows a public IP at 155.x.x.x.
So, raise the remote quality setting to prevent the transcode or figure out why it appears to be on a different network than your server. You could also include that public IP to your PMS settings to treat it as local.
On the bright side, it is using hardware decoding and encoding.
Jul 06, 2022 19:19:36.463 [6542] DEBUG - [Req#66eab/Transcode/f59fd00fe9a83288-com-plexapp-android] TPU: hardware transcoding: final decoder: mediacodecndk, final encoder: mediacodecndk
Thanks, I am definitely on the same network as the NVIDIA Shield (where my Plex Server resides). In fact, playback on the Plex Client on the same Shield device doesnt work either (so that is definitely the same network!)
I think that the log entry you found might have been a remote user trying to play that same content.
I have now set the remote limits to Max, and the episode buffered badly (after waiting for about 3 mins for playback to start)
In this case you are playing on Plex Web (in Firefox). Your video is 10-bit HEVC. Firefox does not support HEVC so it has to transcode. Your logs do confirm this is local.
Is your Shield hardwired or WiFi? If WiFi, check that it is on the correct SSID. Your logs do show a different public IP accessing your server.
What specifically doesnāt work? Nothing plays, it canāt connect to your server, it connects remotely, etc.? The android logs from the Shield will be best to diagnose that issue.
Playback on either devices fails i.e. a orange circle animation for a very long time (10+ minutes), followed by either no playback (on Sony Android TV) or intense buffering (on Plex Web client).
FYI ā This is what happens when I press play from either client ā intense local traffic ā¦ then nothing.
Huh. Your logs indicate the subtitles cannot be direct played nor transcoded. That doesnāt make sense. Can you turn off the subtitles and see if it will play then?
If that works, can you extract the srt from the file and send it to me? Iām wondering if itās not actually srt but named that way and the Android app is failing trying to render it.
