444 10bit HDR output from Vero 4K + NOT PERSISTENT

Thanks for the suggestion.

All the inputs on the AVR are supposed to support 4K HDR, but when I connected it to the one the PS4 is using, I started getting intermittent video with the HDR files (few seconds on and off), which made me suspect the cable:
So I’ve swapped out the HDMI cable that came with the Vero, with a similar length “Amazon Basics High Speed 2.0” HDMI cable, and connected to the original port I was using on the AVR, and it works perfectly now!

I decided to re-test the Vero cable direct to the TV, and in that setup it works fine too: Very strange :slight_smile:

So to summarize:
When using the “Vero supplied HDMI cable” connected to the AVR; HDR does not work or does not work properly, but when connected directly to the TV it is fine.
Weird. Would be interested on anyone’s thoughts on this, from a technical point of view (promise I wont’ be sensitive to any criticism of my AVR :wink: ).
At least the issue is resolved, with a different cable.
Many Thanks for your help.

1 Like

Maybe a splash of contact cleaner would improve things for that cable.

OK: So maybe just an issue with the contacts.

One other thing I noticed with this experimental kernel, is that it would occasionally revert to 8-bit with the HDR. This happened twice, and I think it was after it was powered off. A reboot was required both times.

Do you mean powered off or on standby?

It sounds like an EDID-reading issue. If you start vero with no display connected, it may not be getting the HDR capabilities from the display.

I meant powered off.
But, yes, I just tested it, and it does only revert to 8-bit HDR if the AVR is on standby when it is powered on.
Another mystery solved :slight_smile:

Is it necessary to keep the Vero running in 1080 to ensure the 8bit/10bit colour switching for HDR happens correctly?

I changed the video settings to 2160p, and HDR switching was fine. However the Vero will upscale any 2K video to 4K.

Just to add at 1080p video settings, 4K videos are output correctly at 4K.

[Edit 2]
Actually I only have 10-bit HDR files, and SDR files.

Could you grab debug logs for that situation, please?


I enabled logging.
Powered off the Vero.
Put the AVR in standby.
Powered on the Vero.
Brought the AVR out of standby.
Played a HDR video, and could see posterization in flatish areas.

You could try doing this after booting with the AVR on

That did not work for me.
I can see the disp_cap file under the /home/osmc/.kodi folder, and I can see that it does appear to list all the display modes my TV supports.
However HDR will still be played at 8-bit.

One other thing I noticed is that, in that situation where the AVR is on standby, and the Vero powered on, the gui resolution drops to 720p. And, a subsequent reboot does not resolve this (although HDR video playback is corrected). So I have to manually adjust the resolution again.

Please post a debug log when this happens



I can see what’s happening in the log already posted, but don’t know if that’s before/after producing the disp_cap file. There is no EDID available at boot, and the device is falling back to 720p, RGB. When an EDID does become available, Kodi doesn’t get to know about it.

I’m surprised this is happening with a relatively new Denon. They should report some basic functionality even when turned off as I understand it.

[Edit for clarification]


The original logs are before disp_cap was copied.

These are after:

So the disp_cap file in .kodi makes no difference.
An additional reboot, while the AVR is on fixes HDR playback, but the interface gui is stuck at 720p, unless I manually change it.

1 Like

Maybe this only happens if HDMI passthrough is enabled? In my case it’s disabled because I connect my SAT receiver direct to the TV.

If HDMI passthrough is enabled (on the AVR, I assume) then the AVR may not be offering any EDID configuration or would only offer the EDID of the TV. If it’s disabled, I would expect the AVR to offer some EDID.

13:20:26.238 T:4075360848 ERROR: GetString: error reading /home/osmc/.kodi/userdata/disp_cap

Kodi is struggling to read it - can you post ls -l ~/.kodi/userdata please?

And cat ~/.kodi/userdata/disp_cap.

Edit: Aha! the original instructions are wrong. Should have been:

cp /sys/class/amhdmitx/amhdmitx0/disp_cap /home/osmc/.kodi/userdata/disp_cap

Thanks, that’s pretty much resolved all my issues :slight_smile:

However, I can’t help being a bit curious about the AVR EDIT (admittedly it’s not a term I had any familiarity with until now):
On the PS4 Pro, with all the video settings set to auto (Resolution, RGB Range, HDR, and Deep Color Output), I do not get any issues when starting it up with the AVR still in standby. When the AVR is started the TV will report resolution of 2160p on the login screen, and HDR games all work fine.
What are your thoughts on this ? I appreciate it might simply be a case of different hardware capabilities, or available libraries.
Just curious; I’m more than happy with how the Vero is working.

EDID is how a display and/or amp tells a source what resolutions, audio formats, etc it can handle. The thing seems to be that Kodi only asks for it once when it starts up. If your AVR and/or TV are not on when you power on vero (or the hdmi cable is unplugged) Kodi defaults to something simple (1280x720 IIRC). If my AVR is on (standby), but not my TV, the AVR indicates a short list of resolutions, including 1080p, so that Kodi is happy when it starts. It looks like your AVR is not even doing that. Don’t know why - maybe some setting you can play with there on the AVR. @Chillbo knows about Denons. The disp_cap file is a hack to give Kodi something to work with if it can’t get an EDID.

Your PS4 probably has a method of sensing a change on the hdmi cable, re-reading the EDID and setting itself to the native resolution of the display as soon as it can ‘see’ it. I’m now looking at how we could get Kodi to do that.

Thanks for the comprehensive explanation !