Vero 4K KODI not passing (some) HDR metadata

Thanks. Will check shortly.

Nope. Not working here.

Has the JVC ever shown that data?
We are definitely passing through the metadata.

Can you post a log so I can see what software you’re on?

I’m on the January 2020 update. Haven’t installed March yet. And yes, with my OPPO player I get that data. My Apple TV 4K also passes that data and I see it, though I believe it’s not technically correct because the Apple TV maps everything to 1000 or 4000 (I can’t remember which).

Has anyone else gotten this to work?

If you’re on the January 2020 update you haven’t got the 4.9 kernel installed.
Did you follow the 4.9 installation instructions?

Without 4.9, you won’t get MaxFALL or MaxCLL through.

Cheers

Sam

You’ve been living under a rock.

Details are here: [TESTING] Linux 4.9 kernel and improved video stack for Vero 4K / 4K +

HDR10+ and HLG are now supported as well.

1 Like

Good lord…

I think what happened is I read this under the January, 2020 post:

  • Add initial support for 4.9 kernel on Vero 4K/4K+

And was like, oh sweet - 4.9 is out. I guess I actually have to do more than just get the January update.

It is possible to get MaxFALL/MaxCLL working on 3.14 (can send details / build)
But you’re better off using 4.9 as that’s the way we’re moving shortly and there are numerous playback improvements as a result of being able to leverage improved microcode from the SoC vendor.

OK. Are there any downsides to running 4.9 at this time? And does 4.9 also fix the subtitle+framerate issue I messaged you about/provided file?

It’s experimental – so obviously some things might not work as smoothly.
You can get an idea of the shape of it from the test thread.

Not yet. Apparently it was sort of fixed before (according to @angry.sardine) but now it’s problematic again. I’ll look in to that soon and see what can be done.

Roger that. I’ll give it a go on my projector Vero 4K+ and report back…

edit

Updating now…

The JVC should then show that the metadata is being passed through.

1 Like

I’m assuming that because I haven’t updated to the March, 2020 update this won’t be an issue.

You’ll be updated to March + 4.9, provided that you only append the repository list and don’t remove anything.

Ah. Hah. OK. Yep I just added the line per the instructions and didn’t touch anything else. Still updating - must be the longest update I’ve seen since owning a 4K and now 4K+.

It’s probably also bringing in a large Debian base update, so it’ll take a few minutes.
The Debian Buster update will probably take 30-45 minutes.

Sam

112640 bytes (113 kB, 110 KiB) copied, 0.0100766 s, 11.2 MB/s

Setting up vero364-kernel-osmc:arm64 (3.9.169) …

Setting up python-imaging (4.0.0-4+deb9u1) …

Setting up vero3-mediacenter-osmc (18.6.0-8) …

Setting up armv7-network-osmc (1.7.7) …

Progress: [ 95%] [#######################################################…]

System is up but is stuck in Terminal at 95%.

HDR isn’t enabling for some reason on my projector, hmm.

SSH always disconnects when the network package is updating.
If you don’t press any keys, the connection will gracefully restore.

If you hit enter etc, then Putty will realise the connection has dropped and you will lose the connection.

Did you reboot?
When you login to OSMC, does it show a 4.9 kernel (uname -a)?