HDR10+ on Apple TV (2022)

My tv is not hdr10+ capable,
here’s a hdr10+ dynamic metadata test file for anyone interested to test

1 Like

Thanks for posting!

Just tested here, and the picture changed every 10s for me - indicating the HDR10+ metadata was processed correctly.

Hi James, I can see the mp4 file metadata is processed but I don’t suppose you can confirm the same for uhd mkv rips?

Given what plex does with profile 7 DV ( kicks in the appropriate mode but doesn’t actually process anything) and historically the static metadata on HDR10 with both infuse and plex with generative values being sent I am a bit weary of just accepting what the TV is doing and presume it’s correct.

If the new gen ATV is now processing metadata correctly from uhd rips with dynamic metadata I don’t suppose it can be checked if this also applies to to static?

Thanks for your help


The easiest way to confirm is to run the sample posted above, and you can see the metadata is respected.

The playback container doesn’t make much difference to Infuse, so MP4, MKV, etc will perform the same.

Apps that switch to DV for unsupported profiles (like profile 7) are making a choice to do so, as this is not normal behavior of the Apple TV APIs. This is definitely not the case here with Infuse.

We’ll continue to gather feedback as more and more people upgrade to the new devices and HD10+ content becomes more widely used, but based on what I’ve observed I believe HDR10+ is working correctly in the current version.

Hi James

Firstly thanks very much for your reply,I should have worded my post more clearly sorry for that, my concern was specific for backups made from uhd disks. Most will say HDR10 is fully supported within infuse but it’s long been known the metadata is ignored and standard values are sent.

Considering most current HDR10+ disks are also dual layer (HDR10+ base layer with the additional DV layer), are we sure the dynamic metadata is passed? Could it be flagging HDR10+ yet behaving like it does with regular HDR10 backups?

If the new ATV is passing the dynamic metadata from the base layer of HDR10+ releases then it should also be passing the static metadata from regular HDR10 as they are located in the same place which would be great news indeed. Hopefully someone with the necessary tools will be able to confirm this in due course