Can you check with a direct connection to the TV?
YCC support 0x03, VIC (native 97):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 16 31 102 101 4 19 5 20 3 2 18 32 33 34 21 1 93 94 95 98 99 100 63 64 95 94 93 98
720p24Hz is VIC 60, which is not in this list.
Currently your system reports support for the following modes:
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz
smpte50hz
smpte60hz
2160p50hz
2160p60hz*
The asterisk indicates that 2160p60hz is the native mode.
Here you go https://paste.osmc.tv/vuridibodi
I believe you if you say the TV is only reporting certain things, it just seems odd to me it worked fine before the update.
I tried with whitelist (what setting you suggest in my case) and nothing. If I put TV output to 1080/24 instead of 1080/60 then every file work perfectly, 23.976,24,25⌠are switched as it should. Before Leia it worked also in 1080/60 output.
With Krypton, it was possible for kodi to use a mode which wasnât advertised in the EDID, and I guess itâs possible a TV can also display a mode it doesnât advertise.
Perhaps they have increased the checks with Leia. I havenât looked closely at the code, yet.
Setting output to 1080p/50 also eliminate a problem in my case. Only 1080p/60 output with 720p/24 (not 23.976) files are affected.
What exactly does âlock HDMI hdpâ do? Does it lock the current settings for possible resolutions / refresh rates and ignore further signals in the future? My problem is that since the big update and since the two or three mini updates since then, I have inconsistencies with the auto refresh rate. If I enabled âlock HDMI hdpâ when things are working, would that protect me against possible miscommunications of the hdmi chain afterwards?
And you were right, my Tv (as most others) donât support 720/24p (23.976). What the Vero 4k did reliably in the past was displaying 720/24p as 1080/24p. Now it seems that sometimes it does not do that, but instead uses 1080/60p (gui settings). It happened just two times and eventually rebooting the Vero 4k helped.
Funny thing is, that for me 720p@23.976 was the problem. Anyway, the problem seems to be strictly 720p and resolutions that are not supported by the HDMI chain (most TVs don not get lower than 30hz on 720p)âŚ
No idea. From my perspective itâs something that used to work that now doesnât. Personally i rarely watch 720p files so itâs not a huge deal but itâs still a negative from the update.
The Lock HPD setting should only be used if you find that you donât have a signal when changing / cycling inputs on the TV.
It requires a reboot.
Sam
Ok thx, just saw this as being new after the update.
I will upload a log if and when the problem with 720/24p occurs again. I canât force the issue once it is working and I have no clue (yet) what causes it⌠and even the solution (reboot until its working) does not feel like one,
This is not what happens; the refresh rate stays at 60Hz.
According to the EDID info from my log:
YCC support 0x03, VIC (native 16):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
16 31 4 19 5 20 3 18 32 33 34 15 30 36 38
From what I could find in Wikipedia, 32 means 23.98/24Hz, so in principle this should be supported.
Maybe relevant is that this is only the EDID Information returned by the receiver. Could it be the Samsung TV thatâs attached to the receiver doesnât support mode 32?
At any rate, I am now quite sure that my movies play smoothly at 60Hz, so there isnât really a problem anymore, just my curiosity. According to this Kodi Forum Post, 60Hz seems actually a suitable refresh rate for 23.978 FPS content:
Looking back at what initially caused me to make this post, it seems now quite plausible that since the update, Kodi after turning on is running already at 60Hz, while previously the skin was running at 50Hz. So previously, a resolution switch from 50 to 60Hz would have been needed to play most content, while now this is no longer the case.