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

FFmpeg trac at avcodec.org
Sat Jan 18 15:26:40 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 mario66):

 Part of the success of ffmpeg is that if you leave out options it will
 choose the most reasonable default value for that. Imagine every single
 command line option here: https://ffmpeg.org/ffmpeg.html#Options
 would have unintuitive / surprising default values and to get a simple
 video converted, every single one of those options needed to be set to a
 reasonable value.
 No one would use ffmpeg. Ever.
 I understand that you are an expert and you do not rely on default values
 anyway, but this is the exception.

 For example in my case (for SDR videos), I used to just call:
 ffmpeg -i in.mkv -map 0:v -map 0:a? -map 0:s? -c:v libx265 -crf 18 -c:a
 copy -c:s copy out.mkv
 and I was happy with the result all the time... until HDR came along.

 Copying HDR10 metadata could be done in ffmpeg as a simple post processing
 step, independent of the video codec. Only for HDR10+ or Dolby Vision you
 need support from the codec. And there your are right, the x265 guys need
 to submit patches for this.

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

More information about the FFmpeg-trac mailing list