Mercurial > mplayer.hg
annotate DOCS/video.html @ 1975:93028c9ee819
ready
author | gabucino |
---|---|
date | Wed, 26 Sep 2001 23:48:12 +0000 |
parents | 7fb1fb6f295f |
children | c4dbfa55d873 |
rev | line source |
---|---|
1612 | 1 <HTML> |
1704 | 2 <BODY BGCOLOR=white> |
3 | |
4 <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2> | |
1612 | 5 |
1682 | 6 <P><B><A NAME=2.2.1>2.2.1. Video output devices</A></B></P> |
1612 | 7 |
1682 | 8 <TABLE BORDER=0> |
9 | |
10 <TD COLSPAN=4><P><B>General:</B></P></TD><TR> | |
1612 | 11 |
1682 | 12 <TD> </TD><TD VALIGN=top>x11</TD><TD> </TD><TD>X11 with optional SHM extension</TD><TR> |
13 <TD></TD><TD VALIGN=top>xv</TD><TD></TD><TD>X11 using overlays with the Xvideo extension (hardware YUV & scaling)</TD><TR> | |
14 <TD></TD><TD VALIGN=top>gl</TD><TD></TD><TD>OpenGL renderer, so far works only with: | |
15 <UL><LI>all cards with Utah-GLX | |
16 <LI>Matrox cards with X/DRI >=4.0.3 | |
17 <LI>Radeon with X/DRI CVS</UL></TD><TR> | |
18 <TD></TD><TD VALIGN=top>dga</TD><TD></TD><TD>X11 DGA extension</TD><TR> | |
19 <TD></TD><TD VALIGN=top>fbdev</TD><TD></TD><TD>Output to general framebuffers</TD><TR> | |
20 <TD></TD><TD VALIGN=top>svga</TD><TD></TD><TD>Output to SVGAlib</TD><TR> | |
21 <TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD> | |
22 <CODE>1.1.7:</CODE> supports software scaling<BR> | |
23 <CODE>1.1.8:</CODE> supports Xvideo (hardware scaling/fullscreen)<BR> | |
24 <CODE>1.2.0:</CODE> supports AAlib (-vo aa is very recommended, see below!)</TD><TR> | |
25 <TD></TD><TD VALIGN=top>ggi</TD><TD></TD><TD>similar to SDL</TD><TR> | |
26 <TD></TD><TD VALIGN=top>aa</TD><TD></TD><TD>textmode rendering with AAlib</TD><TR> | |
27 | |
28 <TD COLSPAN=4><P><B>Card specific:</B></P></TD><TR> | |
1612 | 29 |
1682 | 30 <TD> </TD><TD VALIGN=top>mga</TD><TD> </TD><TD>Matrox G200/G400 hardware YUV overlay via the mga_vid device</TD><TR> |
31 <TD></TD><TD VALIGN=top>xmga</TD><TD></TD><TD>Matrox G200/G400 overlay (mga_vid) in X11 window<BR> | |
32 (<I>Xv emulation on X 3.3.x!</I>)</TD><TR> | |
33 <TD></TD><TD VALIGN=top>syncfb</TD><TD></TD><TD>Matrox G400 YUV support on framebuffer (obsoleted, use mga/xmga)</TD><TR> | |
34 <TD></TD><TD VALIGN=top>3dfx</TD><TD></TD><TD>Voodoo2/3 hardware YUV (/dev/3dfx) support (not yet tested, maybe | |
35 broken)</TD><TR> | |
36 | |
37 <TD COLSPAN=4><P><B>Special:</B></P></TD><TR> | |
1612 | 38 |
1682 | 39 <TD> </TD><TD VALIGN=top>png</TD><TD> </TD><TD>PNG files output (use -z switch to set compression)</TD><TR> |
40 <TD></TD><TD VALIGN=top>pgm</TD><TD></TD><TD>PGM files output (for testing purposes or ffmpeg encoding)</TD><TR> | |
41 <TD></TD><TD VALIGN=top>md5</TD><TD></TD><TD>MD5sum output (for MPEG conformance tests)</TD><TR> | |
1898 | 42 <TD></TD><TD VALIGN=top>odivx</TD><TD></TD><TD>OpenDivX AVI File writer (use -br to set encoding bitrate) (<B>WITHOUT SOUND</B>!)</TD><TR> |
1682 | 43 <TD></TD><TD VALIGN=top>null</TD><TD></TD><TD>Null output (for speed tests/benchmarking)</TD><TR> |
44 </TABLE> | |
1612 | 45 |
1682 | 46 <P>NOTE: <I>check the following subsections for details and requirements!</I></P> |
1612 | 47 |
48 | |
1682 | 49 <P><B><A NAME=2.2.1.1>2.2.1.1. MTRR</A></B></P> |
1612 | 50 |
1946 | 51 <P>It is VERY recommended to check if the MTRR registers are set up properly, |
52 because they can give a big performance boost.</P> | |
53 | |
54 <P>Do a '<CODE>cat /proc/mtrr</CODE>' :</P> | |
55 | |
56 <P><CODE> | |
57 --($:~)-- cat /proc/mtrr<BR> | |
58 reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9<BR> | |
59 reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<BR> | |
60 </CODE></P> | |
61 | |
62 <P>It's right, shows my Matrox G400 with 16Mb memory. I did this from | |
63 XFree 4.x.x , which sets up MTRR registers automatically.</P> | |
64 | |
65 If nothing worked, you have to do it manually. First, you have to find the base | |
66 address. | |
1682 | 67 You have 3 ways to find it:</P> |
1612 | 68 |
1682 | 69 <P><UL> |
70 <LI>from X11 startup messages, for example: | |
71 <P><CODE>(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000<BR> | |
72 (--) SVGA: Linear framebuffer at 0xD8000000</CODE></P> | |
73 <LI>from /proc/pci (use lspci -v command): | |
74 <P><TABLE> | |
75 <TD VALIGN=top><CODE>01:00.0</CODE></TD><TD><CODE>VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525</CODE></TD><TR> | |
76 <TD></TD><TD><CODE>Memory at d8000000 (32-bit, prefetchable)</CODE></TD><TR> | |
77 </TABLE></P></CODE> | |
78 <LI>from mga_vid kernel driver messages (use dmesg): | |
79 <P><CODE>mga_mem_base = d8000000</CODE></P> | |
80 </UL></P> | |
1612 | 81 |
1682 | 82 <P>Then let's find the memory size. This is very easy, just convert video ram |
83 size to hexadecimal, or use this table:</P> | |
1612 | 84 |
1682 | 85 <TABLE BORDER=0> |
86 <TD> </TD><TD>1 MB</TD><TD WIDTH=10%></TD><TD>0x100000</TD><TR> | |
87 <TD></TD><TD>2 MB</TD><TD></TD><TD>0x200000</TD><TR> | |
88 <TD></TD><TD>4 MB</TD><TD></TD><TD>0x400000</TD><TR> | |
89 <TD></TD><TD>8 MB</TD><TD></TD><TD>0x800000</TD><TR> | |
90 <TD></TD><TD>16 MB</TD><TD></TD><TD>0x1000000</TD><TR> | |
91 <TD></TD><TD>32 MB</TD><TD></TD><TD>0x2000000</TD><TR> | |
92 </TABLE> | |
1612 | 93 |
94 | |
1682 | 95 <P>You know base address and memory size, let's setup mtrr registers! |
96 For example, for the Matrox card above (base=0xd8000000) with 32MB | |
97 ram (size=0x2000000) just execute:</P> | |
1612 | 98 |
99 | |
1682 | 100 <P><CODE> echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr</CODE></P> |
1612 | 101 |
102 | |
1682 | 103 <P>Not all CPUs support MTRRs. For example older K6-2's [around 266Mhz, |
104 stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat /proc/cpuinfo</CODE>' | |
1686 | 105 to check it</CODE>').</P> |
1612 | 106 |
1682 | 107 <P><B><A NAME=2.2.1.2>2.2.1.2. Xv</A></B></P> |
1612 | 108 |
1682 | 109 <P>Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines |
110 using the XVideo extension. This is what the option '-vo xv' uses. | |
111 In order to make this work, be sure to check the following:</P> | |
112 <P><UL> | |
113 <LI>You have to use XFree86 4.0.2 or newer (former versions don't have XVideo) | |
114 <LI>Your card actually supports harware acceleration (modern cards do) | |
115 <LI>X loads the XVideo extension, it's something like this: | |
1612 | 116 |
1682 | 117 <P><CODE> (II) Loading extension XVideo</CODE></P> |
118 <P>in /var/log/XFree86.0.log</P> | |
1612 | 119 |
1682 | 120 <P>NOTE: this loads only the XFree86's extension. In a good install, this is |
121 always loaded, and doesn't mean that the _card's_ XVideo support is loaded!</P> | |
1612 | 122 |
1682 | 123 <LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the |
124 part of the XFree86 distribution. It should display a long text, similar | |
125 to this: | |
126 <PRE> | |
1612 | 127 X-Video Extension version 2.2 |
128 screen #0 | |
129 Adaptor #0: "Savage Streams Engine" | |
130 number of ports: 1 | |
131 port base: 43 | |
132 operations supported: PutImage | |
133 supported visuals: | |
134 depth 16, visualID 0x22 | |
135 depth 16, visualID 0x23 | |
136 number of attributes: 5 | |
137 (...) | |
138 Number of image formats: 7 | |
139 id: 0x32595559 (YUY2) | |
140 guid: 59555932-0000-0010-8000-00aa00389b71 | |
141 bits per pixel: 16 | |
142 number of planes: 1 | |
143 type: YUV (packed) | |
144 id: 0x32315659 (YV12) | |
145 guid: 59563132-0000-0010-8000-00aa00389b71 | |
146 bits per pixel: 12 | |
147 number of planes: 3 | |
148 type: YUV (planar) | |
149 (...etc...) | |
1682 | 150 </PRE> |
1612 | 151 |
1682 | 152 <P>It must support YUY2 packed, and YV12 planar pixel formats to be |
153 usable with <B>MPlayer</B>.</P> | |
1612 | 154 |
1682 | 155 <LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support. |
156 ./configure prints this. | |
1612 | 157 |
1682 | 158 </UL></P> |
159 | |
160 <P><B><A NAME=2.2.1.2.1>2.2.1.2.1. 3dfx cards</A></B></P> | |
1612 | 161 |
1682 | 162 <P>Older 3dfx drivers were known to have problems with XVideo acceleration, |
163 it didn't support either YUY2 or YV12, and so. Verify that you have | |
164 XFree86 version 4.1.0 or greater, it works ok. Alternatively, you can use | |
165 <A HREF="http://dri.sourceforge.net">DRI</A> cvs. | |
166 If you experience strange effects using -vo xv, try SDL (it has XVideo too) | |
167 and see if it helps. Check the <A HREF="#2.2.1.4">SDL section</A> for details.</P> | |
1612 | 168 |
169 | |
1682 | 170 <P><B><A NAME=2.2.1.2.2>2.2.1.2.2. S3 cards</A></B></P> |
171 | |
172 <P>S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3 | |
173 or greater. As for S3 Virge.. sell it.</P> | |
174 | |
175 <P><B><A NAME=2.2.1.2.3>2.2.1.2.3. nVidia cards</A></B></P> | |
1612 | 176 |
1682 | 177 <P>nVidia isn't a very good choice under Linux.. You'll have to use the |
178 binary nVidia driver, available at nVidia's website. The standard X | |
179 driver doesn't support XVideo for these cards, due to nVidia's closed | |
180 sources/specifications.</P> | |
1612 | 181 |
1682 | 182 <P><UL><LI>Riva128 cards don't have XVideo support even with the nvidia driver :( |
183 Complain to NVidia.</UL></P> | |
1612 | 184 |
185 | |
1682 | 186 <P><B><A NAME=2.2.1.2.4>2.2.1.2.4. ATI cards</A></B></P> |
1612 | 187 |
1920 | 188 <P> |
189 <LI>The GATOS driver has VSYNC enabled by default. It means that decoding speed | |
1682 | 190 (!) is synced to the monitor's refresh rate. If playing seems to be slow, try |
1920 | 191 disabling VSYNC somehow, or set refresh rate to n*(fps of the movie) Hz.</LI> |
192 | |
193 <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version | |
194 4.1.0 doesn't. No TV-out support.</LI> | |
195 </P> | |
1612 | 196 |
197 | |
1922
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
198 <P><B><A NAME=2.2.1.2.5>2.2.1.2.5. NeoMagic cards</A></B></P> |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
199 |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
200 <P> |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
201 These cards can be found in many laptops. Under Linux, their peak is only DGA. |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
202 Unfortunately, the DGA driver in X 4.1.0 doesn't work, you'll have to wait for |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
203 4.2.0, or download a modified driver for 4.0.3 or 4.1.0 from here : |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
204 <A HREF="http://www.mplayerhq.hu/MPlayer/incoming/NeoMagic-driver">http://www.mplayerhq.hu/MPlayer/incoming/NeoMagic-driver</A> |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
205 (there is also the patch to the driver's source).<BR> |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
206 Drivers provided by <A HREF="mailto:tomee@cpi.pl">Tomek Jarzynka</A>. |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
207 </P> |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
208 |
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
209 |
1682 | 210 <P><B><A NAME=2.2.1.3>2.2.1.3. DGA</A></B></P> |
1612 | 211 |
1682 | 212 <P><B><A NAME=2.2.1.3.1>2.2.1.3.1. Summary</A></B></P> |
1612 | 213 |
1682 | 214 <P>This document tries to explain in some words what DGA is in general and |
215 what the DGA video output driver for mplayer can do (and what it can't).</P> | |
1612 | 216 |
217 | |
1682 | 218 <P><B><A NAME=2.2.1.3.2>2.2.1.3.2. What is DGA</A></B></P> |
1612 | 219 |
1682 | 220 <P>DGA is short for Direct Graphics Access and is a means for a program to |
221 bypass the X-Server and directly modifying the framebuffer memory. | |
222 Technically spoken this happens by mapping the framebuffer memory into | |
223 the memory range of your process. This is allowed by the kernel only | |
224 if you have superuser privileges. You can get these either by logging in | |
225 as root or by setting the suid bit on the mplayer excecutable (NOT | |
226 recommended!).</P> | |
1612 | 227 |
1682 | 228 <P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was |
229 introduced with XFree 4.0.1.</P> | |
1612 | 230 |
1682 | 231 <P>DGA1 provides only direct framebuffer access as described above. For |
232 switching the resolution of the video signal you have to rely on the | |
233 XVidMode extension.</P> | |
1612 | 234 |
1682 | 235 <P>DGA2 incorporates the features of XVidMode extension and also allows |
236 switching the depth of the display. So you may, although basically | |
237 running a 32 bit depth XServer, switch to a depth of 15 bits and vice | |
238 versa. </P> | |
1612 | 239 |
1682 | 240 <P>However DGA has some drawbacks. It seems it is somewhat dependent on the |
241 graphics chip you use and on the implementation of the XServer's video | |
242 driver that controls this chip. So it does not work on every system ...</P> | |
1612 | 243 |
244 | |
1682 | 245 <P><B><A NAME=2.2.1.3.3>2.2.1.3.3. Installing DGA support for MPlayer</A></B></P> |
246 | |
247 <P>First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:</P> | |
248 | |
249 <P> <CODE>(II) Loading extension XFree86-DGA</CODE></P> | |
250 | |
251 <P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! | |
252 <B>MPlayer</B>'s DGA driver is autodetected on ./configure, or you can force it | |
253 with --enable-dga.</P> | |
1612 | 254 |
1682 | 255 <P>If the driver couldn't switch to a smaller resolution, experiment with |
256 switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that | |
257 the movie fits in. There is no converter right now.. :(</P> | |
1612 | 258 |
1682 | 259 <P>Become ROOT. DGA needs root access to be able to write directly video memory. |
260 If you want to run it as user, then install <B>MPlayer</B> SUID root:</P> | |
1612 | 261 |
1682 | 262 <P><CODE> |
263 <CODE>chown root /usr/local/bin/mplayer<BR> | |
1686 | 264 chmod 750 /usr/local/bin/mplayer<BR> |
265 chmod +s /usr/local/bin/mplayer</CODE></P> | |
1612 | 266 |
267 | |
1682 | 268 <P>Now it works as a simple user, too.</P> |
1612 | 269 |
270 | |
1682 | 271 <P><B>!!!! BUT STAY TUNED !!!!</B><BR> |
272 This is a <B>BIG</B> security risk! Never do this on a server or on a computer | |
273 can be accessed by more people than only you because they can gain root | |
274 privilegies through suid root mplayer.<BR> | |
275 <B>!!!! SO YOU HAVE BEEN WARNED ... !!!!</B></P> | |
276 | |
277 <P>Now use '-vo dga' option, and there you go! (hope so:) | |
278 You should also try if the '-vo sdl:dga' option works for you! It's much | |
279 faster!!!</P> | |
280 | |
281 <P><B><A NAME=2.2.1.3.4>2.2.1.3.4. Resolution switching</A></B></P> | |
282 | |
283 <P>The DGA driver allows for switching the resolution of the output signal. | |
284 This avoids the need for doing (slow) software scaling and at the same | |
285 time provides a fullscreen image. Ideally it would switch to the exact | |
286 resolution (except for honouring aspect ratio) of the video data, but the | |
1686 | 287 XServer only allows switching to resolutions predefined in |
1682 | 288 <CODE>/etc/X11/XF86Config</CODE> (<CODE>/etc/X11/XF86Config-4</CODE> for XFree 4.0.X respectively). |
289 Those are defined by so-called modelines and depend on the capabilites | |
290 of your video hardware. The XServer scans this config file on startup and | |
291 disables the modelines not suitable for your hardware. You can find | |
292 out which modes survive with the X11 log file. It can be found at: | |
293 <CODE>/var/log/XFree86.0.log</CODE>.</P> | |
294 <P>See appendix A for some sample modeline definitions.</P> | |
295 | |
296 <P><B><A NAME=2.2.1.3.5>2.2.1.3.5. DGA & MPlayer</A></B></P> | |
1612 | 297 |
1682 | 298 <P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to make |
299 use of it (-vo sdl:dga) and within the DGA driver (-vo dga). | |
300 The above said is true for both; in the following sections I'll explain | |
301 how the DGA driver for <B>MPlayer</B> works.</P> | |
1612 | 302 |
1682 | 303 <P><B><A NAME=2.2.1.3.6>2.2.1.3.6. Features of the DGA driver</A></B></P> |
304 | |
305 <P>The DGA driver is invoked by specifying -vo dga at the command line. | |
306 The default behaviour is to switch to a resolution matching the original | |
307 resolution of the video as close as possible. It deliberately ignores the | |
308 -vm and -fs switches (enabling of video mode switching and fullscreen) - | |
309 it always tries to cover as much area of your screen as possible by switching | |
310 the video mode, thus refraining to use a single additional cycle of your CPU | |
311 to scale the image. | |
312 If you don't like the mode it chooses you may force it to choose the mode | |
313 matching closest the resolution you specify by -x and -y. | |
314 By providing the -v option, the DGA driver will print, among a lot of other | |
315 things, a list of all resolutions supported by your current XF86-Config | |
316 file. | |
317 Having DGA2 you may also force it to use a certain depth by using the -bpp | |
318 option. Valid depths are 15, 16, 24 and 32. It depends on your hardware | |
319 whether these depths are natively supported or if a (possibly slow) | |
320 conversion has to be done.</P> | |
321 | |
322 <P>If you should be lucky enough to have enough offscreen memory left to | |
323 put a whole image there, the DGA driver will use doublebuffering, which | |
324 results in much smoother movie replaying. It will tell you whether double- | |
325 buffering is enabled or not.</P> | |
1612 | 326 |
1682 | 327 <P>Doublebuffering means that the next frame of your video is being drawn in |
328 some offscreen memory while the current frame is being displayed. When the | |
329 next frame is ready, the graphics chip is just told the location in memory | |
330 of the new frame and simply fetches the data to be displayed from there. | |
331 In the meantime the other buffer in memory will be filled again with new | |
332 video data.</P> | |
333 | |
334 Doublebuffering may be switched on by using the option -double and may be | |
335 disabled with -nodouble. Current default option is to disable | |
336 doublebuffering. When using the DGA driver, onscreen display (OSD) only | |
337 works with doublebuffering enabled. However, enabling doublebuffering may | |
338 result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of | |
339 CPU time!) depending on the implementation of DGA for your hardware.</P> | |
340 | |
341 | |
342 <P><B><A NAME=2.2.1.3.7>2.2.1.3.7. Speed issues</A></B></P> | |
343 | |
344 <P>Generally spoken, DGA framebuffer access should be at least as fast as using | |
345 the X11 driver with the additional benefit of getting a fullscreen image. | |
346 The percentage speed values printed by mplayer have to be interpreted with | |
347 some care, as for example, with the X11 driver they do not include the time | |
348 used by the X-Server needed for the actual drawing. Hook a terminal to a | |
349 serial line of your box and start top to see what is really going on in your | |
350 box ...</P> | |
351 | |
352 <P>Generally spoken, the speedup done by using DGA against 'normal' use of X11 | |
353 highly depends on your graphics card and how well the X-Server module for it | |
354 is optimized.</P> | |
355 | |
356 <P>If you have a slow system, better use 15 or 16bit depth since they require | |
357 only half the memory bandwidth of a 32 bit display.</P> | |
1612 | 358 |
1682 | 359 <P>Using a depth of 24bit is even a good idea if your card natively just supports |
360 32 bit depth since it transfers 25% less data compared to the 32/32 mode.</P> | |
361 | |
362 <P>I've seen some avi files already be replayed on a Pentium MMX 266. AMD K6-2 | |
363 CPUs might work at 400 MHZ and above.</P> | |
1612 | 364 |
1682 | 365 <P><B><A NAME=2.2.1.3.8>2.2.1.3.8. Known bugs</A></B></P> |
366 | |
367 <P>Well, according to some developpers of XFree, DGA is quite a beast. They | |
368 tell you better not to use it. Its implementation is not always flawless | |
369 with every chipset driver for XFree out there.</P> | |
1612 | 370 |
1682 | 371 <P><UL> |
372 <LI>with XFree 4.0.3 and nv.o there is a bug resulting in strange colors | |
373 <LI>ATI driver requires to switch mode back more than once after finishing | |
374 using of DGA | |
375 <LI>some drivers simply fail to switch back to normal resolution (use | |
376 Ctrl-Alt-Keypad +, - to switch back manually) | |
377 <LI>some drivers simply display strange colors | |
378 <LI>some drivers lie about the amount of memory they map into the process's | |
379 address space, thus vo_dga won't use doublebuffering (SIS?) | |
380 <LI>some drivers seem to fail to report even a single valid mode. In this | |
381 case the DGA driver will crash telling you about a nonsense mode of | |
382 100000x100000 or the like ... | |
383 <LI>OSD only works with doublebuffering enabled | |
384 </UL></P> | |
385 | |
386 <P><B><A NAME=2.2.1.3.9>2.2.1.3.9. Future work</A></B></P> | |
387 | |
388 <P><UL><LI>use of the new X11 render interface for OSD | |
389 <LI>where is my TODO list ???? :-(((</UL></P> | |
1612 | 390 |
391 | |
1682 | 392 <P><B><A NAME=2.2.1.3.A>2.2.1.3.A. Some modelines</A></B></P> |
1612 | 393 |
1682 | 394 <PRE> |
1612 | 395 Section "Modes" |
396 Identifier "Modes[0]" | |
397 Modeline "800x600" 40 800 840 968 1056 600 601 605 628 | |
398 Modeline "712x600" 35.0 712 740 850 900 400 410 412 425 | |
399 Modeline "640x480" 25.175 640 664 760 800 480 491 493 525 | |
400 Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan | |
401 Modeline "352x288" 25.10 352 368 416 432 288 296 290 310 | |
402 Modeline "352x240" 15.750 352 368 416 432 240 244 246 262 Doublescan | |
403 Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan | |
404 EndSection | |
1682 | 405 </PRE> |
1612 | 406 |
1682 | 407 <P>These entries work fine with my Riva128 chip, using nv.o XServer driver |
408 module.</P> | |
1612 | 409 |
410 | |
1682 | 411 <P><B><A NAME=2.2.1.3.B>2.2.1.3.B. Bug Reports</A></B></P> |
1612 | 412 |
1682 | 413 <P>If you experience troubles with the DGA driver please feel free to file |
414 a bug report to me (e-mail address below). Please start mplayer with the | |
415 -v option and include all lines in the bug report that start with vo_dga:</P> | |
416 | |
417 <P>Please do also include the version of X11 you are using, the graphics card | |
418 and your CPU type. The X11 driver module (defined in XF86-Config) might | |
419 also help. Thanks!</P> | |
1612 | 420 |
1682 | 421 |
422 <P><I>Acki (acki@acki-netz.de, www.acki-netz.de)</I></P> | |
1612 | 423 |
424 | |
1682 | 425 <P><B><A NAME=2.2.1.4>2.2.1.4. SDL</A></B></P> |
1612 | 426 |
1682 | 427 <P>Here are some notes about SDL out in <B>MPlayer</B>.</P> |
1612 | 428 |
429 | |
430 | |
1682 | 431 <P><TABLE BORDER=0> |
432 <TD COLSPAN=4><P><B>There are several commandline switches for SDL:</B></P></TD><TR> | |
433 <TD> </TD><TD>-vo sdl:name</TD><TD> </TD><TD> | |
434 specifies sdl video driver to use (ie. aalib, dga, x11)</TD><TR> | |
435 <TD></TD><TD>-ao sdl:name</TD><TD></TD><TD>specifies sdl audio driver to use (ie. dsp, | |
436 esd, arts)</TD><TR> | |
437 <TD></TD><TD>-noxv</TD><TD></TD><TD>disables Xvideo hardware acceleration</TD><TR> | |
438 <TD></TD><TD>-forcexv</TD><TD></TD><TD>tries to force Xvideo acceleration</TD><TR> | |
1612 | 439 |
1682 | 440 <TD COLSPAN=4><P><B>SDL Keys:</B></P></TD><TR> |
1612 | 441 |
1682 | 442 <TD></TD><TD>F</TD><TD></TD><TD>toggles fullscreen/windowed mode</TD><TR> |
443 <TD></TD><TD>C</TD><TD></TD><TD>cycles available fullscreen modes</TD><TR> | |
444 <TD></TD><TD>W/S</TD><TD></TD><TD>mappings for * and / (mixer control)</TD><TR> | |
1612 | 445 |
1682 | 446 </TABLE></P> |
1612 | 447 |
1682 | 448 <P><B>KNOWN BUGS:</B></P> |
449 <P><UL><LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa !) | |
450 It's bug in SDL, I can't change it (tested with SDL 1.2.1). | |
451 </UL></P> | |
1612 | 452 |
1682 | 453 <P><B><A NAME=2.2.1.5>2.2.1.5. SVGAlib</A></B></P> |
454 | |
455 <P>If you don't have X, you can use the SVGAlib target! Be sure not to use the | |
456 -fs switch, since it toggles the usage of the software scaler, and it's | |
457 SLOOOW now, unless you have a real fast CPU (and/or MTRR?). :(</P> | |
1612 | 458 |
1682 | 459 <P>Of course you'll have to install svgalib and its development package in |
460 order for <B>MPlayer</B> build its SVGAlib driver (autodetected, but can be | |
461 forced), and don't forget to edit /etc/vga/libvga.config to suit your | |
462 card & monitor.</P> | |
1612 | 463 |
1682 | 464 <P><B><A NAME=2.2.1.6>2.2.1.6. Framebuffer output (FBdev)</A></B></P> |
465 | |
466 <P>Whether to build the FBdev target is autodetected during ./configure . | |
467 Read the framebuffer documentation in the kernel sources | |
468 (Documentation/fb/*) for info on how to enable it, etc.. !</P> | |
1612 | 469 |
1682 | 470 <P>If your card doesn't support VBE 2.0 standard (older ISA/PCI |
471 cards, such as S3 Trio64), only VBE 1.2 (or older?) : | |
472 Well, VESAfb is still available, but you'll have to load SciTech Display | |
473 Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or | |
474 whatever. And don't forget to register your UniVBE ;))</P> | |
1612 | 475 |
1682 | 476 <P>The FBdev output takes some additional parameters above the others:</P> |
1612 | 477 |
1682 | 478 <P><TABLE BORDER=0> |
479 <TD> </TD><TD>-fb</TD><TD> </TD><TD> | |
480 specify the framebuffer device to use (/dev/fd0)</TD><TR> | |
481 <TD></TD><TD>-fbmode</TD><TD></TD><TD>mode name to use (according to /etc/fb.modes)</TD><TR> | |
482 <TD></TD><TD>-fbmodeconfig</TD><TD></TD><TD> config file of modes (default /etc/fb.modes)</TD><TR> | |
483 <TD></TD><TD>-monitor_hfreq</TD><TD></TD><TD ROWSPAN=3>IMPORTANT values, see example.conf</TD><TR> | |
484 <TD></TD><TD>-monitor_vfreq</TD><TD></TD><TR> | |
485 <TD></TD><TD>-monitor_dotclock</TD><TD></TD><TR> | |
486 </TABLE></P> | |
1612 | 487 |
1682 | 488 <P>If you want to change to a specific mode, then use</P> |
1612 | 489 |
1682 | 490 <P><CODE> mplayer -vm -fbmode (NameOfMode) filename</CODE></P> |
1612 | 491 |
1682 | 492 <P><UL><LI><B>-vm</B> alone will choose the most suitable mode from /etc/fb.modes . Can be |
493 used together with -x and -y options too. The -flip option is supported only | |
494 if the movie's pixel format matches the video mode's pixel format. | |
495 Pay attention to the bpp value, fbdev driver tries to use the current, | |
496 or if you specify the -bpp option, then that. | |
497 <LI><B>-zoom</B> option isn't supported (software scaling is slow). -fs option | |
498 isn't supported. You can't use 8bpp (or less) modes.</UL></P> | |
1612 | 499 |
1682 | 500 <P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer, |
501 and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P> | |
1612 | 502 |
1682 | 503 <P><B><A NAME=2.2.1.7>2.2.1.7. Matrox framebuffer (mga_vid)</A></B></P> |
1612 | 504 |
1682 | 505 <P>This section is about the Matrox G200/G400/G450 BES (Back-End Scaler) |
506 support, the mga_vid kernel driver. It's active developed by me (A'rpi), and | |
507 it has hardware VSYNC support with triple buffering. It works on both | |
508 framebuffer console and under X.</P> | |
509 | |
510 <P>To use it, you first have to compile mga_vid.o:</P> | |
1612 | 511 |
1682 | 512 <P><CODE> cd drivers<BR> |
513 make</CODE></P> | |
1612 | 514 |
1682 | 515 <P>Then create /dev/mga_vid device:</P> |
1612 | 516 |
1682 | 517 <P><CODE> mknod /dev/mga_vid c 178 0</CODE></P> |
1612 | 518 |
1682 | 519 <P>and load the driver with</P> |
520 | |
521 <P><CODE> insmod mga_vid.o</CODE></P> | |
1612 | 522 |
1682 | 523 <P>You should verify the memory size detection using the 'dmesg' command. If |
524 it's bad, use the mga_ram_size option (rmmod mga_vid first), specify card's | |
525 memory size in MB:</P> | |
1612 | 526 |
1682 | 527 <P><CODE> insmod mga_vid.o mga_ram_size=16</CODE></P> |
1612 | 528 |
1682 | 529 <P>To make it load/unload automatically when needed, insert the following line |
530 at the end of /etc/modules.conf:</P> | |
1612 | 531 |
1682 | 532 <P><CODE> alias char-major-178 mga_vid</CODE></P> |
1612 | 533 |
1682 | 534 <P>Then run</P> |
1612 | 535 |
1682 | 536 <P><CODE> depmod -a</CODE></P> |
1612 | 537 |
1682 | 538 <P>Now you have to (re)compile <B>MPlayer</B>, ./configure will detect /dev/mga_vid |
539 and build the 'mga' driver. Using it from <B>MPlayer</B> goes by '-vo mga' if | |
540 you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.</P> | |
541 | |
542 <P>Note: '-vo xmga' works under XFree86 4.x.x, but it conflicts with the Xv | |
543 driver, so avoid using both. If you messed up Xv with mga, try running | |
544 <B>MPlayer</B> with '-vo mga' . It should fix Xv.</P> | |
1612 | 545 |
546 | |
1682 | 547 <P><B><A NAME=2.2.1.8>2.2.1.8. SiS 6326 framebuffer (sis_vid)</A></B></P> |
548 | |
549 <P>SiS 6326 YUV Framebuffer driver -> sis_vid kernel driver</P> | |
1612 | 550 |
1682 | 551 <P>Its interface should be compatible with the mga_vid, but the driver was not |
552 updated after the mga_vid changes, so it's outdated now. Volunteers | |
553 needed to test it and bring the code up-to-date.</P> | |
1612 | 554 |
1682 | 555 <P><B><A NAME=2.2.1.9>2.2.1.9. 3dfx YUV support</A></B></P> |
1612 | 556 |
1682 | 557 <P>3dfx has native YUV+scaler support, using /dev/3dfx (tdfx.o driver?) |
558 The /dev/3dfx kernel driver exists only for 2.2.x kernels, for use with | |
559 Glide 2.x Linux ports. It's not tested with <B>MPlayer</B>, and so no more | |
560 supported. Volunteers needed to test it and bring the code up-to-date.</P> | |
1612 | 561 |
1682 | 562 <P><B><A NAME=2.2.1.10>2.2.1.10. OpenGL output</A></B></P> |
1612 | 563 |
1682 | 564 <P><B>MPlayer</B> support displaying movies using OpenGL. Unfortunately, not all |
565 drivers support this ability. For example the Utah-GLX drivers | |
566 (for XFree86 3.3.6) have it, with all cards. | |
567 See <A HREF="http://utah-glx.sourceforge.net">http://utah-glx.sourceforge.net</A> | |
568 for details about how to install it.</P> | |
1612 | 569 |
1682 | 570 <P>XFree86(DRI) >= 4.0.3 supports it only with Matrox, and Radeon cards. |
571 See <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> for download, | |
572 and installation instructions.</P> | |
1612 | 573 |
1682 | 574 <P><B><A NAME=2.2.1.11>2.2.1.11. AAlib - text mode displaying</B></P> |
1612 | 575 |
1682 | 576 <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful |
577 ASCII renderer. There are LOTS of programs already supporting it, like Doom, | |
578 Quake, etc. MPlayer contains a very usable driver for it. | |
579 If ./configure detects aalib installed, the aalib libvo driver will be built.</P> | |
1612 | 580 |
1682 | 581 <P><TABLE BORDER=0> |
582 <TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD><TR> | |
583 <TD> </TD><TD>1</TD><TD> </TD><TD>decrease contrast</TD><TR> | |
584 <TD></TD><TD>2</TD><TD></TD><TD>increase contrast</TD><TR> | |
585 <TD></TD><TD>3</TD><TD></TD><TD>decrease brightness</TD><TR> | |
586 <TD></TD><TD>4</TD><TD></TD><TD>increase brightness</TD><TR> | |
587 <TD></TD><TD>5</TD><TD></TD><TD>switch fast rendering on/off</TD><TR> | |
588 <TD></TD><TD>6</TD><TD></TD><TD>set dithering mode (none, error distribution, floyd steinberg)</TD><TR> | |
589 <TD></TD><TD>7</TD><TD></TD><TD>invert image</TD><TR> | |
590 <TD></TD><TD>a</TD><TD></TD><TD>toggles between aa and mplayer control)</TD><TR> | |
591 | |
592 <TD COLSPAN=4><P><B>The following command line options can be used:</B></P></TD><TR> | |
1612 | 593 |
1682 | 594 <TD></TD><TD>-aaosdcolor=V</TD><TD></TD><TD>change osd color</TD><TR> |
595 <TD></TD><TD>-aasubcolor=V</TD><TD></TD><TD>change subtitle color</TD><TR> | |
596 <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> | |
1612 | 597 |
1682 | 598 <TD COLSPAN=4><P><B>AAlib itselves provides a large sum of options. |
599 Here are some important:</P></B></TD><TR> | |
600 | |
601 <TD></TD><TD>-aadriver</TD><TD></TD><TD>set recommended aa driver (X11, curses, linux)</TD><TR> | |
602 <TD></TD><TD>-aaextended</TD><TD></TD><TD>use all 256 characters</TD><TR> | |
603 <TD></TD><TD>-aaeight</TD><TD></TD><TD>use eight bit ascii</TD><TR> | |
604 <TD></TD><TD>-aahelp</TD><TD></TD><TD>prints out all aalib options</TD><TR> | |
605 </TABLE></P> | |
606 | |
607 <P>NOTE: the rendering is very CPU intensive, especially when using AA-on-X | |
608 (using aalib on X), and it's least CPU intensive on standard, | |
609 non-framebuffer console. Use SVGATextMode to set up a big textmode, | |
610 then enjoy! (secondary head Hercules cards rock :)) (anyone can enhance | |
611 bdev to do conversion/dithering to hgafb? Would be neat :)</P> | |
1612 | 612 |
1682 | 613 <P>Use the -framedrop option if your comp isn't fast enough to render all frames!</P> |
1612 | 614 |
1682 | 615 <P>Playing on terminal you'll get better speed and quality using the linux driver, not |
616 curses (-aadriver linux). But therefore you need write access on /dev/vcsa<terminal>! | |
617 That isn't autodetected by aalib, bu vo_aa tries to find the best mode. | |
1731 | 618 See <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> for further tuning issues.</P> |
1612 | 619 |
1682 | 620 <P><B><A NAME=2.2.1.A>2.2.1.A. TV-out support</A></B></P> |
1612 | 621 |
1682 | 622 <P><B><A NAME=2.2.1.A.1>2.2.1.A.1. Matrox cards</A></B></P> |
1612 | 623 |
1682 | 624 <P><I> What I'd love to see in mplayer is the the same feature that I see in my |
625 windows box. When I start a movie in windows (in a window or in full screen) | |
626 the movie is also redirected to the tv-out and I can also see it full screen | |
627 on my tv. I love this feature and was wondering how hard it would be to add | |
628 such a feature to mplayer.</I></P> | |
1612 | 629 |
1682 | 630 <P>It's a driver limitation. BES (Back-End Scaler, it's the overlay generator |
631 and YUV scaling engine of G200/G400/G450 cards) works only with CRTC1. | |
632 Normally, CRTC1 (textmode, every bpp gfx and BES) is routed to HEAD1, | |
633 and CRTC2 (only 16/32bpp gfx) is routed to HEAD2 (TV-out).</P> | |
1612 | 634 |
1682 | 635 <P>Under linux, you have two choices to get TV-out working:</P> |
1612 | 636 |
1682 | 637 <P><UL> |
638 <LI>Using X 4.0.x + the HAL driver from matrox, so you'll get dual-head | |
639 support, and you'll be able to redirect second output to the TV. | |
640 Unfortunately it has Macrovision encryption enabled, so it will | |
641 only work on directly-connected TV, no through VCR. | |
642 Other problem is that Xv doesn't work on the second head. | |
643 (I don't know how Windows solve it, maybe it swaps the CRTCs between | |
644 the heads, or just uses YUV framebuffer of second DAC with some trick) | |
645 <LI>Using matroxfb with dual-head support enabled (2.4.x kernels). | |
646 You'll be able to get a framebuffer console (using CRTC2, so it's | |
647 slow), and TV-out (using CRTC1, with BES support). | |
648 You have to forget X while using this kind of TV-out! :( | |
649 </UL></P> | |
1612 | 650 |
1682 | 651 <P>Follow these instructions:</P> |
1612 | 652 |
1682 | 653 <P><UL> |
654 <LI>Compile all the matrox-related things to modules in the kernel. | |
655 (you MUST compile them to modules, at least I couldn't get them | |
656 working built-in yet) | |
657 [reboot to new kernel & install modules, but don't load them yet!] | |
658 <P><CODE> | |
659 cd TVout<BR> | |
660 ./compile.sh</CODE></P> | |
661 <LI>Run the 'modules' script from the TV-out directory of mplayer. | |
662 It will switch your console to framebuffer. | |
663 Change to tty1 (ALT+F1)! | |
664 Now run the script 'independent', it will set up your tty's: | |
665 <P>tty 1,2: fb console, CRTC2, head 1 (monitor)<BR> | |
666 tty 3,4,5...: framebuffer+BES, CRTC1, head 2 (TV-out)</P> | |
667 You should run the scripts TV-* and Mon-* to set up resolutions: | |
668 <P>change to tty1 (ALT+F1), and run Mon-* (one of them)<BR> | |
669 change to tty3 (ALT+F3) and then back to tty1 (ALT+F1)</P> | |
670 (this change will select tty3 on /dev/fb1 - tricky)<BR> | |
671 <P>run TV-* (one of them)</P> | |
672 (now you'll get a console on your PAL TV - don't know about NTSC) | |
673 <P>Now if you start mplayer (on tty1), the picture will show up on | |
674 the tty3, so you'll see it on your TV or second monitor.</P> | |
675 </UL></P> | |
1612 | 676 |
1682 | 677 <P>Yes, it is a bit 'hack' now. But I'm waiting for the marvel |
678 project to be finished, it will provide real TV-out drivers, I hope.</P> | |
1612 | 679 |
1682 | 680 <P>My current problem is that BES is working only with CRTC1. So picture |
681 will always shown up on head routed to CRTC1 (normaly the monitor), | |
682 so i have to swap CRTC's, but this way your console will framebuffer | |
683 (CRTC2 can't do text-mode) and a bit slow (no acceleration). :(</P> | |
1612 | 684 |
1682 | 685 <P><I>Anyway i also just get monochrome output on the tv ...</I> |
686 Maybe you have NTSC TV? Or just didn't run one of TV-* scripts.</P> | |
1612 | 687 |
688 </BODY> | |
689 </HTML> |