The Mali doesn’t handle video playback, the VPU does. But EOTF data is handled in the HDMI TX layer.
Thanks for clarifying the terms. But does It means that HDR10+ could be rendered with all guarantees ?
I don’t know yet.
You can test with the HDR10+ file from FF Pictures (original footage from NASA)
2GB file - 4K HDR10+ version
Thanks, will have a look.
Have looked into:
Hdr10+ doesn’t pop up on my 2018 Q9FN, of which I hoped for. Will look into it if that anyhow appear.
Played file direct on TV via usb (stuttering) but can’t select info which displays same info as via HDMI.
Played same file via vero on nfs share (fluently) and then HDMI info displays HDR UHD.
Maybe someone else with same TV has idea of HDR10+ being recognizable.
@mtv Hi. I have a Panasonic FZ800. If I connect a usb directly with the file, the “HDR10 +” icon appears in a corner.
If I do it from the Vero Simply appears HDR.
@Fydo thanks for letting me know, then for sure my Samsung 2018 Q9FN doesn’t display HDR10+ then as an icon, just HDR.
So bottom line seems to be HDR10+ is hardly worth the bother.
Certainly sounds like it. Also makes LG’s comments of them not bothering with HDR10+ because their dynamic tone mapping is just as good a bit more plausible.
TBH, I don’t understand what purpose dynamic metadata serves. Maybe an expert like @Steve_Neal can enlighten us.
just got reply from Vincent from HDTV:
Yes, Samsung’s 2018 TVs currently display [HDR] only even though they
might be playing HDR10+ content.
Got to keep selling those TVs!
I can see curved coming back any time now.
We are still keeping an eye on this though.
I spotted the first HDR10+ rip online today:
Things are moving fast now. My tv will support it, but my receiver and Vero 4K+ will not without a (firmware) update.
This is indeed still the most interesting part… No AVR manufacturer has yet announced how HDR10+ will be supported. Will HDMI 2.1 be needed or will a firmware update do it in the end? So, even if sources will support it, AVR compatability will most likely kill the format for most people.
Good thing that we’re working on it then
AVRs are always more complicated.
If the AVR does support Dolby Vision (which mine does), why should HDR10+ require HDMI 2.1?
If the AVR can support Dolby Vision then all it needs is a firmware update to support HDR10+. I’m thinking the AVR makers don’t even need to pay any additional fees to support it since they’re already doing HDR10. They just need to update the AVR to pass along the additional metadata. I could be wrong, but it sounds like a pretty simple update.
You’re working on HDR10+ now?