From 82cd4227ff58b923cebf643748dbf96e3699e99b Mon Sep 17 00:00:00 2001 From: michael Date: Sat, 1 Jun 2002 02:58:55 +0000 Subject: [PATCH] forgot vpsize git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@6258 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/tech/libavc-options.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/DOCS/tech/libavc-options.txt b/DOCS/tech/libavc-options.txt index 7d6c1ea19e..ba26e11895 100644 --- a/DOCS/tech/libavc-options.txt +++ b/DOCS/tech/libavc-options.txt @@ -102,9 +102,14 @@ vstrict strict standart compliance only recomanded if u want to feed the output into the mpeg4 reference decoder vdpart data partitioning - +2 byte per video packet, and much better looking if the file becomes damaged + +2 byte per video packet + improves resistance against damages after encoding + +vpsize (0-10000) video packet size + 0 disabled (default) + 500-1000 good choice + improves resistance against damages after encoding - lavdopts: (decoder options) ver error resilience -1 needed for some very broken, encoders which completly ignore the standarts @@ -124,6 +129,8 @@ FAQ: Q: the file is much too small A: vqmin=2 or 1 (be carefull with 1, it could cause strange things to happen) Q: i want to use -pass 1 & -pass 2 with vmax_b_frames>0 A: read DOCS/tech/patches.txt and send a patch ;) + Q: which provides better error recovery per filesize increase data partitioning or video packets? + A: data partitioning glossary: MB Macroblock (16x16 luminance & 8x8 chrominance samples)