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

[FFmpeg]

#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 delirio):

 Replying to [comment:67 Balling]:
 > Replying to [comment:66 mario66]:
 > > Replying to [comment:65 gdgsdg123]:
 > > > With this command I suspect you'd already messed with the
 [http://trac.ffmpeg.org/wiki/colorspace colorspace] (color management
 data) quite a lot...
 > >
 > > Thanks, I never thought about this.
 > >
 > > > Anyway from your command parameter choosing I can see that you don't
 care much about quality... that's why many broken things become
 "worksforme".
 > >
 > > I regularly do ABX tests
 > You mean SSIM tests? https://en.wikipedia.org/wiki/Structural_similarity
 >
 > > I just want to be able to execute this right.
 > All my life I have never payed for ANY digital content. Music, video,
 apps. That is what I call cool. I saved for 2080 Ti))
 >
 >
 > > Should every user of ffmpeg do a "Bachelor of Color Management"
 > Yes. At least with HDR. Or just use scripts. Or use mkvmerge.
 >
 > Okay, I will open issue on x265 myself.
 https://bitbucket.org/multicoreware/x265/issues/533/hdr10-metadata-copy-
 by-default-if-no-icc


 Thank you for opening a ticket there. This ticket is indeed going in the
 right direction and I am pretty confident we will have this so desired
 functionality ffmpeg working soon.

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