Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
Now that HDR format detection is working, it would be nice if HDR10+ detection is added as well. Since HDR10+ is backward compatible to HDR10, make the "%HDR" reference code display "HDR" for regular HDR10, and have this display "HDR+" instead if HDR10+ is detected.
Here is the summary from a Grok query:
ffprobe effectively differentiates between HDR10 and HDR10+ video files by analyzing the presence of dynamic metadata in the side data list. HDR10 files contain only static metadata (Mastering Display Metadata and Content Light Level Metadata), while HDR10+ files additionally include Dynamic HDR Plus metadata, which ffprobe reports as a distinct side data type. By using commands like ffprobe -show_frames -show_entries frame=side_data_list, you can reliably identify these formats. The primary difference in ffprobe output is the presence of "side_data_type": "Dynamic HDR Plus" for HDR10+, which is absent in HDR10. For accurate results, ensure you use an up-to-date FFmpeg build and verify HDR10+ metadata with tools like hdr10plus_tool if needed.
This is the link to the Grok query which shows how to differentiate between HDR and HDR+ using ffprobe: https://grok.com/share/c2hhcmQtMg%3D%3D_6b5ed25f-37dc-45e2-95ee-32060e2aedd9
That looks do-able ... will have to figure when I can find some time to implement this (on the To Do list now!).
Did some initial tests with 5 HDR10+ files, and none of the show the tag (ffprobe 7.1.1 - latest AFAIK) suggested in the article.
"side_data_type": "Dynamic HDR Plus"
Quote:
HDR10+ videos explicitly list "side_data_type": "Dynamic HDR Plus" in the side data list, which is absent in HDR10 videos.
Did test these files with MediaInfo as well, which does detect HDR10+ properly.
As you can imagine, I'd rather not switch to the MediaInfo library as it would have a serious impact on RMTV.
To test this use:
ffprobe -show_format -show_streams -v quiet -print_format ini <filename>
This is INI formatted, but it is the same data as JSON formatted.
You can also see this when dropping a video file on RMTV, select and right click that file in RMTV, and choose "copy ffprobe output to clipboard" and paste it in a text editor.
So for now I do not know (yet) how to distinguish HDR from HDR+.
Any ideas?
Oh wait, when using "-show_frames", which outputs a ton of data, the HDR+ tag can be seen (for short test file already 1Mb text output).
Just found a way to limit the ouput:
ffprobe -show_format -show_streams -v quiet -print_format ini -show_frames -read_intervals "%+#2" <filename>
Only problem with that is that the appropriate section comes with 2 numbers, which I'd have to guess or overly analyze the data.
(looking into this)
Eg. The "0" and "2".
[frames.frame.0.side_data_list.side_data.2] side_data_type=HDR Dynamic Metadata SMPTE2094-40 (HDR10+)
Not unsolvable though, but then I went thought the implications on other levels - which has a larger impact than anticipated.
I'll try to find time to implement this but it will probably have to wait until after my vacation.
🥳 I've managed to implement HDR and HDR+ distinction.
So the HDR tag (and .HDR tag of curse) will now return "", "HDR" or "HDR+".
I'll try to release this in a few minutes.
Released 2.3.9 just now (link) for the HDR+ support. 😋
I have tested HDR+ on all platforms, and it seems to work (had to upgrade ffprobe under Windows).
I've mark this topic as "solved" - please confirm it works for you.
Thank you for reporting, testing and confirming that it works now. Much appreciated 😊
