25p content stutter (w/ November update)

Help and Support Vero V
1

Hey, team. Noticed that all my 25.000hz media is stuttering pretty badly since the August update. No improvement with the November update. Any chance you can look into this? Cheers.

August update stutter (known issue at this point):

https://paste.osmc.tv/apeyiforif

November update stutter:

https://paste.osmc.tv/ihasudopic

Test method: Tested on two Vero V units connected to an LG C5 and LG G5 OLEDs with the same results. No issue with playback on iPhone 17 Pro Max or iPad Pro M4 with native Plex app.

2

Hi William,

We’ll check this shortly.

TrueHD capable receiver: true
Adjust display refresh rate: On start / stop ===> Default: Off
Sync playback to display: false
Disable stereoscopic 3D mode when playback ended: true
Playback mode of stereoscopic 3D videos: Ask me
Display 4:3 videos as: Normal
Enable HQ scalers for scaling above: 20
Allow hardware acceleration with DRM PRIME: true
Accelerate MPEG2: Always
Accelerate MPEG4: HD and up
Accelerate h264: Always
Accelerate AV1: Always
Force 422 colour subsampling: false
Force RGB output: false
Use limited colour range (16-235): true
Lock HDMI HPD: false
GUI Resolution: 3840x2160 @ 23.976p

This looks a bit dodgy.
What happens if you allow ‘Always’ for adjust refresh rate and set to 1080p60 (just as a test)

Sam

4

Yeah absolutely no difference.

5

Can you chuck a log after making the change or a sample file?

Sam

6

Yessir. Here you go:

https://paste.osmc.tv/yuhezuvaxu

7

Will check in a bit, thanks for sample.

8

Well, the metadata of your sample says it’s 25 fps progressive. But the decoder says it’s interlaced and that confusion causes the stuttering. If you whitelist 1080p25 then you should get smooth playback.

1 Like
9

Thank you. That did fix it this time. Is there a reason this is a new behavior? The hands-off approach is usually better, but something changed in Kodi to mean one needs to actually fix this before watching? Just seems odd.

10

Well, interlaced material is just a mess. There’re recordings of interlaced streams, (bad) remuxes, bad/wrong information stored in the container or the stream itself. There are streams that switch between progressive and interlaced playback. You get also bad timestamps and wrong frame durations, frame durations are changing within the stream and - of course - contradicting information stored in the metadata of the container and the stream itself. It seems that whatever property is stored in such material can be wrong and/or contradicting. You just can’t rely on anything.

And now the media player should get it right. Most often it just works, but especially, if we get contradicting information we can just guess what’s wrong/right and needed for smooth playback. It’s very easy to break playback of clips by just fixing an issue with another weird “interlaced” clip.

It’s a battle which one can just lose :frowning: .

5 Likes
11

That’s fair enough! Doesn’t seem to be a downside to whitelisting so I guess I’ll just leave it enabled. Thanks again.