[TESTING] Vero 4K / 4K + video improvements

Vertex%20Vero4k%20(Leia)%20Planet%20Earth%20-%20no%20whitelist

Clearing the whitelist enables Vero to play back HDR files at 10bit 444 23.973 on the LG B7 OLED. I’ve double checked.

Looking at the logs

umefixarog : White list detecting wrong resolution

22:16:33.470 T:4071699040 DEBUG: Trying to find exact refresh rate
22:16:33.470 T:4071699040 DEBUG: Matched exact whitelisted Resolution 4096x2160 @ 23.98 - Full Screen (39)
22:16:33.470 T:4071699040 NOTICE: Display resolution ADJUST : 4096x2160 @ 23.98 - Full Screen (39) (weight: 1080.000)

vs. oxotucoyey : No White list - works

21:09:09.900 T:4070335072 DEBUG: Trying to find exact refresh rate
21:09:09.902 T:4070335072 DEBUG: Matched exact whitelisted Resolution 3840x2160 @ 23.98 - Full Screen (37)
21:09:09.902 T:4070335072 NOTICE: Display resolution ADJUST : 3840x2160 @ 23.98 - Full Screen (37) (weight: -0.000)

The only reason I have the whitelist is to to stop kodi from briefly switching to 25Hz before going to 50Hz every time I change TV channel (with 1080i). Thats another story.

Unless you have a specific use case, I would argue that it is better to clear the white list.

1 Like

OK, good. That’s a recent change in Leia - to make it behave like Krypton in the absence of a whitelist. Before, it wouldn’t select any resolution that wasn’t on the whitelist. But why it should mistake 4096 for 3840 someone needs to look into. Good spot.

2 posts were split to a new topic: DVB framerate detection wrong on Leia

If 4096 resolutios are not selected from the whitelist, all files a played ok.
That is the solution for now.
Can those with 2018 LG TVs give some feedback.

@mosmos what do you need from us?

Just to be sure it’s not lost (I added it as edit into my post somewhere above):

Looks like I see terrible lagging (or flickering or what is it) when playing Life Untouched HDR UHD 4K Demo | 4K Media - first 5 seconds camera goes up with tree on the right. The tree itself is flickering a lot (or banding or how the effect is called?) . Both 422 enabled/disabled in attr. I don’t think it was there before. With 422 disabled it plays on 3rd or 4th attempt while with 422 enabled it always plays.

It looks like the move is not fluent and for some reason those branches on tree are “jumping” up and down - like frames are rendered in wrong order.

Other videos are fine (I just tried few another HDR demos)

Just tried it here and I get that jiggering effect. Not massively but noticeable. It’s the same played from Vero as it is played from a USB plugged into the TV.

OK, maybe I did not notice it as I was using these “smart” smooth functions before and I turned all off now. THX Grahamh for testing all of these. You are the best guys.

If you’ve got a 2018 LG OLED TV, can you can deselect the 4096 resoultions from the whitelist and play the troublesome 4KHDR videos.
If you can confirm they can be played ok, I’m sure @sam_nazarko and @grahamh will appreciate the feedback.

Where can I find the whitelist?

if you’ve not used it before, then it is best you don’t touch it as this is what is causing some of the problems.

In my system I have these two kernels installed but still booting from the 117 version

¿ How can I boot from the 126 version ?

vero364-image-3.14.29-117-osmc/unknown,now 117 arm64 [installed,automatic]
vero364-image-3.14.29-126-osmc/unknown,now 126 arm64 [installed,automatic]

Run sudo apt-get install —reinstall version where version is the kernel you wish to use

Thanks. It worked.

I started to experience strange issues related to HDR with 117, I mean it seems that latests kodi leia builds with 117 version does some kind of “non-true-HDR-output”, even if HDR tag is enabled in the display.

But with 126 now HDR works well again.

HDR is HDR.
I suspect the bit depth was incorrect,however.

No doubts about bit depth could be issue (I don’t know low level details about kodi-kernel interaction).

Just mentioning that this specific combination of versions Kernel 3.14.29-117 + Kodi Leia beta wasn’t giving a correct HDR output.

I just didn’t find better words and still wondering how I got 126 installed but still booting from 117.

This can happen if kernels are installed manually
We are looking at ways to improve this.

Sam

Have you done this and if so how would i go about applying it?

No – I’ll just release this as an update shortly

Sam

Any idea when shortly will be? I got the vero for 4k hdr playback but it’s the only thing that’s not working on it so a bit frustrated.