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