did some further testing:
CE 21 nightly behaves exactly the same like 20.5 nighly does…
plus the 1917 Dolby Vision playback freezes after chapterskip or fast forward (works with 20.5)
I did not find any debug log from your setup. So please post at least a dmesg log including when you started first video.
No, this is for 4k50/60Hz
Maybe you have a TV what do need to forced 422 mode, so try to set this in display settings. When I active it I get 4K23.975 422 BT2020 12b HDR+ 297MHz
@Portisch Here is an updated log with with the component logging.
sorry, I don’t get it. Shouldn’t the TV always get the native settings, so it can do the upscaling? Or does the amlogic box always convert it to 12bit 4:4:4?
how can I do that?
https://wiki.coreelec.org/coreelec:debuglogs
https://wiki.coreelec.org/coreelec:kodi_ce_sys_settings#version_2
here
https://paste.coreelec.org/UCEe5C
and here a full log after restart, first playback with wrong colors and second playback with correct colors:
https://paste.coreelec.org/Po80k1
Po80k1 not found.
does this work?
but is 12 bit correct?
I doublechecked with my Vero V device and it shows 10bit 4:4:4
Then maybe your TV doesn’t like 12bit, use force colour depth to 10bit and try again.
Set colour subsampling back to auto.
In past it was maximum 10bit but we did increase it 12bit because of newer TVs do support it.
ok, will try it.
just FYI, I tried it with my second am6b+ device and my Sony A95K (2022 QDOLED with different Chipset). Same behavior with latest CE 21 nightly
ok, tried it with forced 10 bit, but exactly the same behavior…
that my tv doesn’t like 12 bit does not make sense to me, because it plays it flawless on second start. And it did work with older CE versions. I may try the last official 20.5 NG-DV build later on another usb stick to verify that it worked
Edit:
Could you find anything suspicious in my log?
two more observations:
-
I got the same strange colors on first play with stable kodi NG-DV 20.4, too.
-
If I start the HDR file with gui set to 2160p and 23,98, it plays fine from the first start (so it has nothing to do with my tv not liking 12 bit). If I tab out and change from 23,98 to 60 while the video is still playing, it shows the wrong colors again.
When I think about it, it seems it has todo with the cs/cd changing of CE. If it is not involved, it plays fine. Seems to be an older issue. And i can reproduce it on all of my 3 tvs (all Sony, a 2020 model, a 2022 and a 2023 model) and with two different am6b+ devices. My other kodi device (omsc vero v) plays the same files fine doesn’t matter what gui resolution, so the files are not broken.
Maybe I try it with my new qdoled monitor later today…
I hope this helps.
Edit:
I have a theory:
could it be, that the switching of resolution and/or color is to slow or to fast for the sony tv? in this case the player thinks the display is ready and starts playback, while the tv did not finish the resoltution change. In this case the file starts bwith the gui resolution while the tv still changes resolution to the one that is asked to change for ( sourcefile) This would explain why it plays fine on second start (when resolution is already changed) and would explain the same wrong colors when resolution is changed manually during playback…
Edit 2: I set a delayed playback of 12 seconds in the options, did not help.
The strange thing is, it is just the first palyback with resolution change that causes the green/red tint. Every file playback works fine after the first try. Even if I manually change the gui resolution to lets say Fullhd 60p, every file plays fine and resolution change is no problem until I restart the box, then it will habe the error again on first file playback.
Is anything different in the code if the resolution change is made for the forst time than the other times?
I upgraded to latest 21 nightly build, still the same issue, but now player proccess info says pixel format: unknown with all formats, was checking via ssh and dispinfo. Player-led still breaks colors. Do you need any more logs or what I provided is sufficient?
Did you try with a Mkv rip? BL_EL does freeze for me but my rips play fine. 1917 freezes on chapter change.
same here. BL_EL stuttering and 1917 freezing, but my rips seem to work.
@Sunset1982 Outputting content in 24p, whether SDR with BT.709 or HDR BT.2020 in 4:4:4 12-bit is perfectly fine. Your TV is reporting it can handle that format, and so the box sends it as such. Color subsampling and color depth also have nothing to do with upscaling. The only real issue arrises because it exceeds the 340Mhz that HDMI 1.4 can handle for very old setups (whereas 4:2:2 12-bit @ 24p is just under). There’s no reason to chase forcing output of the bare minimum of what the video is encoded in. And it’s a waste of development effort to change this behavior. The key is you have at least the minimum (10-bit 4:2:0). A good read:
The color glitching you’re seeing is most likely from something else in relation to HDR10+ downgrading to HDR10 for compatibility playback. My theory is there is something in the mode setting logic that ends up passing HDR10+ output despite the TV not being able to support it and instead should have set HDR10 instead (but somehow didn’t).
The problem is not hdr+ but normal hdr files. and only the first playback after a fresh boot. don’t know what this causes.
Just found another problem with some UHD 60p files. Those habe terrible screen tearing the whole time.
For DV: latest 21 nightly shows pixelformat unknown and doesnt play 1917
Will sending a different then source color depth not have a negative impact on quality in case of some TVs?
Doesn’t it work in a way that for an 8bit/10bit source, the TV still has the opportunity to image-processing, and in the case of 12bits source, it simply displays what it gets?
I got logs for 1917 and Fel_test.mkv with component logging (checked audio/video).
1917: https://termbin.com/tl6b
Fel_test.mkv: https://termbin.com/s3lm