mirror of https://github.com/mpv-player/mpv
659 lines
29 KiB
HTML
659 lines
29 KiB
HTML
<HTML>
|
|
<BODY BGCOLOR=white>
|
|
|
|
<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>
|
|
|
|
<P><B><A NAME=2.2.1>2.2.1. Video output devices</A></B></P>
|
|
|
|
<TABLE BORDER=0>
|
|
|
|
<TD COLSPAN=4><P><B>General:</B></P></TD><TR>
|
|
|
|
<TD> </TD><TD VALIGN=top>x11</TD><TD> </TD><TD>X11 with optional SHM extension</TD><TR>
|
|
<TD></TD><TD VALIGN=top>xv</TD><TD></TD><TD>X11 using overlays with the Xvideo extension (hardware YUV & scaling)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>gl</TD><TD></TD><TD>OpenGL renderer, so far works only with:
|
|
<UL><LI>all cards with Utah-GLX
|
|
<LI>Matrox cards with X/DRI >=4.0.3
|
|
<LI>Radeon with X/DRI CVS</UL></TD><TR>
|
|
<TD></TD><TD VALIGN=top>dga</TD><TD></TD><TD>X11 DGA extension</TD><TR>
|
|
<TD></TD><TD VALIGN=top>fbdev</TD><TD></TD><TD>Output to general framebuffers</TD><TR>
|
|
<TD></TD><TD VALIGN=top>svga</TD><TD></TD><TD>Output to SVGAlib</TD><TR>
|
|
<TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD>
|
|
<CODE>1.1.7:</CODE> supports software scaling<BR>
|
|
<CODE>1.1.8:</CODE> supports Xvideo (hardware scaling/fullscreen)<BR>
|
|
<CODE>1.2.0:</CODE> supports AAlib (-vo aa is very recommended, see below!)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>ggi</TD><TD></TD><TD>similar to SDL</TD><TR>
|
|
<TD></TD><TD VALIGN=top>aa</TD><TD></TD><TD>textmode rendering with AAlib</TD><TR>
|
|
|
|
<TD COLSPAN=4><P><B>Card specific:</B></P></TD><TR>
|
|
|
|
<TD> </TD><TD VALIGN=top>mga</TD><TD> </TD><TD>Matrox G200/G400 hardware YUV overlay via the mga_vid device</TD><TR>
|
|
<TD></TD><TD VALIGN=top>xmga</TD><TD></TD><TD>Matrox G200/G400 overlay (mga_vid) in X11 window<BR>
|
|
(<I>Xv emulation on X 3.3.x!</I>)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>syncfb</TD><TD></TD><TD>Matrox G400 YUV support on framebuffer (obsoleted, use mga/xmga)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>3dfx</TD><TD></TD><TD>Voodoo2/3 hardware YUV (/dev/3dfx) support (not yet tested, maybe
|
|
broken)</TD><TR>
|
|
|
|
<TD COLSPAN=4><P><B>Special:</B></P></TD><TR>
|
|
|
|
<TD> </TD><TD VALIGN=top>png</TD><TD> </TD><TD>PNG files output (use -z switch to set compression)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>pgm</TD><TD></TD><TD>PGM files output (for testing purposes or ffmpeg encoding)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>md5</TD><TD></TD><TD>MD5sum output (for MPEG conformance tests)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>odivx</TD><TD></TD><TD>OpenDivX AVI File writer (use -br to set encoding bitrate)</TD><TR>
|
|
<TD></TD><TD VALIGN=top>null</TD><TD></TD><TD>Null output (for speed tests/benchmarking)</TD><TR>
|
|
</TABLE>
|
|
|
|
<P>NOTE: <I>check the following subsections for details and requirements!</I></P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.1>2.2.1.1. MTRR</A></B></P>
|
|
|
|
<P>It is VERY recommended to set MTRR registers up properly, because they can
|
|
give a big performance boost. First you have to find the base address.
|
|
You have 3 ways to find it:</P>
|
|
|
|
<P><UL>
|
|
<LI>from X11 startup messages, for example:
|
|
<P><CODE>(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000<BR>
|
|
(--) SVGA: Linear framebuffer at 0xD8000000</CODE></P>
|
|
<LI>from /proc/pci (use lspci -v command):
|
|
<P><TABLE>
|
|
<TD VALIGN=top><CODE>01:00.0</CODE></TD><TD><CODE>VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525</CODE></TD><TR>
|
|
<TD></TD><TD><CODE>Memory at d8000000 (32-bit, prefetchable)</CODE></TD><TR>
|
|
</TABLE></P></CODE>
|
|
<LI>from mga_vid kernel driver messages (use dmesg):
|
|
<P><CODE>mga_mem_base = d8000000</CODE></P>
|
|
</UL></P>
|
|
|
|
<P>Then let's find the memory size. This is very easy, just convert video ram
|
|
size to hexadecimal, or use this table:</P>
|
|
|
|
<TABLE BORDER=0>
|
|
<TD> </TD><TD>1 MB</TD><TD WIDTH=10%></TD><TD>0x100000</TD><TR>
|
|
<TD></TD><TD>2 MB</TD><TD></TD><TD>0x200000</TD><TR>
|
|
<TD></TD><TD>4 MB</TD><TD></TD><TD>0x400000</TD><TR>
|
|
<TD></TD><TD>8 MB</TD><TD></TD><TD>0x800000</TD><TR>
|
|
<TD></TD><TD>16 MB</TD><TD></TD><TD>0x1000000</TD><TR>
|
|
<TD></TD><TD>32 MB</TD><TD></TD><TD>0x2000000</TD><TR>
|
|
</TABLE>
|
|
|
|
|
|
<P>You know base address and memory size, let's setup mtrr registers!
|
|
For example, for the Matrox card above (base=0xd8000000) with 32MB
|
|
ram (size=0x2000000) just execute:</P>
|
|
|
|
|
|
<P><CODE> echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr</CODE></P>
|
|
|
|
|
|
<P>Not all CPUs support MTRRs. For example older K6-2's [around 266Mhz,
|
|
stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat /proc/cpuinfo</CODE>'
|
|
to check it</CODE>').</P>
|
|
|
|
<P><B><A NAME=2.2.1.2>2.2.1.2. Xv</A></B></P>
|
|
|
|
<P>Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines
|
|
using the XVideo extension. This is what the option '-vo xv' uses.
|
|
In order to make this work, be sure to check the following:</P>
|
|
<P><UL>
|
|
<LI>You have to use XFree86 4.0.2 or newer (former versions don't have XVideo)
|
|
<LI>Your card actually supports harware acceleration (modern cards do)
|
|
<LI>X loads the XVideo extension, it's something like this:
|
|
|
|
<P><CODE> (II) Loading extension XVideo</CODE></P>
|
|
<P>in /var/log/XFree86.0.log</P>
|
|
|
|
<P>NOTE: this loads only the XFree86's extension. In a good install, this is
|
|
always loaded, and doesn't mean that the _card's_ XVideo support is loaded!</P>
|
|
|
|
<LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the
|
|
part of the XFree86 distribution. It should display a long text, similar
|
|
to this:
|
|
<PRE>
|
|
X-Video Extension version 2.2
|
|
screen #0
|
|
Adaptor #0: "Savage Streams Engine"
|
|
number of ports: 1
|
|
port base: 43
|
|
operations supported: PutImage
|
|
supported visuals:
|
|
depth 16, visualID 0x22
|
|
depth 16, visualID 0x23
|
|
number of attributes: 5
|
|
(...)
|
|
Number of image formats: 7
|
|
id: 0x32595559 (YUY2)
|
|
guid: 59555932-0000-0010-8000-00aa00389b71
|
|
bits per pixel: 16
|
|
number of planes: 1
|
|
type: YUV (packed)
|
|
id: 0x32315659 (YV12)
|
|
guid: 59563132-0000-0010-8000-00aa00389b71
|
|
bits per pixel: 12
|
|
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>And finally, check if <B>MPlayer</B> was compiled with 'xv' support.
|
|
./configure prints this.
|
|
|
|
</UL></P>
|
|
|
|
<P><B><A NAME=2.2.1.2.1>2.2.1.2.1. 3dfx cards</A></B></P>
|
|
|
|
<P>Older 3dfx drivers were known to have problems with XVideo acceleration,
|
|
it didn't support either YUY2 or YV12, and so. Verify that you have
|
|
XFree86 version 4.1.0 or greater, it works ok. Alternatively, you can use
|
|
<A HREF="http://dri.sourceforge.net">DRI</A> cvs.
|
|
If you experience strange effects using -vo xv, try SDL (it has XVideo too)
|
|
and see if it helps. Check the <A HREF="#2.2.1.4">SDL section</A> for details.</P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.2.2>2.2.1.2.2. S3 cards</A></B></P>
|
|
|
|
<P>S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3
|
|
or greater. As for S3 Virge.. sell it.</P>
|
|
|
|
<P><B><A NAME=2.2.1.2.3>2.2.1.2.3. nVidia cards</A></B></P>
|
|
|
|
<P>nVidia isn't a very good choice under Linux.. You'll have to use the
|
|
binary nVidia driver, available at nVidia's website. The standard X
|
|
driver doesn't support XVideo for these cards, due to nVidia's closed
|
|
sources/specifications.</P>
|
|
|
|
<P><UL><LI>Riva128 cards don't have XVideo support even with the nvidia driver :(
|
|
Complain to NVidia.</UL></P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.2.4>2.2.1.2.4. ATI cards</A></B></P>
|
|
|
|
<P>The GATOS driver 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.</P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.3>2.2.1.3. DGA</A></B></P>
|
|
|
|
<P><B><A NAME=2.2.1.3.1>2.2.1.3.1. Summary</A></B></P>
|
|
|
|
<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>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.3.2>2.2.1.3.2. What is DGA</A></B></P>
|
|
|
|
<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 excecutable (NOT
|
|
recommended!).</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>DGA1 provides only direct framebuffer access as described above. For
|
|
switching the resolution of the video signal you have to rely on the
|
|
XVidMode extension.</P>
|
|
|
|
<P>DGA2 incorporates the features of XVidMode extension and also allows
|
|
switching the depth of the display. So you may, although basically
|
|
running a 32 bit depth XServer, 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 XServer's video
|
|
driver that controls this chip. So it does not work on every system ...</P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.3.3>2.2.1.3.3. Installing DGA support for MPlayer</A></B></P>
|
|
|
|
<P>First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:</P>
|
|
|
|
<P> <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 video memory.
|
|
If you want to run it as user, then install <B>MPlayer</B> SUID root:</P>
|
|
|
|
<P><CODE>
|
|
<CODE>chown root /usr/local/bin/mplayer<BR>
|
|
chmod 750 /usr/local/bin/mplayer<BR>
|
|
chmod +s /usr/local/bin/mplayer</CODE></P>
|
|
|
|
|
|
<P>Now it works as a simple user, too.</P>
|
|
|
|
|
|
<P><B>!!!! BUT STAY TUNED !!!!</B><BR>
|
|
This is a <B>BIG</B> security risk! Never do this on a server or on a computer
|
|
can be accessed by more people than only you because they can gain root
|
|
privilegies through suid root mplayer.<BR>
|
|
<B>!!!! SO YOU HAVE BEEN WARNED ... !!!!</B></P>
|
|
|
|
<P>Now use '-vo dga' option, and there you go! (hope so:)
|
|
You should also try if the '-vo sdl:dga' option works for you! It's much
|
|
faster!!!</P>
|
|
|
|
<P><B><A NAME=2.2.1.3.4>2.2.1.3.4. Resolution switching</A></B></P>
|
|
|
|
<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 honouring aspect ratio) of the video data, but the
|
|
XServer only allows switching to resolutions predefined in
|
|
<CODE>/etc/X11/XF86Config</CODE> (<CODE>/etc/X11/XF86Config-4</CODE> for XFree 4.0.X respectively).
|
|
Those are defined by so-called modelines and depend on the capabilites
|
|
of your video hardware. The XServer scans this 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>
|
|
|
|
<P><B><A NAME=2.2.1.3.5>2.2.1.3.5. DGA & MPlayer</A></B></P>
|
|
|
|
<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>
|
|
|
|
<P><B><A NAME=2.2.1.3.6>2.2.1.3.6. Features of the DGA driver</A></B></P>
|
|
|
|
<P>The DGA driver is invoked by specifying -vo dga at the command line.
|
|
The default behaviour is to switch to a resolution matching the original
|
|
resolution of the video as close as possible. It deliberately ignores the
|
|
-vm and -fs switches (enabling of video mode switching and fullscreen) -
|
|
it always tries to cover as much area of your screen as possible by switching
|
|
the video mode, thus refraining to use a single additional cycle of your CPU
|
|
to scale the image.
|
|
If you don't like the mode it chooses you may force it to choose the mode
|
|
matching closest the resolution you specify by -x and -y.
|
|
By providing the -v option, the DGA driver will print, among a lot of other
|
|
things, a list of all resolutions supported by your current XF86-Config
|
|
file.
|
|
Having DGA2 you may also force it to use a certain depth by using the -bpp
|
|
option. Valid depths are 15, 16, 24 and 32. It depends on your hardware
|
|
whether these depths are natively supported or if a (possibly slow)
|
|
conversion has to be done.</P>
|
|
|
|
<P>If you should be lucky enough to have enough offscreen memory left to
|
|
put a whole image there, the DGA driver will use doublebuffering, which
|
|
results in much smoother movie replaying. It will tell you whether double-
|
|
buffering is enabled or not.</P>
|
|
|
|
<P>Doublebuffering means that the next frame of your video is being drawn in
|
|
some offscreen memory while the current frame is being displayed. When the
|
|
next frame is ready, the graphics chip is just told the location in memory
|
|
of the new frame and simply fetches the data to be displayed from there.
|
|
In the meantime the other buffer in memory will be filled again with new
|
|
video data.</P>
|
|
|
|
Doublebuffering may be switched on by using the option -double and may be
|
|
disabled with -nodouble. Current default option is to disable
|
|
doublebuffering. When using the DGA driver, onscreen display (OSD) only
|
|
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>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.3.7>2.2.1.3.7. Speed issues</A></B></P>
|
|
|
|
<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>If you have a slow system, better use 15 or 16bit depth since they require
|
|
only half the memory bandwidth of a 32 bit display.</P>
|
|
|
|
<P>Using a depth of 24bit is even a good idea if your card natively just supports
|
|
32 bit depth since it transfers 25% less data compared to the 32/32 mode.</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>
|
|
|
|
<P><B><A NAME=2.2.1.3.8>2.2.1.3.8. Known bugs</A></B></P>
|
|
|
|
<P>Well, according to some developpers 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>
|
|
|
|
<P><UL>
|
|
<LI>with XFree 4.0.3 and nv.o there is a bug resulting in strange colors
|
|
<LI>ATI driver requires to switch mode back more than once after finishing
|
|
using of DGA
|
|
<LI>some drivers simply fail to switch back to normal resolution (use
|
|
Ctrl-Alt-Keypad +, - to switch back manually)
|
|
<LI>some drivers simply display strange colors
|
|
<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>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>OSD only works with doublebuffering enabled
|
|
</UL></P>
|
|
|
|
<P><B><A NAME=2.2.1.3.9>2.2.1.3.9. Future work</A></B></P>
|
|
|
|
<P><UL><LI>use of the new X11 render interface for OSD
|
|
<LI>where is my TODO list ???? :-(((</UL></P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.3.A>2.2.1.3.A. Some modelines</A></B></P>
|
|
|
|
<PRE>
|
|
Section "Modes"
|
|
Identifier "Modes[0]"
|
|
Modeline "800x600" 40 800 840 968 1056 600 601 605 628
|
|
Modeline "712x600" 35.0 712 740 850 900 400 410 412 425
|
|
Modeline "640x480" 25.175 640 664 760 800 480 491 493 525
|
|
Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan
|
|
Modeline "352x288" 25.10 352 368 416 432 288 296 290 310
|
|
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 XServer driver
|
|
module.</P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.3.B>2.2.1.3.B. Bug Reports</A></B></P>
|
|
|
|
<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 (acki@acki-netz.de, www.acki-netz.de)</I></P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.4>2.2.1.4. SDL</A></B></P>
|
|
|
|
<P>Here are some notes about SDL out in <B>MPlayer</B>.</P>
|
|
|
|
|
|
|
|
<P><TABLE BORDER=0>
|
|
<TD COLSPAN=4><P><B>There are several commandline switches for SDL:</B></P></TD><TR>
|
|
<TD> </TD><TD>-vo sdl:name</TD><TD> </TD><TD>
|
|
specifies sdl video driver to use (ie. aalib, dga, x11)</TD><TR>
|
|
<TD></TD><TD>-ao sdl:name</TD><TD></TD><TD>specifies sdl audio driver to use (ie. dsp,
|
|
esd, arts)</TD><TR>
|
|
<TD></TD><TD>-noxv</TD><TD></TD><TD>disables Xvideo hardware acceleration</TD><TR>
|
|
<TD></TD><TD>-forcexv</TD><TD></TD><TD>tries to force Xvideo acceleration</TD><TR>
|
|
|
|
<TD COLSPAN=4><P><B>SDL Keys:</B></P></TD><TR>
|
|
|
|
<TD></TD><TD>F</TD><TD></TD><TD>toggles fullscreen/windowed mode</TD><TR>
|
|
<TD></TD><TD>C</TD><TD></TD><TD>cycles available fullscreen modes</TD><TR>
|
|
<TD></TD><TD>W/S</TD><TD></TD><TD>mappings for * and / (mixer control)</TD><TR>
|
|
|
|
</TABLE></P>
|
|
|
|
<P><B>KNOWN BUGS:</B></P>
|
|
<P><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).
|
|
</UL></P>
|
|
|
|
<P><B><A NAME=2.2.1.5>2.2.1.5. SVGAlib</A></B></P>
|
|
|
|
<P>If you don't have X, you can use the SVGAlib target! Be sure not to use the
|
|
-fs switch, since it toggles the usage of the software scaler, and it's
|
|
SLOOOW now, unless you have a real fast CPU (and/or MTRR?). :(</P>
|
|
|
|
<P>Of course 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 & monitor.</P>
|
|
|
|
<P><B><A NAME=2.2.1.6>2.2.1.6. Framebuffer output (FBdev)</A></B></P>
|
|
|
|
<P>Whether to build the FBdev target is autodetected during ./configure .
|
|
Read the framebuffer documentation in the kernel sources
|
|
(Documentation/fb/*) for info on how to enable it, etc.. !</P>
|
|
|
|
<P>If your card doesn't support VBE 2.0 standard (older ISA/PCI
|
|
cards, such as S3 Trio64), only VBE 1.2 (or older?) :
|
|
Well, VESAfb is still available, but you'll have to load SciTech Display
|
|
Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or
|
|
whatever. And don't forget to register your UniVBE ;))</P>
|
|
|
|
<P>The FBdev output takes some additional parameters above the others:</P>
|
|
|
|
<P><TABLE BORDER=0>
|
|
<TD> </TD><TD>-fb</TD><TD> </TD><TD>
|
|
specify the framebuffer device to use (/dev/fd0)</TD><TR>
|
|
<TD></TD><TD>-fbmode</TD><TD></TD><TD>mode name to use (according to /etc/fb.modes)</TD><TR>
|
|
<TD></TD><TD>-fbmodeconfig</TD><TD></TD><TD> config file of modes (default /etc/fb.modes)</TD><TR>
|
|
<TD></TD><TD>-monitor_hfreq</TD><TD></TD><TD ROWSPAN=3>IMPORTANT values, see example.conf</TD><TR>
|
|
<TD></TD><TD>-monitor_vfreq</TD><TD></TD><TR>
|
|
<TD></TD><TD>-monitor_dotclock</TD><TD></TD><TR>
|
|
</TABLE></P>
|
|
|
|
<P>If you want to change to a specific mode, then use</P>
|
|
|
|
<P><CODE> mplayer -vm -fbmode (NameOfMode) filename</CODE></P>
|
|
|
|
<P><UL><LI><B>-vm</B> alone will choose the most suitable mode from /etc/fb.modes . Can be
|
|
used together with -x and -y options too. The -flip option is supported only
|
|
if the movie's pixel format matches the video mode's pixel format.
|
|
Pay attention to the bpp value, fbdev driver tries to use the current,
|
|
or if you specify the -bpp option, then that.
|
|
<LI><B>-zoom</B> option isn't supported (software scaling is slow). -fs option
|
|
isn't supported. You can't use 8bpp (or less) modes.</UL></P>
|
|
|
|
<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>
|
|
|
|
<P><B><A NAME=2.2.1.7>2.2.1.7. Matrox framebuffer (mga_vid)</A></B></P>
|
|
|
|
<P>This section is about the Matrox G200/G400/G450 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>To use it, you first have to compile mga_vid.o:</P>
|
|
|
|
<P><CODE> cd drivers<BR>
|
|
make</CODE></P>
|
|
|
|
<P>Then create /dev/mga_vid device:</P>
|
|
|
|
<P><CODE> mknod /dev/mga_vid c 178 0</CODE></P>
|
|
|
|
<P>and load the driver with</P>
|
|
|
|
<P><CODE> insmod mga_vid.o</CODE></P>
|
|
|
|
<P>You should verify the memory size detection using the 'dmesg' command. If
|
|
it's bad, use the mga_ram_size option (rmmod mga_vid first), specify card's
|
|
memory size in MB:</P>
|
|
|
|
<P><CODE> insmod mga_vid.o mga_ram_size=16</CODE></P>
|
|
|
|
<P>To make it load/unload automatically when needed, insert the following line
|
|
at the end of /etc/modules.conf:</P>
|
|
|
|
<P><CODE> alias char-major-178 mga_vid</CODE></P>
|
|
|
|
<P>Then run</P>
|
|
|
|
<P><CODE> depmod -a</CODE></P>
|
|
|
|
<P>Now you have to (re)compile <B>MPlayer</B>, ./configure will detect /dev/mga_vid
|
|
and build the 'mga' driver. Using it from <B>MPlayer</B> goes by '-vo mga' if
|
|
you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.</P>
|
|
|
|
<P>Note: '-vo xmga' works under XFree86 4.x.x, but it conflicts with the Xv
|
|
driver, so avoid using both. If you messed up Xv with mga, try running
|
|
<B>MPlayer</B> with '-vo mga' . It should fix Xv.</P>
|
|
|
|
|
|
<P><B><A NAME=2.2.1.8>2.2.1.8. SiS 6326 framebuffer (sis_vid)</A></B></P>
|
|
|
|
<P>SiS 6326 YUV Framebuffer driver -> sis_vid kernel driver</P>
|
|
|
|
<P>Its interface should be compatible with the mga_vid, but the driver was not
|
|
updated after the mga_vid changes, so it's outdated now. Volunteers
|
|
needed to test it and bring the code up-to-date.</P>
|
|
|
|
<P><B><A NAME=2.2.1.9>2.2.1.9. 3dfx YUV support</A></B></P>
|
|
|
|
<P>3dfx has native YUV+scaler support, using /dev/3dfx (tdfx.o driver?)
|
|
The /dev/3dfx kernel driver exists only for 2.2.x kernels, for use with
|
|
Glide 2.x Linux ports. It's not tested with <B>MPlayer</B>, and so no more
|
|
supported. Volunteers needed to test it and bring the code up-to-date.</P>
|
|
|
|
<P><B><A NAME=2.2.1.10>2.2.1.10. OpenGL output</A></B></P>
|
|
|
|
<P><B>MPlayer</B> support displaying movies using OpenGL. Unfortunately, not all
|
|
drivers support this ability. For example the Utah-GLX drivers
|
|
(for XFree86 3.3.6) have it, with all cards.
|
|
See <A HREF="http://utah-glx.sourceforge.net">http://utah-glx.sourceforge.net</A>
|
|
for details about how to install it.</P>
|
|
|
|
<P>XFree86(DRI) >= 4.0.3 supports it only with Matrox, and Radeon cards.
|
|
See <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> for download,
|
|
and installation instructions.</P>
|
|
|
|
<P><B><A NAME=2.2.1.11>2.2.1.11. AAlib - text mode displaying</B></P>
|
|
|
|
<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>
|
|
|
|
<P><TABLE BORDER=0>
|
|
<TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD><TR>
|
|
<TD> </TD><TD>1</TD><TD> </TD><TD>decrease contrast</TD><TR>
|
|
<TD></TD><TD>2</TD><TD></TD><TD>increase contrast</TD><TR>
|
|
<TD></TD><TD>3</TD><TD></TD><TD>decrease brightness</TD><TR>
|
|
<TD></TD><TD>4</TD><TD></TD><TD>increase brightness</TD><TR>
|
|
<TD></TD><TD>5</TD><TD></TD><TD>switch fast rendering on/off</TD><TR>
|
|
<TD></TD><TD>6</TD><TD></TD><TD>set dithering mode (none, error distribution, floyd steinberg)</TD><TR>
|
|
<TD></TD><TD>7</TD><TD></TD><TD>invert image</TD><TR>
|
|
<TD></TD><TD>a</TD><TD></TD><TD>toggles between aa and mplayer control)</TD><TR>
|
|
|
|
<TD COLSPAN=4><P><B>The following command line options can be used:</B></P></TD><TR>
|
|
|
|
<TD></TD><TD>-aaosdcolor=V</TD><TD></TD><TD>change osd color</TD><TR>
|
|
<TD></TD><TD>-aasubcolor=V</TD><TD></TD><TD>change subtitle color</TD><TR>
|
|
<TD COLSPAN=3></TD><TD><P><I>where V can be: (0/normal, 1/dark, 2/bold, 3/boldfont, 4/reverse, 5/special)</P></TD><TR>
|
|
|
|
<TD COLSPAN=4><P><B>AAlib itselves provides a large sum of options.
|
|
Here are some important:</P></B></TD><TR>
|
|
|
|
<TD></TD><TD>-aadriver</TD><TD></TD><TD>set recommended aa driver (X11, curses, linux)</TD><TR>
|
|
<TD></TD><TD>-aaextended</TD><TD></TD><TD>use all 256 characters</TD><TR>
|
|
<TD></TD><TD>-aaeight</TD><TD></TD><TD>use eight bit ascii</TD><TR>
|
|
<TD></TD><TD>-aahelp</TD><TD></TD><TD>prints out all aalib options</TD><TR>
|
|
</TABLE></P>
|
|
|
|
<P>NOTE: the rendering is very CPU intensive, especially when using AA-on-X
|
|
(using aalib on X), and it's least CPU intensive on standard,
|
|
non-framebuffer console. Use SVGATextMode to set up a big textmode,
|
|
then enjoy! (secondary head Hercules cards rock :)) (anyone can enhance
|
|
bdev to do conversion/dithering to hgafb? Would be neat :)</P>
|
|
|
|
<P>Use the -framedrop option if your comp isn't fast enough to render all frames!</P>
|
|
|
|
<P>Playing on terminal you'll get better speed and quality using the linux driver, not
|
|
curses (-aadriver linux). But therefore you need write access on /dev/vcsa<terminal>!
|
|
That isn't autodetected by aalib, bu vo_aa tries to find the best mode.
|
|
See http://aa-project.sourceforge.net/tune/ for further tuning issues.</P>
|
|
|
|
<P><B><A NAME=2.2.1.A>2.2.1.A. TV-out support</A></B></P>
|
|
|
|
<P><B><A NAME=2.2.1.A.1>2.2.1.A.1. Matrox cards</A></B></P>
|
|
|
|
<P><I> What I'd love to see in mplayer is the the same feature that I see in my
|
|
windows box. When I start a movie in windows (in a window or in full screen)
|
|
the movie is also redirected to the tv-out and I can also see it full screen
|
|
on my tv. I love this feature and was wondering how hard it would be to add
|
|
such a feature to mplayer.</I></P>
|
|
|
|
<P>It's a driver limitation. BES (Back-End Scaler, it's the overlay generator
|
|
and YUV scaling engine of G200/G400/G450 cards) works only with CRTC1.
|
|
Normally, CRTC1 (textmode, every bpp gfx and BES) is routed to HEAD1,
|
|
and CRTC2 (only 16/32bpp gfx) is routed to HEAD2 (TV-out).</P>
|
|
|
|
<P>Under linux, you have two choices to get TV-out working:</P>
|
|
|
|
<P><UL>
|
|
<LI>Using X 4.0.x + the HAL driver from matrox, so you'll get dual-head
|
|
support, and you'll be able to redirect second output to the TV.
|
|
Unfortunately it has Macrovision encryption enabled, so it will
|
|
only work on directly-connected TV, no through VCR.
|
|
Other problem is that Xv doesn't work on the second head.
|
|
(I don't know how Windows solve it, maybe it swaps the CRTCs between
|
|
the heads, or just uses YUV framebuffer of second DAC with some trick)
|
|
<LI>Using matroxfb with dual-head support enabled (2.4.x kernels).
|
|
You'll be able to get a framebuffer console (using CRTC2, so it's
|
|
slow), and TV-out (using CRTC1, with BES support).
|
|
You have to forget X while using this kind of TV-out! :(
|
|
</UL></P>
|
|
|
|
<P>Follow these instructions:</P>
|
|
|
|
<P><UL>
|
|
<LI>Compile all the matrox-related things to modules in the kernel.
|
|
(you MUST compile them to modules, at least I couldn't get them
|
|
working built-in yet)
|
|
[reboot to new kernel & install modules, but don't load them yet!]
|
|
<P><CODE>
|
|
cd TVout<BR>
|
|
./compile.sh</CODE></P>
|
|
<LI>Run the 'modules' script from the TV-out directory of mplayer.
|
|
It will switch your console to framebuffer.
|
|
Change to tty1 (ALT+F1)!
|
|
Now run the script 'independent', it will set up your tty's:
|
|
<P>tty 1,2: fb console, CRTC2, head 1 (monitor)<BR>
|
|
tty 3,4,5...: framebuffer+BES, CRTC1, head 2 (TV-out)</P>
|
|
You should run the scripts TV-* and Mon-* to set up resolutions:
|
|
<P>change to tty1 (ALT+F1), and run Mon-* (one of them)<BR>
|
|
change to tty3 (ALT+F3) and then back to tty1 (ALT+F1)</P>
|
|
(this change will select tty3 on /dev/fb1 - tricky)<BR>
|
|
<P>run TV-* (one of them)</P>
|
|
(now you'll get a console on your PAL TV - don't know about NTSC)
|
|
<P>Now if you start mplayer (on tty1), the picture will show up on
|
|
the tty3, so you'll see it on your TV or second monitor.</P>
|
|
</UL></P>
|
|
|
|
<P>Yes, it is a bit 'hack' now. But I'm waiting for the marvel
|
|
project to be finished, it will provide real TV-out drivers, I hope.</P>
|
|
|
|
<P>My current problem is that BES is working only with CRTC1. So picture
|
|
will always shown up on head routed to CRTC1 (normaly the monitor),
|
|
so i have to swap CRTC's, but this way your console will framebuffer
|
|
(CRTC2 can't do text-mode) and a bit slow (no acceleration). :(</P>
|
|
|
|
<P><I>Anyway i also just get monochrome output on the tv ...</I>
|
|
Maybe you have NTSC TV? Or just didn't run one of TV-* scripts.</P>
|
|
|
|
</BODY>
|
|
</HTML>
|