The guess work comes from this list: https://developer.apple.com/library/content/technotes/tn2162/_index.html#//apple_ref/doc/uid/DTS40013070-CH1-TNTAG10-SAMPLE__COLR__SETTINGS
and I agree is the source of a lot of chaos, but it is what several tools have done in the absence of any specified values. My usage of the feature is to write the atom when I need to by explicitly enabling it on the command line and I also explicitly set the metadata either from the input file, or by overriding on the command line. Kevin On Mon, Nov 20, 2017 at 4:52 PM, Derek Buitenhuis <derek.buitenh...@gmail.com> wrote: > On 11/20/2017 4:45 PM, Dave Rice wrote: >> What do you propose as the default for guessed_hacky_crap? Also are there >> supporters for the need of a guessed_hacky_crap optio? Is there precedence >> in ffmpeg to enable/disable guesswork via a user option? > > I personally would never use the guesswork stuff, since I think it is a > terrible idea, so can't really propose a default or support it. > > The guesswork stuff was added at the same time as colr support, by Michael, > in 7b6f4191763a5ffde02fa198101aabc3ddb5bf61, so maybe he has some opinion. > > - Derek > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
