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