On Fri, 9 Dec 2011 03:39:25 +0100, Luca Barbato <[email protected]> wrote:
> Remove stale questions and try to make it less offensive.
> ---
> doc/faq.texi | 359
> +++++++---------------------------------------------------
> 1 files changed, 39 insertions(+), 320 deletions(-)
>
> diff --git a/doc/faq.texi b/doc/faq.texi
> index affe88b..3379725 100644
> --- a/doc/faq.texi
> +++ b/doc/faq.texi
> @@ -11,65 +11,11 @@
>
> @chapter General Questions
>
> -@section When will the next Libav version be released? / Why are Libav
> releases so few and far between?
> -
> -Like most open source projects Libav suffers from a certain lack of
> -manpower. For this reason the developers have to prioritize the work
> -they do and putting out releases is not at the top of the list, fixing
> -bugs and reviewing patches takes precedence. Please don't complain or
> -request more timely and/or frequent releases unless you are willing to
> -help out creating them.
> -
> -@section I have a problem with an old version of Libav; where should I
> report it?
> -Nowhere. We do not support old Libav versions in any way, we simply lack
> -the time, motivation and manpower to do so. If you have a problem with an
> -old version of Libav, upgrade to the latest git snapshot. If you
> -still experience the problem, then you can report it according to our
> -@uref{http://libav.org/bugreports.html, bug reporting guidelines}.
> -
> -@section Why doesn't Libav support feature [xyz]?
> -
> -Because no one has taken on that task yet. Libav development is
> -driven by the tasks that are important to the individual developers.
> -If there is a feature that is important to you, the best way to get
> -it implemented is to undertake the task yourself or sponsor a developer.
> -
> -@section Libav does not support codec XXX. Can you include a Windows DLL
> loader to support it?
> -
> -No. Windows DLLs are not portable, bloated and often slow.
> -Moreover Libav strives to support all codecs natively.
> -A DLL loader is not conducive to that goal.
> -
> -@section My bug report/mail to libav-devel/user has not received any replies.
> -
> -Likely reasons
> -@itemize
> -@item We are busy and haven't had time yet to read your report or
> -investigate the issue.
> -@item You did not follow our
> - @uref{http://libav.org/bugreports.html, bug reporting guidelines}.
> -@item You didn't use git master.
> -@item You reported a segmentation fault without gdb output.
> -@item You describe a problem but not how to reproduce it.
> -@item It's unclear if you use ffmpeg as command line tool or use
> -libav* from another application.
> -@item You speak about a video having problems on playback but
> -not what you use to play it.
> -@item We have no faint clue what you are talking about besides
> -that it is related to Libav.
> -@end itemize
> -
> -@section Is there a forum for Libav? I do not like mailing lists.
> -
> -You may view our mailing lists with a more forum-alike look here:
> -@url{http://dir.gmane.org/gmane.comp.video.ffmpeg.user},
> -but, if you post, please remember that our mailing list rules still apply
> there.
> -
> -@section I cannot read this file although this format seems to be supported
> by ffmpeg.
> -
> -Even if ffmpeg can read the container format, it may not support all its
> -codecs. Please consult the supported codec list in the ffmpeg
> -documentation.
> +@section I cannot read this file although this format seems to be supported
> by avconv.
> +
> +Even if avconv can read the container format, it may not support all its
> +codecs. Use @command{avconv -codecs} to have a list of the codecs supported
> +in your specific build.
>
> @section Which codecs are supported by Windows?
>
> @@ -107,155 +53,42 @@ If some MP3 codec like LAME is installed.
> @end table
>
>
> -@chapter Compilation
> -
> -@section @code{error: can't find a register in class 'GENERAL_REGS' while
> reloading 'asm'}
> -
> -This is a bug in gcc. Do not report it to us. Instead, please report it to
> -the gcc developers. Note that we will not add workarounds for gcc bugs.
> -
> -Also note that (some of) the gcc developers believe this is not a bug or
> -not a bug they should fix:
> -@url{http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203}.
> -Then again, some of them do not know the difference between an undecidable
> -problem and an NP-hard problem...
> -
> @chapter Usage
>
> -@section ffmpeg does not work; what is wrong?
> +@section avconv does not work; what is wrong?
>
> -Try a @code{make distclean} in the ffmpeg source directory before the build.
> +Try a @code{make distclean} in the avconv source directory before the build.
This question looks weird. "does not work"?
> If this does not help see our
> -@uref{http://libav.org/bugreports.html, bug reporting guidelines}.
> -
> -@section How do I encode single pictures into movies?
> -
> -First, rename your pictures to follow a numerical sequence.
> -For example, img1.jpg, img2.jpg, img3.jpg,...
> -Then you may run:
> -
> -@example
> - ffmpeg -f image2 -i img%d.jpg /tmp/a.mpg
> -@end example
> +@url{http://libav.org/bugreports.html, bug reporting guidelines}.
>
> -Notice that @samp{%d} is replaced by the image number.
> -
> -@file{img%03d.jpg} means the sequence @file{img001.jpg}, @file{img002.jpg},
> etc...
> -
> -If you have large number of pictures to rename, you can use the
> -following command to ease the burden. The command, using the bourne
> -shell syntax, symbolically links all files in the current directory
> -that match @code{*jpg} to the @file{/tmp} directory in the sequence of
> -@file{img001.jpg}, @file{img002.jpg} and so on.
> -
> -@example
> - x=1; for i in *jpg; do counter=$(printf %03d $x); ln -s "$i"
> /tmp/img"$counter".jpg; x=$(($x+1)); done
> -@end example
> -
> -If you want to sequence them by oldest modified first, substitute
> -@code{$(ls -r -t *jpg)} in place of @code{*jpg}.
> -
> -Then run:
> -
> -@example
> - ffmpeg -f image2 -i /tmp/img%03d.jpg /tmp/a.mpg
> -@end example
> +@section Why do I see a slight quality degradation with multithreaded
> +slice encoding?
>
> -The same logic is used for any image format that ffmpeg reads.
> -
> -@section How do I encode movie to single pictures?
> -
> -Use:
> -
> -@example
> - ffmpeg -i movie.mpg movie%d.jpg
> -@end example
> -
> -The @file{movie.mpg} used as input will be converted to
> -@file{movie1.jpg}, @file{movie2.jpg}, etc...
> -
> -Instead of relying on file format self-recognition, you may also use
> -@table @option
> -@item -vcodec ppm
> -@item -vcodec png
> -@item -vcodec mjpeg
> -@end table
> -to force the encoding.
> -
> -Applying that to the previous example:
> -@example
> - ffmpeg -i movie.mpg -f image2 -vcodec mjpeg menu%d.jpg
> -@end example
> -
> -Beware that there is no "jpeg" codec. Use "mjpeg" instead.
> -
> -@section Why do I see a slight quality degradation with multithreaded MPEG*
> encoding?
> -
> -For multithreaded MPEG* encoding, the encoded slices must be independent,
> -otherwise thread n would practically have to wait for n-1 to finish, so it's
> -quite logical that there is a small reduction of quality. This is not a bug.
> +For multithreaded slice encoding, the encoded slices must be independent,
> +otherwise thread n would practically have to wait for n-1 to finish, so it
> +is expected that there is a small reduction of quality.
> +If you do not have latency concern you should switch to frame multithreaded
> +encoding.
Do any of our encoders honor thread_type?
--
Anton Khirnov
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
