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

FFmpeg trac at avcodec.org
Mon Dec 16 21:48:10 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:43 Balling]:
 Once again thanks for the technical insides you provide. Indeed, this
 makes everything more complicated. Of course this can be optional, but it
 should be simple switch, not a multi-line very complicated bash script
 only those who studied the subject for several years can understand. (what
 you currently would need, see some post above) A simple switch would be
 But I never said this needs to be rushed. I left this bug alone for one
 ''year'' before I for the first time started to complain about no
 progress. Then after another year I now complain again. Did anyone even
 start to look into this in the last 22 month? It doesn't seem so.
 Feel free to use another year to tackle all the API difficulties. There is
 really no hurry. I'm just worried when progress continues with this speed,
 ffmpeg will not have this implemented in 2050, where it will be obsolete
 and only remembered by the elderly: "once there was a tool free of use and
 very powerful, but the developers failed to do some chore once in a while
 that was necessary to keep the project alive. Learn your lessons", I might
 tell my children and grandchildren, "there is no all fun, no chore
 project. Once in a while you have to do what's necessary to continue with
 the fun parts".

 Replying to [comment:44 Tjoppen]:
 Nope, -map_metadata did not copy the metadata. But this is actually what a
 solution could be. Like in this application:
 Make a simple switch "-export_HDR10 [yes|no]" (like in the application
 above). Problem solved. Make the default "no". Then also Balling will be
 You think that monetary incentive would be a solution. I disagree. People
 have an incentive to use their spare time for something useful, without
 the need to give them money. What an intelligent project leader would do
 is to balance those forces so that at the end everyone feels happy ''and''
 necessary features and bugfixes are implemented. Ever heard of
 "gamification"? You can also give non monetary rewards and incentives.
 Look, I do not want that people feel uncomfortable while coding. It is a
 great thing to have fun while coding. But you can trigger "fun" with
 incentives and rewards if you are an intelligent project leader.

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

More information about the FFmpeg-trac mailing list