On 10/12/11 01:13, Diego Biurrun wrote:
On Fri, Dec 09, 2011 at 03:39:25AM +0100, Luca Barbato wrote:
Remove stale questions and try to make it less offensive.
---
doc/faq.texi | 359 +++++++---------------------------------------------------
1 files changed, 39 insertions(+), 320 deletions(-)
Good idea. I would suggest to push it in parts so that the size of
the patch shrinks quickly.
Ok let me try to refresh the patch with just the removals.
--- 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}.
OK
-@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.
This could be amended.
-@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.
This is not something I would remove.
-@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.
OK
-@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.
to see a list of the codecs
@@ -107,155 +53,42 @@ If some MP3 codec like LAME is installed.
-@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...
I'd leave this, the error keeps reappearing.
-@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.
If this does not help see our
-@uref{http://libav.org/bugreports.html, bug reporting guidelines}.
+@url{http://libav.org/bugreports.html, bug reporting guidelines}.
OK
-@section How do I encode single pictures into movies?
-
-@section How do I encode movie to single pictures?
I'm under the impression that these are still FAQs...
The man page and the other documentation explain how to do that already.
-@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.
+@section Why do I see a slight quality degradation with multithreaded
+slice encoding?
+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.
OK
-@section -f jpeg doesn't work.
-
-Try '-f image2 test%d.jpg'.
-
@section Why can I not change the framerate?
Some codecs, like MPEG-1/2, only allow a small number of fixed framerates.
-Choose a different codec with the -vcodec command line option.
+Choose a different codec with the -c:v command line option.
-@section How do I encode Xvid or DivX video with ffmpeg?
+@section How do I encode Xvid or DivX video with avconv?
Both Xvid and DivX (version 4+) are implementations of the ISO MPEG-4
standard (note that there are many other coding formats that use this
-same standard). Thus, use '-vcodec mpeg4' to encode in these formats. The
+same standard). Thus, use '-c:v mpeg4' to encode in these formats. The
default fourcc stored in an MPEG-4-coded file will be 'FMP4'. If you want
-a different fourcc, use the '-vtag' option. E.g., '-vtag xvid' will
+a different fourcc, use the '-tag:v' option. E.g., '-tag:v xvid' will
force the fourcc 'xvid' to be stored as the video fourcc rather than the
default.
OK
-@section How do I encode videos which play on the iPod?
-
-@section How do I encode videos which play on the PSP?
No longer FAQs?
Those are completely outdated, the new firmware supports something quite
different.
--
Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
