[FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding
FFmpeg
trac at avcodec.org
Mon Dec 16 20:36:20 EET 2019
#7037: ffmpeg destroys HDR information when encoding
-------------------------------------+-----------------------------------
Reporter: mario66 | Owner: cehoyos
Type: enhancement | Status: open
Priority: normal | Component: avcodec
Version: git-master | Resolution:
Keywords: libx265 hdr | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-----------------------------------
Comment (by Balling):
Dolby Vision encoding is already supported, what is not supported in h.265
is dual layer (when you have two video steam (one in 4k, the other in full
hd) inside container, see dolby demo blu-ray disks on torrents) and
decoding it (both dual layer and NAL values and EVEN THE ICTCP COLOR,
goddammit, aka Bt.2100).
Codec for HDR10+ is supported (decoding are in patches on patchwork only
and you need to activate it in h.265).
I will point out ;) that ffmpeg should insert metadata in sync with h.265
parameters and color managment filters and nvenc coder. That work need to
be done and there are many crazy things about it. Again read this
https://github.com/sekrit-twc/zimg/issues/117
You must understand that mastering primeries should be applied when you
are mastering the file, not trancoding it. Players should not use that
data, they should use data inside container (again inside metadata which
then is tranfered in SAI of HDMI). If they are not doing that is their
problem. Again this is a library! This changes will broke API! And if we
will do it in a hurry it will broke it more than once, which is
unacceptable. Again as you said there are script that can insert metadata.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/7037#comment:43>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list