This document tries to explain in some words what DGA is in general and what +
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).
-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. @@ -254,7 +254,7 @@ driver that controls this chip. So it does not work on every system ...
-First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:
@@ -291,7 +291,7 @@ much faster. -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 @@ -309,7 +309,7 @@
See appendix A for some sample modeline definitions.
-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 @@ -317,7 +317,7 @@ driver for MPlayer works.
-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 @@ -356,7 +356,7 @@ CPU time!) depending on the implementation of DGA for your hardware.
-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. @@ -381,7 +381,7 @@ CPUs might work at 400 MHZ and above.
-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 @@ -404,7 +404,7 @@ -
Section "Modes" @@ -423,7 +423,7 @@ module. -2.3.1.2.2.B Bug Reports
+BUG REPORTS
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 @@ -480,7 +480,7 @@
- W/Smappings for * and / (mixer control) Known bugs:
+KNOWN BUGS
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 & monitor.
-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 -sws 4
option which will produce bad quality, but is somewhat faster.
SVGAlib incorporates EGAlib, and MPlayer has the possibility to display any movie in 16 colors, thus usable in the following sets:
@@ -745,7 +745,7 @@ (I guess that TV-out frequently is standalone head or standalone output at least.) -Don't use this driver with GCC 2.96! It won't work!
-Command line options available for VESA:
+-vo vesa:optsVIDIX is the abbreviation for VIDeo Interface for
*niX.
VIDIX was designed and introduced as an interface for fast user-space drivers
@@ -854,7 +856,7 @@
team in graphics mode switching). I.e. main goal of this interface is to
maximize the speed of video playback.
-vo xvidixWhen VIDIX is used as subdevice (-vo vesa:vidix) then
video mode configuration is performed by video output device
@@ -1030,7 +1032,7 @@
Then compile and install as usual.
-Hardware decoding (playing standard MPEG1/2 files) can be done with this command:
@@ -1099,7 +1101,7 @@ for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024 -If you have questions or want to hear feature announcements and take part in discussions on this subject, join our @@ -1129,7 +1131,7 @@ Linux site. Configure should detect your card automatically, compilation should go without problems.
--vo dxr3:prebuf:sync:norm=x:<device>overlay activates the overlay instead of TVOut. It requires