Hi, On Tue, Jun 21, 2011 at 6:59 AM, Anton Khirnov <[email protected]> wrote: > > On Tue, 21 Jun 2011 11:31:55 +0200, Diego Biurrun <[email protected]> wrote: >> On Tue, Jun 21, 2011 at 08:44:39AM +0200, Anton Khirnov wrote: >> > They were replaced by (de)muxer private options. >> > --- >> > doc/ffmpeg.texi | 6 ------ >> > ffmpeg.c | 7 ------- >> > 2 files changed, 0 insertions(+), 13 deletions(-) >> > --- a/doc/ffmpeg.texi >> > +++ b/doc/ffmpeg.texi >> > @@ -728,12 +728,6 @@ Only use bit exact algorithms (for codec testing). >> > @item -re >> > Read input at native frame rate. Mainly used to simulate a grab device. >> > -@item -loop_input >> > -Loop over the input stream. Currently it works only for image >> > -streams. This option is used for automatic FFserver testing. >> > -@item -loop_output @var{number_of_times} >> > -Repeatedly loop output for formats that support looping such as animated >> > GIF >> > -(0 will loop the output infinitely). >> >> Now the options are undocumented. This is not good. > > They aren't documented in ffmpeg.texi, yes. But they appear in the help > output.
Didn't we have demuxer and muxer.texi? Also, please keep them around under a compat macro for a while to allow people to move over. Potentially add a printf warning to people to stop using them and advertise the private options. Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
