summaryrefslogtreecommitdiffstats
path: root/doc/faq.texi
diff options
context:
space:
mode:
authorNicolas George <nicolas.george@normalesup.org>2012-11-02 15:50:23 +0100
committerNicolas George <nicolas.george@normalesup.org>2012-11-03 17:03:13 +0100
commit8cf6377ac1cff3f1d851b5eeb0ecb6b543af5469 (patch)
treee85abc0c9bd5a23e93b45b4745c430de91074b21 /doc/faq.texi
parent94f224516cec88aada7c6ae31edb499b3c34a797 (diff)
downloadffmpeg-streaming-8cf6377ac1cff3f1d851b5eeb0ecb6b543af5469.zip
ffmpeg-streaming-8cf6377ac1cff3f1d851b5eeb0ecb6b543af5469.tar.gz
doc/faq: explain why -sameq is gone.
Diffstat (limited to 'doc/faq.texi')
-rw-r--r--doc/faq.texi14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/faq.texi b/doc/faq.texi
index 1158091..7be3fc6 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -385,6 +385,20 @@ The size of the initial scan is controlled by two options: @code{probesize}
(default ~5 Mo) and @code{analyzeduration} (default 5,000,000 µs = 5 s). For
the subtitle stream to be detected, both values must be large enough.
+@section Where did the @option{-sameq} option go?
+
+The @option{-sameq} option meant "same quantizer", and made sense only in a
+very limited set of cases. Unfortunately, a lot of people mistook it for
+"same quality" and used it in places where it did not make sense: it had
+roughly the expected visible effect, but achieved it in a very inefficient
+way.
+
+Each encoder has its own set of options to set the quality-vs-size balance,
+use the options for the encoder you are using to set the quality level to a
+point acceptable for your tastes. The most common options to do that are
+@option{-qscale} and @option{-qmax}, but you should peruse the documentation
+of the encoder you chose.
+
@chapter Development
@section Are there examples illustrating how to use the FFmpeg libraries, particularly libavcodec and libavformat?
OpenPOWER on IntegriCloud