[FFmpeg-devel] [PATCH]lavf/matroska: Support codec id V_FFV1 for FFV1.

wm4 nfxjfg at googlemail.com
Wed Mar 1 15:45:26 EET 2017


On Wed, 1 Mar 2017 14:26:34 +0100
Michael Niedermayer <michael at niedermayer.cc> wrote:

> On Wed, Mar 01, 2017 at 01:36:26PM +0100, wm4 wrote:
> > On Wed, 1 Mar 2017 13:07:12 +0100
> > Michael Niedermayer <michael at niedermayer.cc> wrote:
> >   
> > > On Wed, Mar 01, 2017 at 09:43:57AM +0100, Carl Eugen Hoyos wrote:  
> > > > 2017-03-01 4:40 GMT+01:00 Michael Niedermayer <michael at niedermayer.cc>:    
> > > > > On Tue, Feb 28, 2017 at 08:45:44PM +0100, Carl Eugen Hoyos wrote:    
> > > > >> Hi!
> > > > >>
> > > > >> Attached patch fixes ticket #6206 here.
> > > > >>
> > > > >> Please comment, Carl Eugen    
> > > > >
> > > > > previous ffmpeg versions dont play these files    
> > > > 
> > > > What do you suggest?    
> > > 
> > > support this at the demuxer side, backport such support then
> > > wait till its supported widely before switching the default in the
> > > muxer  
> > 
> > So if I understand this right:
> > - the patch will change the muxer output to use V_FFV1 instead of using
> >   avi-compat muxing
> > - you demand that we wait with this because older ffmpeg versions would
> >   choke on the new version
> > 
> > So what about all the other muxers that exist in the wild and that will
> > break on this file? Will you fix them too? I think this suggestion of
> > waiting until FFmpeg can eat the new output and only then changing the
> > output is possibly slightly self-centric, and also assumes everyone is
> > going to update their copy of FFmpeg.  
> 
> You seem to be reading things in the mail that it didnt say.

Well, I didn't read the following (what's quoted) into it.

> A reply to "What do you suggest?" is a suggestion not a demand
> and
> The suggestion does not refer to FFmpeg and it was not intended to
> imply to refer to FFmpeg, especially the
> "wait till its supported widely" was intended to refer to all software.

Indeed, backporting support FFmpeg will not help that much.

So we either live with the fact that this change will break tons of
consumers, or we just don't make it.

> Its bad if we generate files by default noone can play back
> I dont know how widespread V_FFV1 support is but i assume its not
> widespread yet at all

Agreed.


More information about the ffmpeg-devel mailing list