A non issue for me I just verified by watching the whole thing with Dolby Atmos True HD Audio Codec. I never said it was a Plex issue another user did. I’m just verifying that I don’t have this so called issue you two are referring to. Have watched it twice through already and didn’t skip a beat… 
@Achilles @Nik3sh I can setup a recorded video feed showing my test if you’d like of my receiver playing this audio Codec for the full duration of the movie if you don’t believe me. I am that confident it works flawlessly…
What can I say you’re one of the lucky ones, all I will say this is not a user issue but a shield issue that many people have. You can check other Disney UHD titles like zootopia and tangled to see if you have dropouts. Although I am curious why some users have this issue and others don’t, I have a 2015 model, i might buy a 2019 model and see if it make a difference.
Btw I also have an Apple TV 4K and use infuse connected to Plex that decodes TrueHD Atmos to lossless PCM without losing any audio quality, only Atmos is lost, and have no audio dropouts on high bit rate tracks.
@Nik3sh Maybe an incompatibility issue between shield and AVR? I am running 2015 Shield as well to a Sony Str-dn1080. Maybe if we could get the exact time stamps of when these dropouts occur we could try to troubleshoot them closer. I will try some of the other movies you have mentioned but would be nice to locate some time stamps so I don’t have to watch the whole flick again 
Try Tangled 4K at 00:12s mark.
Direct acknowledgement from Nvidia on their forums:
Shield@NVIDIA
13dThere are no 8.0.1 specific regressions on droputs. There is a long-standing issue with high bit rate audio content that drops out when the bit rate goes above a certain limit. Unfortunately this is a limit with the open source passthrough solutions for high bit rate uncompressed Dolby that cannot be resolved by us.
Shield@NVIDIA
13dIf your audio dropouts happen at the same place, this is not being addressed. If the audio dropouts happen at random places, that is what is being addressed.
There’s no need to troubleshoot, as @Achilles and I have said numerous of times it’s a shield issue with high bit rate audio that is acknowledged by nvidia, I just wanted to buy another one to test if it happens to all shields.
On Zootopia it’s when the rabbit Cop gets on the train Scene sorry can’t remember time stamp off the top my head.
This github issue has a Plex dev involved:
OK going to test all of these scenarios tonight and I will post my results with audio clips at these time marks.
No need if you are trying to prove it doesn’t impact you. That doesn’t negate the fact that there is an issue for others that is acknowledged by Google, Nvidia and Plex devs.
@Nik3sh No need to buy 2019 ShieldTV. I have both 2015 and 2019 ShieldTV Pro and the time specific HD audio passthrough dropouts occur on both. Random HD audio passthrough dropouts no longer occur.
May I be of assistance here?
Have you read through the thread? Did you have a question?
Yes, I read through the thread inclusive of all the edits and deleted posts.
I will ask everyone here to remember the community guidelines
yeah getting pretty rediculous. Do you have an opinion on why these dropouts are only happening to certain people where as some are playing these file types just fine across multiple streaming clients?
In the testing I am doing, I’m finding
-
Shield 2019 Pro - 8.0 (Patch already baked into the OS) does not suffer any dropouts
-
Other Shield models do. There is a correlation between those on 7.2, those with, and those without the hotfix.
-
Nvidia itself has admitted to the problem. I have not yet fully caught up with where they are with problem resolution for all players (2015, 2017 and 2019 models)
Have I missed anything ?
Since adding the shield hot fix to my 2015 model I haven’t noticed a single audio dropout across multiple clients and multiple file types and audio codecs.
All I was trying to convey and help with is that there could possibly be a user’s settings error, hardware incompatibilities, etc. So I thought it was kind of rude and distasteful for a moderator to be knocking down the possibilities of some of these scenarios and basically telling me I’m wrong and wasting my time trying to provide a comparison log of people’s settings and hardware to narrow down where the issues could be coming from. Do we not agree that there could be some sort of human error here. I understand the devs had confirmed there maybe an issue but are you telling me they can’t in no way be wrong in their findings as to the cause since some are not experiencing this at all?
@TechBoi Thank you for your participation and glad that you are not experiencing this issue. Plex has confirmed with NVidia that there is an issue with the way some TrueHD audio tracks are encoded. Not all TrueHD is the same. Our dev team is working on a fix.
There is zero chance that this is a user error setting. This impacts many users. Great that you don’t experience this. Again it does not negate the fact that there is an issue with Google limiting the TrueHD frame size when dealing with Dolby Atmos MAT 2.0.
A few points
-
Achilles writes (and speaks) very directly. I have learned over the years not to confuse statements of fact with perceptions of personal attack. That’s not who he is. He’s one of the most giving and helpful people I know. His skill level is extremely high and one of the most knowledgeable people here. He has been an engineer for a long time (just as I have). When working through a problem, rule #1 is cut the chaff from the facts.
-
As MovieFan pointed out,
a. We know about a number of issues. TrueHD isn’t the only codec with a problem we are working on. The supplemental metadata (which is how the newer codecs work) is where these issues lay and why some users see the problems while others don’t.
b. Some of it is app & codec related while some of it is the platform itself. NVidia’s hotfix has corrected a lot of the problem. Given the app and codecs are dependent on the underlying nVidia platform, now we are working our way back through the codecs and apps. -
I will make one statement about the tone which I previously saw in this thread.
a. Folks are frustrated - Got that
b. I saw what I perceived to be “measuring” which is inappropriate in our forums.
c. I did not like, nor will I allow, a topic to degrade from “constructive & polite debate” into something unacceptable.
d. We all are passionate else we would not be here. - Got that.
e. Be respectful of others and I will not need be Bad Cop
f. Keep it objective.
Thanks.
3 Likes
