From ca0c2746ca701873575e2f1ed8012cebb479f658 Mon Sep 17 00:00:00 2001 From: gpoirier Date: Sat, 20 Aug 2005 20:13:03 +0000 Subject: Encoding setting examples for x264 git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@16278 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/encoding-guide.xml | 44 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) (limited to 'DOCS/xml/en/encoding-guide.xml') diff --git a/DOCS/xml/en/encoding-guide.xml b/DOCS/xml/en/encoding-guide.xml index ac85040b2b..010df15e78 100644 --- a/DOCS/xml/en/encoding-guide.xml +++ b/DOCS/xml/en/encoding-guide.xml @@ -3201,6 +3201,50 @@ codec + + +Encoding settings examples + + + The following settings are examples of different encoding + options combinations that affect the speed VS quality tradeoff + given the same target bitrate. + + If you are aiming at perfect quality without too much thinking and + no size limitation, a low constant quantizer encode (like with + ) with no B-frames + () will probably look very good, but + will needlessly spend lots of bits to encode details that could be + coded more wisely using some advanced settings. + + + + All the encoding settings were tested on a 720x448 @30000/1001 fps + video sample, the target bitrate was 900kbps, and the machine was an + AMD-64 3400+ at 2400 Mhz in 64 bits mode. + Each encoding setting is followed by the encoding speed (in frames + per seconds), the compression efficiency loss (in percent of bitrate) + compared to the "very high quality" setting, and the PSNR loss (in dB). + Please understand that depending on your source your machine type + and the development breakthrough, you may get very different results. + + + +Very high quality: + +6fps, 0%, 0dB. + +High quality: + +13fps, -13%, -0.89dB. + +Fast: + +17fps, -20%, -1.48dB. + + + + -- cgit v1.2.3