I’ve tried latest kernel, nothing improved, banding is still present watching 10bit movies.
Thanks for checking. Can you reboot, play a bit of 10-bit content and give us a debug log, please?
You can learn more about how to submit a useful support request here.
So, in summary:
- activate the logging
- reboot the OSMC device
- reproduce the issue
- upload the log set either using the
Log Uploadermethod within the My OSMC menu in the GUI or thesshmethod invoking commandgrab-logs -A - publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can sort this shortly.
It’s ok, nothing to apologise for. Here is the log as you suggested
https://paste.osmc.tv/ijolufocap
Edit: sorry I forgot, here is the same output for all the three movies I’ve watched logging
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 8-bit
Colourspace: YUV444
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
Aha! You are running Leia. I’ll have to see how that affects things.
Your desktop is set to 4k24Hz. If you set it to 1080p60Hz you should get 10 bit videos OK.
It’s a bug I’m looking into.
Leila let me passthrough TrueHD and DTS MA in a proper way, sorry if I didn’t mention this
NP, but I didn’t know passthrough was different. how is it better?
Setting 1080p@60hz the movie starts with the same resolution. Banding is still present.
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 16
VIC: 16 1920x1080p60hz
Colour depth: 8-bit
Colourspace: YUV444
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
1 Like
Set Player->Adjust refresh rate to on start/stop and you should get 10-bit.
I’ve tried several times to change every setting, including that one. The resolution remains the same of the GUI, same hz even, and 8bit with banding. If you want, I should revert everything to default with a fresh start.
just for fun, can you try
echo 42210bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
That ought to force 10 bits unconditionally. If it does, then probably your settings need looking at, but it could still be there’s something about Leia I haven’t taken account of yet. I haven’t spent much time with Leia.
GUI:
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 10-bit
Colourspace: YUV422
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
During 10bit movie:
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 10-bit
Colourspace: YUV422
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
No banding in the sky…
Did you use resolution whitelisting under Settings/System/Display/Whitelist? You have to activate all resolutions and framerates that your TV supports. Otherwise the output will always stay at the GUI resolution and framerate even though you have adjust framerate activated (this will also affect bit-depth output). This is a bit different in v18 than in v17.
Please try this, if you haven’t already, and also run this command via SSH:
echo now | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
Oh, so I’m not running the latest? Should I run this again? https://discourse.osmc.tv/t/testing-vero-4k-4k-video-improvements/74832/127?u=monochromic
If you are running kernel 121 you are up to date. If not, that’s the way to upgrade. I thought the last log you posted was kernel 119.
I must’ve linked to a log file from some slightly earlier testing. I’m currently running 3.14.29-121-osmc
Did you follow this remark?
Yes, I do have access to such analyzers. Since I’m in the middle of a house move, all my stuff is in storage and I can’t do any testing for at least a month.
@grahamh: Mode 2 enables 4K 50/60 10-bit YCbCr 4:2:0/4:2:2, 8-bit RGB/YCbCr 4:4:4. Oddly @monochromic 's TV doesn’t show 10-bit YCbCr 4:4:4 for 4K 24/25/30 even in Mode 2. It could be that the TV does support greater than 10.2Gbps data rate even when in Mode 1. This might explain why the TV reports 10-bit YCbCr 4:4:4 when 10-bit is enabled in rc.local.
No I didn’t, I’ve just leave everything as default.
I’m gonna take a look.
I’ve tried your command, it replied just “now” and the output has changed, going back to YUV444 8bit:
osmc@osmc : ~ $ echo now | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
now
osmc@osmc : ~ $ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 8-bit
Colourspace: YUV444
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
I’ll try with whitelist stuff…
I’ve enable all resolutions under whitelist and now everything seems fine, also the refresh rate switch between GUI and movies.
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 97
VIC: 97 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV444
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 10-bit
Colourspace: YUV422
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
Is it possible to get YUV444 and 10bit@24hz at the same time? The image look great but I want to be sure I get the best image quality possible. Thank you for the support guys!