[MPlayer-dev-eng] DivX4/DivX5 codecs documentation

[Diego Biurrun]

Arpi writes:
 > 
 > now:
 > there is opendivx 0.48 and divx4linux, their interface is very (90%) similar.
 > they are very similar. they are conflicting because of still using the same
 > function name (encore() and decore()) so cannot be linked to the same
 > program at the same time. so, mplayer can have either opendivx or divx4linux
 > (or xvid, which is the continued development of opendivx cvs) not both.
 > 
 > now. mplayer supports both interfaces, the old opendivx-compatible one (-vc
 > odivx) and the new oen introduced by divx4linux (-vc divx4).
 > but, as divx4linux supports both interfaces, it works wiht both -vc odivx
 > and -vc divx4, but different way. odivx: yv12 exporting, divx4: yuy2/rgb
 > directrendering.

OK, second try, how about this:

  DivX4Linux conflicts with the old OpenDivX because their APIs are similar but 
  incompatible. Therefore you can only have one of them compiled into MPlayer
  at a time.

  DivX4LInux offers an OpenDivX compatibility mode such that you may choose from
  the following options when using this codec:

  -vc odivx     Uses the codec in OpenDivX fashion. In this case it
                produces YV12 images in its own buffer, and MPlayer
                does colorspace conversion via libvo. (RECOMMENDED!)

  -vc divx4     Uses the codec's own colorspace conversion. In this
                mode you can use YUY2/UYVY, too. 


 > i doubt you understand now, but i tried to explain :)

Hopefully I am inching closer to the right solution..


Diego