comparison DOCS/video.html @ 7814:988498df1996

<B>MPlayer</B> ---> MPlayer

7813:76940a39405a

	        number of planes: 3
	        type: YUV (planar)
	(...etc...)
  </PRE>
    <P>It must support YUY2 packed, and YV12 planar pixel formats to be
      usable with <B>MPlayer</B>.</P>
  </LI>
  <LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support.
    ./configure prints this.</LI>
</UL>


<H5><A NAME="xv_3dfx">2.3.1.2.1 3dfx cards</A></H5>

    should use, unless you have Rage128 or Radeon) has VSYNC enabled by
    default. It means that decoding speed (!) is synced to the monitor's
    refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or
    set refresh rate to n*(fps of the movie) Hz.</LI>
  <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version
    4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can
    happily get <B>accelerated</B> display, with or without <B>TV output</B>, and
    no libraries or X are needed. Read <A HREF="#vidix">Vidix</A> section.</LI>
</UL>

<H5><A NAME="dga_summary">2.3.1.3.1 Summary</A></H5>

<P>This document tries to explain in some words what DGA is in general and what
  the DGA video output driver for <B>MPlayer</B> can do (and what it
  can't).</P>


<H5><A NAME="dga_whatis">2.3.1.3.2 What is DGA</A></H5>

<P>DGA is short for Direct Graphics Access and is a means for a program to
  bypass the X-Server and directly modifying the framebuffer memory.
  Technically spoken this happens by mapping the framebuffer memory into
  the memory range of your process. This is allowed by the kernel only
  if you have superuser privileges. You can get these either by logging in
  as root or by setting the SUID bit on the <B>MPlayer</B> executable (<B>not
  recommended</B>).</P>

<P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was
  introduced with XFree 4.0.1.</P>

<P>First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>(II) Loading extension XFree86-DGA</CODE></P>

<P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! <B>MPlayer</B>'s DGA
  driver is autodetected on ./configure, or you can force it with
  --enable-dga.</P>

<P>If the driver couldn't switch to a smaller resolution, experiment with
  switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that
  the movie fits in. There is no converter right now :(</P>

<P>Become root. DGA needs root access to be able to write directly to video
  memory. If you want to run it as user, then install <B>MPlayer</B> SUID
  root:</P>

<P><CODE>
  &nbsp;&nbsp;&nbsp;&nbsp;chown root /usr/local/bin/mplayer<BR>
  &nbsp;&nbsp;&nbsp;&nbsp;chmod 750 /usr/local/bin/mplayer<BR>

<BLOCKQUOTE>
  <B>Warning: security risk</B><BR>
  This is a <B>big</B> security risk! <B>Never</B> do this on a server or on
  a computer that can be accessed by other people because they can gain root
  privileges through SUID root <B>MPlayer</B>.
</BLOCKQUOTE>

<P>Now use the <CODE>-vo dga</CODE> option, and there you go (hope so :))!
  You should also try if the <CODE>-vo sdl:dga</CODE> option works for you. It's
  much faster.</P>

<P>See appendix A for some sample modeline definitions.</P>


<H5><A NAME="dga_mplayer">2.3.1.3.5 DGA &amp; MPlayer</A></H5>

<P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to
  make use of it (-vo sdl:dga) and within the DGA driver (-vo dga). The above
  said is true for both; in the following sections I'll explain how the DGA
  driver for <B>MPlayer</B> works.</P>


<H5><A NAME="dga_features">2.3.1.3.6 Features of the DGA driver</A></H5>

<P>The DGA driver is invoked by specifying -vo dga at the command line.

<H5><A NAME="dga_speed">2.3.1.3.7 Speed issues</A></H5>

<P>Generally spoken, DGA framebuffer access should be at least as fast as using
  the X11 driver with the additional benefit of getting a fullscreen image. 
  The percentage speed values printed by <B>MPlayer</B> have to be interpreted
  with some care, as for example, with the X11 driver they do not include the
  time used by the X-Server needed for the actual drawing. Hook a terminal to a
  serial line of your box and start top to see what is really going on in your
  box...</P>

<H5><A NAME="dga_bug_reports">2.3.1.3.B Bug Reports</A></H5>

<P>If you experience troubles with the DGA driver please feel free to file
  a bug report to me (e-mail address below). Please start <B>MPlayer</B> with
  the -v option and include all lines in the bug report that start with
  vo_dga:</P>

<P>Please do also include the version of X11 you are using, the graphics card
  and your CPU type. The X11 driver module (defined in XF86-Config) might

  or audio driver does SDL actually use. For example a Doom port using SDL can
  run on svgalib, aalib, X, fbdev, and others, you only have to specify the
  (for example) video driver to use with the SDL_VIDEODRIVER environment
  variable. Well, in theory.</P>

<P>With <B>MPlayer</B>, we used its X11 driver's software scaler ability for
  cards/drivers that doesn't support XVideo, until we made our own (faster,
  nicer) software scaler. Also we used its aalib output, but now we have ours
  which is more comfortable. Its DGA mode was better than ours, until
  recently. Get it now? :)</P>

<H4><A NAME="svgalib">2.3.1.5 SVGAlib</A></H4>

<H4>Installation</H4>

<P>You'll have to install svgalib and its development package in order for
  <B>MPlayer</B> build its SVGAlib driver (autodetected, but can be forced),
  and don't forget to edit /etc/vga/libvga.config to suit your card &amp;
  monitor.</P>

<H4>Notes</H4>

  scaler, and it's slow. If you really need it, use the <CODE>-sws 4</CODE>
  option which will produce bad quality, but is somewhat faster.</P>

<H4>EGA (4bpp) support</H4>

<P>SVGAlib incorporates EGAlib, and <B>MPlayer</B> has the possibility to
  display any movie in 16 colors, thus usable in the following sets:</P>

<UL>
  <LI>EGA card with EGA monitor: 320x200x4bpp, 640x200x4bpp, 640x350x4bpp</LI>
  <LI>EGA card with CGA monitor: 320x200x4bpp, 640x200x4bpp</LI>

    To turn the cursor back on: <CODE>echo -e '\033[?25h'</CODE>
    or <CODE>setterm -cursor on</CODE></LI>
</UL>

<P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer,
  and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P>


<H4><A NAME="mga_vid">2.3.1.7 Matrox framebuffer (mga_vid)</A></H4>

<P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)

    <P><CODE>alias char-major-178 mga_vid</CODE></P>
    <P>Then copy the <CODE>mga_vid.o</CODE> module to the appropriate place
      under <CODE>/lib/modules/&lt;kernel version&gt;/somewhere</CODE>.</P>
    <P>Then run</P>
    <P><CODE>depmod -a</CODE></P></LI>
  <LI>Now you have to (re)compile <B>MPlayer</B>, <CODE>configure</CODE> will
    detect <CODE>/dev/mga_vid</CODE> and build the 'mga' driver. Using it from
    <B>MPlayer</B> goes by <CODE>-vo mga</CODE> if you have matroxfb console,
    or <CODE>-vo xmga</CODE> under XFree86 3.x.x or 4.x.x.</LI>
</OL>

<P>The mga_vid driver cooperates with Xv.</P>

  with <CODE>./configure --enable-tdfxfb</CODE></P>


<H4><A NAME="opengl">2.3.1.9 OpenGL output</A></H4>

<P><B>MPlayer</B> supports displaying movies using OpenGL, but if your
  platform/driver supports xv as should be the case on a PC with Linux, use xv
  instead, OpenGL performance is considerably worse. If you have an X11
  implementation without xv support, OpenGL is a viable alternative.</P>

<P>Unfortunately not all drivers support this feature. The Utah-GLX drivers

<H4><A NAME="aalib">2.3.1.10 AAlib - text mode displaying</A></H4>

<P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful
  ASCII renderer. There are LOTS of programs already supporting it, like Doom,
  Quake, etc. <B>MPlayer</B> contains a very usable driver for it.
  If ./configure detects aalib installed, the aalib libvo driver will be
  built.</P>

<TABLE BORDER=0>
  <TR><TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD></TR>

  <TR><TD></TD><TD><CODE>3</CODE></TD><TD></TD><TD>decrease brightness</TD></TR>
  <TR><TD></TD><TD><CODE>4</CODE></TD><TD></TD><TD>increase brightness</TD></TR>
  <TR><TD></TD><TD><CODE>5</CODE></TD><TD></TD><TD>switch fast rendering on/off</TD></TR>
  <TR><TD></TD><TD><CODE>6</CODE></TD><TD></TD><TD>set dithering mode (none, error distribution, Floyd Steinberg)</TD></TR>
  <TR><TD></TD><TD><CODE>7</CODE></TD><TD></TD><TD>invert image</TD></TR>
  <TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and <B>MPlayer</B> control)</TD></TR>
</TABLE>

<P><B>The following command line options can be used:</B></P>
<DL>
  <DT><CODE>-aaosdcolor=V</CODE></DT>

<H4>Known problems and workaround:</H4>

<UL>
  <LI>If you have installed <B>NLS</B> font on your Linux box and run VESA
    driver from text-mode then after terminating <B>MPlayer</B> you will have
    <B>ROM font</B> loaded instead of national. You can load national font again
    by using <B><I>setsysfont</I></B> utility from the Mandrake distribution
    for example.<BR>
    (<B>Hint:</B> The same utility is used for the localization of fbdev).</LI>
  <LI>Some <B>Linux graphics drivers</B> don't update active <B>BIOS mode</B> in

  <LI>video card should be in graphics mode (I write <B>should</B> simply
    because I tested it in text mode - it works but has awful output ;) Use
    AAlib for that).<BR>
    <I>Note: Everyone can try this trick by commenting out mode switching in
    vo_vesa driver.</I></LI>
  <LI><B>MPlayer</B>'s video output driver should know active video mode and be
    able to tell to VIDIX subdevice some video characteristics of server.</LI>
</UL>

I hope that probably every video output driver of <B>MPlayer</B> will
recognize <CODE>:vidix</CODE> subdevice.

<H4>USAGE METHODS</H4>

<P>When VIDIX is used as <B>subdevice</B> (<CODE>-vo vesa:vidix</CODE>) then
  video mode configuration is performed by video output device
  (<B>vo_server</B> in short). Therefore you can pass into command line of
  <B>MPlayer</B> the same keys as for vo_server. In addition it understands
  <CODE>-double</CODE> key as globally visible parameter. (I recommend using
  this key with VIDIX at least for ATI's card).<BR>
  As for <CODE>-vo xvidix</CODE>: currently it recognizes the following
  options: <CODE>-fs -zoom -x -y -double</CODE>.</P>

    32 file.avi</code><BR>
  <BR>
  But it's dangerous, and you shouldn't do that. In this case given driver will
  be forced and result is unpredictable (it may <B>freeze</B> your
  computer). You should do that ONLY if you are absolutely sure it will work,
  and <B>MPlayer</B> doesn't do it automatically. Please tell about it to the
  developers. The Right Way is to use VIDIX without arguments to enable driver
  autodetection.</P>

<P>VIDIX is very new technology and it's extremely possible that on your system
  (OS=abc CPU=xyz) it won't work. In this case only solution for you it's port

<BLOCKQUOTE>
  <B>Warning: security risk</B><BR>
  Unfortunately you <B>must</B> have <B>root</B> privileges to use VIDIX
  due to direct hardware access. At least the <B>SUID</B> bit on the
  <B>MPlayer</B> executable must be set.
</BLOCKQUOTE>

<H4>VIDEO EQUALIZER</H4>

<P>This is a video equalizer implemented especially for VIDIX. You can use
  it either with <B>1-8</B> keys as described in the man page, or
  by command line arguments. <B>MPlayer</B> recognizes the
  following options:</P>

<DL>
  <DT><CODE>-brightness</CODE></DT>
  <DD>Adjust <B>BRIGHTNESS</B> of video output. It's not equal to brightness

  participating in <I>cinerama</I> is four, so you can buid a <CODE>2x2</CODE>
  vidiwall.</P>

<P>Finally an important remark: Do not start or stop XawTV on the playback
  device during playback, it will crash your computer. It is, however, fine to
  <B>FIRST</B> start XawTV, <B>THEN</B> start <B>MPlayer</B>, wait for
  <B>MPlayer</B> to finish and <B>THEN</B> stop XawTV.</P>


<H4><A NAME="dvb">2.3.1.15 DVB</A></H4>

<P><B>MPlayer</B> supports cards with the Siemens DVB chipset from vendors like
  Siemens, Technotrend, Galaxis or Hauppauge.  The latest DVB drivers are
  available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you
  want to do software transcoding you should have at least a 1GHz CPU.</P>

<P>Configure should detect your DVB card. If it did not, force detection with

  decompression).</P>


<H4><A NAME="dxr3">2.3.1.16 DXR3/Hollywood+</A></H4>

<P><B>MPlayer</B> supports hardware accelerated playback with the Creative DXR3
  and Sigma Designs Hollywood Plus cards. These cards both use the em8300 MPEG
  decoder chip from Sigma Designs.</P>

<P>First of all you will need properly installed DXR3/H+ drivers, version
  0.12.0 or later. You can find the drivers and installation instructions at

<DL>
  <DT><CODE>-vo dxr3:noprebuf:&lt;device&gt;</CODE></DT>
  <DD><CODE>noprebuf</CODE> turns off prebuffering. Prebuffering is a feature
    of the em8300 chip that enables it to hold more than one frame of video at
    a time. This means that when you are running with prebuffering (default)
    <B>MPlayer</B> will try to keep the video buffer filled with data at all
    times. If you are on a slow machine <B>MPlayer</B> will probably use close
    to, or precisely 100% of CPU. This is especially common if you play pure MPEG
    streams (like DVDs, SVCDs a.s.o.) since <B>MPlayer</B> will not have to
    reencode it to MPEG it will fill the buffer very fast.<BR>
    With prebuffering video playback is <B>much</B> less sensitive to other
    programs hogging the CPU, it will not drop frames unless applications hog
    the CPU for a long time.<BR>
    Prebuffering does not work on all machines (especially Athlons where it is

</DL>

<H4>Overlay</H4>

<P>To get overlay run dxr3view that comes with the em8300 package before
  starting <B>MPlayer</B>. You can set various options in dxr3view by pressing
  <CODE>T</CODE> while holding the mouse cursor above the window.</P>

<H4>MPEG1, MPEG2, VCD and DVD Notes</H4>

<P>MPEG1/2 content should now automatically be detected by <B>MPlayer</B> and
  it will use the hardware acceleration of the DXR3 to play it. If not, you can
  force it to hardware acceleration with <CODE>-vc mpegpes</CODE>. Also, if you
  plan to use postprocessing filters you must use <CODE>-vc mpeg12</CODE>.</P>

<P>In some instances, subtitles may not appear properly in sync with the A/V
  stream when using hardware decoding (<CODE>-vc mpegpes</CODE>). This is a
  known bug. The em8300 will also improperly handle subtitles that are too big,
  and may hang for a second or two. At this time, the only workaround is to use
  <CODE>-vc mpeg12</CODE> when viewing DVDs with subtitles. When running with
  <CODE>-vc mpeg12</CODE> <B>MPlayer</B> will reencode video to MPEG (even if it
  already is MPEG). This means that it will need more CPU power, and you might
  loose some picture quality.</P>


<H4><A NAME="tv-out">2.3.1.A TV-out support</A></H4>

      <LI>
	If you don't have <CODE>fbset</CODE> installed, enter
        <CODE>TVout/fbset</CODE> and type <CODE>make</CODE>. Install
        <CODE>fbset</CODE> into somewhere in your PATH.</LI>
      <LI>
        Then enter into the <CODE>TVout/</CODE> directory in the <B>MPlayer</B>
        source, and execute <CODE>./modules</CODE> as root. Your text-mode console
        will enter into framebuffer mode (no way back!).</LI>
      <LI>Next, EDIT and run the <CODE>./matroxtv</CODE> script. This will present you
        to a very simple menu. Press <B>2</B> and <B>ENTER</B>. Now you should
	have the same picture on your monitor, and TV. If

<UL>
  <LI><B>ATI Mach64</B>: supported by
    <A HREF="http://gatos.sf.net">gatos</A>.</LI>
  <LI><B>ASIC Radeon VIVO</B>: supported by
  <A HREF="http://gatos.sf.net">gatos</A>.</LI>
  <LI><B>Radeon</B> and <B>Rage128</B>: supported by <B>MPlayer</B>!
    Check <a href="#vesa">VESA driver</a> and <A HREF="#vidix">VIDIX</A>
    sections.</LI>
</UL>

<P>On other cards, just use the <a href="#vesa">VESA driver</a>, without

7814:988498df1996

	        number of planes: 3
	        type: YUV (planar)
	(...etc...)
  </PRE>
    <P>It must support YUY2 packed, and YV12 planar pixel formats to be
      usable with MPlayer.</P>
  </LI>
  <LI>And finally, check if MPlayer was compiled with 'xv' support.
    ./configure prints this.</LI>
</UL>


<H5><A NAME="xv_3dfx">2.3.1.2.1 3dfx cards</A></H5>

    should use, unless you have Rage128 or Radeon) has VSYNC enabled by
    default. It means that decoding speed (!) is synced to the monitor's
    refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or
    set refresh rate to n*(fps of the movie) Hz.</LI>
  <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version
    4.1.0 doesn't. And no TV out support. Of course with MPlayer you can
    happily get <B>accelerated</B> display, with or without <B>TV output</B>, and
    no libraries or X are needed. Read <A HREF="#vidix">Vidix</A> section.</LI>
</UL>

<H5><A NAME="dga_summary">2.3.1.3.1 Summary</A></H5>

<P>This document tries to explain in some words what DGA is in general and what
  the DGA video output driver for MPlayer can do (and what it
  can't).</P>


<H5><A NAME="dga_whatis">2.3.1.3.2 What is DGA</A></H5>

<P>DGA is short for Direct Graphics Access and is a means for a program to
  bypass the X-Server and directly modifying the framebuffer memory.
  Technically spoken this happens by mapping the framebuffer memory into
  the memory range of your process. This is allowed by the kernel only
  if you have superuser privileges. You can get these either by logging in
  as root or by setting the SUID bit on the MPlayer executable (<B>not
  recommended</B>).</P>

<P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was
  introduced with XFree 4.0.1.</P>

<P>First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;<CODE>(II) Loading extension XFree86-DGA</CODE></P>

<P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! MPlayer's DGA
  driver is autodetected on ./configure, or you can force it with
  --enable-dga.</P>

<P>If the driver couldn't switch to a smaller resolution, experiment with
  switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that
  the movie fits in. There is no converter right now :(</P>

<P>Become root. DGA needs root access to be able to write directly to video
  memory. If you want to run it as user, then install MPlayer SUID
  root:</P>

<P><CODE>
  &nbsp;&nbsp;&nbsp;&nbsp;chown root /usr/local/bin/mplayer<BR>
  &nbsp;&nbsp;&nbsp;&nbsp;chmod 750 /usr/local/bin/mplayer<BR>

<BLOCKQUOTE>
  <B>Warning: security risk</B><BR>
  This is a <B>big</B> security risk! <B>Never</B> do this on a server or on
  a computer that can be accessed by other people because they can gain root
  privileges through SUID root MPlayer.
</BLOCKQUOTE>

<P>Now use the <CODE>-vo dga</CODE> option, and there you go (hope so :))!
  You should also try if the <CODE>-vo sdl:dga</CODE> option works for you. It's
  much faster.</P>

<P>See appendix A for some sample modeline definitions.</P>


<H5><A NAME="dga_mplayer">2.3.1.3.5 DGA &amp; MPlayer</A></H5>

<P>DGA is used in two places with MPlayer: The SDL driver can be made to
  make use of it (-vo sdl:dga) and within the DGA driver (-vo dga). The above
  said is true for both; in the following sections I'll explain how the DGA
  driver for MPlayer works.</P>


<H5><A NAME="dga_features">2.3.1.3.6 Features of the DGA driver</A></H5>

<P>The DGA driver is invoked by specifying -vo dga at the command line.

<H5><A NAME="dga_speed">2.3.1.3.7 Speed issues</A></H5>

<P>Generally spoken, DGA framebuffer access should be at least as fast as using
  the X11 driver with the additional benefit of getting a fullscreen image. 
  The percentage speed values printed by MPlayer have to be interpreted
  with some care, as for example, with the X11 driver they do not include the
  time used by the X-Server needed for the actual drawing. Hook a terminal to a
  serial line of your box and start top to see what is really going on in your
  box...</P>

<H5><A NAME="dga_bug_reports">2.3.1.3.B Bug Reports</A></H5>

<P>If you experience troubles with the DGA driver please feel free to file
  a bug report to me (e-mail address below). Please start MPlayer with
  the -v option and include all lines in the bug report that start with
  vo_dga:</P>

<P>Please do also include the version of X11 you are using, the graphics card
  and your CPU type. The X11 driver module (defined in XF86-Config) might

  or audio driver does SDL actually use. For example a Doom port using SDL can
  run on svgalib, aalib, X, fbdev, and others, you only have to specify the
  (for example) video driver to use with the SDL_VIDEODRIVER environment
  variable. Well, in theory.</P>

<P>With MPlayer, we used its X11 driver's software scaler ability for
  cards/drivers that doesn't support XVideo, until we made our own (faster,
  nicer) software scaler. Also we used its aalib output, but now we have ours
  which is more comfortable. Its DGA mode was better than ours, until
  recently. Get it now? :)</P>

<H4><A NAME="svgalib">2.3.1.5 SVGAlib</A></H4>

<H4>Installation</H4>

<P>You'll have to install svgalib and its development package in order for
  MPlayer build its SVGAlib driver (autodetected, but can be forced),
  and don't forget to edit /etc/vga/libvga.config to suit your card &amp;
  monitor.</P>

<H4>Notes</H4>

  scaler, and it's slow. If you really need it, use the <CODE>-sws 4</CODE>
  option which will produce bad quality, but is somewhat faster.</P>

<H4>EGA (4bpp) support</H4>

<P>SVGAlib incorporates EGAlib, and MPlayer has the possibility to
  display any movie in 16 colors, thus usable in the following sets:</P>

<UL>
  <LI>EGA card with EGA monitor: 320x200x4bpp, 640x200x4bpp, 640x350x4bpp</LI>
  <LI>EGA card with CGA monitor: 320x200x4bpp, 640x200x4bpp</LI>

    To turn the cursor back on: <CODE>echo -e '\033[?25h'</CODE>
    or <CODE>setterm -cursor on</CODE></LI>
</UL>

<P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer,
  and don't ask for it, since it's not an MPlayer limitation.</P>


<H4><A NAME="mga_vid">2.3.1.7 Matrox framebuffer (mga_vid)</A></H4>

<P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)

    <P><CODE>alias char-major-178 mga_vid</CODE></P>
    <P>Then copy the <CODE>mga_vid.o</CODE> module to the appropriate place
      under <CODE>/lib/modules/&lt;kernel version&gt;/somewhere</CODE>.</P>
    <P>Then run</P>
    <P><CODE>depmod -a</CODE></P></LI>
  <LI>Now you have to (re)compile MPlayer, <CODE>configure</CODE> will
    detect <CODE>/dev/mga_vid</CODE> and build the 'mga' driver. Using it from
    MPlayer goes by <CODE>-vo mga</CODE> if you have matroxfb console,
    or <CODE>-vo xmga</CODE> under XFree86 3.x.x or 4.x.x.</LI>
</OL>

<P>The mga_vid driver cooperates with Xv.</P>

  with <CODE>./configure --enable-tdfxfb</CODE></P>


<H4><A NAME="opengl">2.3.1.9 OpenGL output</A></H4>

<P>MPlayer supports displaying movies using OpenGL, but if your
  platform/driver supports xv as should be the case on a PC with Linux, use xv
  instead, OpenGL performance is considerably worse. If you have an X11
  implementation without xv support, OpenGL is a viable alternative.</P>

<P>Unfortunately not all drivers support this feature. The Utah-GLX drivers

<H4><A NAME="aalib">2.3.1.10 AAlib - text mode displaying</A></H4>

<P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful
  ASCII renderer. There are LOTS of programs already supporting it, like Doom,
  Quake, etc. MPlayer contains a very usable driver for it.
  If ./configure detects aalib installed, the aalib libvo driver will be
  built.</P>

<TABLE BORDER=0>
  <TR><TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD></TR>

  <TR><TD></TD><TD><CODE>3</CODE></TD><TD></TD><TD>decrease brightness</TD></TR>
  <TR><TD></TD><TD><CODE>4</CODE></TD><TD></TD><TD>increase brightness</TD></TR>
  <TR><TD></TD><TD><CODE>5</CODE></TD><TD></TD><TD>switch fast rendering on/off</TD></TR>
  <TR><TD></TD><TD><CODE>6</CODE></TD><TD></TD><TD>set dithering mode (none, error distribution, Floyd Steinberg)</TD></TR>
  <TR><TD></TD><TD><CODE>7</CODE></TD><TD></TD><TD>invert image</TD></TR>
  <TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and MPlayer control)</TD></TR>
</TABLE>

<P><B>The following command line options can be used:</B></P>
<DL>
  <DT><CODE>-aaosdcolor=V</CODE></DT>

<H4>Known problems and workaround:</H4>

<UL>
  <LI>If you have installed <B>NLS</B> font on your Linux box and run VESA
    driver from text-mode then after terminating MPlayer you will have
    <B>ROM font</B> loaded instead of national. You can load national font again
    by using <B><I>setsysfont</I></B> utility from the Mandrake distribution
    for example.<BR>
    (<B>Hint:</B> The same utility is used for the localization of fbdev).</LI>
  <LI>Some <B>Linux graphics drivers</B> don't update active <B>BIOS mode</B> in

  <LI>video card should be in graphics mode (I write <B>should</B> simply
    because I tested it in text mode - it works but has awful output ;) Use
    AAlib for that).<BR>
    <I>Note: Everyone can try this trick by commenting out mode switching in
    vo_vesa driver.</I></LI>
  <LI>MPlayer's video output driver should know active video mode and be
    able to tell to VIDIX subdevice some video characteristics of server.</LI>
</UL>

I hope that probably every video output driver of MPlayer will
recognize <CODE>:vidix</CODE> subdevice.

<H4>USAGE METHODS</H4>

<P>When VIDIX is used as <B>subdevice</B> (<CODE>-vo vesa:vidix</CODE>) then
  video mode configuration is performed by video output device
  (<B>vo_server</B> in short). Therefore you can pass into command line of
  MPlayer the same keys as for vo_server. In addition it understands
  <CODE>-double</CODE> key as globally visible parameter. (I recommend using
  this key with VIDIX at least for ATI's card).<BR>
  As for <CODE>-vo xvidix</CODE>: currently it recognizes the following
  options: <CODE>-fs -zoom -x -y -double</CODE>.</P>

    32 file.avi</code><BR>
  <BR>
  But it's dangerous, and you shouldn't do that. In this case given driver will
  be forced and result is unpredictable (it may <B>freeze</B> your
  computer). You should do that ONLY if you are absolutely sure it will work,
  and MPlayer doesn't do it automatically. Please tell about it to the
  developers. The Right Way is to use VIDIX without arguments to enable driver
  autodetection.</P>

<P>VIDIX is very new technology and it's extremely possible that on your system
  (OS=abc CPU=xyz) it won't work. In this case only solution for you it's port

<BLOCKQUOTE>
  <B>Warning: security risk</B><BR>
  Unfortunately you <B>must</B> have <B>root</B> privileges to use VIDIX
  due to direct hardware access. At least the <B>SUID</B> bit on the
  MPlayer executable must be set.
</BLOCKQUOTE>

<H4>VIDEO EQUALIZER</H4>

<P>This is a video equalizer implemented especially for VIDIX. You can use
  it either with <B>1-8</B> keys as described in the man page, or
  by command line arguments. MPlayer recognizes the
  following options:</P>

<DL>
  <DT><CODE>-brightness</CODE></DT>
  <DD>Adjust <B>BRIGHTNESS</B> of video output. It's not equal to brightness

  participating in <I>cinerama</I> is four, so you can buid a <CODE>2x2</CODE>
  vidiwall.</P>

<P>Finally an important remark: Do not start or stop XawTV on the playback
  device during playback, it will crash your computer. It is, however, fine to
  <B>FIRST</B> start XawTV, <B>THEN</B> start MPlayer, wait for
  MPlayer to finish and <B>THEN</B> stop XawTV.</P>


<H4><A NAME="dvb">2.3.1.15 DVB</A></H4>

<P>MPlayer supports cards with the Siemens DVB chipset from vendors like
  Siemens, Technotrend, Galaxis or Hauppauge.  The latest DVB drivers are
  available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you
  want to do software transcoding you should have at least a 1GHz CPU.</P>

<P>Configure should detect your DVB card. If it did not, force detection with

  decompression).</P>


<H4><A NAME="dxr3">2.3.1.16 DXR3/Hollywood+</A></H4>

<P>MPlayer supports hardware accelerated playback with the Creative DXR3
  and Sigma Designs Hollywood Plus cards. These cards both use the em8300 MPEG
  decoder chip from Sigma Designs.</P>

<P>First of all you will need properly installed DXR3/H+ drivers, version
  0.12.0 or later. You can find the drivers and installation instructions at

<DL>
  <DT><CODE>-vo dxr3:noprebuf:&lt;device&gt;</CODE></DT>
  <DD><CODE>noprebuf</CODE> turns off prebuffering. Prebuffering is a feature
    of the em8300 chip that enables it to hold more than one frame of video at
    a time. This means that when you are running with prebuffering (default)
    MPlayer will try to keep the video buffer filled with data at all
    times. If you are on a slow machine MPlayer will probably use close
    to, or precisely 100% of CPU. This is especially common if you play pure MPEG
    streams (like DVDs, SVCDs a.s.o.) since MPlayer will not have to
    reencode it to MPEG it will fill the buffer very fast.<BR>
    With prebuffering video playback is <B>much</B> less sensitive to other
    programs hogging the CPU, it will not drop frames unless applications hog
    the CPU for a long time.<BR>
    Prebuffering does not work on all machines (especially Athlons where it is

</DL>

<H4>Overlay</H4>

<P>To get overlay run dxr3view that comes with the em8300 package before
  starting MPlayer. You can set various options in dxr3view by pressing
  <CODE>T</CODE> while holding the mouse cursor above the window.</P>

<H4>MPEG1, MPEG2, VCD and DVD Notes</H4>

<P>MPEG1/2 content should now automatically be detected by MPlayer and
  it will use the hardware acceleration of the DXR3 to play it. If not, you can
  force it to hardware acceleration with <CODE>-vc mpegpes</CODE>. Also, if you
  plan to use postprocessing filters you must use <CODE>-vc mpeg12</CODE>.</P>

<P>In some instances, subtitles may not appear properly in sync with the A/V
  stream when using hardware decoding (<CODE>-vc mpegpes</CODE>). This is a
  known bug. The em8300 will also improperly handle subtitles that are too big,
  and may hang for a second or two. At this time, the only workaround is to use
  <CODE>-vc mpeg12</CODE> when viewing DVDs with subtitles. When running with
  <CODE>-vc mpeg12</CODE> MPlayer will reencode video to MPEG (even if it
  already is MPEG). This means that it will need more CPU power, and you might
  loose some picture quality.</P>


<H4><A NAME="tv-out">2.3.1.A TV-out support</A></H4>

      <LI>
	If you don't have <CODE>fbset</CODE> installed, enter
        <CODE>TVout/fbset</CODE> and type <CODE>make</CODE>. Install
        <CODE>fbset</CODE> into somewhere in your PATH.</LI>
      <LI>
        Then enter into the <CODE>TVout/</CODE> directory in the MPlayer
        source, and execute <CODE>./modules</CODE> as root. Your text-mode console
        will enter into framebuffer mode (no way back!).</LI>
      <LI>Next, EDIT and run the <CODE>./matroxtv</CODE> script. This will present you
        to a very simple menu. Press <B>2</B> and <B>ENTER</B>. Now you should
	have the same picture on your monitor, and TV. If

<UL>
  <LI><B>ATI Mach64</B>: supported by
    <A HREF="http://gatos.sf.net">gatos</A>.</LI>
  <LI><B>ASIC Radeon VIVO</B>: supported by
  <A HREF="http://gatos.sf.net">gatos</A>.</LI>
  <LI><B>Radeon</B> and <B>Rage128</B>: supported by MPlayer!
    Check <a href="#vesa">VESA driver</a> and <A HREF="#vidix">VIDIX</A>
    sections.</LI>
</UL>

<P>On other cards, just use the <a href="#vesa">VESA driver</a>, without