I was playing a 960x720/24Hz video today, and my Vero 4K+ insisted on playing it at 720p/60 instead of 1080p/24.
I was able to get it to play at 1080p/24 by un-whitelisting 720p/60; but in the light of the discussion higher up this thread, I was a little surprised I needed to do that. Is this expected behaviour, or might there be something odd going on?
Happy to post logs, mediainfo, etc. if it sounds like there’s something to look at, but didn’t want to bother if this sounds like correct behaviour.
I don’t think many people know that function is available through the context menu. Is that a relatively new addition? I certainly didn’t know about it until I stumbled upon it a month ago while hopping into the menu to change subtitle placement settings.
I could, but that starts to get annoying after a while if you stop playback and restart later - it doesn’t store the fact that you switched resolution the last time you played that file and you have to set it again each time you restart it.
That combines with another issue where, if I’m watching with the video mode set to “original size”, sometimes it doesn’t keep playing in original size mode after a resolution change.
And if you accidentally hit the Back button one time too many during playback, and then hit it again to get back to the video, that also resets the resolution to the default.
Obviously none of this is that big a deal, but given that the way it’s behaving surprised me, I figured it was worth checking what the behaviour is supposed to be.
It was new in Kodi Leia, I think - not available in Krypton.
Okay, fair enough. It seems odd to me, though - I would have expected it to prioritise matching the refresh rate to matching the resolution (so, given a 720p/24 video I would expect it to pick 1080p/24 in preference to 720p/60). In fact, I thought that was precisely the change you and Sam made back in May… I obviously misunderstood.
I understand you now. When you said “I was a little surprised I needed to do that” [emphasis mine] it sounded like you were saying the normal workaround was not functioning for you.
No - the change we made was if there wasn’t the correct refresh rate at the GUI resolution then try a higher one. Aimed specifically at US TVs without 1080p50Hz but with 2160p50Hz.
TBH I don’t understand Kodi’s thinking. In Krypton they had a scoring system to select the best compromise, and I can’t recall anyone complaining about that, albeit it didn’t consider resolutions less than GUI. They then abandoned that to prioritise width and height. There’s a further go at it in a PR by Lukas but it hasn’t been agreed and I still don’t understand what he’s trying to achieve.
