[FFmpeg-devel] [PATCH] doc/filters: document the unstability of the shorthand options notation.

John Warburton john at johnwarburton.net
Mon Aug 7 20:41:45 EEST 2017

On Mon, Aug 7, 2017 at 10:03 AM, Nicolas George <george at nsup.org> wrote:
>> >Lets take a step back and look at this
>> >
>> >There are some rarely used options in multi input filters like
>> >overlay which break.
>> >Noone even noticed except me

> Now, to all that stated a negative opinion about this:
> I have in the queue a patch series that changes the options in a minor
> way, but at the same time fixes bugs and long-standing limitations of
> lavfi and makes the code more robust and cleaner.
> Do you :
> 1. propose to implement and test compatibility options yourself?
> 2. own up you are blocking these enhancements?
> 3. accept the series and the breakage?

I am not a developer (though am learning to read the source code) but
if an old FFmpeg script of mine breaks, as they have on a couple of
occasions, isn't it logical for a user of the command line to go
straight to the documentation, and the answer (and the fix) always
seems to be there? Or just type "ffmpeg -h filter=scale" or similar,
where the order of un-named options isn't even mentioned? In my
experience today, much more so than in the olden days when we used to
type "C> wp.exe mydoc.wpd", CLI users aren't afraid of documentation
and development.


More information about the ffmpeg-devel mailing list