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