since some weeks ago (probably after an update) 4k videos stutter for some seconds (only video, not audio), oddly enough, always at the same points. The videos are in an external server connected via gigabit ethernet, and iperf3 tests confirm the speed and lack of problems. The disks are mounted using nfs with systemd automount (instead of autofs), which has always worked very well.
Here’s a full log, the last lines about the pattern lost are when the problem happens.
I would try it without the custom cache settings you put in your advancedsettings.xml. If that doesn’t help I would put this file on some portable storage to make sure it is the network and not the file at issue.
Thanks for the help. I put those cache settings because I was trying to get it work, the same problem happens without them. I also just tried to reproduce the file from an USB and the same thing happens, at the same point. That would make me think that the problem is within the files, but it reproduces perfectly in any other player I’ve tried (VLC and mpv), and their logs don’t show anything. I’m going to try as soon as possible with other high bitrate 4k files, to see if it still happens.
Clarification: this happens with many 4k files, not only with the one of the log, and it happens with files in which it didn’t happen some weeks or months ago.
It may be that both downsampling and changing the frame rate of these files is just too much work for the Vero. Your display has very limited view modes so it is necisating both of these things to happen for these particular files.
My screen is 4k (and I see a difference between 4k and 1080p files). I don’t know about framerate, though. And as I said, some of the same files have worked perfectly in the past.
That Kodi log you posted isn’t showing any 4K modes, and it isn’t showing 1080p@24hz support so it is trying to convert it to 1080p@60hz. If you provide full logs perhaps that may show more.
Not that I can see from the log you supplied. Perhaps you should try unplugging your equipment from the wall for a minute and when plugging it back in make sure the Vero is started up after the display has had a chance to fully initialize.
2023-07-14 21:53:50.118 T:2757 info <general>: Current display setting is 0192001080060.00000pstd
2023-07-14 21:53:50.118 T:2757 info <general>: Current output resolution is 0192001080059.94006pstd
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 720 x 480 with 720 x 480 @ 60.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Fallback resolution at 16 + 0 00480060.00000pstd
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 720 x 480 with 720 x 480 @ 59.940060 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 720 x 576 with 720 x 576 @ 50.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Fallback resolution at 16 + 2 00576050.00000pstd
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 1280 x 720 with 1280 x 720 @ 50.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Fallback resolution at 16 + 3 00720050.00000pstd
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 1280 x 720 with 1280 x 720 @ 60.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Fallback resolution at 16 + 4 00720060.00000pstd
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 1280 x 720 with 1280 x 720 @ 59.940060 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 1920 x 1080 with 1920 x 1080 @ 60.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Current resolution setting found at 16 + 6
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 1920 x 1080 with 1920 x 1080 @ 59.940060 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 640 x 480 with 640 x 480 @ 60.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 640 x 480 with 640 x 480 @ 59.940060 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 800 x 600 with 800 x 600 @ 60.000000 Hz
2023-07-14 21:53:50.118 T:2757 info <general>: Found resolution 800 x 600 with 800 x 600 @ 59.940060 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 1024 x 768 with 1024 x 768 @ 60.000000 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 1024 x 768 with 1024 x 768 @ 59.940060 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 640 x 480 with 640 x 480 @ 60.000000 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 640 x 480 with 640 x 480 @ 59.940060 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 800 x 600 with 800 x 600 @ 60.000000 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 800 x 600 with 800 x 600 @ 59.940060 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 1024 x 768 with 1024 x 768 @ 60.000000 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found resolution 1024 x 768 with 1024 x 768 @ 59.940060 Hz
2023-07-14 21:53:50.119 T:2757 info <general>: Found 0192001080060.00000pstd at 22, setting to RES_DESKTOP at 16
2023-07-14 21:53:50.119 T:2757 info <general>: No /home/osmc/.kodi/userdata/disp_cap_3d to read
2023-07-14 21:53:50.119 T:2757 warning <general>: Update3dResolutions: No valid 3D resolutions found.
It is seeing the modes now but you have other issues. You need to set your GUI to 1080p in Kodi’s display settings and turn off sync playback to display in Kodi’s player settings.
The display mode is switching as it should now but I think the message right before you stopped playback was alluding to speed issues. I would try it with direct attached storage again now that the other issue seems to be resolved.
Also messing up with local storage still? Unfortunately, I’m out of ideas other than taking your custom cache settings out of your advancedsettings. Setting higher readfactors can actually have negative effects depending on the situation.
2023-07-16 11:13:40.514 T:3077 debug <general>: CPtsTracker: pattern lost on diff 2959000.000000, number of losses 1
When I search the web for that it seems to allude to a transfer problem.
No luck without the cache options in advancedsettings neither. Thanks for the help anyway.
I haven’t found a lot of things in the internet about this “pattern lost”, but the code seems to suggest is something about recalculating the framerate. Odd, because the file has a constant fps. That part of the code also hasn’t been changed in a lot of time.
I’ve tried to reproduce the error in another kodi instance in my local machine, but here works, but of course it’s a completely different hardware, no 4k screen, etc. I’ve also tried to use an external player like mpv or vlc to see if it fixed it, but I couldn’t manage to get it working. Disabling hw acceleration makes the video unwatchable, as expected for a 4k file. I’ve also tried to play around with the framerate and video sync options, but no success.
All seems to point to an error in the file, but since it works everywhere else, I don’t know.