Oh dear, now I cant play any 4k content HDR or not. I get no signal just setting the resolution to 3840x2160p!!! Weirdly setting it to 4096x2160p gets a picture, but then i’m limited to 24fps framerate.
Did you update to the October release? We will need to see logs please
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. 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 help you get up and running again shortly.
This is me booting the device in 1080p mode, going to settings changing to 3840x2160p [no signal] then pressing back to go to 1080p again.
Do not set the resolution to 4K or an SMPTE mode. Set it to 1080p and enable Adjust Refresh Rate and everything will work as expected.
When you play 4K content, Vero will automatically switch to 4K if your receiver supports it
The issue is caused by the user trying to force 4K and refresh rate for all content. Logs aren’t needed; a settings adjustment is
Incorrect. The same behaviour happens when i chose 1080p and play 4k content
I thought simulating the issue with just a resolution change (that worked before the oct update) would produce the smallest logs.
Here I am at 1080p playing 4k content where it cuts out the same.
Logs available at https://paste.osmc.tv/etizudetey
Thanks for clarifying.
01:31:34.982 T:4075774544 NOTICE: VideoPlayer: OnLostDisplay received
Can you try changing HDMI cable?
As the HDR auto switch did not work properly; it would have only sent the HDR EOTF in most situations, but not adjusted the bit depth. We now do things to spec. This may actually be causing you issues now.
We’ll get this solved for you, don’t worry.
Sam
The Cymatic Jazz demo is 60p, and 4k 4:4:4 10bit 60hz doesn’t fit over HDMI2.0. The Vero should switch to 4:2:0 or 4:2:2 for 4k 60hz.
Edit: It does. Sorry! I was only half-updated when I tested this.
Indeed, hence:
vmode set to 2160p60hz420
I will try and reproduce this first.
Sam
Please post the output of: cat /sys/class/amhdmitx/amhdmitx0/config and cat /sys/class/amhdmitx/amhdmitx0/attr when the GUI is showing and when you have a blankscreen.
working GUI
cur_VIC: 31
VIC: 31 1920x1080p50hz
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
no signal - planet earth clip
cur_VIC: 352
VIC: 352 3840x2160p50hz
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
no signal - LG Cymatic Jazz clip
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 10-bit
Colourspace: YUV420
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
attr is blank all times
I turned off HDMI Deep Colour setting on the port and the picture appeared from the nosignal, but the tv forcibly enabled it again and the nosignal came back 
cur_VIC: 94
VIC: 94 3840x2160p25hz
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
Ive found a different clip that the tv doesn´t force deep colour mode on
(deep colour on - no signal)
osmc@osmc:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 94
VIC: 94 3840x2160p25hz
Colour depth: 10-bit
Colourspace: YUV444
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000b0000
audio config: on
3D config: off
(deep colour off - working)
osmc@osmc:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 94
VIC: 94 3840x2160p25hz
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
Thank you. The only one of those outputs which is not as expected is the first one of your last post. At the moment I can’t see why you get no picture in the other cases but will try to reproduce.
I have just got an LG C8 and am getting the exact same issue with 4k HDR test files. I have the GUI set to 1080p and Adjust Display Refresh Rate on. After playing the file the HDR logo pops up but the screen goes black, then a few seconds later loses the signal completely. Pressing stop on the remote brings the Kodi menu back. If Adjust Display Refresh Rate is off, it plays fine but only in 1080p.
Strangely I then tried to play a 4k HDR movie file and it worked fine. Here are the logs: https://paste.osmc.tv/munodiqipu
I’ve tried 2 cables with the same result.
EDIT - It actually seems to be completely random when it decides to play the file. Maybe 1 in 10 attempts works.
4:4:4 10bit HDMI signal from vero4K just doesn’t work with LG C8, period. Same here:
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
Blank screen. But! If I route signal thru HDMI splitter (gofanco 2:1 splitter, passthru mode) — it works!
Worst thing is that ‘echo 422,12bit’ does not work anymore:
cur_VIC: 93
VIC: 93 3840x2160p24hz
Colour depth: 12-bit
Colourspace: YUV444
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc00002b9, Vid clock div 0x000a38f0
audio config: on
3D config: off
LOLWUT???
We removed the ability to override colourspace with attr. Can’t remember why, now. Will check and put it back if it doesn’t break anything.
I can’t understand why you force 4:4:4 colorspace when playing 4:2:0 media source? Banding problems with 10-bit media sources can be avoided going above 8-bit modes (10 or 12 bit). Why forcing 4:4:4 then?
And, like I said, 4:4:4 10bit mode by Vero4K seems to be incompatible with LG OLED C8 model.
We found that some people got banding, but no one got banding with 444,10.
It must be advertising support for that mode. Maybe we can add a quirk for those screens, like we do for Philips 2009 TVs.
And it’s surprising that 4k50/60 @ 420 isn’t working either (as reported by @darkskiez). It seems we can only get 4k50/60Hz material to play at 422 on C8s. Am I right?