TrueHD seamless branching audio dropouts still a thing?

[Chelesty]

Hi,

I recently started ripping all of my movies and playing the decrypted BDMVs from a Dune HD Pro Vision 4K, which has worked flawlessly up to this point.

Now I've ripped my 4K copy of Frozen 2, and I'm getting audio dropouts. I found several other threads of people with the same issue in the exact same point of the movie. Supposedly it's caused by the way Disney cuts up their streams, if I understand correctly. Regardless of whether I play the BDMV, the MKV made by MakeMKV, or an MKV I remuxed by demuxing the BDMV with DGDemux and using the THD audio stream from that to remux in MKVToolNix, I always get the same issue.

I don't see many recent posts on this topic, has this issue been resolved? I see that since MakeMKV v1.15.3 TrueHD streams are fused properly to prevent sync issues, but I'm running 1.18.1 and still having this issue.

Let me clarify that I understand and agree that this is not inherently a MakeMKV problem. If the hash checks out and all the data from the disc is present in the backup, MakeMKV did its thing for sure. But I wonder if anyone has found a way to maybe, somehow, create a playable TrueHD (with Atmos) stream with no issues from one of these stupid Disney discs.

[SamuriHL]

You aren't alone in seeing this issue. My question is how are you playing them back? Specifically, what player and the hardware is running on? I've seen this issue recently on m3gan 2.0 UHD extended release and Nosferatu UHD extended release. Both being played in pm4k on an am6b+ coreelec cpm build, which means kodi under the covers.

Sent from my SM-S938U1 using Tapatalk

[Reiver]

If you were using Kodi, then up until last year it had a problem with seamless branching in TrueHD Atmos streams until fixed by commit TrueHD rework - totally new MAT packer implementation which was included in v21 I believe. It's possible your Dune device is using an older Kodi version as a base?

[SamuriHL]

I'm running an AM6b+ CoreELEC CPM 14 build on mine. I don't know if Kodi will ever get updated in that version because newer Kodi versions use a new Linux kernel that breaks Dolby Vision playback....kind of the whole point of having the AM6b+ in the first place. I found the situation to be worse on the SHIELD, though, and that's using the latest Kodi from the playstore. I'm able to play them perfectly in JRiver MC so while my equipment may be sensitive to the issue, it's not strictly an equipment problem in my case else JRiver would exhibit the same issue. I don't know anywhere near enough about the inner workings of CoreELEC to know if the patch can be applied there or if it already has and simply doesn't work for my particular setup.

P.S. Both CoreELEC and my SHIELD are using some version of Kodi 21.

[Chelesty]

You aren't alone in seeing this issue. My question is how are you playing them back? Specifically, what player and the hardware is running on? I've seen this issue recently on m3gan 2.0 UHD extended release and Nosferatu UHD extended release. Both being played in pm4k on an am6b+ coreelec cpm build, which means kodi under the covers.

Sent from my SM-S938U1 using Tapatalk

I'm playing from a Dune HD Pro Vision 4K, over SMB share hosted on a Unifi NAS Pro with 40TB, 10Gb SFP+ uplink. The Dune is connected to a Denon AVR-X2700H DAB.

So far I haven't bothered with other OSes or other players because (and I'm somewhat alone in this regard) I really like the Dune OS GUI. My setup should remain somewhat girlfriend-friendly hehe. I don't know what player Dune HD is running under the hood, but with the internal player I get the infamous audio dropouts.

However, Kodi is an optional player in the Dune OS, it boots up Kodi just to play a requested file from "My Collection". Lo and behold, it works perfectly. My issue is that I actually prefer the simplicity of the Dune's internal player. Kodi can be somewhat clunky, especially when used solely as a player, without library management and all that shenanigans.

I'm currently talking with Dune HD Support, I've forwarded them the Github page with the fix Kodi implemented. I really hope they can implement something similar. I'm also a bit surprised nobody's thought of using the Kodi fix to create a TrueHD "fixer" of sorts. If I had the knowhow, I would've loved to dive into it myself...

[SirYodaJedi]

Out of curiosity, do the TrueHD issues with "seamless branching" affect the AC3 fallback "core" in any regard? I don't have an Atmos or even 7.1 setup, so I'm fine with downgrading to the AC3 fallback if necessary.
(I haven't ripped any multi-M2TS TrueHD discs yet, and googling is getting me inconsistent answers.)

[Frage]

Hi,

After a few years I was still buying my 4K Blu-rays because of Dolby Vision support on my 4K BR Player.

I finally decided to buy an AM6Bp with Core Elec for full DV Support and a NAS running Jellyfin. Spent some money on it.

I create my own remux and I also downloaded from some website. I was really happy until I was watching TrueHD movie...

The first few TrueHD movie I watched I noticed 1/2 audio drops at specific timecode. Rewind and drop still appear. Only on the TrueHD track, not present in the compatibility track and DTS-HD MA etc. They are not present when using VLC.

I was OK fine ...

Then I started to watch Disney Movie, for example Indestructibles 2, holy cow, had like 10 drops during the movie. I didn't find any help / fix to avoid these drops. Only happen on TrueHD tracks. If I knew I think I wouldn't have buy all these stuff.

I even tried to remux with the last version of MakeMKV and still have drop on older remux I downloaded.

Example : https://drive.google.com/file/d/1v4KZvZ ... sp=sharing

AM6Bp CoreELEC 21.2-Omega and Jellyfin / Kodi plugins
Direct to AV Processor (AV10)
Running 5.1
NAS with Jellyfin on local network

[SamuriHL]

It's a coreelec/Kodi issue. Other players like lav filters don't have the issue.

Sent from my SM-S938U1 using Tapatalk

[flojo]

You're SOL unless a newer Kodi fixes it _AND_ you backport Kodi, although you might be able to find a backport.

Personally I can't tell the difference between P7 and P8, they literally look identical to me. For that reason I'm looking to leave the AM6B+ behind. Sadly so far I haven't seen a great replacement, but whatever I settle on it will support Google TV and the CPU will be >= ARMv9/Intel N150 (the CPU selection is the problem right now).