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