Android DOLBY out of Sync
#1
Hello,
I get Dolby audio 100 ms lagging behind video and I tried everyhing. Different TV, different connection, latest Nightly build of Kodi, resetting Shield, resetting the receiver, resetting the TV.

2017 Shield >  Onkyo TX-SR393 FW R108 > TV: Sony KD-55XE7077 FW 8.882.

DTS and PCM are in perfect sync. Also disabling passthrough works but that way missing the fancy receiver processing like Dolby Loudness Management.
Also other apps seem to work, tested VLC and FX File Explorer with passthrough enabled, those are in sync.

If there was a way to set delay separately for each audio type? Like set -100 ms for Dobly only?

Also, I have pretty cheap HDMI cables, I think 2.0 no brand. But they seem work with HDR10 4k. Might they be the cause of audio issues? It's like 40 dollars for premium cables do you think it's worth a try?

Also If I can provide any log files I will, but I doubt they'll show anything.
Reply
#2
The HDMI cables have nothing to do with it.

As you run a shield DTS and Dolby use the exactly same code path. Is there some "lipsync AVR setting?" That you can tune?

If nothing works, set your global delay to -50 ms ... that way everything is 50 ms off, but you might not realize it anymore.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#3
(2020-08-19, 09:35)fritsch Wrote: The HDMI cables have nothing to do with it.

As you run a shield DTS and Dolby use the exactly same code path. Is there some "lipsync AVR setting?" That you can tune?

If nothing works, set your global delay to -50 ms ... that way everything is 50 ms off, but you might not realize it anymore.
Yeah the AVR has Auto Lip Sync but doesn't change anything. I guess my TV doesn't support the protocol.
But the 100 ms Dolby delay is present regardless of TV speakers or AVR connected, it's the same.

As you mention "code path", do you mean Kodi code, Android code, or nVidia code? Cause the fault might be at Android or nVidia's part.. sadly nVidia doesn't bother, asked at their forum already.
Reply
#4
all paths possible. You can try the v19 alpha and set your PT device to RAW. V19 has a selection here. That will bring other issues but with that you use the entire android path with kodi doing nothing.

Same delay? Or even worse?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#5
(2020-08-19, 16:47)fritsch Wrote: all paths possible. You can try the v19 alpha and set your PT device to RAW. V19 has a selection here. That will bring other issues but with that you use the entire android path with kodi doing nothing.

Same delay? Or even worse?

Exactly the same with RAW PT. Dolby two frames late (24p) = 83 ms to be precise.

Here are the test files I use:
https://1drv.ms/u/s!AueFEekVDilBmOFSefWx...g?e=rXCXY8
Reply
#6
I have a similar issue with Insignia Fire TV. Not just being .100s out of sync, but pausing or seeking (left or right keypad) throws huge sync errors, with audio cutting in and out. Stopping the video and resuming will typically fix it, unless I pause or seek again. For the log i started a file and paused around 14:10:18 where the issue starts.

https://pastebin.com/y9eZqi2g

Seems to only affect Dolby files. DTS or 5.1 aac that's transcoded (TV doesn't support DTS passthrough) I can pause or seek fine, same with .mp3.
Reply
#7
(2020-08-28, 21:47)burcs Wrote: I have a similar issue with Insignia Fire TV. Not just being .100s out of sync, but pausing or seeking (left or right keypad) throws huge sync errors, with audio cutting in and out. Stopping the video and resuming will typically fix it, unless I pause or seek again. For the log i started a file and paused around 14:10:18 where the issue starts.

https://pastebin.com/y9eZqi2g

Seems to only affect Dolby files. DTS or 5.1 aac that's transcoded (TV doesn't support DTS passthrough) I can pause or seek fine, same with .mp3.

Please open your own issue. You don't have even nearly the OP's issue. You are using a totally different sink implementation (Android RAW format) while the OP uses IEC format. Furthermore your issue only happens after seek where most likely the Delay Code is just foobar.

Therefore: Reproduce with v19 nightly and open your own issue to not clutter OP's issue.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#8
Sorry, thought it might be related. I do have the same sync issue, without pause/seek, just mine's over ARC back to AVR. Dolby has 100ms delay, but not when transcoded. I literally came to the Android forum to search "Dolby out of sync" and here this thread was, so...apologies.
Reply
#9
Your problem is a different one, trust me, there are Android devices out there that have a problem to cope with the high bitrate AC3 we send and can only cope with lower bitrates. A workaround for these broken FW devices exist:

Set Speakers to 2.0 (important !!)
Enable: AC3 and Dolby Transcoding

And now - even you might think it's not relevant - in Video Playback enable: Sync Playback to Display

That will have the effect that also Dolby-Input will be processed, resampled and packed with a lower quality matching your device capabilities.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#10
(2020-08-29, 08:31)fritsch Wrote: Your problem is a different one, trust me, there are Android devices out there that have a problem to cope with the high bitrate AC3 we send and can only cope with lower bitrates. A workaround for these broken FW devices exist:

Set Speakers to 2.0 (important !!)
Enable: AC3 and Dolby Transcoding

And now - even you might think it's not relevant - in Video Playback enable: Sync Playback to Display

That will have the effect that also Dolby-Input will be processed, resampled and packed with a lower quality matching your device capabilities.

Sorry guys,
just realized Netflix's also out of sync +/- 100 ms with Dolby enabled. Clearly not a KODI issue.

Just have to assume Google and/or nVidia need to adopt some quality standards before selling their products. 100 ms is just ridiculous.
Reply
#11
This has been bothering me for 4+ years and I finally figured out the issue. If this has already been discussed I couldn't find it. It comes down to the real cinema option on lg oled tvs

I've been using the nvidia shield with kodi. I always kept both up to date as well as the tv. I have never used arc or earc from the tv because it was a mess when I first got the lg oled. Shield audio always went to receiver first, or was split. I never ran audio through the tv.

The "real cinema" option is how the tv deals with 24 and 23.9 fps videos. With real cinema off tv does 3:2 pull down to get 24 -> 60hz (then x2 I assume), with real cinema on it does 5:5 (24->120) I have always left this off because I personally prefer some minor judder over slight soap opera effect.

Kodi audio was always in sync for pcm 2.0 and 5.1 and dts/dtshd passthrough. All 3 dolby codecs would be out of sync by the 2 frames discussed in this thread (framerate switching off and set to 59.9). Atmos in dd+ and true hd is the only reason I used dolby passthrough. My workaround was to setup 2 profiles in kodi (one with the audio offset at 083 and one without). I recently saw a thread on lg forums saying to leave real cinema on so I tried it and dolby is now in sync. Seems the dolby audio is syncing to 120 instead of 60 which explains the 2 frame offset. I should add that I've been using audiotrack (iec). Audiotrack (raw) was in sync but audio took 5-10 seconds to start playing and often it would drop out entirely after pause, ff, rew.
 
I'm not sure if this is intentional or why only dolby passthough is out of sync with real cinema off, but I'm hoping the devs see this post. I couldn't figure out how to reach Fritsch directly.
Reply
#12
I am having the same audio out of sync issue on a Zidoo Z9X Pro with Kodi 21.1, Kodi Version 21.0 works perfectly as does the internal Zidoo player so I'm pretty sure the file is not the issue.
Reply

Logout Mark Read Team Forum Stats Members Help
DOLBY out of Sync0