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