Why donāt you just stop the video and then start it again? Seems easier than having to rewind multiple times. Thatās what I do when it goes out of sync.
I didnāt realize it might be because of pause/rewind that triggers it.
The main problem I see is that stock Kodi does not support Dolby Vision, especially dual layer P7 FEL. This is CoreELEC fork only.
Also a fact is that most of TK does not even own a HDR screenā¦
I will try this PR if there are improvements or not and pick if it does.
Thanks for looking. Just to clarify scope: this PR is audio-only ā it changes the TrueHD MAT packer and the passthrough audio clock/jitter handling. It doesnāt touch the video pipeline or Dolby Vision in any way.
The trigger it addresses, TrueHD seamless branching, is a Blu-ray/UHD playlist structure (multi-clip titles restart the TrueHD outputTiming counter at clip joins), which is independent of DV. It occurs on standard Blu-rays, non-DV UHDs, and DV titles played as their HDR10 base layer ā all of which stock Kodi plays via libbluray. So you donāt need DV (or the CoreELEC fork) to hit either the seamless-branch dropout or the passthrough A/V drift this fixes; DV support isnāt a prerequisite.
The whole feature is gated behind audiooutput.lavsync (default off), so thereās no change to existing behaviour unless a user opts in. Happy to expand on any specific case ā were you thinking of a particular disc/demux path where DV would affect the audio timing?
All users report TrueHD audio sync issues when using unofficial forks/frankenstein builds by playing Dolby Vision (DV) content, and only the LAV Filters fix it for them.
Itās all about libbluray + ISO and illegal shared media content.
DV is the most popular format used with TrueHD and is also the most complex, especially Profile 7 (P7) FEL dual-layer content.
On official CoreELEC CE-NO 22 there are no such issues. I only know a issue when played a P7 FEL/TrueHD sample I need to reset the TV audio device to get back in sync. Maybe this change will fix this item.
The Martian is another seamless branch title with no DV that drops audio for me in stock Kodi when using passthrough audio. The LAV Audio code I ported fixes it there, as well.
I got a kernel panic after reboot, not a normal Kodi crash. pstore shows stack-protector: Kernel stack is corrupted in: Commit2DmKs+0xd10/0xd14 [dovi_gen_5_15_2026], followed by Kernel panic - not syncing: BRK handler: Fatal exception in interrupt. The call trace goes through Commit2DmKs -> commit_reg -> multi_control_path -> amdolby_vision_process, and boot also logs dovi_gen_5_15_2026: disagrees about version of symbol module_layout / __stack_chk_fail with please rebuild ko.
Using latest nightly on AM9 Pro with 5.15_2.6_dovi_patched_fix_fel.ko
kernel-panic-pstore:
dmesg
Kodi logs shows nothing. Last entry before the restart was 15 min before the crash.
2026-07-06 16:13:51.961 T:5821 info <general>: VideoInfoScanner: Finished scan. Scanning for video info took 8 ms
2026-07-06 16:13:52.008 T:1504 info <general>: JELLYFIN.jellyfin_kodi.monitor -> INFO::jellyfin_kodi/monitor.py:58 -->[ kodi scan/video ]
2026-07-06 16:13:52.017 T:1504 info <general>: JELLYFIN.jellyfin_kodi.monitor -> INFO::jellyfin_kodi/monitor.py:61 --<[ kodi scan/video ]
2026-07-06 16:14:36.848 T:5831 warning <general>: CPythonInvoker(17): Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.
and then
2026-07-06 16:30:41.159 T:1421 info <general>: Starting Kodi (22.0-BETA1 (21.90.801) Git:f37663947cb2440176697d5e496c9260a235947f). Platform: Linux ARM 64-bit
2026-07-06 16:30:41.159 T:1421 info <general>: Using Release Kodi x64
2026-07-06 16:30:41.159 T:1421 info <general>: Kodi compiled 2026-07-06 02:15:23 by GCC 16.1.0 for Linux ARM 64-bit version 5.15.196 (331716)
2026-07-06 16:30:41.159 T:1421 info <general>: Running on Ugoos AM9 Pro with CoreELEC (official): 22.0-Piers_nightly_20260706, kernel: Linux ARM 64-bit version 5.15.196
2026-07-06 16:30:41.159 T:1421 info <general>: FFmpeg version/source: 8.1.2
2026-07-06 16:30:41.159 T:1421 info <general>: 4 CPU cores available
2026-07-06 16:30:41.159 T:1421 info <general>: ARM Features: Neon enabled
2026-07-06 16:30:41.159 T:1421 info <general>: special://xbmc/ is mapped to: /usr/share/kodi/
2026-07-06 16:30:41.159 T:1421 info <general>: special://xbmcbin/ is mapped to: /usr/lib/kodi
2026-07-06 16:30:41.159 T:1421 info <general>: special://xbmcbinaddons/ is mapped to: /usr/lib/kodi/addons
2026-07-06 16:30:41.159 T:1421 info <general>: special://masterprofile/ is mapped to: /storage/.kodi/userdata
2026-07-06 16:30:41.159 T:1421 info <general>: special://envhome/ is mapped to: /storage
2026-07-06 16:30:41.159 T:1421 info <general>: special://home/ is mapped to: /storage/.kodi
2026-07-06 16:30:41.159 T:1421 info <general>: special://temp/ is mapped to: /storage/.kodi/temp
2026-07-06 16:30:41.159 T:1421 info <general>: special://logpath/ is mapped to: /storage/.kodi/temp
2026-07-06 16:30:41.159 T:1421 info <general>: Webserver extra whitelist paths:
2026-07-06 16:30:41.159 T:1421 info <general>: The executable running is: /usr/lib/kodi/kodi.bin
2026-07-06 16:30:41.159 T:1421 info <general>: Local hostname: CoreELEC
2026-07-06 16:30:41.159 T:1421 info <general>: Log File is located: /storage/.kodi/temp/kodi.log
2026-07-06 16:30:41.159 T:1421 info <general>: -----------------------------------------------------------------------
2026-07-06 16:30:41.169 T:1421 info <general>: loading settings
2026-07-06 16:30:41.170 T:1421 info <general>: special://profile/ is mapped to: special://masterprofile/
2026-07-06 16:30:41.196 T:1421 info <general>: Loaded settings file from special://xbmc/system/advancedsettings.xml
2026-07-06 16:30:41.199 T:1421 info <general>: Contents of special://xbmc/system/advancedsettings.xml are...
Not much we can do about it. Try again with every new nightly, maybe some latest commit will fix this item.
Ok, should I post it in a different thread? maybe in Ugoos AM9 Pro - SoC S6 S905X5-J?
Posting in different thread will not solve the issue ![]()
Well ok, u didnāt say why you canāt do much about it. Who was posting the updated dovi.ko files (and where)? The one actually making them might be able to help? ![]()
No, this PR does not fix the item of audio delay after played a FEL/TrueHD sample.
But this is maybe TV issue.
Bad live PVR PT with AC3 is broken with LAV enabled.
Itās not limited to unofficial forks, itās not tied to Dolby Vision, and itās not even CoreELEC specific. It stems from seamless branching titles ripped from disc with MakeMKV. If your argument of āillegalā shared content is about ripped discs in general, than what are we all even doing here? I thought it was generally understood most of us are using these players for local content you paid for and have ripped from disc.
Team Kodi has made efforts around this before in Omega:
https://forum.kodi.tv/showthread.php?tid=377117
They were trying to solve the literal same problem and those changes shipped with v21.0. The problem with the approach that was merged is it treats the SB points as a seek which has varying impacts depending on your downstream audio chain and why some get dropouts. The proposed fix corrects the PTS timing rather than doing simulated seeks so it avoid the dropouts.
Given that MKV is ubiquitous, I find earlier suggestions that nothing should be done in Kodi about it because it works with BDMV to be rubbish. Good, bad, or indifferent, MKV is the hand we have been dealt. There are reasons many of us want to use that rather than BDMV.
The feature doesnāt matter anyway as live PVR get complete broken, stutter and sound stop/break/starts if working at all.
So nothing need to be discussed anymore about it as itās breaking change. End of this topic until PR is fixed.
damn this is unfortunate to hear
glad to hear it, youāre not the first to have an issue with the internal nfs ![]()
the files are broken, period
if you want better handling of broken mkv files then go way upstream and complain to ffmpeg
ffmpeg trips over an error and it ripples all the way down
The setting is default-off and opt-in, so itās not a breaking change ā with it off, behaviour is identical to stock, PVR included.
That said, your live-PVR point is fair: the sync model targets file/disc passthrough, not realtime streams. Iāve pushed a change that excludes realtime/live streams from the LAV path entirely, so itās a no-op for live PVR even when the setting is enabled. Thanks for flagging it.
Ok, stop and restart works, too.
Nevertheless, I would expect that after skipping back or pausing/playing, I should be able to continue watching in sync.
Itās not a Dolby Vision issue, as it occurs with other films as well.