[FFmpeg-devel] [PATCH 1/2] lavf/avio: Extend API with avio_move() and avio_delete()

Mariusz Szczepańczyk mszczepanczyk at gmail.com
Tue Jun 23 00:58:19 CEST 2015

On Mon, Jun 22, 2015 at 11:31 PM, Derek Buitenhuis <
derek.buitenhuis at gmail.com> wrote:

> On 6/22/2015 9:15 PM, Mariusz Szczepańczyk wrote:
> > Thank you for clarification. I understand there are people who are not
> > happy with additions like this. However, there are also people who think
> > these changes are needed and trying to stop them just because "we don't
> > want this here" or worse, making fun of their work is not the way to go
> > to be honest.
> Considering whether a feature should be in a particular library by design
> is a legitimate consideration. You can't just blindly accept all features
> someone might find useful. Some may also think a GUI toolkit and X protocol
> implementation would be awesome to have in libav*, but does it belong? No.
> May I add, that I do not think pushing through APIs and and design choices
> that have registered dissent is kinda of sketchy at best. That is not on
> you though, and I apologize for dragging your GSOC application into it.
> (Also I'm not making fun of your work. If you point out where I've done
> that, I'd be glad to retract and apologize.)
No offence taken. Actually this remark wasn't directed at you any way, just
an observation of what's going on in this thread (and some other).

> > I don't really know how/when this conflict started or have your
> > complaints been answered or not but it seems to me there are some of you
> > who are really frustrated with the direction ffmpeg have taken.
> Yes, it predates your GSOC task, and involves your mentor. Again, apologies
> for it being dumped on you in this thread.
> > So why don't you propose something constructive, e.g. partition into
> > distinct libraries so muxing/demuxing code is not getting "spoiled"?
> > There must be some kind of solution everyone can agree with.
> We did. We proposed it is *not* the task of libav* to do this. It belongs
> in
> the layer above, in the application (e.g. a player). And indeed, this is
> what VLC and mplayer/mpv already do. Your mentor is the only one who
> decided it belongs here, because he wanted to use it.
I don't think it's fair to say Lukasz is the only one standing for these
changes. But let's not make it personal and hold on any grudges for a

My point is that ongoing fights like this are counterproductive and only
discourage people from contributing into open source. I also think everyone
wants the best for the project regardless they are pro or against the

I see the current situation is as follows: there is increasing amount of
code in libav* that you and some others find out of place. This is
obviously not good.

Is there any viable solution not involving removing functionality from
ffmpeg would you agree on and make adding changes like this less painful?
What do you think about making a temporary fork, moving things around there
and showing something that is satisfactory to you?


More information about the ffmpeg-devel mailing list