MediaArea / MediaInfoLib

Convenient unified display of the most relevant technical and tag data for video and audio files.
https://mediaarea.net/MediaInfo
BSD 2-Clause "Simplified" License
639 stars 177 forks source link

[Feature Request] Report correct dolby vision information in raw HEVC file #1482

Open jessielw opened 2 years ago

jessielw commented 2 years ago

When test file is in .mkv format HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible

When test file is in .hevc format (extracted from the above mkv) HDR format : SMPTE ST 2086, HDR10 compatible

Samples https://www.mediafire.com/file/m70xj085hchbk82/samples.zip/file

This was already posted here (https://github.com/MediaArea/MediaInfo/issues/587#issuecomment-1015003888)

However, as quietvoid stated here https://github.com/MediaArea/MediaInfo/issues/587#issuecomment-1015003888 both FFMPEG and MKVToolNix is capable of doing this. Dolby decided to use a specific NALU type (62) to carry the data. I would love for this to be added to mediainfo!

JeromeMartinez commented 2 years ago

Looks like some people found how to decode, e.g. with mkvmerge DOVI parser, from a guy who has a DOVI tools repo. example of parsing.

Looks like a part of the parsing comes from DASH-IF-IOP but no idea about the source of the RPU header and CM_Data() modifications, anyway it is enough for implementing the feature.

jessielw commented 2 years ago

Looks like some people found how to decode, e.g. with mkvmerge DOVI parser, from a guy who has a DOVI tools repo. example of parsing.

Looks like a part of the parsing comes from DASH-IF-IOP but no idea about the source of the RPU header and CM_Data() modifications, anyway it is enough for implementing the feature.

Awesome I'm glad to hear it!

quietvoid commented 2 years ago

See also https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/fe0403373964f6a5e633eb7adf9aa104cf9d59ff. It all comes from a patent, not DASH-IF's specification which refers to Dolby Vision within ITU-T.35 SEI messages.

JeromeMartinez commented 2 years ago

It all comes from a patent

I missed it :). Great.

not DASH-IF's specification which refers to Dolby Vision within ITU-T.35 SEI messages.

I was mentioning it only because there are similar field names (but not positioned at the same place), I guess that some parts are common. BTW, if someone has files with Dolby Vision within ITU-T.35 SEI messages, I am interested.

quietvoid commented 2 years ago

I was mentioning it only because there are similar field names (but not positioned at the same place), I guess that some parts are common. BTW, if someone has files with Dolby Vision within ITU-T.35 SEI messages, I am interested.

The only source I've found for those is here https://dash.akamaized.net/dash264/TestCasesMCA/dolby/6. The EL file contains the SEI.

JeromeMartinez commented 2 years ago

The only source I've found for those is here

Thanks!

JeromeMartinez commented 2 years ago

For reference, the DOVI RPU patent.

medikoo commented 2 years ago

I believe the same issue applies to the detection of Dolby Vision in .m2ts files as found on 4K UHD discs. Mediainfo doesn't see it, while MakeMKV reports it