I just downgaded the version of server but nothing to do … same error.
the server was nothing to do with the TrueHD issue reported in this thread, it was a client issue.
so other than downgrading the server unnecessarily, you have done no other troubleshooting?
I tried to downgrad plex media player on shield tv pro but nothing as well
why are you trying to downgrade?
the current public release version has no issues with TrueHD.
the issue is more likely related to your hardware setup rather than Plex.
But if I it was about harware, plex can convert truehd to other format ?
no idea what you are trying to say there.
plex server is able to transcode (assuming server is capable) audio if that’s what you are trying to say.
Yes. The same here. My Shield TVs are working great with Dolby True HD now.
No more problems for me either.
It’s not the Server it’s the Player. 8.30.2.31202 is the version you want for the Player.
8.30.1.31022 also works perfectly. Is there a reason to use 8.30.2.31202 over that one?
The issue discussed in this thread was fixed with the Android client 9.1 release. We’re now at 9.4.
1 Like
Ok great to know. So is the new version chill then? Are there any other open issues? I’ve been using 8.30.1.31022 for months because I’m afraid to update lol.
1 Like
Oh, there are tons of issues, but nothing show stopping.
Would you be able to name the issues? I’m wondering if I should stick with 8.30.1 lol.
Also, do you know whay the hell “enable i/o cache” does? Do i want this on or off? As usual there is zero explanation or documentation on this new toggle.
The issues that I’m aware of are mostly GUI related at this point. You’d have to do a search (or keep up with the daily bug threads lol).
@sixones explained this a while ago:
The I/O cache sits between the demuxer and your media source, pulling in data from the source in a linear fashion and allowing the demuxer to perform I/O seeks back and forth without hitting the network - allowing for smoother playback and playback of badly muxed videos where the packets arent contained in a linear fashion without excessive buffering. For pretty much all cases it should be left enabled, if a video is behaving badly during playback it can be useful to disable it temporarily to see if the issue is resolved - the option is there for support / debugging capabilities rather than something you want to play with yourself. Might be hidden in the future.
My bad. I can’t keep up with all of the threads in this forum, especially the bug threads. I did a google search for “Enable I/O Cache Plex” and found literally nothing. I found one single Reddit thread that had zero useful answers lol.
Okay I just tried out 9.4 on the shield. Seems solid so far. TrueHD seems fine. Seeking seemed fine. HDR/DV seemed fine (although I know the shield still has inaccurate colors for DV profile 7. I believe this is a nvidia problem and nothing plex can do).
2 Likes
Just upgraded to shield experience 9.1 and Plex 9.5 beta. Dolby TrueHD clips, sounds increase, clips, the Dolby Vision / Dolby Atmos trigger in the top right of my LG C1 is popping on screen every 2-3 seconds.
Changing the audio stream to Dolby AC3 5.1 seems to correct the problem. What is going on here?
Plex media server is up to date as well.
I’m on the latest updates as well, but haven’t experienced any (audio) issues so far. Can you give us an idea of what you were playing? Media info, etc.
Moonfall UHDRemux Dolby Vision Dolby Atmos.
Shield Pro direct to LG C1.
Makemkv for the Remux.
I tried Turning Red UHDRemux as well, HDR10 Dolby Atmos, once I selected the AC3 audio track playback stabilized. Could this actually be a problem with my LG C1’s handling of Dolby atmos tracks ?
