[FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR metadata when encoding

FFmpeg trac at avcodec.org
Sat Jan 18 12:53:29 EET 2020

#7037: ffmpeg destroys HDR metadata 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):

 Replying to [comment:59 mario66]:
 > Replying to [comment:56 delirio]:
 > > They either aren't using ffmpeg at all or just avoid it for 4K HDR
 releases because of missing support.
 > ffmpeg is going to die out, all your hard work you "donated" to this
 project will have no

 Nobody is using x265 directly. It is possible of course, but ffmpeg is
 using x265 and YOU CAN pass arguments to it (-x265-params). Listen: ffmpeg
 is a library, it means that you need to use something like mkvmerge, which
 IS USED by rarbg... Something like:

  ./src/mkvmerge \
       -o output.mkv\
       --colour-matrix 0:9 \
       --colour-range 0:1 \
       --colour-transfer-characteristics 0:16 \
       --colour-primaries 0:9 \
       --max-content-light 0:1000 \
       --max-frame-light 0:300 \
       --max-luminance 0:1000 \
       --min-luminance 0:0.01 \
       --chromaticity-coordinates 0:0.68,0.32,0.265,0.690,0.15,0.06 \
       --white-colour-coordinates 0:0.3127,0.3290 \

 It is really simple.

 So, I will update you. Very soon Google will give us updated HDR10+
 patches, they are already fully ready (they are using it in Youtube and
 Google Films, but GPL 3, ha-ha, so will have to give it to us). And then I
 think we will copy rigaya implementation of metadata or mkvmerge...
 Can you please update that post
 https://forum.doom9.org/showthread.php?p=1886901#post1886901 saying that
 issue was fixed https://trac.ffmpeg.org/ticket/8228? I am not registered

Ticket URL: <https://trac.ffmpeg.org/ticket/7037#comment:60>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list