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