# HG changeset patch
# User arpi
# Date 995586033 0
# Node ID d0d27f5800eaa66675d4c8b2ff7e2c7ace28f9be
# Parent  f32b294e41ad8f7fd1f6c6afa179a3e3372e9654
info about odivx vs. divx4

diff -r f32b294e41ad -r d0d27f5800ea DOCS/DivX4Linux
--- a/DOCS/DivX4Linux	Thu Jul 19 22:49:24 2001 +0000
+++ b/DOCS/DivX4Linux	Thu Jul 19 23:40:33 2001 +0000
@@ -20,8 +20,21 @@
 
 4. Compile mplayer
 
-5. Enjoy it: mplayer -vc divx4 file.avi ...
-   Note: it supports postprocessing, but range of values is strange:
+5. How to enable it?
+ It's a bit tricky. As it conflicts with opendivx (it's API is very
+ similar to opendivx's), opendivx code is disabled, and teh opendivx
+ driver calls this library too.
+ You have 2 choices:
+   -vc odivx : using divx4 codec as a new version of opendivx.
+               in this case it produces YV12 image in its own buffer,
+	       and MPlayer (libvo) does colorspace conversion.
+   -vc divx4 : using divx4 codec's colorspace conversion.
+               in this mode, you can use YUY2/UYVY too.
+ Note: for YV12 (planar YUV 4:2:0) -vc odivx is faster, for packed
+ YUV modes (YUY2, UYVY) use -vc divx4. For RGB modes you can choose,
+ I think their speed is the same. Maybe it depends on current bpp.
+
+ Note: it supports postprocessing too, but range of values is strange:
       0  = no postproc
       10 .. 20 = postproc, normal (like level 2 with divxds)
       30 .. 60 = hard postproc, eats many cpu.  (like level 4 with divxds)