summaryrefslogtreecommitdiff
path: root/doc/rate_distortion.txt
diff options
context:
space:
mode:
authorMichael Niedermayer <michaelni@gmx.at>2009-03-30 10:39:20 +0000
committerMichael Niedermayer <michaelni@gmx.at>2009-03-30 10:39:20 +0000
commit52760ed76e32af032f7640a9886631d889ad1511 (patch)
tree786a5bbafaad2547a6cabfff05b3357b449a54f2 /doc/rate_distortion.txt
parent767e14c3807b6e8d0a47459a1ffceb1665dad251 (diff)
downloadffmpeg-52760ed76e32af032f7640a9886631d889ad1511.tar.gz
The definition of rate and distortion is not conditional of lambda being
fixed (at least the current text sounded odd to me). Originally committed as revision 18244 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/rate_distortion.txt')
-rw-r--r--doc/rate_distortion.txt6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/rate_distortion.txt b/doc/rate_distortion.txt
index 5f19b0d2ea..a7d2c878b2 100644
--- a/doc/rate_distortion.txt
+++ b/doc/rate_distortion.txt
@@ -21,8 +21,10 @@ Let's consider the problem of minimizing:
distortion + lambda*rate
-For a fixed lambda, rate would represent the filesize, while distortion is
-the quality. Is this equivalent to finding the best quality for a given max
+rate is the filesize
+distortion is the quality
+lambda is a fixed value choosen as a tradeoff between quality and filesize
+Is this equivalent to finding the best quality for a given max
filesize? The answer is yes. For each filesize limit there is some lambda
factor for which minimizing above will get you the best quality (using your
chosen quality measurement) at the desired (or lower) filesize.