[FFmpeg-user] FFmpeg problem in Mac

Tom Evans tevans.uk at googlemail.com
Fri Jun 14 15:33:21 CEST 2013

On Fri, Jun 14, 2013 at 1:17 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
> Am 14.06.2013 14:13, schrieb Tom Evans:
>> On Fri, Jun 14, 2013 at 12:14 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
>>> and no - the *ffmpeg only* attitude "take a snapshot" is not
>>> really acceptabl for a enduser and after man yeasr of business
>>> i stll did not see any other software / projtec with it
>> What would be the purpose of a release, apart from to have users
>> running code with bugs that have already been fixed.
> other software using the ffmpeg-libraries is tested against it as example?
>> There are several repositories providing up to date builds of ffmpeg,
>> is it really too much to ask users to use the fixed version rather
>> than the buggy version?
> ah in the snapshot are for sure no bugs at all?
> how comes that i here this since years and there are still bugs?

Because new features keep getting added.

> how comes that usually in software-development bugs are introduced
> due development which means in the current HEAD and finally it is
> lottery which of the bugs are affecting you
> * the old ones which are fixed in the HEAD by using a release
> * the new ones from HEAD which are not in the latest release version

Sorry, you are wrong. Most of the changes to ffmpeg are either
explicitly to fix bugs, or to add new features. Bugs can be introduced
by any changes, but are most likely to be introduced by new features,
not by fixing bugs.

Users affected by bugs are not using new features since they do not
exist in their (old) version of ffmpeg, and therefore bugs introduced
by new features are not relevant. If they are affected by a bug, their
best chance of success is to use the very latest version.

This shows that it is absolutely in the best interest of users to use
the most recent version of ffmpeg they can.

However, this is not actually the most important reason to insist
users use the most recent versions. The most important is that without
it, developers and people offering support must first rule out that
the bug has not already been fixed. It's not about the users at all,
really. The support "contract" for ffmpeg says "If you want free
support, you've got to first rule out the obvious case that we've
already fixed this bug".

Not particularly hard is it?

> and with this two points you should realize that the discussion is
> bullshit

Well, you should realise the discussion is bullshit, because neither
your nor my opinion is even remotely relevant. The status quo is not
going to change.



More information about the ffmpeg-user mailing list