comparison DOCS/codecs.html @ 7099:0b70f3dc34eb

Applied patch by Andras Mohari <[e-mail]>, with some small additions. * Replaced <UL> with <OL> where it made sense (to me :-)). * Moved "Developer Cries" into the appendix (as Appendix F) with s/Flame Wars/Developer Cries/ and s/In medias res/Developer Cries/. * Renamed "Appendix X" to "Appendix E". * Put a "Hint" inside <BLOCKQUOTE>. * Converted 3-pass encoding and mga_vid installation instructions to lists. * Converted options tables (video eq, SDL, fbdev, VESA, DXR3, TV input, DivX4Linux, AAlib) to <DL> lists. * The "sections" for MPsub and INSTALLING OSD are numbered and displayed in the TOC now. * Changed the text inside some <H4> tags.

7098:37b0958a1cad

  compile as usual. If it does not detect it, you did not install or configure
  it correctly.</P>

<P>DivX4Linux works in two modes:</P>

<TABLE BORDER=0>
  <TR><TD>&nbsp;&nbsp;</TD><TD VALIGN=top><CODE>-vc&nbsp;odivx</CODE></TD><TD>&nbsp;&nbsp;</TD>
    <TD>Uses the codec in OpenDivX fashion. In this case it
    produces YV12 images in its own buffer, and <B>MPlayer</B> does colorspace
    conversion via libvo. (<B>Fast, recommended!</B>)</TD></TR>
  <TR><TD></TD><TD VALIGN=top><CODE>-vc&nbsp;divx4</CODE></TD><TD></TD>
    <TD>Uses the colorspace conversion of the codec.
    In this mode you can use YUY2/UYVY, too. (<B>SLOW</B>)</TD></TR>
</TABLE>

<P>The <CODE>-vc odivx</CODE> method is usually faster, due to the fact that it
  transfers image data in YV12 (planar YUV 4:2:0) format, thus requiring much
  less bandwidth on the bus. For packed YUV modes (YUY2, UYVY) use the
  <CODE>-vc divx4</CODE> method. For RGB modes the speed is the same, differing

</P>

<P><B>MPlayer</B> is capable of employing the XAnim codecs for decoding. Follow
  the instructions to enable them:</P>

<UL>
  <LI>Download the codecs you wish to use from the
    <A HREF="http://xanim.va.pubnix.com">XAnim site</A>. The <B>3ivx</B> codec
    is not there, but at the <A HREF="http://www.3ivx.com">3ivx site</A>.</LI>
  <LI>Use the <CODE>--with-xanimlibdir</CODE> option to tell configure where
    to find the XAnim codecs. By default, it looks for them at
    <CODE>/usr/local/lib/xanim/mods, /usr/lib/xanim/mods and /usr/lib/xanim</CODE>.
    Alternatively you can set the environment variable <I>XANIM_MOD_DIR</I> to
    the directory of the XAnim codecs.</LI>
  <LI>Rename/symlink the files, cutting out the architecture stuff, so they will
    have filenames like these: <CODE>vid_cvid.xa, vid_h263.xa, vid_iv50.xa</CODE>.</LI>
</UL>

<P>XAnim is video codec family number 10, so you may want to use the <CODE>-vfm 10</CODE>
  option to tell <B>MPlayer</B> to use them if possible.</P>

<P>Tested codecs include: <B>Indeo 3.2</B>, <B>4.1</B>, <B>5.0</B>, <B>CVID</B>,

  <LI>you have to choose between DivX4 <B>OR</B> XViD support at
    compiletime</LI>
  <LI>under development</LI>
</UL>

<H4>Installation:</H4>

<P>It is currently available only from CVS. Here are the
  download and installation instructions:</P>

<OL>
  <LI><CODE>cvs -z3 -d:pserver:[e-mail]:/xvid login</CODE></LI>
  <LI><CODE>cvs -z3 -d:pserver:[e-mail]:/xvid co xvidcore</CODE></LI>

<UL>
  <LI>SVQ3 is still not reverse engineered.</LI>
</UL>

<H4>Installation:</H4>

<P>It's compiled and usable per default.</P>


<H3><A NAME="audio_codecs">2.2.2  Audio codecs</A></H3>

<P>The most important audio codecs above all:<BR></P>

  <LI>we need the GUID of the codec.
</UL>

<P>Take a deep breath and start searching the registry...</P>

<UL>
  <LI>Start <CODE>regedit</CODE>.
  <LI>Press <CODE>Ctrl-f</CODE>, disable the first two checkboxes, and enable
    the third. Type in the fourcc of the codec (e.g. TM20).
  <LI>You should see a field which contains the path and the filename
    (e.g. <CODE>C:\WINDOWS\SYSTEM\TM20DEC.AX</CODE>).

    when Media Player is playing the file, by checking File -> Properties
    -> Advanced.
    If not, you are out of luck. Try guessing (e.g. search for TrueMotion).
  <LI>If the GUID is found you should see a FriendlyName and a CLSID
    field. Write down the 16 byte CLSID, this is the GUID we need.
</UL>

<P><B>Note:</B> If searching fails, try enabling all the checkboxes. You may have
  false hits, but you may get lucky...</P>

<P>Now that you have all the necessary information (fourcc, GUID, codec file,

7099:0b70f3dc34eb

  compile as usual. If it does not detect it, you did not install or configure
  it correctly.</P>

<P>DivX4Linux works in two modes:</P>

<DL>
  <DT><CODE>-vc odivx</CODE></DT>
  <DD>Uses the codec in OpenDivX fashion. In this case it
    produces YV12 images in its own buffer, and <B>MPlayer</B> does colorspace
    conversion via libvo. (<B>Fast, recommended!</B>)</DD>

  <DT><CODE>-vc divx4</CODE></DT>
  <DD>Uses the colorspace conversion of the codec.
    In this mode you can use YUY2/UYVY, too. (<B>SLOW</B>)</DD>
</DL>

<P>The <CODE>-vc odivx</CODE> method is usually faster, due to the fact that it
  transfers image data in YV12 (planar YUV 4:2:0) format, thus requiring much
  less bandwidth on the bus. For packed YUV modes (YUY2, UYVY) use the
  <CODE>-vc divx4</CODE> method. For RGB modes the speed is the same, differing

</P>

<P><B>MPlayer</B> is capable of employing the XAnim codecs for decoding. Follow
  the instructions to enable them:</P>

<OL>
  <LI>Download the codecs you wish to use from the
    <A HREF="http://xanim.va.pubnix.com">XAnim site</A>. The <B>3ivx</B> codec
    is not there, but at the <A HREF="http://www.3ivx.com">3ivx site</A>.</LI>
  <LI>Use the <CODE>--with-xanimlibdir</CODE> option to tell configure where
    to find the XAnim codecs. By default, it looks for them at
    <CODE>/usr/local/lib/xanim/mods, /usr/lib/xanim/mods and /usr/lib/xanim</CODE>.
    Alternatively you can set the environment variable <I>XANIM_MOD_DIR</I> to
    the directory of the XAnim codecs.</LI>
  <LI>Rename/symlink the files, cutting out the architecture stuff, so they will
    have filenames like these: <CODE>vid_cvid.xa, vid_h263.xa, vid_iv50.xa</CODE>.</LI>
</OL>

<P>XAnim is video codec family number 10, so you may want to use the <CODE>-vfm 10</CODE>
  option to tell <B>MPlayer</B> to use them if possible.</P>

<P>Tested codecs include: <B>Indeo 3.2</B>, <B>4.1</B>, <B>5.0</B>, <B>CVID</B>,

  <LI>you have to choose between DivX4 <B>OR</B> XViD support at
    compiletime</LI>
  <LI>under development</LI>
</UL>

<P>XViD is currently available only from CVS. Here are the
  download and installation instructions:</P>

<OL>
  <LI><CODE>cvs -z3 -d:pserver:[e-mail]:/xvid login</CODE></LI>
  <LI><CODE>cvs -z3 -d:pserver:[e-mail]:/xvid co xvidcore</CODE></LI>

<UL>
  <LI>SVQ3 is still not reverse engineered.</LI>
</UL>

<P>The Sorenson decoder is compiled and usable per default.</P>


<H3><A NAME="audio_codecs">2.2.2  Audio codecs</A></H3>

<P>The most important audio codecs above all:<BR></P>

  <LI>we need the GUID of the codec.
</UL>

<P>Take a deep breath and start searching the registry...</P>

<OL>
  <LI>Start <CODE>regedit</CODE>.
  <LI>Press <CODE>Ctrl-f</CODE>, disable the first two checkboxes, and enable
    the third. Type in the fourcc of the codec (e.g. TM20).
  <LI>You should see a field which contains the path and the filename
    (e.g. <CODE>C:\WINDOWS\SYSTEM\TM20DEC.AX</CODE>).

    when Media Player is playing the file, by checking File -> Properties
    -> Advanced.
    If not, you are out of luck. Try guessing (e.g. search for TrueMotion).
  <LI>If the GUID is found you should see a FriendlyName and a CLSID
    field. Write down the 16 byte CLSID, this is the GUID we need.
</OL>

<P><B>Note:</B> If searching fails, try enabling all the checkboxes. You may have
  false hits, but you may get lucky...</P>

<P>Now that you have all the necessary information (fourcc, GUID, codec file,