[FFmpeg-devel] [PATCH]lavf/isom: Recognize fourcc HEVC
Carl Eugen Hoyos
ceffmpeg at gmail.com
Wed May 2 22:47:00 EEST 2018
2018-05-02 21:26 GMT+02:00, James Almer <jamrial at gmail.com>:
> 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.
How does this help?
We know that several applications write such files and they didn't
stop it when we asked last time?
Much more important: We try not to write invalid files, what is
suddenly bad about trying to support everything out there?
We support quite a few formats that are most likely less
common than hevc-in-avi and this was a very successful
Why suddenly tell users to fuck themselves? Why does
this make sense?
> Alternatively, actually start using avfmtctx->strict_std_compliance on
> demuxers and refuse to handle these files unless it's set as unofficial
> or lower, but i predict a lot of people will come out of the woodworks
> complaining about their broken samples suddenly not working anymore
> because ffmpeg started to honor its own standard compliance settings.
Sounds completely unacceptable to me.
>>> Why the hell is the avi demuxer even looking at mov tags to begin with?
>> Because every other software except FFmpeg writes such files.
> I doubt we're the only ones that try to not write non standard files...
Do you know immediately of another (general-usage!) tool?
More information about the ffmpeg-devel