New test build with a different approach to work around the problem.
https://drive.google.com/drive/folders/1cre_XZ29ilOeePwoNaBGJz4eVuH-jIYg
I just started the upload so it might take a few minutes for builds for all platforms to appear.
The build posted yesterday is not working for me same issue as before. Some stuff I tried yesterday was not HDR it seems.
We are working on it from a different angle, hopefully it’ll fix the problem.
@cdu13a will update when he has a build ready to test.
@richardc1983 Did you get a chance to try the last build I posted today?
https://drive.google.com/drive/folders/1cre_XZ29ilOeePwoNaBGJz4eVuH-jIYg
I will have a go tomorrow, thank you.
Just an update, working fine with the latest build with whitelist disabled and colour depth switching enabled.
Not sure what you have done but it seems to have fixed it, for me anyway.
Can you explain what you have changed and why Kodi was not working that way before as you mentioned something being the new standard which you was working towards?
The change I made was in the HDMI drivers not kodi.
Before the change the HDMI driver was set to automatically use the absolute highest quality setting(YUV444) that the HDMI 2.0 standard would allow for encoding it’s video output for 10bit at uhd/4k resolutions. Some TV’s apparently don’t like this. So I changed it to use the slightly more conservative setting(YUV422), that more TV’s should be ok with.
The change from YUV444 to YUV422 doesn’t make any difference to what you will see on your TV. Since YUV422 is still better then the YUV420 used by consumer video.(Bluray, DVD, streaming formats, etc…)
As for why it was not this way before, YUV422 was at one point in time the default in CoreELEC but with all the changes and improvements with auto switching the colour space/bit depth/HDR/etc… the new code wasn’t setup that way.
1 Like
Hi cdu13a
Just replied to your other post you tagged me in, things are not working again 
Thanks in advance.
Settled down to watch some 4k as been hectic recently so not been time for any 4k action. Were on 9.0.1 and cannot play 4k again with the toggles both off. Both the toggles you mention above are off, however I am getting no signal when trying to play 4k. The GUI is set to 1080p as suggested. If I set it to 4096x 2160 or 3840 resolution 4k starts to work.
If I limit display depth using the 8 bit toggle all works ok as well but with the toggle off 4k (10bit) I am assuming is not working.
If I turn 8 bit toggle off and use the 4.2.2 toggle on then 4k will start playing but when I press stop Kodi seems to go back to no signal or is not switching back, If I press stop Kodi freezes up and I have to reboot the box to get a signal back. This is when using 1080p resolution. If I use 4096 or 3840 resolutions then it will work ok.
Can only get 4k working by setting resolution to 4096x2160 or 3840x2160 and turning on 4.2.2 colour subsampling toggle. If I set it to 1080p as suggested it doesn’t work and I get no signal.
If I use 1080p resolution I have to turn the limit display depth to 8bit and it seems to work correctly in 4k but of course it’s not 10bit.
Everything else results in no signal.
We need dispinfo output when you get no signal.
And please remind us, what brand and model is your TV?
LG B8 65" - seemed to be fine before these updates when we were last mesaaging.
log-2019-04-07-18.50.22.zip (653.2 KB)
Logs attached… This was with 4.2.2 enabled and 1080p resolution.
That’s not the dispinfo output.
Sorry I thought I had provided same logs as last time?
You need to play the video, SSH into the box and type dispinfo. It’ll spit out a URL with the log which you can post here.
Edit: Just dispinfo, no | paste needed.
Ok will have to post TMRW as my brother needs to be on hand to do it.
4k seems to work of any resolution with both toggles off and gui resolution set to 4096. Of course then normal TV can stutter.
What’s changed as we had got this working before, TV has same brand new certified hdmi cable. Turning to 8bit all works ok but it’s in 8 bit.
4096x2160 is the wrong resolution to use. You should be using 3840x2160.
I don’t what version you were using before, but nothing changed recently.
Yes I just get no signal if I try to switch to that in settings.
I thought we were meant to use 1080p?
Without dispinfo output, there’s no way for us to tell you what is wrong.
The idea is that as long as the resolution of the video is equal or greater, it will automatically switch into the correct resolution/refresh rate. I guess that when you set res to 4096, it doesn’t switch resolutions anymore and so everything seems like it’s working.
For me to be able to select 3840 resolution I have to turn on 4.2.2 toggle but then most 4k stuff doesn’t work and I get no signal on most 4k content.
It seems it’s the 10bit stuff that ain’t working.