On 5/3/2018 4:31 PM, Michael Niedermayer wrote: > Hi > > On Wed, May 02, 2018 at 04:26:07PM -0300, James Almer wrote: >> On 5/2/2018 3:59 PM, Carl Eugen Hoyos wrote: >>> 2018-05-02 20:52 GMT+02:00, James Almer <[email protected]>: >>>> On 5/2/2018 3:44 PM, Carl Eugen Hoyos wrote: >>> >>>>> Attached patch fixes ticket #7110 for me. >>>> >>>> hevc in AVI is not a thing, and adding a non official fourcc to >>>> ff_codec_movvideo_tags to support weird files created by >>>> faulty software that are not even mov/mp4 is not a good idea. >>> >>> So what do you suggest? >>> Not supporting files that are written by common software? >> >> Asking the source of these files (VirtualDub) to stop creating them is >> one option. Otherwise we'll be adding a similar tag to support h266 in >> avi five years from now because people refuse to do things right. > > And what would be the argument why a codec be that h265 or h266 should > not be stored in a generic container (avi in this case) ? > > Heres the official register: > https://www.iana.org/assignments/wave-avi-codec-registry/wave-avi-codec-registry.xml > > there are matches for both h265 and h266
There are none for HEVC, which is what this patch is adding (and in the wrong place). > This should not be surprising as avi is intended to be and is a > generic container format. > > Thanks > > [...] > > > > _______________________________________________ > ffmpeg-devel mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
