[FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding
FFmpeg
trac at avcodec.org
Mon Dec 16 16:45:52 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 mario66):
Replying to [comment:38 Balling]:
HDR metadata does specify brightness. This is what "MaxCLL", "MaxFALL" and
others stand for. See: https://www.mysterybox.us/blog/2016/10/19/hdr-
video-part-3-hdr-video-terms-explained
What you probably mean is that it should not be manipulated by the user,
this is somewhat correct. ''This is why we need the metadata.'' Of course
nowadays the user does not really need to change the brightness on his TV
for HDR content, because it is handled by the metadata! What I wanted to
provide is an explanation how we came into the situation we are currently
in, easy to follow for beginners.
However, that you keep complaining about such minor technical inaccuracies
but fail to see the big picture, that is, ''metadata are essential'', is
somewhat symptomatic for this bug tracker discussion. UHD HDR Blu Ray will
be the new standard. ffmpeg needs to preserve the metadata, otherwise the
content will be corrupted. If ffmpeg cannot deal with such videos which in
the future will be the new baseline, ffmpeg will be obsolete! This is the
big pig picture you and others fail so recognize.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/7037#comment:39>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list