Here’s the log and output:
http://paste.osmc.tv/avateyunas
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo 422now | sudo tee attr
422now
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 10-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
Again no signal for that video.
Thank you. There’s a small tweak to Kodi that lets you select 422 at 4k60Hz but it hasn’t made it into the repos yet. But you should be able to select that from the commandline.
If you have a minute, you could try first forcing 8 bits with
echo 8bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
Then set a 4k60Hz GUI the usual way
Then try to set 4k60Hz 444 with
echo 2160p60hz | sudo tee /sys/class/display/mode
this may well blankscreen. If it does,
echo 2160p60hz420 | sudo tee /sys/class/display/mode
… and reset the GUI resolution using the GUI
if it doesn’t blankscreen,
echo 42210bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
if you still have a picture (GUI), that will be interesting. please cat config to confirm.
Playing a 4k60Hz vid now will still blankscreen so no need to try that.
Installed the latest kernel:
Linux vero4k 3.14.29-130-osmc #1 SMP Mon Nov 19 05:38:05 UTC 2018 aarch64 GNU/Linux`
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo 8bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
8bitnow
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo 2160p60hz | sudo tee /sys/class/display/mode
2160p60hz
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 97
VIC: 97 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo 42210bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
42210bitnow
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 97
VIC: 97 3840x2160p60hz
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
Switched GUI resolution back and forth to 2160:
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 10-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$
Always had a picture, however after the 42210bitnow (I had to switch resolutions back and forth in the GUI for the change to happen) the GUI display and audio was flaky… menu sounds where garbled, and the picture got lost for a second from time to time.
The projector reported 2160p60 420 8 bit even after the command for 444 mode.
Thanks but not sure I understand. You issue 42210bitnow and you are in 42210bit mode with the GUI showing, right?
Why do you have to switch resolutions? The change has already happened, hasn’t it?
Also, you are playing a video (EOTF: HDR10). That wasn’t the intention - unless you have that special
kodi tweak, starting a video will always try to set it back to 4k60 420.
ok, here we go again, tried to document everything exactly on a tablet as I went along (my problem is that the vero/projector are in the basement and the pc is upstairs – lot’s of running up and down ;))
reboot vero, starts up in 1080p60, 8bit, projector reports 1080p60 444 no hdr
cur_VIC: 16
VIC: 16 1920x1080p60hz
Colour depth: 10-bit
Colourspace: YUV444
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
echo 8bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
screen flashes to no signal for a couple seconds, then projector reports 1080p60 444 no hdr again
cur_VIC: 16
VIC: 16 1920x1080p60hz
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
set gui to 3840x2160, projector reports 2160p60 420 no hdr
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV420
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
echo 2160p60hz | sudo tee /sys/class/display/mode
screen goes to no signal for a second, then back again. projector reports 2160p60 420 no hdr
cur_VIC: 97
VIC: 97 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV420
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
echo 42210bitnow | sudo tee /sys/class/amhdmitx/amhdmitx0/attr
screen goes to no signal twice and then back again. projector reports 2160p60 422 no hdr
cur_VIC: 97
VIC: 97 3840x2160p60hz
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
tried moving around in the menus, menu sounds where ok and display was always fine.
then I tried playing 24fps 2160p hdr10 media, played fine, but after stopping playback the menu sounds were garbled and display lost signal for a second every 5-10 seconds (which was the same as my previous post above).
Hope this helps!
Perfect, thanks! All as I expected and confirmed by others. Stand by for the next testing upgrade.
Obstler42 was right if I leave out the denon AVR then 4k / 4k hdr playback works ( I’m still running that dev build I was suggested to download in some of the earlier post here, shall I return to the main build?? )
However this setup messed up the audio playback. So the AVR is still connected to the TV’s ARC hdmi input but I only get stereo audio played back by the AVR anything else is just silence so I would prefer if you could solve the original issue so I could return to the original chain: vero connect to AVR and AVR connected to TV.
The next release should give you some more options to try. I can’t recall if you have tried different cables. Can you get a picture with a direct connection using either the cable you are using to connect vero to the AVR or the one connecting AVR to TV?
I just had a look at your projector specs. It says only 422 is supported at 4k60Hz which is what we seem to have confirmed.
It’s HDMI 2.0b 18gbit/s, so 4k60p HDR is only possible at 422 – 444 would need more b/w and HDMI 2.1.
Updated to the latest -131 kernel today, but still no change. Can only play 4k 24Hz when setting 422now to attr first and no 4k60hz at all.
Device specs and cables are besides the issue IMHO, as any and all 4k (incl. 4k 60p HDR) played before the October update through the AVR, and still play now when I take the Denon AVR out and connect the vero4k directly to the projector.
Please wait until Kodi is updated. Then we can get this sorted.
I will try out with new HDMI cables, any suggestions on what to look for when buying? Shall I buy ultra high speed HDMI 2.1 cables just to be sure? Are they backward compatible cause my AVR (AVR-X3300W) support only HDMI 2.0B and my TV (Samsung UE65KS8000) apparently supports only HDMI 2.0?
Could be my TV a bottleneck due to only supporting HDMI 2.0 and new cables won’t fix the issue?
Ultra high speed cables are backward compatible. OSMC’s cable is premium high speed. If you ned a different length, Amazon basics’ 18Gbit/s cables have been found OK by users in here.
Thx Gtahamh and and what do you think about the fact that my TV supports only HDMI 2.0? Can that be a problem too? I read that 2.0a added some HDR stuff
No it can’t be a problem. If it plays HDR10 (which I assume it does) it’s HDMI2.0a. If it plays HLG, it’s HDMI2.0b. The cables are the same. The bandwidths are the same.
Upgraded to dev -132 kernel today, again no playback of 4k content until echo 422.
sorry, didn’t specify exactly… 
I meant any 4K content… just posting updates on new kernels to help track development.
So kernel -132, after reboot:
No 4k content plays
after echo 422now
2160p24 content plays – 60Hz still doesn’t
Thanks for the clarification. So your Sony has the LG disease. 422 at 60Hz will not be available until Kodi is bumped.
Actually it is some combination of the October updates and having the Denon AVR in between vero and the Sony projector:
