Thanks, I’ve edited your post. So banding due to wrong bitdepth is no longer a problem. Residual banding still exists, at least on LG OLEDs, at least on Revenant. If anyone can clip me that part of Revenant I will see if it’s noticeable on my Panny and have a fiddle with the dithering settings.
If you know the time stamp I can send you a sample of the remux I should have the file in 4k somewhere on my PC still was getting it for a friend when it was freshly released
It’s most visible in the section between 00:01:30 and 00:02:10, from memory. There’s a fade out of a scene with a very gradual gradient sky which shows it very clearly.
This is interesting, I’ll try and see whether I can get a picture on 122 with PC mode disabled, I don’t think I was able to on the B8, but I have tried so many permutations with some inconsistent results, so i’m not 100% sure.
This is exactly what I see, some banding but better than with 8bit output, I hope I get the same result as you with PC mode disabled.
Ok I made a sample that starts at 90s into the movie and goes for 90s so that should show the affected moments.
Link : Revsample4k
Rar password is osmc
No problems with that test clip on my Sony KD55XD8005
OSMC 17.8-347 with the 122 kernel.
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
I have now tested it by directly connecting the Vero to the tv. I get a “no signal” regardless of setting the input of the Vero to PC mode. Strange, but because I want to use the AVR, I stop trying to get that to work. If it helps anyone, I can give it another go.
Via my AVR 444 10 bit works with and without enabling PC mode. The AVR reports the input signal as 444 10 bit. It seems the AVR changes the signal, because with a direct connection between the Vero and the TV I get “no signal”. I can’t see what the AVR outputs (the AVR nor the TV display it), but it is possible the AVR converts to 422, because the TV doesn’t support it. Just guessing.
It might be the cable… 444 10bit needs more bandwidth than 422. Are you using the same cable that you used to connect your Vero to your AVR with?
Yes. Banding still there via Plex/XPlay/direct USB. .
Also, the built-in LG C7 decoder is broken for UHDs. Lots of movies with macroblocking issues. No other devices have that issue.
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config cur_VIC: 93 VIC: 93 3840x2160p24hz Colour depth: 10-bit Colourspace: YUV422
I noticed that your config when playing that clip shows YUV422 colourspace, whereas on my original comment about banding in the movie it shows YUV444. I have no idea if that is expected behaviour with different panels?
VIC: 93 3840x2160p24hz Colour depth: 10-bit Colourspace: YUV422
We are building up our collection of EDIDs. If you haven’t done so, can you post cat /sys/class/amhdmitx/amhdmitx0/rawedid
and cat /sys/class/amhdmitx/amhdmitx0/edid
please?
Yes, I would like to know that as well.
It might be the cable… 444 10bit needs more bandwidth than 422. Are you using the same cable that you used to connect your Vero to your AVR with?
Yes. I tried both the cable that’s between the Vero and the AVR (included with the Vero) and the cable that’s between the AVR and the TV.
We are building up our collection of EDIDs. If you haven’t done so, can you post
My values:
osmc@Vero4Kp : ~ $ cat /sys/class/amhdmitx/amhdmitx0/rawedid
00ffffffffffff003dcb610f000000000019010380a05a780aee91a3544c99260f50542108003140454061400101818001010101010108e80030f2705a80b0588a0040846300001e023a801871382d40582c450040846300001e000000fc0054582d4e523634360a20202020000000fd003a791e883c000a2020202020200151020363f0596160101f666504130514030212202122015d5e5f6263643f403b097f070f7f071707503f06c04902005706015f7e035f7e01677f01834f00006e030c002300b83c2000800102030467d85dc401788003e305c000e200cfe20f33e3060501662150b051001b304070360040846300001e00000000000000000000e1
osmc@Vero4Kp : ~ $ cat /sys/class/amhdmitx/amhdmitx0/edid
Rx Brand Name: ONK
Rx Product Name: TX-NR646
Manufacture Week: 0
Manufacture Year: 2015
Physical size(cm): 160 x 90
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0x51
Source Physical Address[a.b.c.d]: 2.3.0.0
YCC support 0x03, VIC (native 255):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 16 31 102 101 4 19 5 20 3 2 18 32 33 34 1 93 94 95 98 99 100 63 64 95 94 93 98 353 352 358 357
Audio {format, channel, freq, cce}
{1, 1, 0x7f, 0x07}
{1, 7, 0x7f, 0x07}
{2, 7, 0x07, 0x00}
{7, 7, 0x06, 0x00}
{9, 1, 0x02, 0x00}
{10, 7, 0x06, 0x01}
{11, 7, 0x7e, 0x03}
{11, 7, 0x7e, 0x01}
{12, 7, 0x7f, 0x01}
Speaker Allocation: 0x4f
Vendor: 0xc03
MaxTMDSClock1 300 MHz
Vendor2: 0xd85dc4
MaxTMDSClock2 600 MHz
ColorMetry: 0xc0
SCDC: 1
RR_Cap: 0
LTE_340M_Scramble: 0
HDR DeepColor
checkvalue: 0x51e10000
We are building up our collection of EDIDs. If you haven’t done so, can you post
No problem
osmc@osmc:~/.kodi/userdata$ cat /sys/class/amhdmitx/amhdmitx0/rawedid
00ffffffffffff004dd903f301010101011a0103807a44780a0dc9a05747982712484c2108008180a9c0714fb3000101010101010101023a801871382d40582c4500c2ad4200001e011d007251d01e206e285500c2ad4200001e000000fc00534f4e5920545620202a30300a000000fd00303e0e461e000a20202020202001ca02034df0575d5e5f621f101405130420223c3e1216030711150206012c0d7f071507503d07bc570600830f00006e030c004000b83c2f008001020304e200f9e305ff01e50e60616566e3060d01011d8018711c1620582c2500c2ad4200009e000000000000000000000000000000000000000000000000000000000000000041
osmc@osmc:~/.kodi/userdata$ cat /sys/class/amhdmitx/amhdmitx0/edid
Rx Brand Name: SNY
Rx Product Name: SONY
Manufacture Week: 1
Manufacture Year: 2016
Physical size(cm): 122 x 68
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0xca
Source Physical Address[a.b.c.d]: 4.0.0.0
YCC support 0x03, VIC (native 255):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
93 94 95 98 31 16 20 5 19 4 32 34 60 62 18 22 3 7 17 21 2 6 1 95 94 93 98 352 353 357 358
Audio {format, channel, freq, cce}
{1, 5, 0x7f, 0x07}
{2, 5, 0x07, 0x00}
{7, 5, 0x07, 0x04}
{10, 7, 0x06, 0x00}
Speaker Allocation: 0x0f
Vendor: 0xc03
MaxTMDSClock1 300 MHz
ColorMetry: 0xff
SCDC: 0
RR_Cap: 0
LTE_340M_Scramble: 0
HDR DeepColor
checkvalue: 0xca410000
ATM, if you change the TV mode you will have to reboot vero or at least restart kodi (Power->Exit) to get it to re-read the EDID. That may be why it works with one setup but not another.
That will be fixed in the next update.
My values:
So this is for through yr AVR but with or without PC mode?
I noticed that your config when playing that clip shows YUV422 colourspace, whereas on my original comment about banding in the movie it shows YUV444. I have no idea if that is expected behaviour with different panels?
Yep, I’ve move my Vero to a different HDMI port on my TV. On some Sony TV’s only 2 of the ports are full bandwidth and support 10bit444 the other 2 only support 10bit422.
Edit:- Just to be thorough I’ve move my Vero back to one of the full bandwidth port and tried the test clip again, and at 10bit444 it still plays without any banding.
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 10-bit
Colourspace: YUV444
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
So this is for through yr AVR but with or without PC mode?
Without PC mode.