comparison DOCS/video.html @ 9255:c82e31b31194

my patches sent to dev-eng (i feel me brave) Diego, fix my wording bugs, and dont be angry.

9254:a35bf9da25db

    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>


<H4><A NAME="xv_neomagic">2.3.1.2.1.5 NeoMagic cards</A></H4>

<H4><A NAME="dga">2.3.1.2.2 DGA</A></H4>


<H4><A NAME="dga_summary">2.3.1.2.2.1 Summary</A></H4>

<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>


<H4><A NAME="dga_whatis">2.3.1.2.2.2 What is DGA</A></H4>

<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

  running a 32 bit depth X server, switch to a depth of 15 bits and vice
  versa. </P>

<P>However DGA has some drawbacks. It seems it is somewhat dependent on the
  graphics chip you use and on the implementation of the X server's video
  driver that controls this chip. So it does not work on every system ...</P>


<H4><A NAME="dga_installation">2.3.1.2.2.3 Installing DGA support for MPlayer</A></H4>

<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>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>


<H4><A NAME="dga_resolution">2.3.1.2.2.4 Resolution switching</A></H4>

<P>The DGA driver allows for switching the resolution of the output signal. 
  This avoids the need for doing (slow) software scaling and at the same time
  provides a fullscreen image. Ideally it would switch to the exact resolution
  (except for honoring aspect ratio) of the video data, but the X server only

  config file on startup and disables the modelines not suitable for your
  hardware. You can find out which modes survive with the X11 log file. It can
  be found at:
  <CODE>/var/log/XFree86.0.log</CODE>.</P>

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


<H4><A NAME="dga_mplayer">2.3.1.2.2.5 DGA &amp; MPlayer</A></H4>

<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>


<H4><A NAME="dga_features">2.3.1.2.2.6 Features of the DGA driver</A></H4>

<P>The DGA driver is invoked by specifying -vo dga at the command line.
  The default behavior is to switch to a resolution matching the original
  resolution of the video as close as possible. It deliberately ignores the
  -vm and -fs options (enabling of video mode switching and fullscreen) -

  works with doublebuffering enabled. However, enabling doublebuffering may
  result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of
  CPU time!) depending on the implementation of DGA for your hardware.</P>


<H4><A NAME="dga_speed">2.3.1.2.2.7 Speed issues</A></H4>

<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>

<P>Generally spoken, the speedup done by using DGA against 'normal' use of X11
  highly depends on your graphics card and how well the X-Server module for it
  is optimized.</P>

<P>I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2
  CPUs might work at 400 MHZ and above.</P>


<H4><A NAME="dga_bugs">2.3.1.2.2.8 Known bugs</A></H4>

<P>Well, according to some developers of XFree, DGA is quite a beast. They
  tell you better not to use it. Its implementation is not always flawless
  with every chipset driver for XFree out there.</P>

  <LI>Some drivers simply fail to switch back to normal resolution (use
    Ctrl-Alt-Keypad +, - to switch back manually).</LI>
  <LI>Some drivers simply display strange colors.</LI>
  <LI>Some drivers lie about the amount of memory they map into the process's
    address space, thus vo_dga won't use doublebuffering (SIS?).</LI>
  <LI>some drivers seem to fail to report even a single valid mode. In this
    case the DGA driver will crash telling you about a nonsense mode of
    100000x100000 or the like ...</LI>
   <LI>OSD only works with doublebuffering enabled.</LI>
</UL>


<H4><A NAME="dga_modelines">2.3.1.2.2.A Some modelines</A></H4>

<PRE>
  Section "Modes"
    Identifier    "Modes[0]"
    Modeline	"800x600"  40     800 840 968 1056  600 601 605 628

    Modeline	"352x240"  15.750 352 368 416 432   240 244 246 262 Doublescan
    Modeline	"320x240"  12.588 320 336 384 400   240 245 246 262 Doublescan
  EndSection
</PRE>

<P>These entries work fine with my Riva128 chip, using nv.o X server driver
  module.</P>


<H4><A NAME="dga_bug_reports">2.3.1.2.2.B Bug Reports</A></H4>

<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
  also help. Thanks!</P>

<P><I>Acki ([e-mail], www.acki-netz.de)</I></P>


<H4><A NAME="sdl">2.3.1.2.3 SDL</A></H4>

<P>SDL (Simple Directmedia Layer) is basically a unified video/audio

  <TR><TD></TD><TD><CODE>F</CODE></TD><TD></TD><TD>toggles fullscreen/windowed mode</TD></TR>
  <TR><TD></TD><TD><CODE>C</CODE></TD><TD></TD><TD>cycles available fullscreen modes</TD></TR>
  <TR><TD></TD><TD><CODE>W/S</CODE></TD><TD></TD><TD>mappings for * and / (mixer control)</TD></TR>
</TABLE>

<H4>Known bugs:</H4>

<UL>
  <LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa!)
    It's bug in SDL, I can't change it (tested with SDL 1.2.1).</LI>
  <LI>DO NOT USE SDL with GUI! It won't work as it should.</LI>
</UL>


<H4><A NAME="svgalib">2.3.1.2.4 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>

<P>Be sure not to use the -fs option, since it toggles the usage of the software
  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>

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

<P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)
  support, the mga_vid kernel driver. It's active developed by me (A'rpi), and
  it has hardware VSYNC support with triple buffering. It works on both
  framebuffer console and under X.</P>

<P><B>NOTE</B>: This is Linux only! On non-Linux (tested on FreeBSD) systems,
  you can use <A HREF="#vidix">VIDIX</A> instead!</P>

<P>So you have chances to get working TV-out by using this driver.<BR>
  (I guess that TV-out frequently is standalone head or standalone output
  at least.)</P>

<H4>Advantages:</H4>

<UL>
  <LI>You have the possibility to watch movies <B>even if Linux doesn't know</B>
    your video hardware.</LI>
  <LI>You don't need to have installed any graphics' related things on your Linux

  <LI>You have chances to get <B>working TV-out</B>. (It's known at least for
    ATI's cards).</LI>
  <LI>This driver calls <B>int 10h</B> handler thus it's not an emulator - it
    calls <B>real</B> things of <B>real</B> BIOS in <B>real</B>-mode. (Finely -
    in vm86 mode).</LI>
  <LI>You can use Vidix with it, thus getting accelerated video display
    <B>AND</B> TV output at the same time! (recommended for ATI cards)</LI>
  <LI>If you have VESA VBE 3.0+, and you had specified <CODE>monitor_hfreq</CODE>,
    <CODE>monitor_vfreq</CODE>, <CODE>monitor_dotclock</CODE> somewhere (config
    file, or commandline) you will get the highest possible refresh rate. (Using
    General Timing Formula). To enable this feature you have to specify
    <B>all</B> your monitor options.</LI>
</UL>

<H4>Disadvantages:</H4>

<UL>
  <LI>It works only on <B>x86 systems</B>.</LI>
  <LI>It can be used only by <B>root</B>.</LI>
  <LI>Currently it's available only for <B>Linux</B>.</LI>
</UL>

<P>Don't use this driver with <B>GCC 2.96</B>! It won't work!</P>

<P><B>Command line options available for VESA:</B></P>
<DL>
  <DT><CODE>-vo vesa:opts</CODE></DT>
  <DD>currently recognized: <B>dga</B> to force dga mode and <B>nodga</B> to
    disable dga mode. In dga mode you can enable double buffering via the
    <CODE>-double</CODE> option. Note: you may omit these parameters to enable
    <B>autodetection</B> of dga mode.</DD>
</DL>

<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

  video modes.</P>


<H4><A NAME="vidix">2.3.1.2.12 VIDIX</A></H4>

<P>VIDIX is the abbreviation for <B>VID</B>eo <B>I</B>nterface for
  *ni<B>X</B>.<BR>
  VIDIX was designed and introduced as an interface for fast user-space drivers
  providing such video performance as mga_vid does for Matrox cards. It's
  also very portable.</P>

<P>This interface was designed as an attempt to fit existing video acceleration
  interfaces (known as mga_vid, rage128_vid, radeon_vid, pm3_vid) into a fixed scheme. It
  provides highlevel interface to chips which are known as BES (BackEnd
  scalers) or OV (Video Overlays). It doesn't provide lowlevel interface to
  things which are known as graphics servers. (I don't want to compete with X11
  team in graphics mode switching). I.e. main goal of this interface is to
  maximize the speed of video playback.</P>

<H4>USAGE</H4>

<UL>
  <LI>You can use standalone video output driver: <CODE>-vo xvidix</CODE><BR>
    This driver was developed as X11's front end to VIDIX technology. It
    requires X server and can work only under X server. Note that, as it

    <CODE>-vo vesa:vidix</CODE> (<B>Linux only</B>) and <CODE>-vo fbdev:vidix</CODE></LI>
</UL>

Indeed it doesn't matter which video output driver is used with <B>VIDIX</B>.

<H4>REQUIREMENTS</H4>

<UL>
  <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>

    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>

<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>

<P>Also you can specify VIDIX's driver directly as third subargument in command
  line:<BR>

  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 the only solution for you is
  porting (mainly libdha) it. But there is a hope, that it will work on those
  systems where X11 does.</P>

<P>Since VIDIX requires direct hardware access you can either run it as root or
  set the SUID bit on the MPlayer binary (<B>Warning: This is a security
  risk!</B>). Alternatively, you can use a special kernel module, like this:</P>

<OL>
  <LI>Download the
    <A HREF="http://www.arava.co.il/matan/svgalib/">development version</A>
    of svgalib (for example 1.9.17).</LI>
  <LI>Move the <CODE>svgalib-1.9.17/kernel/svgalib_helper</CODE> directory to
    <CODE>mplayer/main/libdha/svgalib_helper</CODE>.</LI>
  <LI>Compile the module in the <CODE> svgalib_helper</CODE> directory and
    insmod it.</LI>
  <LI>Recompile and install libdha.</LI>
</OL>


<H4><A NAME="vidix_ati">2.3.1.2.12.1 ATI cards</A></H4>

  ./configure --with-extraincdir=<DVB source directory>/ost/include
</PRE>

<P>Then compile and install as usual.</P>

<H4>USAGE</H4>

<P>Hardware decoding (playing standard MPEG1/2 files) can be done with this
  command:</P>

<PRE>

<PRE>
for  3:4 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale
for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
</PRE>

<H4>FUTURE</H4>

<P>If you have questions or want to hear feature announcements and take part in
  discussions on this subject, join our
  <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</A>
  mailing list. Please remember that the list language is English.</P>

  0.12.0 or later. You can find the drivers and installation instructions at
  the <A HREF="http://dxr3.sourceforge.net/">DXR3 &amp; Hollywood Plus for
  Linux</A> site. Configure should detect your card automatically, compilation
  should go without problems.</P>

<H4>Usage:</H4>
<DL>
  <DT><CODE>-vo dxr3:prebuf:sync:norm=x:&lt;device&gt;</CODE></DT>
  <DD><CODE>overlay</CODE> activates the overlay instead of TVOut. It requires
    that you have a properly configured overlay setup to work right. The easiest
    way to configure the overlay is to first run autocal. Then run mplayer with

9255:c82e31b31194

    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>


<H4><A NAME="xv_neomagic">2.3.1.2.1.5 NeoMagic cards</A></H4>

<H4><A NAME="dga">2.3.1.2.2 DGA</A></H4>


<H5>PREAMBLE</H4>

<P>This section 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>WHAT IS DGA</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

  running a 32 bit depth X server, switch to a depth of 15 bits and vice
  versa. </P>

<P>However DGA has some drawbacks. It seems it is somewhat dependent on the
  graphics chip you use and on the implementation of the X server's video
  driver that controls this chip. So it does not work on every system.</P>


<H5>INSTALLING DGA SUPPORT FOR MPLAYER</H5>

<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>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>


<H5>RESOLUTION SWITCHING</H5>

<P>The DGA driver allows for switching the resolution of the output signal. 
  This avoids the need for doing (slow) software scaling and at the same time
  provides a fullscreen image. Ideally it would switch to the exact resolution
  (except for honoring aspect ratio) of the video data, but the X server only

  config file on startup and disables the modelines not suitable for your
  hardware. You can find out which modes survive with the X11 log file. It can
  be found at:
  <CODE>/var/log/XFree86.0.log</CODE>.</P>

<P>See some working modeline definitions <A HREF="#dga_modelines">here</A>.</P>


<H5>DGA &amp; MPLAYER</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>FEATURES</H5>

<P>The DGA driver is invoked by specifying -vo dga at the command line.
  The default behavior is to switch to a resolution matching the original
  resolution of the video as close as possible. It deliberately ignores the
  -vm and -fs options (enabling of video mode switching and fullscreen) -

  works with doublebuffering enabled. However, enabling doublebuffering may
  result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of
  CPU time!) depending on the implementation of DGA for your hardware.</P>


<H5>SPEED ISSUES</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>

<P>Generally spoken, the speedup done by using DGA against 'normal' use of X11
  highly depends on your graphics card and how well the X-Server module for it
  is optimized.</P>

<P>I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2
  CPUs might work at 400 MHZ and above.</P>


<H5>KNOWN BUGS</H5>

<P>Well, according to some developers of XFree, DGA is quite a beast. They
  tell you better not to use it. Its implementation is not always flawless
  with every chipset driver for XFree out there.</P>

  <LI>Some drivers simply fail to switch back to normal resolution (use
    Ctrl-Alt-Keypad +, - to switch back manually).</LI>
  <LI>Some drivers simply display strange colors.</LI>
  <LI>Some drivers lie about the amount of memory they map into the process's
    address space, thus vo_dga won't use doublebuffering (SIS?).</LI>
  <LI>Some drivers seem to fail to report even a single valid mode. In this
    case the DGA driver will crash telling you about a nonsense mode of
    100000x100000 or someathing like that.</LI>
   <LI>OSD only works with doublebuffering enabled (else it flickers).</LI>
</UL>


<H5><A NAME="dga_modelines">SOME MODELINES</A></H5>

<PRE>
  Section "Modes"
    Identifier    "Modes[0]"
    Modeline	"800x600"  40     800 840 968 1056  600 601 605 628

    Modeline	"352x240"  15.750 352 368 416 432   240 244 246 262 Doublescan
    Modeline	"320x240"  12.588 320 336 384 400   240 245 246 262 Doublescan
  EndSection
</PRE>

<P>These entries work fine with authors (Acki) Riva128 chip, using nv.o X server driver
  module.</P>


<H4><A NAME="sdl">2.3.1.2.3 SDL</A></H4>

<P>SDL (Simple Directmedia Layer) is basically a unified video/audio

  <TR><TD></TD><TD><CODE>F</CODE></TD><TD></TD><TD>toggles fullscreen/windowed mode</TD></TR>
  <TR><TD></TD><TD><CODE>C</CODE></TD><TD></TD><TD>cycles available fullscreen modes</TD></TR>
  <TR><TD></TD><TD><CODE>W/S</CODE></TD><TD></TD><TD>mappings for * and / (mixer control)</TD></TR>
</TABLE>

<H5>KNOWN BUGS</H5>

<UL>
  <LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa!)
    It's bug in SDL, I can't change it (tested with SDL 1.2.1).</LI>
  <LI>DO NOT USE SDL with GUI! It won't work as it should.</LI>
</UL>


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

<H5>INSTALLATION</H5>

<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>

<H5>NOTES</H5>

<P>Be sure not to use the -fs option, since it toggles the usage of the software
  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>

<H5>EGA (4BPP) SUPPORT</H5>

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

<UL>

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

<P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)
  support, the mga_vid kernel driver. It's active developed by A'rpi, and
  it has hardware VSYNC support with triple buffering. It works on both
  framebuffer console and under X.</P>

<P><B>NOTE</B>: This is Linux only! On non-Linux (tested on FreeBSD) systems,
  you can use <A HREF="#vidix">VIDIX</A> instead!</P>

<P>So you have chances to get working TV-out by using this driver.<BR>
  (I guess that TV-out frequently is standalone head or standalone output
  at least.)</P>

<H5>ADVANTAGES</H5>

<UL>
  <LI>You have the possibility to watch movies <B>even if Linux doesn't know</B>
    your video hardware.</LI>
  <LI>You don't need to have installed any graphics' related things on your Linux

  <LI>You have chances to get <B>working TV-out</B>. (It's known at least for
    ATI's cards).</LI>
  <LI>This driver calls <B>int 10h</B> handler thus it's not an emulator - it
    calls <B>real</B> things of <B>real</B> BIOS in <B>real</B>-mode. (Finely -
    in vm86 mode).</LI>
  <LI>You can use VIDIX with it, thus getting accelerated video display
    <B>AND</B> TV output at the same time! (recommended for ATI cards)</LI>
  <LI>If you have VESA VBE 3.0+, and you had specified <CODE>monitor_hfreq</CODE>,
    <CODE>monitor_vfreq</CODE>, <CODE>monitor_dotclock</CODE> somewhere (config
    file, or commandline) you will get the highest possible refresh rate. (Using
    General Timing Formula). To enable this feature you have to specify
    <B>all</B> your monitor options.</LI>
</UL>

<H5>DISADVANTAGES</H5>

<UL>
  <LI>It works only on <B>x86 systems</B>.</LI>
  <LI>It can be used only by <B>root</B>.</LI>
  <LI>Currently it's available only for <B>Linux</B>.</LI>
</UL>

<P>Don't use this driver with <B>GCC 2.96</B>! It won't work!</P>

<H5>COMMAND LINE OPTIONS AVAILABLE FOR VESA</H5>
<DL>
  <DT><CODE>-vo vesa:opts</CODE></DT>
  <DD>currently recognized: <B>dga</B> to force dga mode and <B>nodga</B> to
    disable dga mode. In dga mode you can enable double buffering via the
    <CODE>-double</CODE> option. Note: you may omit these parameters to enable
    <B>autodetection</B> of dga mode.</DD>
</DL>

<H5>KNOWN PROBLEMS AND WORKAROUNDS</H5>

<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

  video modes.</P>


<H4><A NAME="vidix">2.3.1.2.12 VIDIX</A></H4>

<H5>PREAMBLE</H5>

<P>VIDIX is the abbreviation for <B>VID</B>eo <B>I</B>nterface for *ni<B>X</B>.
  It was designed and introduced as an interface for fast user-space drivers
  providing such video performance as mga_vid does for Matrox cards. It's also
  very portable.</P>

<P>This interface was designed as an attempt to fit existing video acceleration
  interfaces (known as mga_vid, rage128_vid, radeon_vid, pm3_vid) into a fixed scheme. It
  provides highlevel interface to chips which are known as BES (BackEnd
  scalers) or OV (Video Overlays). It doesn't provide lowlevel interface to
  things which are known as graphics servers. (I don't want to compete with X11
  team in graphics mode switching). I.e. main goal of this interface is to
  maximize the speed of video playback.</P>

<H5>USAGE</H5>

<UL>
  <LI>You can use standalone video output driver: <CODE>-vo xvidix</CODE><BR>
    This driver was developed as X11's front end to VIDIX technology. It
    requires X server and can work only under X server. Note that, as it

    <CODE>-vo vesa:vidix</CODE> (<B>Linux only</B>) and <CODE>-vo fbdev:vidix</CODE></LI>
</UL>

Indeed it doesn't matter which video output driver is used with <B>VIDIX</B>.

<H5>REQUIREMENTS</H5>

<UL>
  <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>

    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>

<H5>USAGE METHODS</H5>

<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 cards).<BR>
  As for <CODE>-vo xvidix</CODE>: currently it recognizes the following
  options: <CODE>-fs -zoom -x -y -double</CODE>.</P>

<P>Also you can specify VIDIX's driver directly as third subargument in command
  line:<BR>

  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 a new technology and it's extremely possible that on your system
  it won't work. In this case the only solution for you is porting (mainly
  libdha) it. But there is a hope, that it will work on those systems where X11
  does.</P>

<P>Since VIDIX requires direct hardware access you can either run it as root or
  set the SUID bit on the MPlayer binary (<B>Warning: This is a security
  risk!</B>). Alternatively, you can use a special kernel module, like this:</P>

<OL>
  <LI>Download the
    <A HREF="http://www.arava.co.il/matan/svgalib/">development version</A>
    of svgalib (for example 1.9.17).</LI>
  <LI><B>OR</B> download a version made by Alex especially for usage with
    MPlayer (it doesn't need the svgalib source to compile) from
    <A HREF="http://www.mplayerhq.hu/~alex/svgalib_helper-1.9.17-mplayer.tar.bz2">
    here</A>.
  <LI>Compile the module in the <CODE>svgalib_helper</CODE> directory (it can
    be found inside the <CODE>svgalib-1.9.17/kernel/</CODE> directory if you've
    downloaded the source from the svgalib site) and insmod it.</LI>
  <LI>Move the <CODE>svgalib_helper</CODE> directory to
    <CODE>mplayer/main/libdha/svgalib_helper</CODE>.</LI>
  <LI>Required if you download the source from the svgalib site: remove the
    comment before the CFLAGS line containing "svgalib_helper" string from the
    <CODE>libdha/Makefile</CODE>.</LI>
  <LI>Recompile and install libdha.</LI>
</OL>


<H4><A NAME="vidix_ati">2.3.1.2.12.1 ATI cards</A></H4>

  ./configure --with-extraincdir=<DVB source directory>/ost/include
</PRE>

<P>Then compile and install as usual.</P>

<H5>USAGE</H5>

<P>Hardware decoding (playing standard MPEG1/2 files) can be done with this
  command:</P>

<PRE>

<PRE>
for  3:4 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale
for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
</PRE>

<H5>FUTURE</H5>

<P>If you have questions or want to hear feature announcements and take part in
  discussions on this subject, join our
  <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</A>
  mailing list. Please remember that the list language is English.</P>

  0.12.0 or later. You can find the drivers and installation instructions at
  the <A HREF="http://dxr3.sourceforge.net/">DXR3 &amp; Hollywood Plus for
  Linux</A> site. Configure should detect your card automatically, compilation
  should go without problems.</P>

<H5>USAGE</H5>
<DL>
  <DT><CODE>-vo dxr3:prebuf:sync:norm=x:&lt;device&gt;</CODE></DT>
  <DD><CODE>overlay</CODE> activates the overlay instead of TVOut. It requires
    that you have a properly configured overlay setup to work right. The easiest
    way to configure the overlay is to first run autocal. Then run mplayer with