[FFmpeg-devel] [PATCH]lavf/isom: Recognize fourcc HEVC

Michael Niedermayer michael at niedermayer.cc
Thu May 3 22:31:06 EEST 2018


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 <jamrial at gmail.com>:
> >> 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
This should not be surprising as avi is intended to be and is a
generic container format. 

Thanks

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Avoid a single point of failure, be that a person or equipment.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20180503/7e5a357a/attachment.sig>


More information about the ffmpeg-devel mailing list