Mercurial > mplayer.hg
annotate DOCS/xml/en/video.xml @ 11031:f57563a141aa
libfaad FAQ, external FAAD info added back.
author | diego |
---|---|
date | Tue, 07 Oct 2003 10:18:55 +0000 |
parents | 6da8652f129b |
children | 9ae01c61a346 |
rev | line source |
---|---|
9675 | 1 <?xml version="1.0" encoding="iso-8859-1"?> |
10913
49b1a67e7381
Add revision keyword to english xml files, to ease translation synchronization
lumag
parents:
10869
diff
changeset
|
2 <!-- $Revision$ --> |
9675 | 3 <sect2 id="video-dev"> |
4 <title>Video output devices</title> | |
5 | |
6 <sect3 id="mtrr"> | |
7 <title>Setting up MTRR</title> | |
8 | |
9 <para> | |
10 It is VERY recommended to check if the MTRR registers | |
11 are set up properly, because they can give a big performance boost. | |
12 </para> | |
13 | |
14 <para> | |
15 Do a <command>/proc/mtrr</command>: | |
16 <screen> | |
17 <prompt>--($:~)--</prompt> cat /proc/mtrr | |
18 reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9 | |
19 reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<!-- | |
20 --></screen> | |
21 </para> | |
22 | |
23 <para> | |
24 It's right, shows my Matrox G400 with 16MB memory. I did this from | |
25 XFree 4.x.x , which sets up MTRR registers automatically. | |
26 </para> | |
27 | |
28 <para> | |
29 If nothing worked, you have to do it manually. First, you have to find the | |
30 base address. You have 3 ways to find it: | |
31 | |
32 <orderedlist> | |
33 <listitem><para> | |
34 from X11 startup messages, for example: | |
35 <screen> | |
36 (--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000 | |
37 (--) SVGA: Linear framebuffer at 0xD8000000<!-- | |
38 --></screen> | |
39 </para></listitem> | |
40 <listitem><para> | |
41 from <filename>/proc/pci</filename> (use <command>lspci -v</command> | |
42 command): | |
43 <screen> | |
44 01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525 | |
45 Memory at d8000000 (32-bit, prefetchable) | |
46 </screen> | |
47 </para></listitem> | |
48 <listitem><para> | |
49 from mga_vid kernel driver messages (use <command>dmesg</command>): | |
50 <screen>mga_mem_base = d8000000</screen> | |
51 </para></listitem> | |
52 </orderedlist> | |
53 </para> | |
54 | |
55 <para> | |
56 Then let's find the memory size. This is very easy, just convert video RAM | |
57 size to hexadecimal, or use this table: | |
58 <informaltable frame="none"> | |
59 <tgroup cols="2"> | |
60 <tbody> | |
61 <row><entry>1 MB</entry><entry>0x100000</entry></row> | |
62 <row><entry>2 MB</entry><entry>0x200000</entry></row> | |
63 <row><entry>4 MB</entry><entry>0x400000</entry></row> | |
64 <row><entry>8 MB</entry><entry>0x800000</entry></row> | |
65 <row><entry>16 MB</entry><entry>0x1000000</entry></row> | |
66 <row><entry>32 MB</entry><entry>0x2000000</entry></row> | |
67 </tbody> | |
68 </tgroup> | |
69 </informaltable> | |
70 </para> | |
71 | |
72 <para> | |
73 You know base address and memory size, let's setup MTRR registers! | |
74 For example, for the Matrox card above (<literal>base=0xd8000000</literal>) | |
75 with 32MB ram (<literal>size=0x2000000</literal>) just execute: | |
76 <screen> | |
77 echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr | |
78 </screen> | |
79 </para> | |
80 | |
81 <para> | |
82 Not all CPUs support MTRRs. For example older K6-2's (around 266MHz, | |
83 stepping 0) doesn't support MTRR, but stepping 12's do (<command>cat /proc/cpuinfo | |
84 </command> to check it). | |
85 </para> | |
86 </sect3> | |
87 | |
88 <sect3 id="output-trad"> | |
89 <title>Video outputs for traditional video cards</title> | |
90 <sect4 id="xv"> | |
91 <title>Xv</title> | |
92 | |
93 <para> | |
94 Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines | |
95 using the XVideo extension. This is what the option '<option>-vo | |
96 xv</option>' uses. Also, this is driver supports adjusting | |
97 brightness/contrast/hue/etc (unless you use the old, slow DirectShow DivX | |
98 codec, which supports it everywhere), see the man page. | |
99 </para> | |
100 | |
101 <para> | |
102 In order to make this work, be sure to check the following: | |
103 | |
104 <orderedlist> | |
105 <listitem><para> | |
106 You have to use XFree86 4.0.2 or newer (former versions don't have XVideo) | |
107 </para></listitem> | |
108 <listitem><para> | |
109 Your card actually supports hardware acceleration (modern cards do) | |
110 </para></listitem> | |
111 <listitem><para> | |
112 X loads the XVideo extension, it's something like this: | |
113 <programlisting>(II) Loading extension XVideo</programlisting> | |
114 in <filename>/var/log/XFree86.0.log</filename> | |
115 <note><para> | |
116 This loads only the XFree86's extension. In a good install, this is | |
117 always loaded, and doesn't mean that the <emphasis role="bold">card's</emphasis> | |
118 XVideo support is loaded! | |
119 </para></note> | |
120 </para></listitem> | |
121 <listitem><para> | |
122 Your card has Xv support under Linux. To check, try | |
123 <command>xvinfo</command>, it is the part of the XFree86 distribution. It | |
124 should display a long text, similar to this: | |
125 <screen> | |
126 X-Video Extension version 2.2 | |
127 screen #0 | |
128 Adaptor #0: "Savage Streams Engine" | |
129 number of ports: 1 | |
130 port base: 43 | |
131 operations supported: PutImage | |
132 supported visuals: | |
133 depth 16, visualID 0x22 | |
134 depth 16, visualID 0x23 | |
135 number of attributes: 5 | |
136 (...) | |
137 Number of image formats: 7 | |
138 id: 0x32595559 (YUY2) | |
139 guid: 59555932-0000-0010-8000-00aa00389b71 | |
140 bits per pixel: 16 | |
141 number of planes: 1 | |
142 type: YUV (packed) | |
143 id: 0x32315659 (YV12) | |
144 guid: 59563132-0000-0010-8000-00aa00389b71 | |
145 bits per pixel: 12 | |
146 number of planes: 3 | |
147 type: YUV (planar) | |
148 (...etc...)<!-- | |
149 --></screen> | |
150 It must support YUY2 packed, and YV12 planar pixel formats to be usable | |
151 with <application>MPlayer</application>. | |
152 </para></listitem> | |
153 <listitem><para> | |
154 And finally, check if <application>MPlayer</application> was compiled | |
155 with 'xv' support. <filename>./configure</filename> prints this. | |
156 </para></listitem> | |
157 </orderedlist> | |
158 </para> | |
159 | |
160 <sect5 id="tdfx"> | |
161 <title>3dfx cards</title> | |
162 | |
163 <para> | |
164 Older 3dfx drivers were known to have problems with XVideo acceleration, it | |
165 didn't support either YUY2 or YV12, and so. Verify that you have XFree86 | |
166 version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous | |
167 versions, including 4.1.0, <emphasis role="bold">crashes with YV12</emphasis>. | |
10111 | 168 If you experience strange effects using <option>-vo xv</option>, try SDL (it has XVideo too) and |
9675 | 169 see if it helps. Check the <link linkend="sdl">SDL section</link> for details. |
170 </para> | |
171 | |
172 <para> | |
173 <emphasis role="bold">OR</emphasis>, try the NEW | |
174 <option>-vo tdfxfb</option> driver! See the <link linkend="tdfxfb">tdfxfb</link> | |
175 section. | |
176 </para> | |
177 </sect5> | |
178 | |
179 | |
180 <sect5 id="s3"> | |
181 <title>S3 cards</title> | |
182 | |
183 <para> | |
184 S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3 | |
185 or greater (in case of image problems, try 16bpp). As for S3 Virge: there is | |
186 xv support, but the card itself is very slow, so you better sell it. | |
187 </para> | |
188 | |
189 <note> | |
190 <para> | |
191 It's currently unclear which Savage models lack YV12 support, and convert by | |
192 driver (slow). If you suspect your card, get a newer driver, or ask politely | |
193 on the mplayer-users mailing list for an MMX/3DNow enabled driver. | |
194 </para> | |
195 </note> | |
196 </sect5> | |
197 | |
198 | |
199 <sect5 id="nvidia"> | |
200 <title>nVidia cards</title> | |
201 | |
202 <para> | |
203 nVidia isn't a very good choice under Linux (according to nVidia, this is | |
204 <link linkend="nvidia-opinions">not true</link>)... You'll have to use the | |
205 binary closed-source nVidia driver, available at nVidia's web site. The | |
206 standard XFree86 driver doesn't support XVideo for these cards, due to | |
207 nVidia's closed sources/specifications. | |
208 </para> | |
209 | |
210 <para> | |
211 As far as I know the latest XFree86 driver contains XVideo support for | |
212 GeForce 2 and 3. | |
213 </para> | |
214 | |
215 <para> | |
216 Riva128 cards don't have XVideo support even with the nVidia driver :( | |
217 Complain to nVidia. | |
218 </para> | |
219 </sect5> | |
220 | |
221 | |
222 <sect5 id="ati"> | |
223 <title>ATI cards</title> | |
224 | |
225 <para> | |
226 The <ulink url="http://www.linuxvideo.org/gatos">GATOS driver</ulink> | |
227 (which you should use, unless you have Rage128 or Radeon) has VSYNC enabled | |
228 by default. It means that decoding speed (!) is synced to the monitor's | |
229 refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or | |
230 set refresh rate to a n*(fps of the movie) Hz. | |
231 </para> | |
232 | |
233 <para> | |
10132 | 234 Radeon VE - if you need X, use XFree86 4.2.0 or greater for this card. |
235 No TV out support. Of course with <application>MPlayer</application> you can | |
9675 | 236 happily get <emphasis role="bold">accelerated</emphasis> display, with or without |
237 <emphasis role="bold">TV output</emphasis>, and no libraries or X are needed. | |
238 Read the <link linkend="vidix">VIDIX</link> section. | |
239 </para> | |
240 </sect5> | |
241 | |
242 | |
243 <sect5 id="neomagic"> | |
244 <title>NeoMagic cards</title> | |
245 | |
246 <para> | |
10132 | 247 These cards can be found in many laptops. You must use XFree86 4.3.0 or |
248 above, or else use Stefan Seyfried's | |
10068 | 249 <ulink url="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/">Xv-capable drivers</ulink>. |
10132 | 250 Just choose the one that applies to your version of XFree86. |
10068 | 251 </para> |
252 | |
253 <para> | |
254 XFree86 4.3.0 includes Xv support, yet Bohdan Horst sent a small | |
255 <ulink url="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/neo_driver.patch">patch</ulink> | |
10132 | 256 against the XFree86 sources that speeds up framebuffer operations (so XVideo) |
257 up to four times. The patch has been included in XFree86 CVS and should be in the | |
258 next release after 4.3.0. | |
9675 | 259 </para> |
260 | |
261 <para> | |
262 To allow playback of DVD sized content change your XF86Config like this: | |
263 <programlisting> | |
264 Section "Device" | |
265 [...] | |
266 Driver "neomagic" | |
267 <emphasis>Option "OverlayMem" "829440"</emphasis> | |
268 [...] | |
269 EndSection<!-- | |
270 --></programlisting> | |
271 </para> | |
272 </sect5> | |
273 | |
274 | |
275 <sect5 id="trident"> | |
276 <title>Trident cards</title> | |
277 <para> | |
278 If you want to use xv with a trident card, provided that it doesn't work | |
279 with 4.1.0, install XFree 4.2.0. 4.2.0 adds support for fullscreen xv | |
280 support with the Cyberblade XP card. | |
281 </para> | |
282 </sect5> | |
283 | |
284 | |
285 <sect5 id="kyro"> | |
286 <title>Kyro/PowerVR cards</title> | |
287 <para> | |
288 If you want to use Xv with a Kyro based card (for example Hercules | |
289 Prophet 4000XT), you should download the drivers from the | |
290 <ulink url="http://www.powervr.com/">PowerVR site</ulink> | |
291 </para> | |
292 </sect5> | |
293 </sect4> | |
294 | |
295 <!-- ********** --> | |
296 | |
297 <sect4 id="dga"> | |
298 <title>DGA</title> | |
299 | |
300 <formalpara> | |
301 <title>PREAMBLE</title> | |
302 <para> | |
303 This document tries to explain in some words what DGA is in general and | |
304 what the DGA video output driver for <application>MPlayer</application> | |
305 can do (and what it can't). | |
306 </para> | |
307 </formalpara> | |
308 | |
309 <formalpara> | |
310 <title>WHAT IS DGA</title> | |
311 <para> | |
312 <acronym>DGA</acronym> is short for <emphasis>Direct Graphics | |
313 Access</emphasis> and is a means for a program to bypass the X server and | |
314 directly modifying the framebuffer memory. Technically spoken this happens | |
315 by mapping the framebuffer memory into the memory range of your process. | |
316 This is allowed by the kernel only if you have superuser privileges. You | |
317 can get these either by logging in as <systemitem | |
318 class="username">root</systemitem> or by setting the SUID bit on the | |
319 <application>MPlayer</application> executable (<emphasis role="bold">not | |
320 recommended</emphasis>). | |
321 </para> | |
322 </formalpara> | |
323 <para> | |
324 There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was | |
325 introduced with XFree 4.0.1. | |
326 </para> | |
327 | |
328 <para> | |
329 DGA1 provides only direct framebuffer access as described above. For | |
330 switching the resolution of the video signal you have to rely on the | |
331 XVidMode extension. | |
332 </para> | |
333 | |
334 <para> | |
335 DGA2 incorporates the features of XVidMode extension and also allows | |
336 switching the depth of the display. So you may, although basically | |
337 running a 32 bit depth X server, switch to a depth of 15 bits and vice | |
338 versa. | |
339 </para> | |
340 | |
341 <para> | |
342 However DGA has some drawbacks. It seems it is somewhat dependent on the | |
343 graphics chip you use and on the implementation of the X server's video | |
344 driver that controls this chip. So it does not work on every system... | |
345 </para> | |
346 | |
347 <formalpara> | |
348 <title>INSTALLING DGA SUPPORT FOR MPLAYER</title> | |
349 | |
350 <para> | |
351 First make sure X loads the DGA extension, see in | |
352 <filename>/var/log/XFree86.0.log</filename>: | |
353 | |
354 <programlisting>(II) Loading extension XFree86-DGA</programlisting> | |
355 | |
356 See, XFree86 4.0.x or greater is VERY RECOMMENDED! | |
357 <application>MPlayer</application>'s DGA driver is autodetected by | |
358 <filename>./configure</filename>, or you can force it | |
359 with <option>--enable-dga</option>. | |
360 </para> | |
361 </formalpara> | |
362 | |
363 <para> | |
364 If the driver couldn't switch to a smaller resolution, experiment with | |
365 options <option>-vm</option> (only with X 3.3.x), <option>-fs</option>, | |
366 <option>-bpp</option>, <option>-zoom</option> to find a video mode that | |
367 the movie fits in. There is no converter right now :( | |
368 </para> | |
369 | |
370 <para> | |
371 Become <systemitem class="username">root</systemitem>. DGA needs root | |
372 access to be able to write directly video memory. If you want to run it as | |
373 user, then install <application>MPlayer</application> SUID root: | |
374 | |
375 <screen> | |
376 chown root /usr/local/bin/mplayer | |
377 chmod 750 /usr/local/bin/mplayer | |
378 chmod +s /usr/local/bin/mplayer | |
379 </screen> | |
380 | |
381 Now it works as a simple user, too. | |
382 </para> | |
383 | |
384 <caution> | |
385 <title>Security risk</title> | |
386 <para> | |
10111 | 387 This is a <emphasis role="bold">big</emphasis> security risk! |
388 <emphasis role="bold">Never</emphasis> do this on a server or on a computer can be | |
389 accessed by other people because they can gain root privileges through SUID root | |
9675 | 390 <application>MPlayer</application>. |
391 </para> | |
392 </caution> | |
393 | |
394 <para> | |
395 Now use <option>-vo dga</option> option, and there you go! (hope so:) You | |
396 should also try if the <option>-vo sdl:dga</option> option works for you! | |
397 It's much faster! | |
398 </para> | |
399 | |
400 | |
401 <formalpara id="dga-modelines"> | |
402 <title>RESOLUTION SWITCHING</title> | |
403 | |
404 <para> | |
405 The DGA driver allows for switching the resolution of the output signal. | |
406 This avoids the need for doing (slow) software scaling and at the same time | |
407 provides a fullscreen image. Ideally it would switch to the exact | |
408 resolution (except for honoring aspect ratio) of the video data, but the X | |
409 server only allows switching to resolutions predefined in | |
410 <filename>/etc/X11/XF86Config</filename> | |
411 (<filename>/etc/X11/XF86Config-4</filename> for XFree 4.X.X respectively). | |
412 Those are defined by so-called modelines and depend on | |
413 the capabilities of your video hardware. The X server scans this config | |
414 file on startup and disables the modelines not suitable for your hardware. | |
415 You can find out which modes survive with the X11 log file. It can be found | |
416 at: <filename>/var/log/XFree86.0.log</filename>. | |
417 </para> | |
418 </formalpara> | |
419 | |
420 <para> | |
421 These entries are known to work fine with a Riva128 chip, using the nv.o X | |
422 server driver module. | |
423 </para> | |
424 | |
425 | |
426 <para><programlisting> | |
427 Section "Modes" | |
428 Identifier "Modes[0]" | |
429 Modeline "800x600" 40 800 840 968 1056 600 601 605 628 | |
430 Modeline "712x600" 35.0 712 740 850 900 400 410 412 425 | |
431 Modeline "640x480" 25.175 640 664 760 800 480 491 493 525 | |
432 Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan | |
433 Modeline "352x288" 25.10 352 368 416 432 288 296 290 310 | |
434 Modeline "352x240" 15.750 352 368 416 432 240 244 246 262 Doublescan | |
435 Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan | |
436 EndSection | |
437 </programlisting></para> | |
438 | |
439 | |
440 <formalpara> | |
441 <title>DGA & MPLAYER</title> | |
442 <para> | |
443 DGA is used in two places with <application>MPlayer</application>: The SDL | |
444 driver can be made to make use of it (<option>-vo sdl:dga</option>) and | |
445 within the DGA driver (<option>-vo dga</option>). The above said is true | |
446 for both; in the following sections I'll explain how the DGA driver for | |
447 <application>MPlayer</application> works. | |
448 </para> | |
449 </formalpara> | |
450 | |
451 | |
452 <formalpara> | |
453 <title>FEATURES</title> | |
454 | |
455 <para> | |
456 The DGA driver is invoked by specifying <option>-vo dga</option> at the | |
457 command line. The default behavior is to switch to a resolution matching | |
458 the original resolution of the video as close as possible. It deliberately | |
459 ignores the <option>-vm</option> and <option>-fs</option> options | |
460 (enabling of video mode switching and fullscreen) - it always tries to | |
461 cover as much area of your screen as possible by switching the video mode, | |
462 thus refraining to use a single additional cycle of your CPU to scale the | |
463 image. If you don't like the mode it chooses you may force it to choose | |
464 the mode matching closest the resolution you specify by <option>-x</option> | |
465 and <option>-y</option>. By providing the <option>-v</option> option, the | |
466 DGA driver will print, among a lot of other things, a list of all | |
467 resolutions supported by your current <filename>XF86Config</filename> file. | |
468 Having DGA2 you may also force it to use a certain depth by using the | |
469 <option>-bpp</option> option. Valid depths are 15, 16, 24 and 32. It | |
470 depends on your hardware whether these depths are natively supported or if | |
471 a (possibly slow) conversion has to be done. | |
472 </para> | |
473 </formalpara> | |
474 <para> | |
475 If you should be lucky enough to have enough offscreen memory left to | |
476 put a whole image there, the DGA driver will use doublebuffering, which | |
477 results in much smoother movie replaying. It will tell you whether | |
478 double-buffering is enabled or not. | |
479 </para> | |
480 | |
481 <para> | |
482 Doublebuffering means that the next frame of your video is being drawn in | |
483 some offscreen memory while the current frame is being displayed. When the | |
484 next frame is ready, the graphics chip is just told the location in memory | |
485 of the new frame and simply fetches the data to be displayed from there. | |
486 In the meantime the other buffer in memory will be filled again with new | |
487 video data. | |
488 </para> | |
489 | |
490 <para> | |
491 Doublebuffering may be switched on by using the option | |
492 <option>-double</option> and may be disabled with | |
493 <option>-nodouble</option>. Current default option is to disable | |
494 doublebuffering. When using the DGA driver, onscreen display (OSD) only | |
495 works with doublebuffering enabled. However, enabling doublebuffering may | |
496 result in a big speed penalty (on my K6-II+ 525 it used an additional 20% | |
497 of CPU time!) depending on the implementation of DGA for your hardware. | |
498 </para> | |
499 | |
500 | |
501 <formalpara> | |
502 <title>SPEED ISSUES</title> | |
503 | |
504 <para> | |
505 Generally spoken, DGA framebuffer access should be at least as fast as | |
506 using the X11 driver with the additional benefit of getting a fullscreen | |
507 image. The percentage speed values printed by | |
508 <application>MPlayer</application> have to be interpreted with some care, | |
509 as for example, with the X11 driver they do not include the time used by | |
510 the X server needed for the actual drawing. Hook a terminal to a serial | |
511 line of your box and start <command>top</command> to see what is really | |
512 going on in your box. | |
513 </para> | |
514 </formalpara> | |
515 | |
516 <para> | |
517 Generally spoken, the speedup done by using DGA against 'normal' use of X11 | |
518 highly depends on your graphics card and how well the X server module for it | |
519 is optimized. | |
520 </para> | |
521 | |
522 <para> | |
523 If you have a slow system, better use 15 or 16 bit depth since they require | |
524 only half the memory bandwidth of a 32 bit display. | |
525 </para> | |
526 | |
527 <para> | |
528 Using a depth of 24 bit is even a good idea if your card natively just supports | |
529 32 bit depth since it transfers 25% less data compared to the 32/32 mode. | |
530 </para> | |
531 | |
532 <para> | |
533 I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2 | |
534 CPUs might work at 400 MHZ and above. | |
535 </para> | |
536 | |
537 | |
538 <formalpara> | |
539 <title>KNOWN BUGS</title> | |
540 | |
541 <para> | |
542 Well, according to some developers of XFree, DGA is quite a beast. They | |
543 tell you better not to use it. Its implementation is not always flawless | |
544 with every chipset driver for XFree out there. | |
545 </para> | |
546 </formalpara> | |
547 | |
548 <itemizedlist> | |
549 <listitem><simpara> | |
550 With XFree 4.0.3 and <filename>nv.o</filename> there is a bug resulting | |
551 in strange colors. | |
552 </simpara></listitem> | |
553 <listitem><simpara> | |
554 ATI driver requires to switch mode back more than once after finishing | |
555 using of DGA. | |
556 </simpara></listitem> | |
557 <listitem><simpara> | |
558 Some drivers simply fail to switch back to normal resolution (use | |
559 <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>Keypad +</keycap> and | |
560 <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>Keypad -</keycap> | |
561 to switch back manually). | |
562 </simpara></listitem> | |
563 <listitem><simpara> | |
564 Some drivers simply display strange colors. | |
565 </simpara></listitem> | |
566 <listitem><simpara> | |
567 Some drivers lie about the amount of memory they map into the process's | |
568 address space, thus vo_dga won't use doublebuffering (SIS?). | |
569 </simpara></listitem> | |
570 <listitem><simpara> | |
571 Some drivers seem to fail to report even a single valid mode. In this | |
572 case the DGA driver will crash telling you about a nonsense mode of | |
573 100000x100000 or something like that. | |
574 </simpara></listitem> | |
575 <listitem><simpara> | |
576 OSD only works with doublebuffering enabled (else it flickers). | |
577 </simpara></listitem> | |
578 </itemizedlist> | |
579 | |
580 </sect4> | |
581 <!--</sect3>--> | |
582 | |
583 <!-- ********** --> | |
584 | |
585 <sect4 id="sdl"> | |
586 <title>SDL</title> | |
587 | |
588 <para> | |
10111 | 589 <acronym>SDL</acronym> (Simple Directmedia Layer) is basically a unified |
9675 | 590 video/audio interface. Programs that use it know only about SDL, and not |
591 about what video or audio driver does SDL actually use. For example a Doom | |
592 port using SDL can run on svgalib, aalib, X, fbdev, and others, you only | |
593 have to specify the (for example) video driver to use with the | |
594 <envar>SDL_VIDEODRIVER</envar> environment variable. Well, in theory. | |
595 </para> | |
596 | |
597 <para> | |
598 With <application>MPlayer</application>, we used its X11 driver's software | |
599 scaler ability for cards/drivers that doesn't support XVideo, until we made | |
600 our own (faster, nicer) software scaler. Also we used its aalib output, but | |
601 now we have ours which is more comfortable. Its DGA mode was better than | |
602 ours, until recently. Get it now? :) | |
603 </para> | |
604 | |
605 <para> | |
606 It also helps with some buggy drivers/cards if the video is jerky (not slow | |
607 system problem), or audio is lagging. | |
608 </para> | |
609 | |
610 <para> | |
611 SDL video output supports displaying subtitles under the movie, on the (if | |
612 present) black bar. | |
613 </para> | |
614 | |
615 <variablelist> | |
616 <title>There are several command line switches for SDL:</title> | |
617 <varlistentry> | |
618 <term><option>-vo sdl:<replaceable>name</replaceable></option></term> | |
619 <listitem><simpara> | |
620 specifies SDL video driver to use (i.e. <literal>aalib</literal>, | |
621 <literal>dga</literal>, <literal>x11</literal>) | |
622 </simpara></listitem> | |
623 </varlistentry> | |
624 <varlistentry> | |
625 <term><option>-ao sdl:<replaceable>name</replaceable></option></term> | |
626 <listitem><simpara> | |
627 specifies SDL audio driver to use (i.e. <literal>dsp</literal>, | |
628 <literal>esd</literal>, <literal>arts</literal>) | |
629 </simpara></listitem> | |
630 </varlistentry> | |
631 <varlistentry> | |
632 <term><option>-noxv</option></term> | |
633 <listitem><simpara> | |
634 disables XVideo hardware acceleration | |
635 </simpara></listitem> | |
636 </varlistentry> | |
637 <varlistentry> | |
638 <term><option>-forcexv</option></term> | |
639 <listitem><simpara> | |
640 tries to force XVideo acceleration | |
641 </simpara></listitem> | |
642 </varlistentry> | |
643 </variablelist> | |
644 | |
645 <table> | |
10869 | 646 <title>SDL only keys</title> |
9675 | 647 <tgroup cols="2"> |
648 <thead> | |
649 <row><entry>Key</entry><entry>Action</entry></row> | |
650 </thead> | |
651 <tbody> | |
10869 | 652 <row><entry><keycap>c</keycap></entry><entry> |
9675 | 653 cycles available fullscreen modes |
654 </entry></row> | |
10869 | 655 <row><entry><keycap>n</keycap></entry><entry> |
656 changes back to normal mode | |
9675 | 657 </entry></row> |
658 </tbody> | |
659 </tgroup> | |
660 </table> | |
661 | |
662 <itemizedlist> | |
663 <title>Known bugs:</title> | |
664 <listitem><simpara> | |
665 Keys pressed under sdl:aalib console driver repeat forever. (use | |
666 <option>-vo aa</option>!) It's bug in SDL, I can't change it (tested with | |
667 SDL 1.2.1). | |
668 </simpara></listitem> | |
669 <listitem><simpara> | |
670 DO NOT USE SDL with GUI! It won't work as it should. | |
671 </simpara></listitem> | |
672 </itemizedlist> | |
673 </sect4> | |
674 | |
675 | |
676 <sect4 id="svgalib"> | |
677 <title>SVGAlib</title> | |
678 | |
679 <formalpara> | |
680 <title>INSTALLATION</title> | |
681 <para> | |
682 You'll have to install svgalib and its development package in order for | |
683 <application>MPlayer</application> build its SVGAlib driver (autodetected, | |
684 but can be forced), and don't forget to edit | |
685 <filename>/etc/vga/libvga.config</filename> to suit your card and monitor. | |
686 </para> | |
687 </formalpara> | |
688 | |
689 <note> | |
690 <para> | |
691 Be sure not to use the <option>-fs</option> switch, since it toggles the | |
692 usage of the software scaler, and it's slow. If you really need it, use the | |
693 <option>-sws 4</option> option which will produce bad quality, but is | |
694 somewhat faster. | |
695 </para> | |
696 </note> | |
697 | |
698 <formalpara><title>EGA (4BPP) SUPPORT</title> | |
699 <para> | |
700 SVGAlib incorporates EGAlib, and <application>MPlayer</application> has the | |
701 possibility to display any movie in 16 colors, thus usable in the following | |
702 sets: | |
703 </para> | |
704 </formalpara> | |
705 | |
706 <itemizedlist> | |
707 <listitem><simpara> | |
708 EGA card with EGA monitor: 320x200x4bpp, 640x200x4bpp, 640x350x4bpp | |
709 </simpara></listitem> | |
710 <listitem><simpara> | |
711 EGA card with CGA monitor: 320x200x4bpp, 640x200x4bpp | |
712 </simpara></listitem> | |
713 </itemizedlist> | |
714 | |
715 <para> | |
716 The bpp (bits per pixel) value must be set to 4 by hand: | |
717 <option>-bpp 4</option> | |
718 </para> | |
719 | |
720 <para> | |
721 The movie probably must be scaled down to fit in EGA mode: | |
9677 | 722 <screen>-vf scale=640:350</screen> |
9675 | 723 or |
9677 | 724 <screen>-vf scale=320:200</screen> |
9675 | 725 </para> |
726 | |
727 <para> | |
728 For that we need fast but bad quality scaling routine: | |
729 <screen>-sws 4</screen> | |
730 </para> | |
731 | |
732 <para> | |
733 Maybe automatic aspect correction has to be shut off: | |
734 <screen>-noaspect</screen> | |
735 </para> | |
736 | |
737 <note><para> | |
9683 | 738 According to my experience the best image quality on |
9675 | 739 EGA screens can be achieved by decreasing the brightness a bit: |
9677 | 740 <option>-vf eq=-20:0</option>. I also needed to lower the audio |
9675 | 741 samplerate on my box, because the sound was broken on 44kHz: |
742 <option>-srate 22050</option>. | |
743 </para></note> | |
744 | |
745 <para> | |
9683 | 746 You can turn on OSD and subtitles only with the <systemitem>expand</systemitem> |
9675 | 747 filter, see the man page for exact parameters. |
748 </para> | |
749 </sect4> | |
750 | |
751 | |
752 <sect4 id="fbdev"> | |
753 <title>Framebuffer output (FBdev)</title> | |
754 | |
755 <para> | |
756 Whether to build the FBdev target is autodetected during | |
10111 | 757 <filename>./configure</filename>. Read the framebuffer documentation in |
9675 | 758 the kernel sources (<filename>Documentation/fb/*</filename>) for more |
759 information. | |
760 </para> | |
761 | |
762 <para> | |
763 If your card doesn't support VBE 2.0 standard (older ISA/PCI cards, such as | |
764 S3 Trio64), only VBE 1.2 (or older?): Well, VESAfb is still available, but | |
765 you'll have to load SciTech Display Doctor (formerly UniVBE) before booting | |
766 Linux. Use a DOS boot disk or whatever. And don't forget to register your | |
767 UniVBE ;)) | |
768 </para> | |
769 | |
770 <para> | |
771 The FBdev output takes some additional parameters above the others: | |
772 </para> | |
773 | |
774 <variablelist> | |
775 <varlistentry> | |
776 <term><option>-fb</option></term> | |
777 <listitem><simpara> | |
778 specify the framebuffer device to use (<filename>/dev/fb0</filename>) | |
779 </simpara></listitem> | |
780 </varlistentry> | |
781 <varlistentry> | |
782 <term><option>-fbmode</option></term> | |
783 <listitem><simpara> | |
784 mode name to use (according to <filename>/etc/fb.modes</filename>) | |
785 </simpara></listitem> | |
786 </varlistentry> | |
787 <varlistentry> | |
788 <term><option>-fbmodeconfig</option></term> | |
789 <listitem><simpara> | |
790 config file of modes (default <filename>/etc/fb.modes</filename>) | |
791 </simpara></listitem> | |
792 </varlistentry> | |
793 <varlistentry> | |
794 <term><option>-monitor_hfreq</option></term> | |
795 <term><option>-monitor_vfreq</option></term> | |
796 <term><option>-monitor_dotclock</option></term> | |
797 <listitem><simpara> | |
798 <emphasis role="bold">important</emphasis> values, see | |
799 <filename>example.conf</filename> | |
800 </simpara></listitem> | |
801 </varlistentry> | |
802 </variablelist> | |
803 | |
804 <para> | |
805 If you want to change to a specific mode, then use | |
806 <screen>mplayer -vm -fbmode <replaceable>name_of_mode</replaceable> <replaceable>filename</replaceable></screen> | |
807 </para> | |
808 | |
809 <itemizedlist> | |
810 <listitem><para> | |
811 <option>-vm</option> alone will choose the most suitable mode from | |
812 <filename>/etc/fb.modes</filename>. Can be used together with | |
813 <option>-x</option> and <option>-y</option> options too. The | |
814 <option>-flip</option> option is supported only if the movie's pixel | |
10132 | 815 format matches the video mode's pixel format. Pay attention to the bpp |
9675 | 816 value, fbdev driver tries to use the current, or if you specify the |
817 <option>-bpp</option> option, then that. | |
818 </para></listitem> | |
819 <listitem><para> | |
10132 | 820 <option>-zoom</option> option isn't supported (use <option>-vf scale</option>). |
821 You can't use 8bpp (or less) modes. | |
9675 | 822 </para></listitem> |
823 <listitem><para> | |
824 You possibly want to turn the cursor off: | |
825 <screen>echo -e '\033[?25l'</screen> | |
826 or | |
827 <screen>setterm -cursor off</screen> | |
828 and the screen saver: | |
829 <screen>setterm -blank 0</screen> | |
830 To turn the cursor back on: | |
831 <screen>echo -e '\033[?25h'</screen> | |
832 or | |
833 <screen>setterm -cursor on</screen> | |
834 </para></listitem> | |
835 </itemizedlist> | |
836 | |
837 <note> | |
838 <para> | |
839 FBdev video mode changing <emphasis>does not work</emphasis> with the VESA | |
840 framebuffer, and don't ask for it, since it's not an | |
841 <application>MPlayer</application> limitation. | |
842 </para> | |
843 </note> | |
844 </sect4> | |
845 | |
846 | |
847 <sect4 id="mga_vid"> | |
848 <title>Matrox framebuffer (mga_vid)</title> | |
849 | |
850 <para> | |
851 This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler) | |
852 support, the mga_vid kernel driver. It's actively developed by A'rpi, and | |
853 it has hardware VSYNC support with triple buffering. It works on both | |
854 framebuffer console and under X. | |
855 </para> | |
856 | |
857 <warning> | |
858 <para> | |
859 This is Linux only! On non-Linux (tested on FreeBSD) systems, you can use | |
860 <link linkend="vidix">VIDIX</link> instead! | |
861 </para> | |
862 </warning> | |
863 | |
864 <procedure> | |
865 <title>Installation:</title> | |
866 <step><para> | |
867 To use it, you first have to compile <filename>mga_vid.o</filename>: | |
868 <screen> | |
869 cd drivers | |
870 make<!-- | |
871 --></screen> | |
872 </para></step> | |
873 <step><para> | |
874 Then create <filename>/dev/mga_vid</filename> device: | |
875 <screen>mknod /dev/mga_vid c 178 0</screen> | |
876 and load the driver with | |
877 <screen>insmod mga_vid.o</screen> | |
878 </para></step> | |
879 <step><para> | |
880 You should verify the memory size detection using the | |
881 <command>dmesg</command> command. If it's bad, use the | |
882 <option>mga_ram_size</option> option | |
883 (<command>rmmod mga_vid</command> first), | |
884 specify card's memory size in MB: | |
885 <screen>insmod mga_vid.o mga_ram_size=16</screen> | |
886 </para></step> | |
887 <step><para> | |
888 To make it load/unload automatically when needed, first insert the | |
889 following line at the end of <filename>/etc/modules.conf</filename>: | |
890 | |
891 <programlisting>alias char-major-178 mga_vid</programlisting> | |
892 | |
893 Then copy the <filename>mga_vid.o</filename> module to the appropriate | |
894 place under <filename>/lib/modules/<replaceable>kernel | |
895 version</replaceable>/<replaceable>somewhere</replaceable></filename>. | |
896 </para><para> | |
897 Then run | |
898 <screen>depmod -a</screen> | |
899 </para></step> | |
900 <step><para> | |
901 Now you have to (re)compile <application>MPlayer</application>, | |
902 <filename>./configure</filename> will detect | |
903 <filename>/dev/mga_vid</filename> and build the 'mga' driver. Using it | |
904 from <application>MPlayer</application> goes by <option>-vo mga</option> | |
905 if you have matroxfb console, or <option>-vo xmga</option> under XFree86 | |
906 3.x.x or 4.x.x. | |
907 </para></step> | |
908 </procedure> | |
909 | |
910 <para> | |
911 The mga_vid driver cooperates with Xv. | |
912 </para> | |
913 | |
914 <para> | |
915 The <filename>/dev/mga_vid</filename> device file can be read for some | |
916 info, for example by | |
917 <screen>cat /dev/mga_vid</screen> | |
918 and can be written for brightness change: | |
919 <screen>echo "brightness=120" > /dev/mga_vid</screen> | |
920 </para> | |
921 </sect4> | |
922 | |
923 | |
924 <sect4 id="tdfxfb" xreflabel="3Dfx YUV support (tdfxfb)"> | |
925 <title>3Dfx YUV support</title> | |
926 <para> | |
927 This driver uses the kernel's tdfx framebuffer driver to play movies with | |
928 YUV acceleration. You'll need a kernel with tdfxfb support, and recompile | |
929 with | |
930 <screen>./configure --enable-tdfxfb</screen> | |
931 </para> | |
932 </sect4> | |
933 | |
934 | |
935 <sect4 id="opengl"> | |
936 <title>OpenGL output</title> | |
937 | |
938 <para> | |
939 <application>MPlayer</application> supports displaying movies using OpenGL, | |
940 but if your platform/driver supports xv as should be the case on a PC with | |
941 Linux, use xv instead, OpenGL performance is considerably worse. If you | |
942 have an X11 implementation without xv support, OpenGL is a viable | |
943 alternative. | |
944 </para> | |
945 | |
946 <para> | |
947 Unfortunately not all drivers support this feature. The Utah-GLX drivers | |
948 (for XFree86 3.3.6) support it for all cards. | |
949 See <ulink url="http://utah-glx.sourceforge.net"/> for details about how to | |
950 install it. | |
951 </para> | |
952 | |
953 <para> | |
954 XFree86(DRI) 4.0.3 or later supports OpenGL with Matrox and Radeon cards, | |
955 4.2.0 or later supports Rage128. | |
956 See <ulink url="http://dri.sourceforge.net"/> for download and installation | |
957 instructions. | |
958 </para> | |
10526 | 959 |
960 <para> | |
961 A hint from one of our users: the GL video output can be used to get | |
962 vsynced TV output. You'll have to set an environment variable (at | |
963 least on nVidia): | |
964 </para> | |
965 | |
966 <para> | |
967 <command>export $__GL_SYNC_TO_VBLANK=1</command> | |
968 </para> | |
969 | |
9675 | 970 </sect4> |
971 | |
972 | |
973 <sect4 id="aalib"> | |
974 <title>AAlib - text mode displaying</title> | |
975 | |
976 <para> | |
977 AAlib is a library for displaying graphics in text mode, using powerful | |
978 ASCII renderer. There are <emphasis>lots</emphasis> of programs already | |
979 supporting it, like Doom, Quake, etc. <application>MPlayer</application> | |
10111 | 980 contains a very usable driver for it. If <filename>./configure</filename> |
9675 | 981 detects aalib installed, the aalib libvo driver will be built. |
982 </para> | |
983 | |
984 <para> | |
985 You can use some keys in the AA Window to change rendering options: | |
986 </para> | |
987 | |
988 <informaltable> | |
989 <tgroup cols="2"> | |
990 <thead> | |
991 <row><entry>Key</entry><entry>Action</entry></row> | |
992 </thead> | |
993 <tbody> | |
994 <row><entry><keycap>1</keycap></entry><entry> | |
995 decrease contrast | |
996 </entry></row> | |
997 <row><entry><keycap>2</keycap></entry><entry> | |
998 increase contrast | |
999 </entry></row> | |
1000 <row><entry><keycap>3</keycap></entry><entry> | |
1001 decrease brightness | |
1002 </entry></row> | |
1003 <row><entry><keycap>4</keycap></entry><entry> | |
1004 increase brightness | |
1005 </entry></row> | |
1006 <row><entry><keycap>5</keycap></entry><entry> | |
1007 switch fast rendering on/off | |
1008 </entry></row> | |
1009 <row><entry><keycap>6</keycap></entry><entry> | |
1010 set dithering mode (none, error distribution, Floyd Steinberg) | |
1011 </entry></row> | |
1012 <row><entry><keycap>7</keycap></entry><entry> | |
1013 invert image | |
1014 </entry></row> | |
1015 <row><entry><keycap>8</keycap></entry><entry> | |
1016 toggles between aa and <application>MPlayer</application> control | |
1017 </entry></row> | |
1018 </tbody> | |
1019 </tgroup> | |
1020 </informaltable> | |
1021 | |
1022 <variablelist> | |
1023 <title>The following command line options can be used:</title> | |
1024 <varlistentry> | |
1025 <term><option>-aaosdcolor=<replaceable>V</replaceable></option></term> | |
1026 <listitem><para> | |
1027 change OSD color | |
1028 </para></listitem> | |
1029 </varlistentry> | |
1030 <varlistentry> | |
1031 <term><option>-aasubcolor=<replaceable>V</replaceable></option></term> | |
1032 <listitem><para> | |
1033 change subtitle color | |
1034 </para><para> | |
1035 where <replaceable>V</replaceable> can be: | |
1036 <literal>0</literal> (normal), | |
1037 <literal>1</literal> (dark), | |
1038 <literal>2</literal> (bold), | |
1039 <literal>3</literal> (bold font), | |
1040 <literal>4</literal> (reverse), | |
1041 <literal>5</literal> (special). | |
1042 </para></listitem> | |
1043 </varlistentry> | |
1044 </variablelist> | |
1045 | |
1046 <variablelist> | |
1047 <title>AAlib itself provides a large sum of options. Here are some | |
1048 important:</title> | |
1049 <varlistentry> | |
1050 <term><option>-aadriver</option></term> | |
1051 <listitem><simpara> | |
1052 set recommended aa driver (X11, curses, Linux) | |
1053 </simpara></listitem> | |
1054 </varlistentry> | |
1055 <varlistentry> | |
1056 <term><option>-aaextended</option></term> | |
1057 <listitem><simpara> | |
1058 use all 256 characters | |
1059 </simpara></listitem> | |
1060 </varlistentry> | |
1061 <varlistentry> | |
1062 <term><option>-aaeight</option></term> | |
1063 <listitem><simpara> | |
1064 use eight bit ASCII | |
1065 </simpara></listitem> | |
1066 </varlistentry> | |
1067 <varlistentry> | |
1068 <term><option>-aahelp</option></term> | |
1069 <listitem><simpara> | |
1070 prints out all aalib options | |
1071 </simpara></listitem> | |
1072 </varlistentry> | |
1073 </variablelist> | |
1074 | |
1075 <note> | |
1076 <para> | |
1077 The rendering is very CPU intensive, especially when using AA-on-X | |
1078 (using aalib on X), and it's least CPU intensive on standard, | |
1079 non-framebuffer console. Use SVGATextMode to set up a big textmode, | |
1080 then enjoy! (secondary head Hercules cards rock :)) (but imho you | |
10111 | 1081 can use <option>-vf 1bpp</option> option to get graphics on hgafb:) |
9675 | 1082 </para> |
1083 </note> | |
1084 | |
1085 <para> | |
1086 Use the <option>-framedrop</option> option if your computer isn't fast | |
1087 enough to render all frames! | |
1088 </para> | |
1089 | |
1090 <para> | |
1091 Playing on terminal you'll get better speed and quality using the Linux | |
1092 driver, not curses (<option>-aadriver linux</option>). But therefore you | |
1093 need write access on | |
1094 <filename>/dev/vcsa<replaceable><terminal></replaceable></filename>! | |
1095 That isn't autodetected by aalib, but vo_aa tries to find the best mode. | |
1096 See <ulink url="http://aa-project.sourceforge.net/tune"/> for further | |
1097 tuning issues. | |
1098 </para> | |
1099 </sect4> | |
1100 | |
1101 | |
1102 <sect4 id="vesa"> | |
1103 <title>VESA - output to VESA BIOS</title> | |
1104 | |
1105 <para> | |
1106 This driver was designed and introduced as a <emphasis role="bold">generic | |
1107 driver</emphasis> for any video card which has VESA VBE 2.0 compatible | |
1108 BIOS. Another advantage of this driver is that it tries to force TV output | |
1109 on. | |
1110 <citetitle>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, | |
1111 1998</citetitle> (Page 70) says: | |
1112 </para> | |
1113 | |
1114 <blockquote> | |
1115 <formalpara><title>Dual-Controller Designs</title> | |
1116 <para> | |
1117 VBE 3.0 supports the dual-controller design by assuming that since both | |
1118 controllers are typically provided by the same OEM, under control of a | |
1119 single BIOS ROM on the same graphics card, it is possible to hide the fact | |
1120 that two controllers are indeed present from the application. This has the | |
1121 limitation of preventing simultaneous use of the independent controllers, | |
1122 but allows applications released before VBE 3.0 to operate normally. The | |
1123 VBE Function 00h (Return Controller Information) returns the combined | |
1124 information of both controllers, including the combined list of available | |
1125 modes. When the application selects a mode, the appropriate controller is | |
1126 activated. Each of the remaining VBE functions then operates on the active | |
1127 controller. | |
1128 </para> | |
1129 </formalpara> | |
1130 </blockquote> | |
1131 | |
1132 <para> | |
1133 So you have chances to get working TV-out by using this driver. | |
1134 (I guess that TV-out frequently is standalone head or standalone output | |
1135 at least.) | |
1136 </para> | |
1137 | |
1138 <itemizedlist spacing="compact"> | |
1139 <title>ADVANTAGES</title> | |
1140 <listitem><simpara> | |
1141 You have chances to watch movies <emphasis role="bold">if Linux even doesn't | |
1142 know</emphasis> your video hardware. | |
1143 </simpara></listitem> | |
1144 <listitem><simpara> | |
1145 You don't need to have installed any graphics' related things on your | |
1146 Linux (like X11 (aka XFree86), fbdev and so on). This driver can be run | |
1147 from <emphasis role="bold">text-mode</emphasis>. | |
1148 </simpara></listitem> | |
1149 <listitem><simpara> | |
1150 You have chances to get <emphasis role="bold">working TV-out</emphasis>. | |
1151 (It's known at least for ATI's cards). | |
1152 </simpara></listitem> | |
1153 <listitem><simpara> | |
1154 This driver calls <function>int 10h</function> handler thus it's not | |
1155 an emulator - it calls <emphasis role="bold">real</emphasis> things of | |
10971
12315a6590a1
Clumsy wording improved byRuben Garcia <ruben@ugr.es> and
diego
parents:
10965
diff
changeset
|
1156 <emphasis>real</emphasis> BIOS in <emphasis>real-mode</emphasis> |
12315a6590a1
Clumsy wording improved byRuben Garcia <ruben@ugr.es> and
diego
parents:
10965
diff
changeset
|
1157 (actually in vm86 mode). |
9675 | 1158 </simpara></listitem> |
1159 <listitem><simpara> | |
1160 You can use VIDIX with it, thus getting accelerated video display | |
1161 <emphasis role="bold">and</emphasis> TV output at the same time! | |
1162 (Recommended for ATI cards.) | |
1163 </simpara></listitem> | |
10111 | 1164 <listitem><simpara> |
1165 If you have VESA VBE 3.0+, and you had specified | |
1166 <systemitem>monitor_hfreq, monitor_vfreq, monitor_dotclock</systemitem> somewhere | |
1167 (config file, or commandline) you will get the highest possible refresh rate. | |
1168 (Using General Timing Formula). To enable this feature you have to specify | |
1169 <emphasis role="bold">all</emphasis> your monitor options. | |
1170 </simpara></listitem> | |
9675 | 1171 </itemizedlist> |
1172 | |
1173 <itemizedlist spacing="compact"> | |
1174 <title>DISADVANTAGES</title> | |
1175 <listitem><simpara> | |
1176 It works only on <emphasis role="bold">x86 systems</emphasis>. | |
1177 </simpara></listitem> | |
1178 <listitem><simpara> | |
1179 It can be used only by <systemitem class="username">root</systemitem>. | |
1180 </simpara></listitem> | |
1181 <listitem><simpara> | |
1182 Currently it's available only for <emphasis role="bold">Linux</emphasis>. | |
1183 </simpara></listitem> | |
1184 </itemizedlist> | |
1185 | |
1186 <important> | |
1187 <para> | |
1188 Don't use this driver with <emphasis role="bold">GCC 2.96</emphasis>! | |
1189 It won't work! | |
1190 </para> | |
1191 </important> | |
1192 | |
1193 <variablelist> | |
1194 <title>COMMAND LINE OPTIONS AVAILABLE FOR VESA</title> | |
1195 <varlistentry> | |
1196 <term><option>-vo vesa:<replaceable>opts</replaceable></option></term> | |
1197 <listitem><simpara> | |
1198 currently recognized: <literal>dga</literal> to force dga mode and | |
1199 <literal>nodga</literal> to disable dga mode. In dga mode you can enable | |
10111 | 1200 double buffering via the <option>-double</option> option. Note: you may omit |
1201 these parameters to enable <emphasis role="bold">autodetection</emphasis> of | |
1202 dga mode. | |
9675 | 1203 </simpara></listitem> |
1204 </varlistentry> | |
1205 </variablelist> | |
1206 | |
1207 <itemizedlist spacing="compact"> | |
1208 <title>KNOWN PROBLEMS AND WORKAROUNDS</title> | |
1209 <listitem><simpara> | |
1210 If you have installed <emphasis role="bold">NLS</emphasis> font on your | |
1211 Linux box and run VESA driver from text-mode then after terminating | |
1212 <application>MPlayer</application> you will have | |
1213 <emphasis role="bold">ROM font</emphasis> loaded instead of national. | |
1214 You can load national font again by using <command>setsysfont</command> | |
10965 | 1215 utility from the Mandrake distribution for example. |
9675 | 1216 (<emphasis role="bold">Hint</emphasis>: The same utility is used for |
1217 localization of fbdev). | |
1218 </simpara></listitem> | |
1219 <listitem><simpara> | |
1220 Some <emphasis role="bold">Linux graphics drivers</emphasis> don't update | |
1221 active <emphasis role="bold">BIOS mode</emphasis> in DOS memory. | |
1222 So if you have such problem - always use VESA driver only from | |
1223 <emphasis role="bold">text-mode</emphasis>. Otherwise text-mode (#03) will | |
1224 be activated anyway and you will need restart your computer. | |
1225 </simpara></listitem> | |
1226 <listitem><simpara> | |
10111 | 1227 Often after terminating VESA driver you get <emphasis role="bold">black</emphasis> |
1228 screen. To return your screen to original state - simply switch to other console | |
1229 (by pressing <keycap>Alt</keycap>+<keycap>F<x></keycap>) | |
9675 | 1230 then switch to your previous console by the same way. |
1231 </simpara></listitem> | |
1232 <listitem><simpara> | |
1233 To get <emphasis role="bold">working TV-out</emphasis> you need have plugged | |
1234 TV-connector in before booting your PC since video BIOS initializes | |
1235 itself only once during POST procedure. | |
1236 </simpara></listitem> | |
1237 </itemizedlist> | |
1238 </sect4> | |
1239 | |
1240 | |
1241 <sect4 id="x11"> | |
1242 <title>X11</title> | |
1243 | |
1244 <para> | |
1245 Avoid if possible. Outputs to X11 (uses shared memory extension), with no | |
1246 hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but | |
1247 still slow) software scaling, use the options <option>-fs -zoom</option>. | |
1248 Most cards have hardware scaling support, use the <option>-vo xv</option> | |
1249 output for them, or <option>-vo xmga</option> for Matroxes. | |
1250 </para> | |
1251 | |
1252 <para> | |
1253 The problem is that most cards' driver doesn't support hardware | |
1254 acceleration on the second head/TV. In those cases, you see green/blue | |
1255 colored window instead of the movie. This is where this driver comes in | |
1256 handy, but you need powerful CPU to use software scaling. Don't use the SDL | |
1257 driver's software output+scaler, it has worse image quality! | |
1258 </para> | |
1259 | |
1260 <para> | |
1261 Software scaling is very slow, you better try changing video modes instead. | |
1262 It's very simple. See the <link linkend="dga-modelines">DGA section's | |
1263 modelines</link>, and insert them into your <filename>XF86Config</filename>. | |
1264 | |
1265 <itemizedlist spacing="compact"> | |
1266 <listitem><simpara> | |
1267 If you have XFree86 4.x.x: use the <option>-vm</option> option. It will | |
1268 change to a resolution your movie fits in. If it doesn't: | |
1269 </simpara></listitem> | |
1270 <listitem><simpara> | |
1271 With XFree86 3.x.x: you have to cycle through available resolutions | |
1272 with the | |
1273 <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>plus</keycap> | |
1274 and | |
1275 <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>minus</keycap> | |
1276 keys. | |
1277 </simpara></listitem> | |
1278 </itemizedlist> | |
1279 </para> | |
1280 | |
1281 <para> | |
1282 If you can't find the modes you inserted, browse XFree86's output. Some | |
1283 drivers can't use low pixelclocks that are needed for low resolution | |
1284 video modes. | |
1285 </para> | |
1286 </sect4> | |
1287 | |
1288 | |
1289 <sect4 id="vidix"> | |
1290 <title>VIDIX</title> | |
1291 | |
1292 <formalpara> | |
1293 <title>PREAMBLE</title> | |
1294 <para> | |
10111 | 1295 <acronym>VIDIX</acronym> is the abbreviation for <emphasis role="bold">VID</emphasis>eo |
9675 | 1296 <emphasis role="bold">I</emphasis>nterface for *ni<emphasis role="bold">X</emphasis>. |
1297 VIDIX was designed and introduced as an interface for fast user-space drivers | |
1298 providing such video performance as mga_vid does for Matrox cards. It's also very | |
1299 portable. | |
1300 </para> | |
1301 </formalpara> | |
1302 <para> | |
1303 This interface was designed as an attempt to fit existing video | |
1304 acceleration interfaces (known as mga_vid, rage128_vid, radeon_vid, | |
1305 pm3_vid) into a fixed scheme. It provides highlevel interface to chips | |
1306 which are known as BES (BackEnd scalers) or OV (Video Overlays). It doesn't | |
1307 provide lowlevel interface to things which are known as graphics servers. | |
1308 (I don't want to compete with X11 team in graphics mode switching). I.e. | |
1309 main goal of this interface is to maximize the speed of video playback. | |
1310 </para> | |
1311 | |
1312 <itemizedlist spacing="compact"> | |
1313 <title>USAGE</title> | |
1314 <listitem><simpara> | |
1315 You can use standalone video output driver: <option>-vo xvidix</option>. | |
1316 This driver was developed as X11's front end to VIDIX technology. It | |
1317 requires X server and can work only under X server.Note that, as it directly | |
1318 accesses the hardware and circumvents the X driver, pixmaps cached in the | |
1319 graphics card's memory may be corrupted. You can prevent this by limiting | |
1320 the amount of video memory used by X with the XF86Config option "VideoRam" | |
1321 in the device section. You should set this to the amount of memory installed | |
1322 on your card minus 4MB. If you have less than 8MB of video ram, you can use | |
1323 the option "XaaNoPixmapCache" in the screen section instead. | |
1324 </simpara></listitem> | |
1325 <listitem><simpara> | |
1326 You can use VIDIX subdevice which was applied to several video output | |
1327 drivers, such as: <option>-vo vesa:vidix</option> | |
1328 (<emphasis role="bold">Linux only</emphasis>) and | |
1329 <option>-vo fbdev:vidix</option>. | |
1330 </simpara></listitem> | |
1331 </itemizedlist> | |
1332 | |
1333 <para> | |
1334 Indeed it doesn't matter which video output driver is used with | |
1335 <emphasis role="bold">VIDIX</emphasis>. | |
1336 </para> | |
1337 | |
1338 <itemizedlist spacing="compact"> | |
1339 <title>REQUIREMENTS</title> | |
1340 <listitem><simpara> | |
1341 Video card should be in graphics mode (I write <emphasis role="bold">should</emphasis> | |
1342 simply because I tested it in text mode - it works but has awful output ;) Use | |
1343 AAlib for that). | |
1344 <emphasis role="bold">Note</emphasis>: Everyone can try this trick by commenting out mode | |
1345 switching in vo_vesa driver. | |
1346 </simpara></listitem> | |
1347 <listitem><simpara> | |
1348 <application>MPlayer</application>'s video output driver should know | |
1349 active video mode and be able to tell to VIDIX subdevice some video | |
1350 characteristics of server. | |
1351 </simpara></listitem> | |
1352 </itemizedlist> | |
1353 | |
1354 <formalpara> | |
1355 <title>USAGE METHODS</title> | |
1356 <para> | |
10111 | 1357 When VIDIX is used as <emphasis role="bold">subdevice</emphasis> (<option>-vo |
9675 | 1358 vesa:vidix</option>) then video mode configuration is performed by video |
10111 | 1359 output device (<emphasis role="bold">vo_server</emphasis> in short). Therefore you can |
9675 | 1360 pass into command line of <application>MPlayer</application> the same keys |
1361 as for vo_server. In addition it understands <option>-double</option> key | |
1362 as globally visible parameter. (I recommend using this key with VIDIX at | |
1363 least for ATI's card). As for <option>-vo xvidix</option> : currently it | |
1364 recognizes the following options: <option>-fs -zoom -x -y -double</option>. | |
1365 </para> | |
1366 </formalpara> | |
1367 <para> | |
1368 Also you can specify VIDIX's driver directly as third subargument in | |
1369 command line: | |
1370 | |
1371 <screen>mplayer -vo xvidix:mga_vid.so -fs -zoom -double file.avi</screen> | |
1372 or | |
1373 <screen>mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp 32 file.avi</screen> | |
1374 | |
1375 But it's dangerous, and you shouldn't do that. In this case given driver | |
1376 will be forced and result is unpredictable (it may | |
1377 <emphasis role="bold">freeze</emphasis> your computer). You should do that | |
1378 ONLY if you are absolutely sure it will work, and | |
1379 <application>MPlayer</application> doesn't do it automatically. Please tell | |
1380 about it to the developers. The right way is to use VIDIX without arguments | |
1381 to enable driver autodetection. | |
1382 </para> | |
1383 | |
1384 <para> | |
1385 VIDIX is new technology and it's extremely possible that on your | |
1386 system it won't work. In this case only solution for you | |
1387 it's port it (mainly libdha). But there is hope that it will work on those | |
1388 systems where X11 does. | |
1389 </para> | |
1390 | |
1391 <para> | |
1392 Since VIDIX requires direct hardware access you can either run it as root | |
1393 or set the SUID bit on the <application>MPlayer</application> binary | |
10111 | 1394 (<emphasis role="bold">Warning: This is a security risk!</emphasis>). |
9675 | 1395 Alternatively, you can use a special kernel module, like this: |
1396 </para> | |
1397 | |
1398 <procedure> | |
1399 <step><para> | |
1400 Download the <ulink url="http://www.arava.co.il/matan/svgalib/">development version</ulink> | |
1401 of svgalib (for example 1.9.17), <emphasis role="bold">OR</emphasis> | |
1402 download a version made by Alex especially for usage with <application>MPlayer</application> | |
1403 (it doesn't need the svgalib source to compile) from | |
1404 <ulink url="http://www.mplayerhq.hu/~alex/svgalib_helper-1.9.17-mplayer.tar.bz2">here</ulink>. | |
1405 </para></step> | |
1406 <step><para> | |
1407 Compile the module in the <filename class="directory">svgalib_helper</filename> | |
10111 | 1408 directory (it can be found inside the <filename class="directory">svgalib-1.9.17/kernel/</filename> |
9675 | 1409 directory if you've downloaded the source from the svgalib site) and insmod it. |
1410 </para></step> | |
1411 <step><para> | |
11022 | 1412 To create the neccessary devices in the <filename class="directory">/dev</filename> |
1413 directory, do a <screen>make device</screen> in the <filename class="directory">svgalib_helper</filename> | |
1414 dir, as root. | |
1415 </para></step> | |
1416 <step><para> | |
9675 | 1417 Move the <filename class="directory">svgalib_helper</filename> directory to |
1418 <filename class="directory">mplayer/main/libdha/svgalib_helper</filename>. | |
1419 </para></step> | |
1420 <step><para> | |
1421 Required if you download the source from the svgalib site: Remove the comment before the | |
1422 CFLAGS line containing "svgalib_helper" string from the | |
1423 <filename class="directory">libdha/Makefile</filename>. | |
1424 </para></step> | |
1425 <step><para> | |
1426 Recompile and install libdha. | |
1427 </para></step> | |
1428 </procedure> | |
1429 | |
1430 <sect5 id="vidix-ati"> | |
1431 <title>ATI cards</title> | |
1432 <para> | |
1433 Currently most ATI cards are supported natively, from Mach64 to the | |
1434 newest Radeons. | |
1435 </para> | |
1436 | |
1437 <para> | |
1438 There are two compiled binaries: <filename>radeon_vid</filename> for Radeon and | |
1439 <filename>rage128_vid</filename> for Rage 128 cards. You may force one or let | |
1440 the VIDIX system autoprobe all available drivers. | |
1441 </para> | |
1442 </sect5> | |
1443 | |
1444 <sect5 id="vidix-mga"> | |
1445 <title>Matrox cards</title> | |
1446 <para> | |
1447 Matrox G200,G400,G450 and G550 have been reported to work. | |
1448 </para> | |
1449 | |
1450 <para> | |
1451 The driver supports video equalizers and should be nearly as fast as the | |
1452 <link linkend="mga_vid">Matrox framebuffer</link> | |
1453 </para> | |
1454 </sect5> | |
1455 | |
1456 <sect5 id="vidix-trident"> | |
1457 <title>Trident cards</title> | |
1458 <para> | |
1459 There is a driver available for the Trident Cyberblade/i1 chipset, which | |
1460 can be found on VIA Epia motherboards. | |
1461 </para> | |
1462 | |
1463 <para> | |
1464 The driver was written and is maintained by Alastair M. Robinson, who | |
1465 offers the very latest driver versions for download from his | |
1466 <ulink url="http://www.blackfiveservices.co.uk/EPIAVidix.shtml">homepage</ulink>. | |
10111 | 1467 The drivers are added to <application>MPlayer</application> with only a short |
1468 delay, so CVS should always be up to date. | |
9675 | 1469 </para> |
1470 </sect5> | |
1471 | |
1472 <sect5 id="vidix-3dlabs"> | |
1473 <title>3DLabs cards</title> | |
1474 <para> | |
1475 Although there is a driver for the 3DLabs GLINT R3 and Permedia3 chips, no one | |
1476 has tested it, so reports are welcome. | |
1477 </para> | |
1478 </sect5> | |
1479 </sect4> | |
1480 | |
1481 <sect4 id="directfb"> | |
1482 <title>DirectFB</title> | |
1483 <blockquote><para> | |
1484 "DirectFB is a graphics library which was designed with embedded systems | |
1485 in mind. It offers maximum hardware accelerated performance at a minimum | |
1486 of resource usage and overhead." - quoted from <ulink url="http://www.directfb.org"/> | |
1487 </para></blockquote> | |
1488 | |
1489 <para>I'll exclude DirectFB features from this section.</para> | |
1490 | |
1491 <para> | |
10111 | 1492 Though <application>MPlayer</application> is not supported as a "video |
1493 provider" in DirectFB, this output driver will enable video playback through | |
1494 DirectFB. It will - of course - be accelerated, on my Matrox G400 DirectFB's speed | |
1495 was the same as XVideo. | |
9675 | 1496 </para> |
1497 | |
1498 <para> | |
1499 Always try to use the newest version of DirectFB. You can use DirectFB options on | |
1500 the command line, using the <option>-dfbopts</option> option. Layer selection can | |
1501 be done by the subdevice method, e.g.: <option>-vo directfb:2</option> | |
1502 (layer -1 is default: autodetect) | |
1503 </para> | |
1504 </sect4> | |
1505 | |
1506 <sect4 id="dfbmga"> | |
1507 <title>DirectFB/Matrox (dfbmga)</title> | |
1508 <para> | |
1509 Please read the <link linkend="directfb">main DirectFB section</link> or general | |
1510 informations. | |
1511 </para> | |
1512 | |
1513 <para>This video output driver will enable CRTC2 (on the second head) on the | |
9683 | 1514 Matrox G400/G450/G550 card, displaying video <emphasis role="bold">independently</emphasis> |
9675 | 1515 of the first head. |
1516 </para> | |
1517 | |
1518 <para> | |
1519 Instructions on how to make it work can be found in the | |
1520 <ulink url="../../tech/directfb.txt">tech section</ulink> | |
1521 or directly on Ville Syrjala's | |
9677 | 1522 <ulink url="http://www.sci.fi/~syrjala/directfb/Matrox_TV-out_README.txt">home page</ulink>. |
9675 | 1523 </para> |
1524 | |
1525 <note><para> | |
10132 | 1526 the first DirectFB version with which we could kick this working was |
1527 0.9.17 (it's buggy, needs that <systemitem>surfacemanager</systemitem> patch from | |
1528 the URL above). Anyway, porting of the CRTC2 code to <emphasis role="bold">mga_vid</emphasis> | |
1529 is underway. | |
9675 | 1530 </para></note> |
1531 </sect4> | |
1532 </sect3> | |
1533 | |
1534 <sect3 id="mpeg_decoders"> | |
1535 <title>MPEG decoders</title> | |
1536 | |
1537 <sect4 id="dvb"> | |
1538 <title>DVB</title> | |
1539 <para> | |
1540 <application>MPlayer</application> supports cards with the Siemens DVB chipset | |
1541 from vendors like Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB | |
1542 drivers are available from the <ulink url="http://www.linuxtv.org">Linux TV site</ulink>. | |
1543 If you want to do software transcoding you should have at least a 1GHz CPU. | |
1544 </para> | |
1545 | |
1546 <para> | |
1547 Configure should detect your DVB card. If it did not, force detection with | |
1548 </para> | |
1549 | |
1550 <para><screen>./configure --enable-dvb</screen></para> | |
1551 | |
1552 <para>If you have ost headers at a non-standard path, set the path with</para> | |
1553 | |
10111 | 1554 <para><screen>./configure --with-extraincdir=<replaceable>DVB source directory</replaceable>/ost/include |
9675 | 1555 </screen></para> |
1556 | |
1557 <para>Then compile and install as usual.</para> | |
1558 | |
1559 <formalpara> | |
1560 <title>USAGE</title> | |
1561 <para> | |
1562 Hardware decoding (playing standard MPEG1/2 files) can be done with this command: | |
1563 </para> | |
1564 </formalpara> | |
1565 <para><screen>mplayer -ao mpegpes -vo mpegpes file.mpg|vob</screen></para> | |
1566 | |
1567 <para> | |
1568 Software decoding or transcoding different formats to MPEG1 can be achieved using | |
1569 a command like this: | |
1570 </para> | |
1571 <para><screen> | |
1572 mplayer -ao mpegpes -vo mpegpes yourfile.ext | |
9677 | 1573 mplayer -ao mpegpes -vo mpegpes -vf expand yourfile.ext |
9675 | 1574 </screen></para> |
1575 | |
1576 <para> | |
1577 Note that DVB cards only support heights 288 and 576 for PAL or 240 and 480 for | |
10938 | 1578 NTSC. You <emphasis role="bold">must</emphasis> rescale for other heights by adding |
9675 | 1579 <option>scale=width:height</option> with the width and height you want to the |
9677 | 1580 <option>-vf</option> option. DVB cards accept various widths, like 720, 704, |
9675 | 1581 640, 512, 480, 352 etc and do hardware scaling in horizontal direction, so you |
1582 do not need to scale horizontally in most cases. For a 512x384 (aspect 4:3) | |
1583 DivX try: | |
1584 </para> | |
1585 | |
9677 | 1586 <para><screen>mplayer -ao mpegpes -vo mpegpes -vf scale=512:576</screen></para> |
9675 | 1587 |
1588 <para>If you have a widescreen movie and you do not want to scale it to full height, | |
1589 you can use the <option>expand=w:h</option> filter to add black bands. To view a | |
1590 640x384 DivX, try: | |
1591 </para> | |
1592 | |
9677 | 1593 <para><screen>mplayer -ao mpegpes -vo mpegpes -vf expand=640:576 file.avi |
9675 | 1594 </screen></para> |
1595 | |
1596 <para>If your CPU is too slow for a full size 720x576 DivX, try downscaling:</para> | |
1597 | |
9677 | 1598 <para><screen>mplayer -ao mpegpes -vo mpegpes -vf scale=352:576 file.avi |
9675 | 1599 </screen></para> |
1600 | |
1601 <para>If speed does not improve, try vertical downscaling, too:</para> | |
1602 | |
9677 | 1603 <para><screen>mplayer -ao mpegpes -vo mpegpes -vf scale=352:288 file.avi |
9675 | 1604 </screen></para> |
1605 | |
1606 <para> | |
1607 For OSD and subtitles use the OSD feature of the expand filter. So, instead of | |
1608 <option>expand=w:h</option> or <option>expand=w:h:x:y</option>, use | |
1609 <option>expand=w:h:x:y:1</option> (the 5th parameter <option>:1</option> | |
1610 at the end will enable OSD rendering). You may want to move the image up a bit | |
1611 to get a bigger black zone for subtitles. You may also want to move subtitles up, | |
1612 if they are outside your TV screen, use the <option>-subpos <0-100></option> | |
1613 option to adjust this (<option>-subpos 80</option> is a good choice). | |
1614 </para> | |
1615 | |
1616 <para> | |
1617 In order to play non-25fps movies on a PAL TV or with a slow CPU, add the | |
1618 <option>-framedrop</option> option. | |
1619 </para> | |
1620 | |
1621 <para> | |
1622 To keep the aspect ratio of DivX files and get the optimal scaling | |
1623 parameters (hardware horizontal scaling and software vertical scaling | |
1624 while keeping the right aspect ratio), use the new dvbscale filter: | |
1625 </para> | |
1626 | |
1627 <para><screen> | |
10682 | 1628 for a 4:3 TV: -vf dvbscale,scale=-1:0,expand=-1:576:-1:-1:1 |
1629 for a 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1 | |
9675 | 1630 </screen></para> |
1631 | |
1632 <formalpara> | |
1633 <title>FUTURE</title> | |
1634 <para> | |
1635 If you have questions or want to hear feature announcements and take part in | |
1636 discussions on this subject, join our | |
1637 <ulink url="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</ulink> | |
1638 mailing list. Please remember that the list language is English. | |
1639 </para> | |
1640 </formalpara> | |
1641 | |
1642 <para> | |
1643 In the future you may expect the ability to display OSD and subtitles using | |
1644 the native OSD feature of DVB cards, as well as more fluent playback of | |
1645 non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial | |
1646 decompression). | |
1647 </para> | |
1648 </sect4> | |
1649 | |
1650 <sect4 id="dxr2"> | |
1651 <title>DXR2</title> | |
1652 <para>MPlayer supports hardware accelerated playback with the Creative DXR2 card.</para> | |
1653 <para> | |
1654 First of all you will need properly installed DXR2 drivers. You can find | |
1655 the drivers and installation instructions at the | |
1656 <ulink url="http://dxr2.sourceforge.net/">DXR2 Resource Center</ulink> site. | |
1657 </para> | |
1658 | |
1659 <variablelist> | |
1660 <title>USAGE</title> | |
1661 <varlistentry> | |
1662 <term><option>-vo dxr2</option></term> | |
1663 <listitem><para>enable TV output</para></listitem> | |
1664 </varlistentry> | |
1665 | |
1666 <varlistentry> | |
1667 <term><option>-vo dxr2:x11</option> or <option>-vo dxr2:xv</option></term> | |
1668 <listitem><para>enable Overlay output in X11</para></listitem> | |
1669 </varlistentry> | |
1670 | |
1671 <varlistentry> | |
1672 <term><option>-dxr2 <option1:option2:...></option></term> | |
1673 <listitem><para>This option is used to control the DXR2 driver.</para></listitem> | |
1674 </varlistentry> | |
1675 </variablelist> | |
1676 | |
1677 <para> | |
1678 The overlay chipset used on the DXR2 is of pretty bad quality but the | |
1679 default settings should work for everybody. The OSD may be usable with the | |
1680 overlay (not on TV) by drawing it in the colorkey. With the default colorkey | |
1681 settings you may get variable results, usually you will see the colorkey | |
1682 around the characters or some other funny effect. But if you properly adjust | |
1683 the colorkey settings you should be able to get acceptable results. | |
1684 </para> | |
1685 | |
1686 <para>Please see the manpage for available options.</para> | |
1687 </sect4> | |
1688 | |
1689 <sect4 id="dxr3"> | |
1690 <title>DXR3/Hollywood+</title> | |
1691 <para> | |
1692 <application>MPlayer</application> supports hardware accelerated playback | |
1693 with the Creative DXR3 and Sigma Designs Hollywood Plus cards. These cards | |
1694 both use the em8300 MPEG decoder chip from Sigma Designs. | |
1695 </para> | |
1696 | |
1697 <para> | |
1698 First of all you will need properly installed DXR3/H+ drivers, version 0.12.0 | |
1699 or later. You can find the drivers and installation instructions at the | |
1700 <ulink url="http://dxr3.sourceforge.net/">DXR3 & Hollywood Plus for Linux</ulink> | |
10111 | 1701 site. <filename>configure</filename> should detect your card automatically, |
1702 compilation should go without problems. | |
9675 | 1703 </para> |
1704 | |
1705 <!-- FIXME: find a more clear presentation --> | |
1706 <variablelist> | |
1707 <title>USAGE</title> | |
1708 <varlistentry> | |
10111 | 1709 <term><option>-vo dxr3:prebuf:sync:norm=x:<replaceable>device</replaceable></option></term> |
9675 | 1710 <listitem><para> |
1711 <option>overlay</option> activates the overlay instead of TVOut. It requires | |
1712 that you have a properly configured overlay setup to work right. The easiest | |
1713 way to configure the overlay is to first run autocal. Then run mplayer with | |
1714 dxr3 output and without overlay turned on, run dxr3view. In dxr3view you can | |
1715 tweak the overlay settings and see the effects in realtime, perhaps this feature | |
1716 will be supported by the MPlayer GUI in the future. When overlay is properly set | |
10111 | 1717 up you will no longer need to use dxr3view. |
9675 | 1718 <option>prebuf</option> turns on prebuffering. Prebuffering is a feature of the |
1719 em8300 chip that enables it to hold more than one frame of video at a time. This | |
1720 means that when you are running with prebuffering MPlayer will try to keep the | |
1721 video buffer filled with data at all times. If you are on a slow machine MPlayer | |
1722 will probably use close to, or precisely 100% of CPU. This is especially common | |
1723 if you play pure MPEG streams (like DVDs, SVCDs a.s.o.) since MPlayer will not | |
1724 have to reencode it to MPEG it will fill the buffer very fast. | |
1725 With prebuffering video playback is <emphasis role="bold">much</emphasis> | |
1726 less sensitive to other programs hogging the CPU, it will not drop frames unless | |
1727 applications hog the CPU for a long time. | |
1728 When running without prebuffering the em8300 is much more sensitive to CPU load, | |
1729 so it is highly suggested that you turn on MPlayer's <option>-framedrop</option> | |
1730 option to avoid further loss of sync. | |
1731 <option>sync</option> will turn on the new sync-engine. This is currently an | |
1732 experimental feature. With the sync feature turned on the em8300's internal clock | |
1733 will be monitored at all times, if it starts to deviate from MPlayer's clock it | |
1734 will be reset causing the em8300 to drop any frames that are lagging behind. | |
1735 <option>norm=x</option> will set the TV norm of the DXR3 card without the need | |
1736 for external tools like em8300setup. Valid norms are 5 = NTSC, 4 = PAL-60, | |
1737 3 = PAL. Special norms are 2 (auto-adjust using PAL/PAL-60) and 1 (auto-adjust | |
1738 using PAL/NTSC) because they decide which norm to use by looking at the frame | |
1739 rate of the movie. norm = 0 (default) does not change the current norm. | |
10111 | 1740 <option><replaceable>device</replaceable></option> = device number to use if you have more than one em8300 |
9675 | 1741 card. |
1742 Any of these options may be left out. | |
1743 <option>:prebuf:sync</option> seems to work great when playing DivX movies. People | |
1744 have reported problems using the prebuf option when playing MPEG1/2 files. You | |
1745 might want to try running without any options first, if you have sync problems, | |
1746 or DVD subtitle problems, give <option>:sync</option> a try. | |
1747 </para></listitem> | |
1748 </varlistentry> | |
1749 | |
1750 <varlistentry> | |
1751 <term><option>-ao oss:/dev/em8300_ma-<replaceable>X</replaceable></option></term> | |
1752 <listitem><para> | |
1753 For audio output, where <replaceable>X</replaceable> is the device number (0 if one card). | |
1754 </para></listitem> | |
1755 </varlistentry> | |
1756 | |
1757 <varlistentry> | |
1758 <term><option>-aop list=resample:fout=<replaceable>xxxxx</replaceable></option></term> | |
1759 <listitem><para> | |
1760 The em8300 cannot play back samplerates lower than 44100Hz. If the sample | |
1761 rate is below 44100Hz select either 44100Hz or 48000Hz depending on which | |
1762 one matches closest. I.e. if the movie uses 22050Hz use 44100Hz as | |
1763 44100 / 2 = 22050, if it is 24000Hz use 48000Hz as 48000 / 2 = 24000 and so on. | |
1764 This does not work with digital audio output (<option>-ac hwac3</option>). | |
1765 </para></listitem> | |
1766 </varlistentry> | |
1767 | |
1768 <varlistentry> | |
9677 | 1769 <term><option>-vf lavc/fame</option></term> |
9675 | 1770 <listitem><para> |
1771 To watch non-MPEG content on the em8300 (i.e. DivX or RealVideo) you have to | |
1772 specify an MPEG1 video filter such as libavcodec (lavc) or libfame (fame). At | |
1773 the moment lavc is both faster and gives better image quality, it is suggested | |
1774 that you use that unless you have problems with it. See the man page for further | |
9677 | 1775 info about <option>-vf lavc/fame</option>. |
9675 | 1776 Using lavc is highly recommended. Currently there is no way of setting the fps |
1777 of the em8300 which means that it is fixed to 29.97fps. Because of this it is | |
10111 | 1778 highly recommended that you use <option>-vf lavc=<replaceable>quality</replaceable>:25</option> |
9675 | 1779 especially if you are using prebuffering. Then why 25 and not 29.97? Well, the |
1780 thing is that when you use 29.97 the picture becomes a bit jumpy. The reason for | |
1781 this is unknown to us. If you set it to somewhere between 25 and 27 the picture | |
1782 becomes stable. For now all we can do is accept this for a fact. | |
1783 </para></listitem> | |
1784 </varlistentry> | |
1785 | |
1786 <varlistentry> | |
9677 | 1787 <term><option>-vf expand=-1:-1:-1:-1:1</option></term> |
9675 | 1788 <listitem><para> |
1789 Although the DXR3 driver can put some OSD onto the MPEG1/2/4 video, it has | |
1790 much lower quality than MPlayer's traditional OSD, and has several refresh | |
1791 problems as well. The command line above will firstly convert the input | |
1792 video to MPEG4 (this is mandatory, sorry), then apply an expand filter which | |
1793 won't expand anything (-1: default), but apply the normal OSD onto the picture | |
1794 (that's what the "1" at the end does). | |
1795 </para></listitem> | |
1796 </varlistentry> | |
1797 | |
1798 <varlistentry> | |
1799 <term><option>-ac hwac3</option></term> | |
1800 <listitem><para> | |
1801 The em8300 supports playing back AC3 audio (surround sound) through the | |
1802 digital audio output of the card. See the <option>-ao oss</option> option above, | |
1803 it must be used to specify the DXR3's output instead of a soundcard. | |
1804 </para></listitem> | |
1805 </varlistentry> | |
1806 </variablelist> | |
1807 </sect4> | |
1808 | |
1809 </sect3> | |
1810 | |
1811 <sect3 id="other"> | |
1812 <title>Other visualization hardware</title> | |
1813 | |
1814 <sect4 id="zr"> | |
1815 <title>Zr</title> | |
1816 | |
1817 <para> | |
1818 This is a display-driver (<option>-vo zr</option>) for a number of MJPEG | |
1819 capture/playback cards (tested for DC10+ and Buz, and it should work for the | |
1820 LML33, the DC10). The driver works by encoding the frame to JPEG and then | |
1821 sending it to the card. For the JPEG encoding <systemitem>libavcodec</systemitem> | |
1822 is used, and required. With the special <emphasis>cinerama</emphasis> mode, | |
1823 you can watch movies in true wide screen provided that you have two beamers | |
1824 and two MJPEG cards. Depending on resolution and quality settings, this driver | |
1825 may require a lot of CPU power, remember to specify <option>-framedrop</option> | |
1826 if your machine is too slow. Note: My AMD K6-2 350MHz is (with | |
1827 <option>-framedrop</option>) quite adequate for watching VCD sized material and | |
1828 downscaled movies. | |
1829 </para> | |
1830 | |
1831 <para> | |
1832 This driver talks to the kernel driver available at | |
1833 <ulink url="http://mjpeg.sourceforge.net"/>, so | |
1834 you must get it working first. The presence of an MJPEG card is autodetected by the | |
1835 <filename>configure</filename> script, if autodetection fails, force detection with | |
1836 <screen>./configure --enable-zr</screen> | |
1837 </para> | |
1838 <para> | |
1839 The output can be controlled by several options, a long description of the | |
1840 options can be found in the man page, a short list of options can be viewed | |
1841 by running | |
1842 <screen>mplayer -zrhelp</screen> | |
1843 </para> | |
1844 | |
1845 <para> | |
1846 Things like scaling and the OSD (on screen display) are not handled by | |
1847 this driver but can be done using the video filters. For example, suppose | |
1848 that you have a movie with a resolution of 512x272 and you want to view it | |
1849 fullscreen on your DC10+. There are three main possibilities, you may scale | |
1850 the movie to a width of 768, 384 or 192. For performance and quality reasons, | |
1851 I would choose to scale the movie to 384x204 using the fast bilinear software | |
1852 scaler. The commandline is | |
9677 | 1853 <screen>mplayer -vo zr -sws 0 -vf scale=384:204 movie.avi</screen> |
9675 | 1854 </para> |
1855 | |
1856 <para> | |
1857 Cropping can be done by the <systemitem>crop</systemitem> filter and by this | |
1858 driver itself. Suppose that a movie is too wide for display on your Buz and | |
1859 that you want to use <option>-zrcrop</option> to make the movie less wide, | |
9784
286ac03ce5c5
Typos, noticed by Roberto Togni <r_togni@libero.it>.
diego
parents:
9683
diff
changeset
|
1860 then you would issue the following command |
9675 | 1861 <screen>mplayer -vo zr -zrcrop 720x320+80+0 benhur.avi</screen> |
1862 </para> | |
1863 | |
1864 <para> | |
10111 | 1865 if you want to use the <option>crop</option> filter, you would do |
9677 | 1866 <screen>mplayer -vo zr -vf crop=720:320:80:0 benhur.avi</screen> |
9675 | 1867 </para> |
1868 | |
1869 <para> | |
10975
96cd8d4e98d4
Typos and some confusion noticed by Lukasz frogu Proszek <l_j_p@wp.pl>.
diego
parents:
10971
diff
changeset
|
1870 Extra occurrences of <option>-zrcrop</option> invoke <emphasis>cinerama</emphasis> |
96cd8d4e98d4
Typos and some confusion noticed by Lukasz frogu Proszek <l_j_p@wp.pl>.
diego
parents:
10971
diff
changeset
|
1871 mode, i.e. you can distribute the movie over several TV's or beamers to create a |
9675 | 1872 larger screen. Suppose you have two beamers. The left one is connected to your |
1873 Buz at <systemitem>/dev/video1</systemitem> and the right one is connected to | |
1874 your DC10+ at <systemitem>/dev/video0</systemitem>. The movie has a resolution | |
1875 of 704x288. Suppose also that you want the right beamer in black and white and | |
10975
96cd8d4e98d4
Typos and some confusion noticed by Lukasz frogu Proszek <l_j_p@wp.pl>.
diego
parents:
10971
diff
changeset
|
1876 that the left beamer should have JPEG frames at quality 10, then you would |
9675 | 1877 issue the following command |
1878 <screen> | |
1879 mplayer -vo zr -zrdev /dev/video0 -zrcrop 352x288+352+0 -zrxdoff 0 -zrbw \ | |
1880 -zrcrop 352x288+0+0 -zrdev /dev/video1 -zrquality 10 movie.avi | |
1881 </screen> | |
1882 </para> | |
1883 | |
1884 <para> | |
1885 You see that the options appearing before the second <option>-zrcrop</option> | |
1886 only apply to the DC10+ and that the options after the second | |
1887 <option>-zrcrop</option> apply to the Buz. The maximum number of MJPEG cards | |
9784
286ac03ce5c5
Typos, noticed by Roberto Togni <r_togni@libero.it>.
diego
parents:
9683
diff
changeset
|
1888 participating in <emphasis>cinerama</emphasis> is four, so you can build a |
9675 | 1889 2x2 vidiwall. |
1890 </para> | |
1891 | |
1892 <para> | |
10111 | 1893 Finally an important remark: Do not start or stop XawTV on the playback device |
9675 | 1894 during playback, it will crash your computer. It is, however, fine to |
1895 <emphasis role="bold">FIRST</emphasis> start XawTV, <emphasis role="bold">THEN</emphasis> | |
1896 start MPlayer, wait for MPlayer to finish and <emphasis role="bold">THEN</emphasis> | |
1897 stop XawTV. | |
1898 </para> | |
1899 </sect4> | |
1900 | |
1901 <sect4 id="blinkenlights"> | |
1902 <title>Blinkenlights</title> | |
1903 <para> | |
1904 This driver is capable of playback using the Blinkenlights UDP protocol. If you | |
1905 don't know what <ulink url="http://www.blinkenlights.de/">Blinkenlights</ulink> | |
1906 is, you don't need this driver. | |
1907 </para> | |
1908 </sect4> | |
1909 </sect3> | |
1910 | |
1911 <sect3 id="tvout"> | |
1912 <title>TV-out support</title> | |
1913 | |
1914 <sect4 id="tvout-mga-g400"> | |
1915 <title>Matrox G400 cards</title> | |
1916 | |
1917 <para> | |
1918 Under Linux you have two methods to get G400 TV out working: | |
1919 </para> | |
1920 | |
1921 <important> | |
1922 <para> | |
1923 for Matrox G450/G550 TV-out instructions, please see the next section! | |
1924 </para> | |
1925 </important> | |
1926 | |
1927 <variablelist> | |
1928 <varlistentry> | |
1929 <term>XFree86</term> | |
1930 <listitem><para> | |
1931 Using the driver and the HAL module, available from <ulink | |
1932 url="http://www.matrox.com">Matrox's site</ulink>. This will give you X | |
1933 on the TV. | |
1934 </para><para> | |
1935 <emphasis role="bold">This method doesn't give you accelerated playback</emphasis> | |
1936 as under Windows! The second head has only YUV framebuffer, the <emphasis>BES</emphasis> | |
1937 (Back End Scaler, the YUV scaler on G200/G400/G450/G550 cards) doesn't | |
1938 work on it! The windows driver somehow workarounds this, probably by | |
1939 using the 3D engine to zoom, and the YUV framebuffer to display the | |
1940 zoomed image. If you really want to use X, use the <option>-vo x11 -fs | |
1941 -zoom</option> options, but it will be <emphasis role="bold">SLOW</emphasis>, | |
1942 and has <emphasis role="bold">Macrovision</emphasis> copy protection enabled | |
1943 (you can "workaround" Macrovision using this | |
10111 | 1944 <ulink url="http://avifile.sourceforge.net/mgamacro.pl">perl script</ulink>). |
9675 | 1945 </para></listitem> |
1946 </varlistentry> | |
1947 <varlistentry> | |
1948 <term>Framebuffer</term> | |
1949 <listitem><para> | |
1950 Using the <emphasis role="bold">matroxfb modules</emphasis> in the 2.4 | |
1951 kernels. 2.2 kernels don't have the TVout feature in them, thus unusable | |
1952 for this. You have to enable ALL matroxfb-specific feature during compilation | |
10254 | 1953 (except MultiHead), and compile them into <emphasis role="bold">modules</emphasis>! |
9675 | 1954 You'll also need I2C enabled. |
1955 </para> | |
1956 | |
1957 <procedure> | |
1958 <step><para> | |
1959 Enter <filename class="directory">TVout/matroxset</filename> and type | |
1960 <command>make</command>. Install <filename class="directory">matroxset</filename> into | |
1961 somewhere in your <envar>PATH</envar>. | |
1962 </para></step> | |
1963 <step><para> | |
1964 If you don't have <command>fbset</command> installed, enter | |
1965 <filename class="directory">TVout/fbset</filename> and type <command>make</command>. | |
1966 Install <filename class="directory">fbset</filename> into somewhere in your | |
1967 <envar>PATH</envar>. | |
1968 </para></step> | |
1969 <step><para> | |
10254 | 1970 If you don't have <command>con2fb</command> installed, enter |
1971 <filename class="directory">TVout/con2fb</filename> and type <command>make</command>. | |
1972 Install <filename class="directory">con2fb</filename> into somewhere in your | |
1973 <envar>PATH</envar>. | |
1974 </para></step> | |
1975 <step><para> | |
9675 | 1976 Then enter into the <filename class="directory">TVout/</filename> directory |
1977 in the <application>MPlayer</application> source, and execute | |
1978 <filename>./modules</filename> as root. Your text-mode console will | |
1979 enter into framebuffer mode (no way back!). | |
1980 </para></step> | |
1981 <step><para> | |
1982 Next, EDIT and run the <filename>./matroxtv</filename> script. This will | |
1983 present you to a very simple menu. Press <keycap>2</keycap> and | |
1984 <keycap>Enter</keycap>. Now you should have the same picture on your | |
10111 | 1985 monitor, and TV. If the TV (PAL by default) |
9675 | 1986 picture has some weird stripes on it, the script wasn't able to set the |
1987 resolution correctly (to 640x512 by default). Try other resolutions | |
1988 from the menu and/or experiment with fbset. | |
1989 </para></step> | |
1990 <step><para> | |
1991 Yoh. Next task is to make the cursor on tty1 (or whatever) to | |
1992 disappear, and turn off screen blanking. Execute the following | |
1993 commands: | |
1994 | |
1995 <screen> | |
1996 echo -e '\033[?25l' | |
1997 setterm -blank 0<!-- | |
1998 --></screen> | |
1999 or | |
2000 <screen> | |
2001 setterm -cursor off | |
2002 setterm -blank 0<!-- | |
2003 --></screen> | |
2004 | |
2005 You possibly want to put the above into a script, and also clear the | |
2006 screen. To turn the cursor back: | |
2007 <screen>echo -e '\033[?25h'</screen> or | |
2008 <screen>setterm -cursor on</screen> | |
2009 </para></step> | |
2010 <step><para> | |
2011 Yeah kewl. Start movie playing with | |
2012 <screen> | |
2013 mplayer -vo mga -fs -screenw 640 -screenh 512 <replaceable>filename</replaceable><!-- | |
2014 --></screen> | |
2015 | |
2016 (If you use X, now change to matroxfb with for example | |
2017 <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>F1</keycap>.) | |
2018 Change <literal>640</literal> and <literal>512</literal> if you set | |
2019 the resolution to other... | |
2020 </para></step> | |
2021 <step><para> | |
2022 <emphasis role="bold">Enjoy the ultra-fast ultra-featured Matrox TV | |
2023 output (better than Xv)!</emphasis> | |
2024 </para></step> | |
2025 </procedure> | |
2026 </listitem> | |
2027 </varlistentry> | |
2028 </variablelist> | |
2029 | |
2030 <formalpara> | |
2031 <title>Building a Matrox TV-out cable</title> | |
2032 <para> | |
2033 No one takes any responsibility, nor guarantee for any damage caused | |
2034 by this documentation. | |
2035 </para> | |
2036 </formalpara> | |
2037 | |
2038 <formalpara> | |
2039 <title>Cable for G400</title> | |
2040 <para> | |
2041 The CRTC2 connector's fourth pin is the composite video signal. The | |
2042 ground are the sixth, seventh and eighth pins. (info contributed | |
2043 from Balázs Rácz) | |
2044 </para> | |
2045 </formalpara> | |
2046 | |
2047 <formalpara> | |
2048 <title>Cable for G450</title> | |
2049 <para> | |
2050 The CRTC2 connector's first pin is the composite video signal. The | |
2051 ground are the fifth, sixth, seventh, and fifteenth (5, 6, 7, 15) | |
2052 pins. (info contributed from Balázs Kerekes) | |
2053 </para> | |
2054 </formalpara> | |
2055 </sect4> | |
2056 | |
2057 <sect4 id="tv-out_matrox_g450"> | |
2058 <title>Matrox G450/G550 cards</title> | |
2059 <para> | |
2060 TV output support for these cards has only been recently introduced, and is | |
2061 not yet in the mainstream kernel. Currently the <emphasis role="bold">mga_vid</emphasis> | |
2062 module can't be used AFAIK, because the G450/G550 driver works only in one | |
2063 configuration: the first CRTC chip (with much more features) on the first display | |
2064 (on monitor), and the second CRTC (no <emphasis role="bold">BES</emphasis> - for | |
2065 explanation on BES, please see the G400 section above) on TV. So you can only | |
2066 use <application>MPlayer</application>'s <emphasis>fbdev</emphasis> output driver | |
2067 at the present. | |
2068 </para> | |
2069 | |
2070 <para> | |
2071 The first CRTC can't be routed to the second head currently. The author of the | |
2072 kernel matroxfb driver - Petr Vandrovec - will maybe make support for this, by | |
2073 displaying the first CRTC's output onto both of the heads at once, as currently | |
2074 recommended for G400, see the section above. | |
2075 </para> | |
2076 | |
2077 <para> | |
2078 The necessary kernel patch and the detailed howto is downloadable from | |
9948 | 2079 <ulink url="http://www.bglug.ca/matrox_tvout/"/> |
9675 | 2080 </para> |
2081 </sect4> | |
2082 | |
2083 | |
2084 <sect4 id="tvout-ati"> | |
2085 <title>ATI cards</title> | |
2086 | |
2087 <formalpara> | |
2088 <title>PREAMBLE</title> | |
2089 <para> | |
2090 Currently ATI doesn't want to support any of its TV-out chips under Linux, | |
2091 because of their licensed Macrovision technology. | |
2092 </para> | |
2093 </formalpara> | |
2094 | |
2095 <itemizedlist> | |
2096 <title>ATI CARDS TV-OUT STATUS ON LINUX</title> | |
2097 <listitem><simpara> | |
2098 <emphasis role="bold">ATI Mach64</emphasis>: | |
2099 supported by <ulink url="http://gatos.sf.net">gatos</ulink>. | |
2100 </simpara></listitem> | |
2101 <listitem><simpara> | |
2102 <emphasis role="bold">ASIC Radeon VIVO</emphasis>: | |
2103 supported by <ulink url="http://gatos.sf.net">gatos</ulink>. | |
2104 </simpara></listitem> | |
2105 <listitem><simpara> | |
2106 <emphasis role="bold">Radeon</emphasis> and <emphasis role="bold">Rage128</emphasis>: | |
2107 supported by <application>MPlayer</application>! | |
2108 Check <link linkend="vesa">VESA driver</link> and | |
2109 <link linkend="vidix">VIDIX</link> sections. | |
2110 </simpara></listitem> | |
2111 <listitem><simpara> | |
2112 <emphasis role="bold">Rage Mobility P/M, Radeon, Rage 128, Mobility M3/M4</emphasis>: | |
2113 supported by <ulink url="http://www.stud.uni-hamburg.de/users/lennart/projects/atitvout/">atitvout</ulink>. | |
2114 </simpara></listitem> | |
2115 </itemizedlist> | |
2116 | |
2117 <para> | |
2118 On other cards, just use the <link linkend="vesa">VESA</link> driver, | |
2119 without VIDIX. Powerful CPU is needed, though. | |
2120 </para> | |
2121 | |
2122 <para> | |
2123 Only thing you need to do - <emphasis role="bold">Have the TV connector | |
2124 plugged in before booting your PC</emphasis> since video BIOS initializes | |
2125 itself only once during POST procedure. | |
2126 </para> | |
2127 </sect4> | |
2128 | |
2129 | |
2130 <sect4 id="tvout-voodoo"> | |
2131 <title>Voodoo 3</title> | |
2132 <para> | |
2133 Check <ulink url="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</ulink>. | |
2134 </para> | |
2135 </sect4> | |
2136 | |
2137 <sect4 id="tvout-nvidia"> | |
10111 | 2138 <title>nVidia</title> |
9675 | 2139 <para> |
2140 First, you MUST download the closed-source drivers from <ulink url="http://nvidia.com"/>. | |
2141 I will not describe the installation and configuration process because it does not cover | |
2142 the scope of this documentation. | |
2143 </para> | |
2144 | |
2145 <para> | |
2146 After XFree86, XVideo, and 3D acceleration is properly working, edit your | |
2147 card's Device section in the <filename>XF86Config</filename> file, according | |
2148 to the following example (adapt for your card/TV): | |
2149 | |
2150 <programlisting> | |
2151 Section "Device" | |
2152 Identifier "GeForce" | |
2153 VendorName "ASUS" | |
2154 BoardName "nVidia GeForce2/MX 400" | |
2155 Driver "nvidia" | |
2156 #Option "NvAGP" "1" | |
2157 Option "NoLogo" | |
2158 Option "CursorShadow" "on" | |
2159 | |
2160 Option "TwinView" | |
2161 Option "TwinViewOrientation" "Clone" | |
2162 Option "MetaModes" "1024x768,640x480" | |
2163 Option "ConnectedMonitor" "CRT, TV" | |
2164 Option "TVStandard" "PAL-B" | |
2165 Option "TVOutFormat" "Composite" | |
2166 | |
2167 EndSection | |
2168 </programlisting> | |
2169 </para> | |
2170 | |
2171 <para> | |
2172 Of course the important thing is the TwinView part. | |
2173 </para> | |
2174 </sect4> | |
2175 </sect3> | |
2176 </sect2> |