Nvidia Shield Dolby TrueHD playback is borked

8.31.1 was announced over 3 days ago but I have yet to see it offered to me. I personally do not have Google Play Store auto-update any apps. This is how I control what is updated and what is not.

Guess it depends on varying AV setups. Full quality remuxes with TrueHD is played throughout the day on a daily basis and I am not observing any audio sync drift with 8.30.2. Like I said, the dev is still working on it to flush out this issue.

This will be entirely dependent upon the upstream mpv developers. As of last I read, Dolby Vision support is a pipe dream. Same with Kodi.

Oh I’m well aware it’s gonna be a while, bit it will happen… Eventually :roll_eyes:

I do watch a lot of movies, and most of my collection is now full on BR rips with TrueHD / Atmos since I finally managed to get the capability.

And in all fairness, I have only watched the 1 movie today, so I’ll try a few others and report back…

Some further context around my statement. I am talking about Dolby Vision with Plex HTPC for Linux. Since it sounds like you are using Windows, you can try vo=gpu-next

Oh really???

Might just havta give that a go :+1::+1:

But this is to tonemap DV to SDR from what I understand. Passthrough to a DV capable display is still not possible.

Ah ok. Well, will give it a try none the less…

Ok, so I’m now 20 mins into Blade Runner 2049, with TrueHD and Atmos, and no audio sync issues, so it might have been the specific movie I was watching this afternoon.

Anyways, now I’ve started this movie, gonna have to finish it :smiley:

Some movies will have issues no matter what and it is due to seamless branching on the disc. The root cause is with the remuxing process. Example of such title is Black Hawk Down extended edition. The dev can try to workaround this problem but the real fix is for tools like MakeMKV to solve the root cause.

@axemanuk666

See here

Garbage in, garbage out—as the old adage goes…

1 Like

Thanks @Achilles, and it was The Martian 4K Extended edition that I was watching earlier this afternoon, so it appears I was having the same problem as mentioned in that thread.

1 Like

It’s not related to (or at least not fully) with a month old bug in MakeMKV

For those of us who take remuxes seriously and who wouldn’t touch garbage like MakeMKV with a barge pole it’s a Plex issue.

It doesn’t happen in a Emby, Jellyfin or a non screwed Plex release.

It does happen with Atmos movies from several years ago that predate any mention of this issue ( in both Plex and MakeMKV combination that played fine previously.)

Sorry but the solutions are

  1. The devs actually use their beta releases.
  2. The devs actually read feedback on their beta releases.
  3. Nobody uses the beta releases (as suggested by a ninja earlier in this thread) and wait for something to go through three beta releases with ignored feedback and get pushed to the edge of stable and see what that leads to?

Then of course all these issues coincided with a release note that offered ā€œbetter support for TrueHD/Atmosā€ :joy::joy::joy::rofl:
Cos we all believe in coincidences.

I’m still really curious at what point anyone took notice. Here, Reddit (highly recommended for non patronising replies) or the Google Play store?

But I do thank the ninjas for actually confirming this is a real issue even unofficially. It must be one of the regular non denial period’s for a Plex employee/dev.

OT: If not MakeMKV, what do you use to make your rips? Why is MakeMKV ā€œgarbageā€?

Only because of the constant bugs.

Months of being fine and then weeks of bugs.

Super curious to find out what alternative you would recommend? I have only ever used make MKV. I’m open to using something new if it’s really that better but if it’s much more complicated then using make MKV I would be less eager.

So which remuxing app do you use to maintain DV? I am curious as not aware there is an alternative to MakeMKV for doing so?

I am experiencing the same audio dropout and subsequent drastic audio sync delay with Black Hawk Down Extended @ 14m36s when playing back using Emby and Jellyfin on the Shield Pro. This common denominator points me to the root cause being an improper remux with these seamless branching titles.

1 Like

Yep, apologies I stand corrected on this, having checked with my brother who sometimes rips for me.

Then im curious why rolling back client version and the issue no longer seems to be there… I will take a look at Black Hawk Down.

I got that same remux so I can check it too.

The weird thing is that my copies of LOTR extended cuts…for the first two films everything is fine at the merge point for parts 1 and 2. On the third film however I get the out of sync issue at the merge point.

I feel like the key to the entire thing is sitting right there in plain sight for whoever is knowledgeable enough. All three films would have had their parts 1 and 2 joined the same way, so you would think they would all have this issue right? If someone could just figure out what is different that causes the sync issue only on return of the king then you will figure out what the issue is on all of these atmos movies with branching cuts.

I must be just lucky, never had many issues with MakeMKV. Or just well timed when I did.

1 Like