Lip-sync errors after latest update?

MrMC just is no option. I own an Apple TV 4k for DRM streaming and it is superb for that, just brilliant, nothing is even close. But MrMC is still just terrible and probably always will be.

Has they fixxed the 24.000 fps bug?

https://www.avsforum.com/forum/39-networking-media-servers-content-streaming/2961262-apple-tv-4k-lacks-support-24-000-video.html

thats actually the thing why i didnt bought one yet.

Don‘t buy the Apple TV 4k for Kodi/MrMC. It just won‘t satisfy you with all the restrictions, no audio passthrough, crappy skins etc… Lip Sync is perfect but the rest is garbage.

No idea about the 24p bug, I use the Apple TV 4k for 25/30/50/60 fps Content… for that it is the best there is, especially for European users who often get broken 25/50 playback on many many devices.

Thats the problem Netflix also have 24.000 fps content like “bird box” and “dark”

That is strange. 24.000 content is really rare.

Back to the topic. Sam told me he is working very hard on a fix. I just hope it is more than just a fix but eliminates the issue by the roots.

I won’t have access to any HDMI connected speakers for the next three weeks, but I should have a fix already. I just can’t verify this presently.

I’m not sure what you mean by this. Ideally it needs fixing in Kodi.

Its not rare :wink: you just watch the wrong shows. But maybe the Netflix App on the AppleTV is working differently and fix the bug or the TV does no idea.

@sam_nazarko
Has your fix already been included in the devel-builds?
There is some note about a timing fix in the changelog.
If yes, then it doesn’t work :frowning:

Best regards,
Marc

Yes, the changes were released on Sunday.

For me the lipsync issues still occurs. Could log files be of any use to you ?

I think the problem has been reduced but it’s definitively not resolved.

In my 4K sample video with 2x DD5.1 and 2x Dolby Atmos only one Atmos track is in sync, the others are still late (more about 100 ms and not 250 as before and different on each track).

Then I tested some tv series clips, in some of them the audio is now indeed faster than the video (before audio was always late), but they are not sync at all.
Then I re-enabled my Denon AVRs “Lip sync”-Mode, which delays audio for 96 ms in my setup, but it’s still not sync.
As I cannot delay audio in the Vero 4K while playback (as this doesn’t do anything) it’s hard to test and to find the correct setting.

And it is not the same delay for all files, that’s for sure.

I might be ignored again but this lip sync issues pre dates the Leia update. Like I mentioned many posts above, it was already there in the Krypton build. Roughly 100-120ms or 3 frames… it just got worse with Leia to 140-180ms or 4 frames, in extreme cases 5 frames.

It might be back to what it was in Krypton with whatever fix was done (and had been active in Krypton) but the underlying issue is not fixed. That is what I meant cleaning things up at the roots.

And it isn‘t like the issue went unnoticed during the Krypton days. It just wasn‘t that bad, 3 frames vs 4 or even 5 frames is just the difference to notice.

I have downgraded my Vero 4k to my secondary player and now use a dirt cheap S905X box with libreelec on Krypton 17.6 as my main. No audio delay at all. 0ms. And as mentioned above, downgrading the Vero 4k to 17.6 will still result in an audio delay of three frames / 100ms on affected files.

Looking how perfectly the dirt cheap S905X libreelec box handles sync (even though it is just 17.6) makes me unwilling to accept any kind of random 100ms audio delay. I could live with downgrading the Vero 4k to 17.6 but that simply solves nothing.

I’ve read all your posts :wink:

I don’t watch native english stuff very much, but mostly dubbed movies, so real lipsync is hard for me to detect - I focus on sound effects and names. I have edited quite some music videos in the past and think that I am very sensitive to audio delays though.

I did not detect those delays in the Krypton times but instantly after switching to a very late beta of Leia. In Matrix nothing changed (till the latest fix).

I will do some more tests tonight with this fix.

It will get solved, but currently I’m on holiday with zero access to testing equipment needed.

There were some improvements in the June update and I hope to refine that shortly.

Let’s focus on Leia for now.

@sam_nazarko
just to be sure, I am currently running 3.14.29-150.

Isn’t that Matrix? Does this have your fix?

Have a nice holiday!

That’s a kernel version, not a Kodi version.

I like how you guys are chasing this problem. The Vero is imho the gold standard for media playback and therefore any delay greater then a few ms is not good. Especially when we know that in theory perfect sync should be possible (as measured by Nickelig on his S905X box). Keep up the good work everyone!

3 Likes

Yes it is apart from DIY libreelec/coreelec solutions, which may or may not give you the same experience. I have no idea how the communication/relation is between all those with osmc but in this case maybe it would be a good idea to look at how the other guys handled it.

To me it looks like we opened a can of worms here. Sync probably wasn‘t all that great before (pre Leia) but if it was out of sync for max. 3 frames, nobody probably looked closer because 3 frames is on the edge of noticable. One user did notice it in January (angry sardine), who is - I hope he doesn‘t mind saying it - putting everything under the microscope. So most people didn‘t notice it and only some did but managed.

But now with the increased delay in Leia (april/may), people started to get aware of lip sync. That is where the opening of the can or worms comes into play. Now that you saw lip sync issues, people look very closely, just like one user did some months earlier. And while the June fix lessened the problem and probably got us to the point where we were with Krypton, people will probably not ignore that the audio still is late ~100ms on affected files. If you spent many hours on lip sync, matching offsets etc. your eyes get quite educated on the issue. can of worms opened, now sync has to be great or bust.

Sam has his well deserved holidays, I wish I had mine, I would prefer Iceland right now with the heat wave in central Europe. Anyway. nothing we can do, other than other users confirming what we have reported.

But to me, I would look what makes affected files lag in audio. While lessening the audio lag is helpful, a real solution would be eliminating the audio lag on affected files by finding the issue that makes files affected. We also have lots of files that are not affected, the issue obviously is not universal. I understand that the quick fix worked in the past as it kept the audio delay in the ranged of max. 3 frames but I think that probably won‘t do anymore.

The team will figure it out.

LibreELEC does not release AMLogic based on vendor kernels, i.e. 3.14/4.9 anymore. So what may have been borderline with 17.6 would probably be quite rough with v18 releases if they were still producing those.

CoreELEC kernels are derived from OSMC. At least for S905x/S912. This isn’t the case for the S922. Interestingly, I can see reports from CE devs that audio offset is broken in CE but not OSMC. See here. So I think there is more than meets the eye; and there are specific conditions that need to be triggered for these issues to arise.

Don’t worry – we will get it solved. While I am on holiday, I am still working. Things may just take a bit longer as I will to need to defer to others to test rather than rely on testing equipment. I have some equipment here, but not everything.

Cheers

Sam

Thx for the infos. That was quite interesting.

Guess with Leia, it is a new ballgame after all. And I have to admit, I have yet to test any Leia build other than the Vero 4k. Android TV / shield Tv is no option anyway, consistent sync is hopelessly broken for all eternity there, heck even stable passthrough is sometimes a challenge. That was the main reason, by far the biggest reason to give up on the shield TV.

Though I am looking at a possible S922X device (though my Odroid N2 went up in flames literally on first boot, the onboard usb controller just died in smoke) just for the fun of tinkering with it. But it is clearly not the best choice right now if you prefer stability, as things change daily. I think I wouldn‘t mind a Vero 5 with a S922X SoC one day :wink: