Not a bad idea. Of course that test would be specifically for my client/TV/AVR combination.
I don’t have any movies with DTS-X or Atmos soundtracks but I have files with TrueHD and DTS-HD Master Audio and they have mostly worked. I ran into a couple TrueHD tracks that have caused issues.
there no KNOWN combinations of E-ARC TV + E-ARC AVR that can pass TRUEHD+ATMOS via plex.
If the combination of LG 65C9 OLED & Sony STR-DH790 truly pass unmodified truehd+atmos, I would like screen shots of the plexweb status, and a picture of the receiver with truehd+atmos indicators lit up.
OK, I reconfigured my speakers to 3.1.2 and was able to get ATMOS to display on my AVR using both 1) the LG TV’s built in Disney+ app playing Empire Strikes Back, and 2) using the Shield Pro to play the Dolby_Amaze_Lossless-ATMOS-thedigitaltheater.mkv file from the Dolby Trailers page I linked earlier. It says the file has Dolby TrueHD 7.1 ATMOS.
The Plex dashboard doesn’t specifically say ATMOS so I’m not sure if that means anything.
Also, the receiver display scrolled through the text “DOLBY ATMOS - DOLBY TRUEHD” and then settled on displaying ATMOS after the scrolling was complete.
Is that a successful test? I know these things can be more complicated than they seem.
Oh yeah, here is a shot of my LG TV eARC settings:
Interesting, I’ve just tried the 200mbps hevc jellyfish file and it plays without any issues on my Shield TV Pro (2019) with the new player. My server is on a Windows 10 Pro machine. Everything’s wired (10G + 1G). I hope this helps in your investigation in some way.
The 250mbps file is being transcoded (not sure why yet).
Hmm. I just tried the 200Mbps file again in case the last client update changed something but I still get the error on the Shield TV Pro (2019). Curious. Perhaps it is a matter of hardware quality for each individual Shield. Sort of like when PC folk would overclock their machines. People would have varying results on how high they could get their CPU running based on the quality of their inividual CPU (for a group of people using the same CPU model). Just speculation, of course.
The same 200Mpbs file plays on my PC using Plex for Windows and all the hardware is the same up to the network switch that the PC and Shield are both plugged into.
So, there’s a small update. The file I was using was jellyfish-200-mbps-4k-uhd-hevc-10bit.mkv.
After I’ve tried out the 200mbps (successful) and 250mbps (unsuccessful) videos I’ve changed to the old player and tried the 200mbps file -> it transcoded.
I’ve closed the plex app and started it again, was greeted with a new splash screen (new watch together feature) and since then I haven’t managed to direct play the 200mbps video anymore.
Before it definitely direct played, in several attempts.
I even made a screenshot:
Plex for Kodi on the other hand has no trouble direct playing the 200mbps and even the 250mbps HEVC 4K versions. I’m currently downloading the 300mbps and 400mbps files to try them out.
Mysterious. I seem to recall something about Plex analyzing the files during maintenance. I wonder if, during that process, it sets up a parameter that tells the server to transcode that file or not.
Edit: found a link to a relevant post…
I haven’t tried Plex for Kodi yet but it sounds like I need to set that up as a fallback/troubleshooting player.
Looks like we are all getting slightly different results for the same files on the same hardware. Odd.