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