Mercurial > mplayer.hg
annotate DOCS/xml/en/video.xml @ 24689:85f578745278
Documentation follows implementation: Encrytped DVB channels are never
skipped.
(German was wrong anyway)
author | cehoyos |
---|---|
date | Fri, 05 Oct 2007 12:36:17 +0000 |
parents | bdef7723fd23 |
children | 119acb03c645 |
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> |
8e92dd0ff93a
Add YUY2 and back end scaling on S3 Virge chips in combination with fbdev.
gpoirier
parents:
17559
diff
changeset
|
196 There is now a native framebuffer driver for S3 Virge cards similiar to |
18547 | 197 tdfxfb. Set up your framebuffer (e.g. append |
20857 | 198 "<option>vga=792 video=vesa:mtrr</option>" to your kernel comand line) and use |
18535
8e92dd0ff93a
Add YUY2 and back end scaling on S3 Virge chips in combination with fbdev.
gpoirier
parents:
17559
diff
changeset
|
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 |
9babdd441b76
Some more details for the mga_vid section taken from drivers/README.
diego
parents:
22384
diff
changeset
|
841 a Linux kernel module that utilitizes the Matrox G200/G400/G450/G550 video |
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> | |
857 To use it, you first have to compile <filename>mga_vid.o</filename>: | |
858 <screen> | |
859 cd drivers | |
860 make<!-- | |
861 --></screen> | |
20862 | 862 </para></step> |
9675 | 863 <step><para> |
22686
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
864 Then run (as <systemitem class="username">root</systemitem>) |
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
865 <screen>make install</screen> |
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
866 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
|
867 Load the driver with |
9675 | 868 <screen>insmod mga_vid.o</screen> |
20862 | 869 </para></step> |
9675 | 870 <step><para> |
871 You should verify the memory size detection using the | |
872 <command>dmesg</command> command. If it's bad, use the | |
873 <option>mga_ram_size</option> option | |
874 (<command>rmmod mga_vid</command> first), | |
875 specify card's memory size in MB: | |
876 <screen>insmod mga_vid.o mga_ram_size=16</screen> | |
20862 | 877 </para></step> |
9675 | 878 <step><para> |
879 To make it load/unload automatically when needed, first insert the | |
880 following line at the end of <filename>/etc/modules.conf</filename>: | |
12815 | 881 |
9675 | 882 <programlisting>alias char-major-178 mga_vid</programlisting> |
20862 | 883 </para></step> |
9675 | 884 <step><para> |
885 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
|
886 <command>./configure</command> will detect |
9675 | 887 <filename>/dev/mga_vid</filename> and build the 'mga' driver. Using it |
888 from <application>MPlayer</application> goes by <option>-vo mga</option> | |
889 if you have matroxfb console, or <option>-vo xmga</option> under XFree86 | |
890 3.x.x or 4.x.x. | |
20862 | 891 </para></step> |
9675 | 892 </procedure> |
893 | |
894 <para> | |
895 The mga_vid driver cooperates with Xv. | |
896 </para> | |
897 | |
898 <para> | |
899 The <filename>/dev/mga_vid</filename> device file can be read for some | |
900 info, for example by | |
901 <screen>cat /dev/mga_vid</screen> | |
902 and can be written for brightness change: | |
903 <screen>echo "brightness=120" > /dev/mga_vid</screen> | |
904 </para> | |
22661
9babdd441b76
Some more details for the mga_vid section taken from drivers/README.
diego
parents:
22384
diff
changeset
|
905 |
9babdd441b76
Some more details for the mga_vid section taken from drivers/README.
diego
parents:
22384
diff
changeset
|
906 <para> |
9babdd441b76
Some more details for the mga_vid section taken from drivers/README.
diego
parents:
22384
diff
changeset
|
907 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
|
908 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
|
909 </para> |
9babdd441b76
Some more details for the mga_vid section taken from drivers/README.
diego
parents:
22384
diff
changeset
|
910 |
22836 | 911 </sect1> |
9675 | 912 |
20862 | 913 <!-- ********** --> |
9675 | 914 |
22836 | 915 <sect1 id="tdfxfb" xreflabel="3Dfx YUV support (tdfxfb)"> |
9675 | 916 <title>3Dfx YUV support</title> |
20862 | 917 |
9675 | 918 <para> |
919 This driver uses the kernel's tdfx framebuffer driver to play movies with | |
920 YUV acceleration. You'll need a kernel with tdfxfb support, and recompile | |
921 with | |
922 <screen>./configure --enable-tdfxfb</screen> | |
923 </para> | |
22836 | 924 </sect1> |
9675 | 925 |
20862 | 926 <!-- ********** --> |
9675 | 927 |
22836 | 928 <sect1 id="tdfx_vid"> |
21878 | 929 <title>tdfx_vid</title> |
930 | |
931 <para> | |
932 This is a combination of a Linux kernel module and a video output | |
933 driver, similar to <link linkend="mga_vid">mga_vid</link>. | |
934 You'll need a 2.4.x kernel with the <systemitem>agpgart</systemitem> | |
935 driver since <systemitem>tdfx_vid</systemitem> uses AGP. | |
936 Pass <option>--enable-tdfxfb</option> to <command>configure</command> | |
937 to build the video output driver and build the kernel module with | |
938 the following instructions. | |
939 </para> | |
940 | |
941 <procedure> | |
942 <title>Installing the tdfx_vid.o kernel module:</title> | |
943 <step><para> | |
944 Compile <filename>tdfx_vid.o</filename>: | |
945 <screen> | |
946 cd drivers | |
22668 | 947 make</screen> |
21878 | 948 </para></step> |
949 <step><para> | |
22686
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
950 Then run (as <systemitem class="username">root</systemitem>) |
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
951 <screen>make install</screen> |
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
952 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
|
953 Load the driver with |
21878 | 954 <screen>insmod tdfx_vid.o</screen> |
955 </para></step> | |
956 <step><para> | |
957 To make it load/unload automatically when needed, first insert the | |
958 following line at the end of <filename>/etc/modules.conf</filename>: | |
959 | |
960 <programlisting>alias char-major-178 tdfx_vid</programlisting> | |
961 </para></step> | |
962 </procedure> | |
963 | |
22686
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
964 <para> |
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
965 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
|
966 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
|
967 </para> |
2677b18556f9
'make install' now takes care of most manual installation steps for *_vid.o.
diego
parents:
22677
diff
changeset
|
968 |
22836 | 969 </sect1> |
21878 | 970 |
971 <!-- ********** --> | |
972 | |
22836 | 973 <sect1 id="opengl"> |
9675 | 974 <title>OpenGL output</title> |
975 | |
976 <para> | |
977 <application>MPlayer</application> supports displaying movies using OpenGL, | |
978 but if your platform/driver supports xv as should be the case on a PC with | |
979 Linux, use xv instead, OpenGL performance is considerably worse. If you | |
980 have an X11 implementation without xv support, OpenGL is a viable | |
981 alternative. | |
982 </para> | |
983 | |
984 <para> | |
985 Unfortunately not all drivers support this feature. The Utah-GLX drivers | |
986 (for XFree86 3.3.6) support it for all cards. | |
13977 | 987 See <ulink url="http://utah-glx.sf.net"/> for details about how to |
9675 | 988 install it. |
989 </para> | |
990 | |
991 <para> | |
992 XFree86(DRI) 4.0.3 or later supports OpenGL with Matrox and Radeon cards, | |
993 4.2.0 or later supports Rage128. | |
13977 | 994 See <ulink url="http://dri.sf.net"/> for download and installation |
9675 | 995 instructions. |
996 </para> | |
10526 | 997 |
998 <para> | |
999 A hint from one of our users: the GL video output can be used to get | |
1000 vsynced TV output. You'll have to set an environment variable (at | |
1001 least on nVidia): | |
1002 </para> | |
1003 | |
1004 <para> | |
20857 | 1005 <command>export __GL_SYNC_TO_VBLANK=1</command> |
10526 | 1006 </para> |
22836 | 1007 </sect1> |
9675 | 1008 |
20862 | 1009 <!-- ********** --> |
9675 | 1010 |
22836 | 1011 <sect1 id="aalib"> |
21521 | 1012 <title>AAlib – text mode displaying</title> |
9675 | 1013 |
1014 <para> | |
1015 AAlib is a library for displaying graphics in text mode, using powerful | |
1016 ASCII renderer. There are <emphasis>lots</emphasis> of programs already | |
1017 supporting it, like Doom, Quake, etc. <application>MPlayer</application> | |
10111 | 1018 contains a very usable driver for it. If <filename>./configure</filename> |
9675 | 1019 detects aalib installed, the aalib libvo driver will be built. |
1020 </para> | |
1021 | |
1022 <para> | |
1023 You can use some keys in the AA Window to change rendering options: | |
1024 </para> | |
1025 | |
1026 <informaltable> | |
1027 <tgroup cols="2"> | |
1028 <thead> | |
1029 <row><entry>Key</entry><entry>Action</entry></row> | |
1030 </thead> | |
1031 <tbody> | |
1032 <row><entry><keycap>1</keycap></entry><entry> | |
1033 decrease contrast | |
20862 | 1034 </entry></row> |
9675 | 1035 <row><entry><keycap>2</keycap></entry><entry> |
1036 increase contrast | |
20862 | 1037 </entry></row> |
9675 | 1038 <row><entry><keycap>3</keycap></entry><entry> |
1039 decrease brightness | |
20862 | 1040 </entry></row> |
9675 | 1041 <row><entry><keycap>4</keycap></entry><entry> |
1042 increase brightness | |
20862 | 1043 </entry></row> |
9675 | 1044 <row><entry><keycap>5</keycap></entry><entry> |
1045 switch fast rendering on/off | |
20862 | 1046 </entry></row> |
9675 | 1047 <row><entry><keycap>6</keycap></entry><entry> |
1048 set dithering mode (none, error distribution, Floyd Steinberg) | |
20862 | 1049 </entry></row> |
9675 | 1050 <row><entry><keycap>7</keycap></entry><entry> |
1051 invert image | |
20862 | 1052 </entry></row> |
9675 | 1053 <row><entry><keycap>8</keycap></entry><entry> |
1054 toggles between aa and <application>MPlayer</application> control | |
20862 | 1055 </entry></row> |
9675 | 1056 </tbody> |
1057 </tgroup> | |
1058 </informaltable> | |
1059 | |
1060 <variablelist> | |
1061 <title>The following command line options can be used:</title> | |
1062 <varlistentry> | |
1063 <term><option>-aaosdcolor=<replaceable>V</replaceable></option></term> | |
1064 <listitem><para> | |
1065 change OSD color | |
20862 | 1066 </para></listitem> |
9675 | 1067 </varlistentry> |
1068 <varlistentry> | |
1069 <term><option>-aasubcolor=<replaceable>V</replaceable></option></term> | |
1070 <listitem><para> | |
18649 | 1071 Change subtitle color |
9675 | 1072 </para><para> |
1073 where <replaceable>V</replaceable> can be: | |
1074 <literal>0</literal> (normal), | |
1075 <literal>1</literal> (dark), | |
1076 <literal>2</literal> (bold), | |
1077 <literal>3</literal> (bold font), | |
1078 <literal>4</literal> (reverse), | |
1079 <literal>5</literal> (special). | |
20862 | 1080 </para></listitem> |
9675 | 1081 </varlistentry> |
1082 </variablelist> | |
1083 | |
1084 <variablelist> | |
1085 <title>AAlib itself provides a large sum of options. Here are some | |
1086 important:</title> | |
1087 <varlistentry> | |
1088 <term><option>-aadriver</option></term> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1089 <listitem><para> |
18649 | 1090 Set recommended aa driver (X11, curses, Linux). |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1091 </para></listitem> |
9675 | 1092 </varlistentry> |
1093 <varlistentry> | |
1094 <term><option>-aaextended</option></term> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1095 <listitem><para> |
18649 | 1096 Use all 256 characters. |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1097 </para></listitem> |
9675 | 1098 </varlistentry> |
1099 <varlistentry> | |
1100 <term><option>-aaeight</option></term> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1101 <listitem><para> |
18649 | 1102 Use eight bit ASCII. |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1103 </para></listitem> |
9675 | 1104 </varlistentry> |
1105 <varlistentry> | |
1106 <term><option>-aahelp</option></term> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1107 <listitem><para> |
18649 | 1108 Prints out all aalib options. |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1109 </para></listitem> |
9675 | 1110 </varlistentry> |
1111 </variablelist> | |
1112 | |
21521 | 1113 <note><para> |
9675 | 1114 The rendering is very CPU intensive, especially when using AA-on-X |
1115 (using aalib on X), and it's least CPU intensive on standard, | |
1116 non-framebuffer console. Use SVGATextMode to set up a big textmode, | |
12349 | 1117 then enjoy! (secondary head Hercules cards rock :)) (but IMHO you |
10111 | 1118 can use <option>-vf 1bpp</option> option to get graphics on hgafb:) |
21521 | 1119 </para></note> |
9675 | 1120 |
1121 <para> | |
1122 Use the <option>-framedrop</option> option if your computer isn't fast | |
1123 enough to render all frames! | |
1124 </para> | |
1125 | |
1126 <para> | |
1127 Playing on terminal you'll get better speed and quality using the Linux | |
1128 driver, not curses (<option>-aadriver linux</option>). But therefore you | |
1129 need write access on | |
1130 <filename>/dev/vcsa<replaceable><terminal></replaceable></filename>! | |
1131 That isn't autodetected by aalib, but vo_aa tries to find the best mode. | |
13977 | 1132 See <ulink url="http://aa-project.sf.net/tune"/> for further |
9675 | 1133 tuning issues. |
1134 </para> | |
22836 | 1135 </sect1> |
9675 | 1136 |
20862 | 1137 <!-- ********** --> |
9675 | 1138 |
22836 | 1139 <sect1 id="caca"> |
21521 | 1140 <title> |
1141 <systemitem class="library">libcaca</systemitem> – Color ASCII Art library | |
1142 </title> | |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1143 |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1144 <para> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1145 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
|
1146 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
|
1147 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
|
1148 <systemitem class="library">AAlib</systemitem> library. |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1149 <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
|
1150 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
|
1151 <systemitem class="library">slang</systemitem> library or the |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1152 <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
|
1153 <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
|
1154 using either <systemitem class="library">slang</systemitem> or |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1155 <systemitem class="library">ncurses</systemitem> (through Cygwin emulation) or |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1156 <systemitem class="library">conio.h</systemitem>. If |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1157 <filename>./configure</filename> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1158 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
|
1159 will be built. |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1160 </para> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1161 |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1162 <itemizedlist> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1163 <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
|
1164 the following:</title> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1165 <listitem><para> |
12349 | 1166 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
|
1167 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1168 <listitem><para> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1169 color image dithering |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1170 </para></listitem> |
12216
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 |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1173 <itemizedlist> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1174 <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
|
1175 following limitations:</title> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1176 <listitem><para> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1177 no support for brightness, contrast, gamma |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1178 </para></listitem> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1179 </itemizedlist> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1180 |
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 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
|
1183 </para> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1184 |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1185 <informaltable> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1186 <tgroup cols="2"> |
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 <row><entry>Key</entry><entry>Action</entry></row> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1189 </thead> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1190 <tbody> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1191 <row><entry><keycap>d</keycap></entry><entry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1192 Toggle <systemitem class="library">libcaca</systemitem> dithering methods. |
20862 | 1193 </entry></row> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1194 <row><entry><keycap>a</keycap></entry><entry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1195 Toggle <systemitem class="library">libcaca</systemitem> antialiasing. |
20862 | 1196 </entry></row> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1197 <row><entry><keycap>b</keycap></entry><entry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1198 Toggle <systemitem class="library">libcaca</systemitem> background. |
20862 | 1199 </entry></row> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1200 </tbody> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1201 </tgroup> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1202 </informaltable> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1203 |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1204 <variablelist> |
21521 | 1205 <title><systemitem class="library">libcaca</systemitem> will also look for |
1206 certain environment variables:</title> | |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1207 <varlistentry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1208 <term><option>CACA_DRIVER</option></term> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1209 <listitem><para> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1210 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
|
1211 </para></listitem> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1212 </varlistentry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1213 <varlistentry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1214 <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
|
1215 <listitem><para> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1216 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
|
1217 </para></listitem> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1218 </varlistentry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1219 <varlistentry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1220 <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
|
1221 <listitem><para> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1222 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
|
1223 </para></listitem> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1224 </varlistentry> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1225 </variablelist> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1226 |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1227 <para> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1228 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
|
1229 enough to render all frames. |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1230 </para> |
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1231 |
22836 | 1232 </sect1> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1233 |
20862 | 1234 <!-- ********** --> |
12216
d4e2bdc246a3
-vo caca documentation, patch by Pigeon <pigeon@pigeond.net>
diego
parents:
12188
diff
changeset
|
1235 |
22836 | 1236 <sect1 id="vesa"> |
9675 | 1237 <title>VESA - output to VESA BIOS</title> |
1238 | |
1239 <para> | |
1240 This driver was designed and introduced as a <emphasis role="bold">generic | |
1241 driver</emphasis> for any video card which has VESA VBE 2.0 compatible | |
1242 BIOS. Another advantage of this driver is that it tries to force TV output | |
1243 on. | |
1244 <citetitle>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, | |
1245 1998</citetitle> (Page 70) says: | |
1246 </para> | |
1247 | |
1248 <blockquote> | |
1249 <formalpara><title>Dual-Controller Designs</title> | |
1250 <para> | |
1251 VBE 3.0 supports the dual-controller design by assuming that since both | |
1252 controllers are typically provided by the same OEM, under control of a | |
1253 single BIOS ROM on the same graphics card, it is possible to hide the fact | |
1254 that two controllers are indeed present from the application. This has the | |
1255 limitation of preventing simultaneous use of the independent controllers, | |
1256 but allows applications released before VBE 3.0 to operate normally. The | |
1257 VBE Function 00h (Return Controller Information) returns the combined | |
1258 information of both controllers, including the combined list of available | |
14318 | 1259 modes. When the application selects a mode, the appropriate controller is |
1260 activated. Each of the remaining VBE functions then operates on the active | |
9675 | 1261 controller. |
1262 </para> | |
1263 </formalpara> | |
1264 </blockquote> | |
1265 | |
1266 <para> | |
1267 So you have chances to get working TV-out by using this driver. | |
1268 (I guess that TV-out frequently is standalone head or standalone output | |
1269 at least.) | |
1270 </para> | |
1271 | |
1272 <itemizedlist spacing="compact"> | |
1273 <title>ADVANTAGES</title> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1274 <listitem><para> |
9675 | 1275 You have chances to watch movies <emphasis role="bold">if Linux even doesn't |
1276 know</emphasis> your video hardware. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1277 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1278 <listitem><para> |
9675 | 1279 You don't need to have installed any graphics' related things on your |
13222 | 1280 Linux (like X11 (AKA XFree86), fbdev and so on). This driver can be run |
9675 | 1281 from <emphasis role="bold">text-mode</emphasis>. |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1282 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1283 <listitem><para> |
9675 | 1284 You have chances to get <emphasis role="bold">working TV-out</emphasis>. |
1285 (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
|
1286 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1287 <listitem><para> |
9675 | 1288 This driver calls <function>int 10h</function> handler thus it's not |
1289 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
|
1290 <emphasis>real</emphasis> BIOS in <emphasis>real-mode</emphasis> |
12315a6590a1
Clumsy wording improved byRuben Garcia <ruben@ugr.es> and
diego
parents:
10965
diff
changeset
|
1291 (actually in vm86 mode). |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1292 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1293 <listitem><para> |
9675 | 1294 You can use VIDIX with it, thus getting accelerated video display |
1295 <emphasis role="bold">and</emphasis> TV output at the same time! | |
1296 (Recommended for ATI cards.) | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1297 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1298 <listitem><para> |
10111 | 1299 If you have VESA VBE 3.0+, and you had specified |
11287 | 1300 <option>monitor-hfreq, monitor-vfreq, monitor-dotclock</option> somewhere |
12349 | 1301 (config file, or command line) you will get the highest possible refresh rate. |
10111 | 1302 (Using General Timing Formula). To enable this feature you have to specify |
1303 <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
|
1304 </para></listitem> |
9675 | 1305 </itemizedlist> |
1306 | |
1307 <itemizedlist spacing="compact"> | |
1308 <title>DISADVANTAGES</title> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1309 <listitem><para> |
9675 | 1310 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
|
1311 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1312 <listitem><para> |
9675 | 1313 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
|
1314 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1315 <listitem><para> |
9675 | 1316 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
|
1317 </para></listitem> |
9675 | 1318 </itemizedlist> |
1319 | |
21521 | 1320 <important><para> |
9675 | 1321 Don't use this driver with <emphasis role="bold">GCC 2.96</emphasis>! |
1322 It won't work! | |
21521 | 1323 </para></important> |
9675 | 1324 |
1325 <variablelist> | |
1326 <title>COMMAND LINE OPTIONS AVAILABLE FOR VESA</title> | |
1327 <varlistentry> | |
1328 <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
|
1329 <listitem><para> |
9675 | 1330 currently recognized: <literal>dga</literal> to force dga mode and |
1331 <literal>nodga</literal> to disable dga mode. In dga mode you can enable | |
10111 | 1332 double buffering via the <option>-double</option> option. Note: you may omit |
1333 these parameters to enable <emphasis role="bold">autodetection</emphasis> of | |
1334 dga mode. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1335 </para></listitem> |
9675 | 1336 </varlistentry> |
1337 </variablelist> | |
1338 | |
1339 <itemizedlist spacing="compact"> | |
1340 <title>KNOWN PROBLEMS AND WORKAROUNDS</title> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1341 <listitem><para> |
9675 | 1342 If you have installed <emphasis role="bold">NLS</emphasis> font on your |
1343 Linux box and run VESA driver from text-mode then after terminating | |
1344 <application>MPlayer</application> you will have | |
1345 <emphasis role="bold">ROM font</emphasis> loaded instead of national. | |
1346 You can load national font again by using <command>setsysfont</command> | |
15894 | 1347 utility from the Mandrake/Mandriva distribution for example. |
9675 | 1348 (<emphasis role="bold">Hint</emphasis>: The same utility is used for |
1349 localization of fbdev). | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1350 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1351 <listitem><para> |
9675 | 1352 Some <emphasis role="bold">Linux graphics drivers</emphasis> don't update |
1353 active <emphasis role="bold">BIOS mode</emphasis> in DOS memory. | |
1354 So if you have such problem - always use VESA driver only from | |
1355 <emphasis role="bold">text-mode</emphasis>. Otherwise text-mode (#03) will | |
1356 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
|
1357 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1358 <listitem><para> |
21521 | 1359 Often after terminating VESA driver you get |
1360 <emphasis role="bold">black</emphasis> screen. To return your screen to | |
21720 | 1361 original state - simply switch to other console (by pressing |
1362 <keycombo><keycap>Alt</keycap><keycap>F<x></keycap></keycombo>) | |
9675 | 1363 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
|
1364 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1365 <listitem><para> |
9675 | 1366 To get <emphasis role="bold">working TV-out</emphasis> you need have plugged |
1367 TV-connector in before booting your PC since video BIOS initializes | |
1368 itself only once during POST procedure. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1369 </para></listitem> |
9675 | 1370 </itemizedlist> |
22836 | 1371 </sect1> |
9675 | 1372 |
20862 | 1373 <!-- ********** --> |
9675 | 1374 |
22836 | 1375 <sect1 id="x11"> |
9675 | 1376 <title>X11</title> |
1377 | |
1378 <para> | |
1379 Avoid if possible. Outputs to X11 (uses shared memory extension), with no | |
1380 hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but | |
1381 still slow) software scaling, use the options <option>-fs -zoom</option>. | |
1382 Most cards have hardware scaling support, use the <option>-vo xv</option> | |
12349 | 1383 output for them, or <option>-vo xmga</option> for Matrox cards. |
9675 | 1384 </para> |
1385 | |
1386 <para> | |
1387 The problem is that most cards' driver doesn't support hardware | |
1388 acceleration on the second head/TV. In those cases, you see green/blue | |
1389 colored window instead of the movie. This is where this driver comes in | |
1390 handy, but you need powerful CPU to use software scaling. Don't use the SDL | |
1391 driver's software output+scaler, it has worse image quality! | |
1392 </para> | |
1393 | |
1394 <para> | |
1395 Software scaling is very slow, you better try changing video modes instead. | |
1396 It's very simple. See the <link linkend="dga-modelines">DGA section's | |
1397 modelines</link>, and insert them into your <filename>XF86Config</filename>. | |
1398 | |
1399 <itemizedlist spacing="compact"> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1400 <listitem><para> |
9675 | 1401 If you have XFree86 4.x.x: use the <option>-vm</option> option. It will |
1402 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
|
1403 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1404 <listitem><para> |
9675 | 1405 With XFree86 3.x.x: you have to cycle through available resolutions |
1406 with the | |
21720 | 1407 <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Keypad +</keycap></keycombo> |
9675 | 1408 and |
21720 | 1409 <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Keypad -</keycap></keycombo> |
9675 | 1410 keys. |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1411 </para></listitem> |
9675 | 1412 </itemizedlist> |
1413 </para> | |
1414 | |
1415 <para> | |
1416 If you can't find the modes you inserted, browse XFree86's output. Some | |
1417 drivers can't use low pixelclocks that are needed for low resolution | |
1418 video modes. | |
1419 </para> | |
22836 | 1420 </sect1> |
9675 | 1421 |
20862 | 1422 <!-- ********** --> |
9675 | 1423 |
22836 | 1424 <sect1 id="vidix"> |
9675 | 1425 <title>VIDIX</title> |
1426 | |
21521 | 1427 <formalpara><title>PREAMBLE</title> |
9675 | 1428 <para> |
21521 | 1429 <acronym>VIDIX</acronym> is the abbreviation for |
1430 <emphasis role="bold">VID</emphasis>eo | |
1431 <emphasis role="bold">I</emphasis>nterface | |
1432 for *ni<emphasis role="bold">X</emphasis>. | |
9675 | 1433 VIDIX was designed and introduced as an interface for fast user-space drivers |
21521 | 1434 providing such video performance as mga_vid does for Matrox cards. It's also |
1435 very portable. | |
9675 | 1436 </para> |
1437 </formalpara> | |
21521 | 1438 |
9675 | 1439 <para> |
1440 This interface was designed as an attempt to fit existing video | |
1441 acceleration interfaces (known as mga_vid, rage128_vid, radeon_vid, | |
12349 | 1442 pm3_vid) into a fixed scheme. It provides a high level interface to chips |
9675 | 1443 which are known as BES (BackEnd scalers) or OV (Video Overlays). It doesn't |
12349 | 1444 provide low level interface to things which are known as graphics servers. |
9675 | 1445 (I don't want to compete with X11 team in graphics mode switching). I.e. |
1446 main goal of this interface is to maximize the speed of video playback. | |
1447 </para> | |
1448 | |
1449 <itemizedlist spacing="compact"> | |
1450 <title>USAGE</title> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1451 <listitem><para> |
9675 | 1452 You can use standalone video output driver: <option>-vo xvidix</option>. |
14318 | 1453 This driver was developed as X11's front end to VIDIX technology. It |
11497 | 1454 requires X server and can work only under X server. Note that, as it directly |
9675 | 1455 accesses the hardware and circumvents the X driver, pixmaps cached in the |
1456 graphics card's memory may be corrupted. You can prevent this by limiting | |
1457 the amount of video memory used by X with the XF86Config option "VideoRam" | |
1458 in the device section. You should set this to the amount of memory installed | |
1459 on your card minus 4MB. If you have less than 8MB of video ram, you can use | |
1460 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
|
1461 </para></listitem> |
20862 | 1462 <listitem> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1463 <para> |
11136 | 1464 There is a console VIDIX driver: <option>-vo cvidix</option>. |
11067
2340e006992f
updated Vidix section to reflect newest developments
gabucino
parents:
11065
diff
changeset
|
1465 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
|
1466 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
|
1467 <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
|
1468 are able to output truly graphical video on a real text console. See the |
11483 | 1469 <link linkend="vidix-nvidia">nvidia_vid</link> section for more information. |
20556 | 1470 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
|
1471 </para> |
20555 | 1472 |
1473 <screen>setterm -cursor off > /dev/tty9</screen> | |
1474 | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1475 <para> |
20555 | 1476 (assuming <systemitem>tty9</systemitem> is unused so far) and then |
1477 switch to <systemitem>tty9</systemitem>. | |
1478 On the other hand, <option>-colorkey 0</option> should give you a video | |
1479 running in the "background", though this depends on the colorkey | |
1480 functionality to work right. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1481 </para> |
20862 | 1482 </listitem> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1483 <listitem><para> |
9675 | 1484 You can use VIDIX subdevice which was applied to several video output |
1485 drivers, such as: <option>-vo vesa:vidix</option> | |
1486 (<emphasis role="bold">Linux only</emphasis>) and | |
1487 <option>-vo fbdev:vidix</option>. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1488 </para></listitem> |
9675 | 1489 </itemizedlist> |
1490 | |
1491 <para> | |
1492 Indeed it doesn't matter which video output driver is used with | |
1493 <emphasis role="bold">VIDIX</emphasis>. | |
1494 </para> | |
1495 | |
1496 <itemizedlist spacing="compact"> | |
1497 <title>REQUIREMENTS</title> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1498 <listitem><para> |
11067
2340e006992f
updated Vidix section to reflect newest developments
gabucino
parents:
11065
diff
changeset
|
1499 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
|
1500 <option>-vo cvidix</option> output driver). |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1501 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1502 <listitem><para> |
9675 | 1503 <application>MPlayer</application>'s video output driver should know |
1504 active video mode and be able to tell to VIDIX subdevice some video | |
1505 characteristics of server. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
1506 </para></listitem> |
9675 | 1507 </itemizedlist> |
1508 | |
21521 | 1509 <formalpara><title>USAGE METHODS</title> |
9675 | 1510 <para> |
10111 | 1511 When VIDIX is used as <emphasis role="bold">subdevice</emphasis> (<option>-vo |
9675 | 1512 vesa:vidix</option>) then video mode configuration is performed by video |
10111 | 1513 output device (<emphasis role="bold">vo_server</emphasis> in short). Therefore you can |
9675 | 1514 pass into command line of <application>MPlayer</application> the same keys |
1515 as for vo_server. In addition it understands <option>-double</option> key | |
1516 as globally visible parameter. (I recommend using this key with VIDIX at | |
11136 | 1517 least for ATI's card). As for <option>-vo xvidix</option>, currently it |
9675 | 1518 recognizes the following options: <option>-fs -zoom -x -y -double</option>. |
1519 </para> | |
1520 </formalpara> | |
20862 | 1521 |
9675 | 1522 <para> |
1523 Also you can specify VIDIX's driver directly as third subargument in | |
1524 command line: | |
21521 | 1525 <screen> |
1526 mplayer -vo xvidix:mga_vid.so -fs -zoom -double <replaceable>file.avi</replaceable> | |
1527 </screen> | |
9675 | 1528 or |
21521 | 1529 <screen> |
1530 mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp 32 <replaceable>file.avi</replaceable> | |
1531 </screen> | |
9675 | 1532 But it's dangerous, and you shouldn't do that. In this case given driver |
1533 will be forced and result is unpredictable (it may | |
1534 <emphasis role="bold">freeze</emphasis> your computer). You should do that | |
1535 ONLY if you are absolutely sure it will work, and | |
1536 <application>MPlayer</application> doesn't do it automatically. Please tell | |
1537 about it to the developers. The right way is to use VIDIX without arguments | |
1538 to enable driver autodetection. | |
1539 </para> | |
1540 | |
1541 <para> | |
1542 Since VIDIX requires direct hardware access you can either run it as root | |
1543 or set the SUID bit on the <application>MPlayer</application> binary | |
10111 | 1544 (<emphasis role="bold">Warning: This is a security risk!</emphasis>). |
9675 | 1545 Alternatively, you can use a special kernel module, like this: |
1546 </para> | |
1547 | |
1548 <procedure> | |
1549 <step><para> | |
21521 | 1550 Download the |
1551 <ulink url="http://www.arava.co.il/matan/svgalib/">development version</ulink> | |
9675 | 1552 of svgalib (for example 1.9.17), <emphasis role="bold">OR</emphasis> |
21521 | 1553 download a version made by Alex especially for usage with |
1554 <application>MPlayer</application> (it doesn't need the svgalib source to | |
1555 compile) from | |
15753 | 1556 <ulink url="http://www.mplayerhq.hu/MPlayer/contrib/svgalib/svgalib_helper-1.9.17-mplayer.tar.bz2">here</ulink>. |
20862 | 1557 </para></step> |
9675 | 1558 <step><para> |
21521 | 1559 Compile the module in the |
1560 <filename class="directory">svgalib_helper</filename> directory (it can be | |
1561 found inside the | |
1562 <filename class="directory">svgalib-1.9.17/kernel/</filename> directory if | |
1563 you've downloaded the source from the svgalib site) and insmod it. | |
20862 | 1564 </para></step> |
9675 | 1565 <step><para> |
21521 | 1566 To create the necessary devices in the |
1567 <filename class="directory">/dev</filename> directory, do a | |
1568 <screen>make device</screen> in the | |
1569 <filename class="directory">svgalib_helper</filename> dir, as root. | |
20862 | 1570 </para></step> |
11022 | 1571 <step><para> |
9675 | 1572 Move the <filename class="directory">svgalib_helper</filename> directory to |
23253 | 1573 the <filename class="directory">vidix</filename> subdirectory of the |
1574 <application>MPlayer</application> source tree. | |
23254 | 1575 </para></step> |
9675 | 1576 <step><para> |
22782
142a2a3b7218
Get rid of useless conditional, using svgalib_helper now requires modifying
diego
parents:
22686
diff
changeset
|
1577 Remove the comment before the CFLAGS line containing the "svgalib_helper" |
23253 | 1578 string from <filename class="directory">vidix/Makefile</filename>. |
20862 | 1579 </para></step> |
9675 | 1580 <step><para> |
23253 | 1581 Recompile. |
20862 | 1582 </para></step> |
9675 | 1583 </procedure> |
1584 | |
20862 | 1585 |
22836 | 1586 <sect2 id="vidix-ati"> |
9675 | 1587 <title>ATI cards</title> |
20862 | 1588 |
9675 | 1589 <para> |
1590 Currently most ATI cards are supported natively, from Mach64 to the | |
1591 newest Radeons. | |
1592 </para> | |
1593 | |
1594 <para> | |
1595 There are two compiled binaries: <filename>radeon_vid</filename> for Radeon and | |
1596 <filename>rage128_vid</filename> for Rage 128 cards. You may force one or let | |
1597 the VIDIX system autoprobe all available drivers. | |
1598 </para> | |
22836 | 1599 </sect2> |
9675 | 1600 |
20862 | 1601 |
22836 | 1602 <sect2 id="vidix-mga"> |
9675 | 1603 <title>Matrox cards</title> |
20862 | 1604 |
9675 | 1605 <para> |
11497 | 1606 Matrox G200, G400, G450 and G550 have been reported to work. |
9675 | 1607 </para> |
1608 | |
1609 <para> | |
1610 The driver supports video equalizers and should be nearly as fast as the | |
1611 <link linkend="mga_vid">Matrox framebuffer</link> | |
1612 </para> | |
22836 | 1613 </sect2> |
9675 | 1614 |
20862 | 1615 |
22836 | 1616 <sect2 id="vidix-trident"> |
9675 | 1617 <title>Trident cards</title> |
20862 | 1618 |
9675 | 1619 <para> |
1620 There is a driver available for the Trident Cyberblade/i1 chipset, which | |
1621 can be found on VIA Epia motherboards. | |
1622 </para> | |
1623 | |
1624 <para> | |
11079
d4df1e5e5e49
the author's homepage points to us as the latest driver's source, so we
gabucino
parents:
11067
diff
changeset
|
1625 The driver was written and is maintained by |
20857 | 1626 <ulink url="http://www.blackfiveservices.co.uk/EPIAVidix.shtml">Alastair M. Robinson</ulink>. |
9675 | 1627 </para> |
22836 | 1628 </sect2> |
9675 | 1629 |
20862 | 1630 |
22836 | 1631 <sect2 id="vidix-3dlabs"> |
9675 | 1632 <title>3DLabs cards</title> |
20862 | 1633 |
9675 | 1634 <para> |
1635 Although there is a driver for the 3DLabs GLINT R3 and Permedia3 chips, no one | |
1636 has tested it, so reports are welcome. | |
1637 </para> | |
22836 | 1638 </sect2> |
11040 | 1639 |
20862 | 1640 |
22836 | 1641 <sect2 id="vidix-nvidia"> |
11040 | 1642 <title>nVidia cards</title> |
11065 | 1643 |
11040 | 1644 <para> |
21521 | 1645 An unique feature of the nvidia_vid driver is its ability to display video on |
1646 <emphasis role="bold">plain, pure, text-only console</emphasis> - with no | |
1647 framebuffer or X magic whatsoever. For this purpose, we'll have to use the | |
1648 <option>cvidix</option> video output, as the following example shows: | |
1649 <screen>mplayer -vo cvidix <replaceable>example.avi</replaceable></screen> | |
11040 | 1650 </para> |
22836 | 1651 </sect2> |
11040 | 1652 |
1653 | |
22836 | 1654 <sect2 id="vidix-sis"> |
11040 | 1655 <title>SiS cards</title> |
20862 | 1656 |
11040 | 1657 <para> |
1658 This is very experimental code, just like nvidia_vid. | |
1659 </para> | |
1660 | |
1661 <para> | |
12815 | 1662 It's been tested on SiS 650/651/740 (the most common chipsets used in the |
11040 | 1663 SiS versions of the "Shuttle XPC" barebones boxes out there) |
1664 </para> | |
1665 | |
1666 <para> | |
1667 Reports awaited! | |
1668 </para> | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
1669 </sect2> |
22836 | 1670 </sect1> |
9675 | 1671 |
20862 | 1672 <!-- ********** --> |
1673 | |
22836 | 1674 <sect1 id="directfb"> |
9675 | 1675 <title>DirectFB</title> |
20862 | 1676 |
9675 | 1677 <blockquote><para> |
21596 | 1678 "DirectFB is a graphics library which was designed with embedded systems |
9675 | 1679 in mind. It offers maximum hardware accelerated performance at a minimum |
21596 | 1680 of resource usage and overhead." - quoted from |
21521 | 1681 <ulink url="http://www.directfb.org"/> |
9675 | 1682 </para></blockquote> |
1683 | |
1684 <para>I'll exclude DirectFB features from this section.</para> | |
1685 | |
1686 <para> | |
21596 | 1687 Though <application>MPlayer</application> is not supported as a "video |
1688 provider" in DirectFB, this output driver will enable video playback | |
21521 | 1689 through DirectFB. It will - of course - be accelerated, on my Matrox G400 |
1690 DirectFB's speed was the same as XVideo. | |
9675 | 1691 </para> |
1692 | |
1693 <para> | |
21521 | 1694 Always try to use the newest version of DirectFB. You can use DirectFB options |
1695 on the command line, using the <option>-dfbopts</option> option. Layer | |
1696 selection can be done by the subdevice method, e.g.: | |
1697 <option>-vo directfb:2</option> (layer -1 is default: autodetect) | |
9675 | 1698 </para> |
22836 | 1699 </sect1> |
9675 | 1700 |
20862 | 1701 <!-- ********** --> |
1702 | |
22836 | 1703 <sect1 id="dfbmga"> |
9675 | 1704 <title>DirectFB/Matrox (dfbmga)</title> |
20862 | 1705 |
9675 | 1706 <para> |
21521 | 1707 Please read the <link linkend="directfb">main DirectFB</link> section for |
1708 general information. | |
9675 | 1709 </para> |
1710 | |
1711 <para> | |
11824
ce44fb6eb15c
Our DirectFB documentation is dated, the current version is now linked to
diego
parents:
11822
diff
changeset
|
1712 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
|
1713 G400/G450/G550 cards, displaying video |
ce44fb6eb15c
Our DirectFB documentation is dated, the current version is now linked to
diego
parents:
11822
diff
changeset
|
1714 <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
|
1715 </para> |
ce44fb6eb15c
Our DirectFB documentation is dated, the current version is now linked to
diego
parents:
11822
diff
changeset
|
1716 |
ce44fb6eb15c
Our DirectFB documentation is dated, the current version is now linked to
diego
parents:
11822
diff
changeset
|
1717 <para> |
12815 | 1718 Ville Syrjala's has a |
11824
ce44fb6eb15c
Our DirectFB documentation is dated, the current version is now linked to
diego
parents:
11822
diff
changeset
|
1719 <ulink url="http://www.sci.fi/~syrjala/directfb/Matrox_TV-out_README.txt">README</ulink> |
12815 | 1720 and a |
14649 | 1721 <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
|
1722 on his homepage that explain how to make DirectFB TV output run on Matrox cards. |
9675 | 1723 </para> |
1724 | |
1725 <note><para> | |
11824
ce44fb6eb15c
Our DirectFB documentation is dated, the current version is now linked to
diego
parents:
11822
diff
changeset
|
1726 the first DirectFB version with which we could get this working was |
13490 | 1727 0.9.17 (it's buggy, needs that <systemitem>surfacemanager</systemitem> |
1728 patch from the URL above). Porting the CRTC2 code to | |
1729 <link linkend="mga_vid">mga_vid</link> has been planned for years, | |
1730 <ulink url="../../tech/patches.txt">patches</ulink> are welcome. | |
9675 | 1731 </para></note> |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
1732 </sect1> |
9675 | 1733 |
20862 | 1734 |
1735 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
1736 | |
1737 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
1738 <sect1 id="mpeg_decoders"> |
9675 | 1739 <title>MPEG decoders</title> |
1740 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
1741 <sect2 id="dvb"> |
11358
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1742 <title>DVB output and input</title> |
20862 | 1743 |
9675 | 1744 <para> |
1745 <application>MPlayer</application> supports cards with the Siemens DVB chipset | |
1746 from vendors like Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB | |
21521 | 1747 drivers are available from the |
1748 <ulink url="http://www.linuxtv.org">Linux TV site</ulink>. | |
9675 | 1749 If you want to do software transcoding you should have at least a 1GHz CPU. |
1750 </para> | |
1751 | |
1752 <para> | |
1753 Configure should detect your DVB card. If it did not, force detection with | |
21521 | 1754 <screen>./configure --enable-dvb</screen> |
1755 If you have ost headers at a non-standard path, set the path with | |
1756 <screen> | |
1757 ./configure --with-extraincdir=<replaceable>DVB source directory</replaceable>/ost/include | |
1758 </screen> | |
1759 Then compile and install as usual.</para> | |
9675 | 1760 |
21521 | 1761 <formalpara><title>USAGE</title> |
9675 | 1762 <para> |
22183 | 1763 Hardware decoding of streams containing MPEG-1/2 video and/or MPEG audio can be done with this |
21521 | 1764 command: |
1765 <screen> | |
1766 mplayer -ao mpegpes -vo mpegpes <replaceable>file.mpg|vob</replaceable> | |
1767 </screen> | |
9675 | 1768 </para> |
1769 </formalpara> | |
11358
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1770 |
11713 | 1771 <para> |
22183 | 1772 Decoding of any other type of video stream requires transcoding to MPEG-1, thus it's slow |
1773 and may not be worth the trouble, especially if your computer is slow. | |
1774 It can be achieved using a command like this: | |
21521 | 1775 <screen> |
11713 | 1776 mplayer -ao mpegpes -vo mpegpes <replaceable>yourfile.ext</replaceable> |
1777 mplayer -ao mpegpes -vo mpegpes -vf expand <replaceable>yourfile.ext</replaceable> | |
9675 | 1778 </screen></para> |
1779 | |
1780 <para> | |
1781 Note that DVB cards only support heights 288 and 576 for PAL or 240 and 480 for | |
21521 | 1782 NTSC. You <emphasis role="bold">must</emphasis> rescale for other heights by |
1783 adding <option>scale=width:height</option> with the width and height you want | |
1784 to the <option>-vf</option> option. DVB cards accept various widths, like 720, | |
1785 704, 640, 512, 480, 352 etc. and do hardware scaling in horizontal direction, | |
1786 so you do not need to scale horizontally in most cases. | |
1787 For a 512x384 (aspect 4:3) MPEG-4 (DivX) try: | |
1788 <screen>mplayer -ao mpegpes -vo mpegpes -vf scale=512:576</screen> | |
9675 | 1789 </para> |
1790 | |
11713 | 1791 <para> |
21521 | 1792 If you have a widescreen movie and you do not want to scale it to full height, |
1793 you can use the <option>expand=w:h</option> filter to add black bands. To view a | |
1794 640x384 MPEG-4 (DivX), try: | |
1795 <screen> | |
1796 mplayer -ao mpegpes -vo mpegpes -vf expand=640:576 <replaceable>file.avi</replaceable> | |
11713 | 1797 </screen> |
1798 </para> | |
9675 | 1799 |
13961
2946cbf097b5
DivX is MPEG4, so let's call it MPEG4 to avoid confusion.
diego
parents:
13912
diff
changeset
|
1800 <para> |
14024 | 1801 If your CPU is too slow for a full size 720x576 MPEG-4 (DivX), try downscaling: |
21521 | 1802 <screen> |
1803 mplayer -ao mpegpes -vo mpegpes -vf scale=352:576 <replaceable>file.avi</replaceable> | |
11713 | 1804 </screen> |
1805 </para> | |
9675 | 1806 |
21521 | 1807 <para>If speed does not improve, try vertical downscaling, too: |
1808 <screen> | |
1809 mplayer -ao mpegpes -vo mpegpes -vf scale=352:288 <replaceable>file.avi</replaceable> | |
11713 | 1810 </screen> |
1811 </para> | |
9675 | 1812 |
1813 <para> | |
1814 For OSD and subtitles use the OSD feature of the expand filter. So, instead of | |
1815 <option>expand=w:h</option> or <option>expand=w:h:x:y</option>, use | |
1816 <option>expand=w:h:x:y:1</option> (the 5th parameter <option>:1</option> | |
1817 at the end will enable OSD rendering). You may want to move the image up a bit | |
21521 | 1818 to get a bigger black zone for subtitles. You may also want to move subtitles |
1819 up, if they are outside your TV screen, use the | |
1820 <option>-subpos <0-100></option> | |
9675 | 1821 option to adjust this (<option>-subpos 80</option> is a good choice). |
1822 </para> | |
1823 | |
1824 <para> | |
1825 In order to play non-25fps movies on a PAL TV or with a slow CPU, add the | |
1826 <option>-framedrop</option> option. | |
1827 </para> | |
1828 | |
1829 <para> | |
14024 | 1830 To keep the aspect ratio of MPEG-4 (DivX) files and get the optimal scaling |
9675 | 1831 parameters (hardware horizontal scaling and software vertical scaling |
1832 while keeping the right aspect ratio), use the new dvbscale filter: | |
21521 | 1833 <screen> |
10682 | 1834 for a 4:3 TV: -vf dvbscale,scale=-1:0,expand=-1:576:-1:-1:1 |
1835 for a 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1 | |
21521 | 1836 </screen> |
1837 </para> | |
9675 | 1838 |
21521 | 1839 <formalpara><title>Digital TV (DVB input module)</title> |
11888 | 1840 <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
|
1841 </formalpara> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1842 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1843 <para> |
21521 | 1844 You should have the programs <command>scan</command> and |
1845 <command>szap/tzap/czap/azap</command> installed; they are all included in | |
1846 the drivers package. | |
11358
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1847 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1848 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1849 <para> |
21521 | 1850 Verify that your drivers are working properly with a program such as |
1851 <ulink url="http://sf.net/projects/dvbtools/"><command>dvbstream</command></ulink> | |
1852 (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
|
1853 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1854 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1855 <para> |
21521 | 1856 Now you should compile a <filename>~/.mplayer/channels.conf</filename> |
1857 file, with the syntax accepted by <command>szap/tzap/czap/azap</command>, or | |
1858 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
|
1859 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1860 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1861 <para> |
21521 | 1862 If you have more than one card type (e.g. Satellitar, Terrestrial, Cable and ATSC) |
1863 you can save your channels files as | |
1864 <filename>~/.mplayer/channels.conf.sat</filename>, | |
1865 <filename>~/.mplayer/channels.conf.ter</filename>, | |
1866 <filename>~/.mplayer/channels.conf.cbl</filename>, | |
1867 and <filename>~/.mplayer/channels.conf.atsc</filename>, | |
1868 respectively, so as to implicitly hint <application>MPlayer</application> | |
1869 to use these files rather than <filename>~/.mplayer/channels.conf</filename>, | |
1870 and you only need to specify which card to use. | |
12188 | 1871 </para> |
1872 | |
1873 <para> | |
21521 | 1874 Make sure that you have have <emphasis>only</emphasis> Free to Air |
1875 channels in your <filename>channels.conf</filename> file, or | |
24689
85f578745278
Documentation follows implementation: Encrytped DVB channels are never
cehoyos
parents:
24160
diff
changeset
|
1876 <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
|
1877 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1878 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1879 <para> |
21521 | 1880 In your audio and video fields you can use an extended syntax: |
1881 <option>...:pid[+pid]:...</option> (for a maximum of 6 pids each); | |
1882 in this case <application>MPlayer</application> will include in the | |
1883 stream all the indicated pids, plus pid 0 (that contains the PAT). | |
1884 You are encouraged to include in each row the PMT pid for the | |
1885 corresponding channel (if you know it). | |
22384
989613a9a15b
Explain how to select all DVB channels on a frequency.
reimar
parents:
22183
diff
changeset
|
1886 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
|
1887 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
|
1888 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
|
1889 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
|
1890 for these. |
21521 | 1891 Other possible uses are: televideo pid, second audio track, etc. |
19601 | 1892 </para> |
12814 | 1893 |
1894 <para> | |
21521 | 1895 If <application>MPlayer</application> complains frequently about |
1896 <screen>Too many video/audio packets in the buffer</screen> or | |
1897 if you notice a growing desynchronization between audio and | |
1898 video try to use the libavformat MPEG-TS demuxer by adding | |
1899 <option>-demuxer lavf -lavfdopts probesize=128</option> | |
1900 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
|
1901 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1902 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1903 <para> |
21521 | 1904 To show the first of the channels present in your list, run |
1905 <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
|
1906 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1907 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1908 <para> |
21521 | 1909 If you want to watch a specific channel, such as R1, run |
1910 <screen>mplayer dvb://<replaceable>R1</replaceable></screen> | |
12310
da00c08d8279
DVB now supports multiple cards, patch by Nico Sabbi.
diego
parents:
12216
diff
changeset
|
1911 </para> |
da00c08d8279
DVB now supports multiple cards, patch by Nico Sabbi.
diego
parents:
12216
diff
changeset
|
1912 |
21521 | 1913 <para> |
1914 If you have more than one card you also need to specify the number of the card | |
1915 where the channel is visible (e.g. 2) with the syntax: | |
1916 <screen>mplayer dvb://<replaceable>2@R1</replaceable></screen> | |
1917 </para> | |
12310
da00c08d8279
DVB now supports multiple cards, patch by Nico Sabbi.
diego
parents:
12216
diff
changeset
|
1918 |
da00c08d8279
DVB now supports multiple cards, patch by Nico Sabbi.
diego
parents:
12216
diff
changeset
|
1919 <para> |
21521 | 1920 To change channels press the <keycap>h</keycap> (next) and |
1921 <keycap>k</keycap> (previous) keys, or use the | |
1922 <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
|
1923 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1924 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1925 <para> |
21521 | 1926 If your <filename>~/.mplayer/menu.conf</filename> contains a |
1927 <literal><dvbsel></literal> entry, such as the one in the example | |
1928 file <filename>etc/dvb-menu.conf</filename> (that you can use to overwrite | |
1929 <filename>~/.mplayer/menu.conf</filename>), the main menu will show a | |
1930 sub-menu entry that will permit you to choose one of the channels present | |
1931 in your <filename>channels.conf</filename>, possibly preceded by a menu | |
1932 with the list of cards available if more than one is usable by | |
1933 <application>MPlayer</application>. | |
11358
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1934 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1935 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1936 <para> |
21521 | 1937 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
|
1938 <screen> |
21521 | 1939 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
|
1940 </screen> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1941 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1942 |
21521 | 1943 <para> |
1944 If you want to record it in a different format (re-encoding it) instead | |
1945 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
|
1946 <screen> |
21521 | 1947 mencoder -o <replaceable>r1.avi</replaceable> -ovc xvid -xvidencopts bitrate=800 \ |
1948 -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
|
1949 </screen> |
21521 | 1950 </para> |
11358
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1951 |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1952 <para> |
21521 | 1953 Read the man page for a list of options that you can pass to the |
1954 DVB input module. | |
11358
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1955 </para> |
7d120a00fcf7
DVB section expanded based on a patch by Nico Sabbi that was committed to
diego
parents:
11287
diff
changeset
|
1956 |
21521 | 1957 <formalpara><title>FUTURE</title> |
9675 | 1958 <para> |
1959 If you have questions or want to hear feature announcements and take part in | |
1960 discussions on this subject, join our | |
19709 | 1961 <ulink url="http://lists.mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</ulink> |
9675 | 1962 mailing list. Please remember that the list language is English. |
1963 </para> | |
1964 </formalpara> | |
1965 | |
1966 <para> | |
1967 In the future you may expect the ability to display OSD and subtitles using | |
1968 the native OSD feature of DVB cards, as well as more fluent playback of | |
14024 | 1969 non-25fps movies and realtime transcoding between MPEG-2 and MPEG-4 (partial |
9675 | 1970 decompression). |
1971 </para> | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
1972 </sect2> |
9675 | 1973 |
20862 | 1974 <!-- ********** --> |
1975 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
1976 <sect2 id="dxr2"> |
9675 | 1977 <title>DXR2</title> |
20862 | 1978 |
21521 | 1979 <para> |
1980 <application>MPlayer</application> supports hardware accelerated playback | |
1981 with the Creative DXR2 card. | |
1982 </para> | |
1983 | |
9675 | 1984 <para> |
1985 First of all you will need properly installed DXR2 drivers. You can find | |
1986 the drivers and installation instructions at the | |
13977 | 1987 <ulink url="http://dxr2.sf.net/">DXR2 Resource Center</ulink> site. |
9675 | 1988 </para> |
1989 | |
21521 | 1990 <variablelist><title>USAGE</title> |
9675 | 1991 <varlistentry> |
21521 | 1992 <term><option>-vo dxr2</option></term> |
1993 <listitem><para>Enable TV output.</para></listitem> | |
9675 | 1994 </varlistentry> |
1995 <varlistentry> | |
21521 | 1996 <term><option>-vo dxr2:x11</option> or <option>-vo dxr2:xv</option></term> |
1997 <listitem><para>Enable Overlay output in X11.</para></listitem> | |
9675 | 1998 </varlistentry> |
1999 <varlistentry> | |
21521 | 2000 <term><option>-dxr2 <option1:option2:...></option></term> |
2001 <listitem><para> | |
2002 This option is used to control the DXR2 driver. | |
2003 </para></listitem> | |
9675 | 2004 </varlistentry> |
2005 </variablelist> | |
2006 | |
2007 <para> | |
2008 The overlay chipset used on the DXR2 is of pretty bad quality but the | |
2009 default settings should work for everybody. The OSD may be usable with the | |
2010 overlay (not on TV) by drawing it in the colorkey. With the default colorkey | |
2011 settings you may get variable results, usually you will see the colorkey | |
2012 around the characters or some other funny effect. But if you properly adjust | |
2013 the colorkey settings you should be able to get acceptable results. | |
2014 </para> | |
2015 | |
11731 | 2016 <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
|
2017 </sect2> |
9675 | 2018 |
20862 | 2019 <!-- ********** --> |
2020 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2021 <sect2 id="dxr3"> |
9675 | 2022 <title>DXR3/Hollywood+</title> |
20862 | 2023 |
9675 | 2024 <para> |
2025 <application>MPlayer</application> supports hardware accelerated playback | |
2026 with the Creative DXR3 and Sigma Designs Hollywood Plus cards. These cards | |
2027 both use the em8300 MPEG decoder chip from Sigma Designs. | |
2028 </para> | |
2029 | |
2030 <para> | |
2031 First of all you will need properly installed DXR3/H+ drivers, version 0.12.0 | |
2032 or later. You can find the drivers and installation instructions at the | |
13977 | 2033 <ulink url="http://dxr3.sf.net/">DXR3 & Hollywood Plus for Linux</ulink> |
10111 | 2034 site. <filename>configure</filename> should detect your card automatically, |
2035 compilation should go without problems. | |
9675 | 2036 </para> |
2037 | |
2038 <!-- FIXME: find a more clear presentation --> | |
2039 <variablelist> | |
2040 <title>USAGE</title> | |
2041 <varlistentry> | |
10111 | 2042 <term><option>-vo dxr3:prebuf:sync:norm=x:<replaceable>device</replaceable></option></term> |
9675 | 2043 <listitem><para> |
2044 <option>overlay</option> activates the overlay instead of TVOut. It requires | |
2045 that you have a properly configured overlay setup to work right. The easiest | |
2046 way to configure the overlay is to first run autocal. Then run mplayer with | |
2047 dxr3 output and without overlay turned on, run dxr3view. In dxr3view you can | |
2048 tweak the overlay settings and see the effects in realtime, perhaps this feature | |
11540 | 2049 will be supported by the <application>MPlayer</application> GUI in the future. |
2050 When overlay is properly set up you will no longer need to use dxr3view. | |
9675 | 2051 <option>prebuf</option> turns on prebuffering. Prebuffering is a feature of the |
21521 | 2052 em8300 chip that enables it to hold more than one frame of video at a time. |
2053 This means that when you are running with prebuffering | |
2054 <application>MPlayer</application> will try to keep the video buffer filled | |
2055 with data at all times. | |
2056 If you are on a slow machine <application>MPlayer</application> will probably | |
2057 use close to, or precisely 100% of CPU. | |
2058 This is especially common if you play pure MPEG streams | |
11540 | 2059 (like DVDs, SVCDs a.s.o.) since <application>MPlayer</application> will not have |
2060 to reencode it to MPEG it will fill the buffer very fast. | |
9675 | 2061 With prebuffering video playback is <emphasis role="bold">much</emphasis> |
2062 less sensitive to other programs hogging the CPU, it will not drop frames unless | |
2063 applications hog the CPU for a long time. | |
2064 When running without prebuffering the em8300 is much more sensitive to CPU load, | |
12349 | 2065 so it is highly suggested that you turn on <application>MPlayer</application>'s |
11540 | 2066 <option>-framedrop</option> option to avoid further loss of sync. |
9675 | 2067 <option>sync</option> will turn on the new sync-engine. This is currently an |
21521 | 2068 experimental feature. With the sync feature turned on the em8300's internal |
2069 clock will be monitored at all times, if it starts to deviate from | |
2070 <application>MPlayer</application>'s clock it will be reset causing the em8300 | |
2071 to drop any frames that are lagging behind. | |
9675 | 2072 <option>norm=x</option> will set the TV norm of the DXR3 card without the need |
2073 for external tools like em8300setup. Valid norms are 5 = NTSC, 4 = PAL-60, | |
2074 3 = PAL. Special norms are 2 (auto-adjust using PAL/PAL-60) and 1 (auto-adjust | |
2075 using PAL/NTSC) because they decide which norm to use by looking at the frame | |
2076 rate of the movie. norm = 0 (default) does not change the current norm. | |
21521 | 2077 <option><replaceable>device</replaceable></option> = device number to use if |
2078 you have more than one em8300 card. Any of these options may be left out. | |
2079 <option>:prebuf:sync</option> seems to work great when playing MPEG-4 (DivX) | |
2080 movies. People have reported problems using the prebuf option when playing | |
2081 MPEG-1/2 files. | |
2082 You might want to try running without any options first, if you have sync | |
2083 problems, or DVD subtitle problems, give <option>:sync</option> a try. | |
9675 | 2084 </para></listitem> |
2085 </varlistentry> | |
2086 | |
2087 <varlistentry> | |
21521 | 2088 <term><option>-ao oss:/dev/em8300_ma-<replaceable>X</replaceable></option></term> |
2089 <listitem><para> | |
2090 For audio output, where <replaceable>X</replaceable> is the device number | |
2091 (0 if one card). | |
2092 </para></listitem> | |
2093 </varlistentry> | |
2094 | |
2095 <varlistentry> | |
2096 <term><option>-af resample=<replaceable>xxxxx</replaceable></option></term> | |
2097 <listitem><para> | |
2098 The em8300 cannot play back samplerates lower than 44100Hz. If the sample | |
2099 rate is below 44100Hz select either 44100Hz or 48000Hz depending on which | |
2100 one matches closest. I.e. if the movie uses 22050Hz use 44100Hz as | |
2101 44100 / 2 = 22050, if it is 24000Hz use 48000Hz as 48000 / 2 = 24000 | |
2102 and so on. | |
2103 This does not work with digital audio output (<option>-ac hwac3</option>). | |
2104 </para></listitem> | |
9675 | 2105 </varlistentry> |
2106 | |
2107 <varlistentry> | |
21521 | 2108 <term><option>-vf lavc</option></term> |
2109 <listitem><para> | |
2110 To watch non-MPEG content on the em8300 (i.e. MPEG-4 (DivX) or RealVideo) | |
2111 you have to specify an MPEG-1 video filter such as | |
2112 <systemitem class="library">libavcodec</systemitem> (lavc). | |
2113 See the man page for further info about <option>-vf lavc</option>. | |
2114 Currently there is no way of setting the fps of the em8300 which means that | |
2115 it is fixed to 30000/1001 fps. | |
2116 Because of this it is highly recommended that you use | |
2117 <option>-vf lavc=<replaceable>quality</replaceable>:25</option> | |
2118 especially if you are using prebuffering. Then why 25 and not 30000/1001? | |
2119 Well, the thing is that when you use 30000/1001 the picture becomes a bit | |
2120 jumpy. | |
2121 The reason for this is unknown to us. | |
2122 If you set it to somewhere between 25 and 27 the picture becomes stable. | |
2123 For now all we can do is accept this for a fact. | |
2124 </para></listitem> | |
9675 | 2125 </varlistentry> |
2126 | |
2127 <varlistentry> | |
21521 | 2128 <term><option>-vf expand=-1:-1:-1:-1:1</option></term> |
2129 <listitem><para> | |
2130 Although the DXR3 driver can put some OSD onto the MPEG-1/2/4 video, it has | |
2131 much lower quality than <application>MPlayer</application>'s traditional OSD, | |
2132 and has several refresh problems as well. The command line above will firstly | |
2133 convert the input video to MPEG-4 (this is mandatory, sorry), then apply an | |
2134 expand filter which won't expand anything (-1: default), but apply the normal | |
2135 OSD onto the picture (that's what the "1" at the end does). | |
2136 </para></listitem> | |
2137 </varlistentry> | |
2138 | |
2139 <varlistentry> | |
2140 <term><option>-ac hwac3</option></term> | |
2141 <listitem><para> | |
24036 | 2142 The em8300 supports playing back AC-3 audio (surround sound) through the |
21521 | 2143 digital audio output of the card. See the <option>-ao oss</option> option |
2144 above, it must be used to specify the DXR3's output instead of a sound card. | |
2145 </para></listitem> | |
9675 | 2146 </varlistentry> |
2147 </variablelist> | |
13912
c66b1514ce5b
Remove pointless devices section, make video and audio top level sections.
diego
parents:
13908
diff
changeset
|
2148 </sect2> |
20862 | 2149 </sect1> |
13912
c66b1514ce5b
Remove pointless devices section, make video and audio top level sections.
diego
parents:
13908
diff
changeset
|
2150 |
20862 | 2151 |
2152 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
2153 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2154 |
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2155 <sect1 id="other"> |
9675 | 2156 <title>Other visualization hardware</title> |
2157 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2158 <sect2 id="zr"> |
9675 | 2159 <title>Zr</title> |
2160 | |
2161 <para> | |
2162 This is a display-driver (<option>-vo zr</option>) for a number of MJPEG | |
2163 capture/playback cards (tested for DC10+ and Buz, and it should work for the | |
2164 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
|
2165 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
|
2166 <systemitem class="library">libavcodec</systemitem> |
9675 | 2167 is used, and required. With the special <emphasis>cinerama</emphasis> mode, |
2168 you can watch movies in true wide screen provided that you have two beamers | |
2169 and two MJPEG cards. Depending on resolution and quality settings, this driver | |
2170 may require a lot of CPU power, remember to specify <option>-framedrop</option> | |
2171 if your machine is too slow. Note: My AMD K6-2 350MHz is (with | |
2172 <option>-framedrop</option>) quite adequate for watching VCD sized material and | |
2173 downscaled movies. | |
2174 </para> | |
2175 | |
2176 <para> | |
2177 This driver talks to the kernel driver available at | |
13977 | 2178 <ulink url="http://mjpeg.sf.net"/>, so |
21521 | 2179 you must get it working first. The presence of an MJPEG card is autodetected by |
2180 the <filename>configure</filename> script, if autodetection fails, force | |
2181 detection with | |
9675 | 2182 <screen>./configure --enable-zr</screen> |
2183 </para> | |
21521 | 2184 |
9675 | 2185 <para> |
2186 The output can be controlled by several options, a long description of the | |
2187 options can be found in the man page, a short list of options can be viewed | |
2188 by running | |
2189 <screen>mplayer -zrhelp</screen> | |
2190 </para> | |
2191 | |
2192 <para> | |
2193 Things like scaling and the OSD (on screen display) are not handled by | |
2194 this driver but can be done using the video filters. For example, suppose | |
2195 that you have a movie with a resolution of 512x272 and you want to view it | |
2196 fullscreen on your DC10+. There are three main possibilities, you may scale | |
2197 the movie to a width of 768, 384 or 192. For performance and quality reasons, | |
2198 I would choose to scale the movie to 384x204 using the fast bilinear software | |
12349 | 2199 scaler. The command line is |
11713 | 2200 <screen> |
2201 mplayer -vo zr -sws 0 -vf scale=384:204 <replaceable>movie.avi</replaceable> | |
2202 </screen> | |
9675 | 2203 </para> |
2204 | |
2205 <para> | |
11214 | 2206 Cropping can be done by the <option>crop</option> filter and by this |
9675 | 2207 driver itself. Suppose that a movie is too wide for display on your Buz and |
2208 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
|
2209 then you would issue the following command |
11713 | 2210 <screen> |
2211 mplayer -vo zr -zrcrop 720x320+80+0 <replaceable>benhur.avi</replaceable> | |
2212 </screen> | |
9675 | 2213 </para> |
2214 | |
2215 <para> | |
10111 | 2216 if you want to use the <option>crop</option> filter, you would do |
11713 | 2217 <screen> |
2218 mplayer -vo zr -vf crop=720:320:80:0 <replaceable>benhur.avi</replaceable> | |
2219 </screen> | |
9675 | 2220 </para> |
2221 | |
2222 <para> | |
21521 | 2223 Extra occurrences of <option>-zrcrop</option> invoke |
2224 <emphasis>cinerama</emphasis> mode, i.e. you can distribute the movie over | |
2225 several TV's or beamers to create a larger screen. | |
2226 Suppose you have two beamers. The left one is connected to your | |
11359 | 2227 Buz at <filename>/dev/video1</filename> and the right one is connected to |
2228 your DC10+ at <filename>/dev/video0</filename>. The movie has a resolution | |
9675 | 2229 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
|
2230 that the left beamer should have JPEG frames at quality 10, then you would |
9675 | 2231 issue the following command |
2232 <screen> | |
2233 mplayer -vo zr -zrdev /dev/video0 -zrcrop 352x288+352+0 -zrxdoff 0 -zrbw \ | |
21521 | 2234 -zrcrop 352x288+0+0 -zrdev /dev/video1 -zrquality 10 \ |
2235 <replaceable>movie.avi</replaceable> | |
9675 | 2236 </screen> |
2237 </para> | |
2238 | |
2239 <para> | |
2240 You see that the options appearing before the second <option>-zrcrop</option> | |
2241 only apply to the DC10+ and that the options after the second | |
2242 <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
|
2243 participating in <emphasis>cinerama</emphasis> is four, so you can build a |
9675 | 2244 2x2 vidiwall. |
2245 </para> | |
2246 | |
2247 <para> | |
10111 | 2248 Finally an important remark: Do not start or stop XawTV on the playback device |
9675 | 2249 during playback, it will crash your computer. It is, however, fine to |
21521 | 2250 <emphasis role="bold">FIRST</emphasis> start XawTV, |
2251 <emphasis role="bold">THEN</emphasis> start <application>MPlayer</application>, | |
2252 wait for <application>MPlayer</application> | |
11540 | 2253 to finish and <emphasis role="bold">THEN</emphasis> stop XawTV. |
9675 | 2254 </para> |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2255 </sect2> |
9675 | 2256 |
20862 | 2257 <!-- ********** --> |
2258 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2259 <sect2 id="blinkenlights"> |
9675 | 2260 <title>Blinkenlights</title> |
20862 | 2261 |
9675 | 2262 <para> |
2263 This driver is capable of playback using the Blinkenlights UDP protocol. If you | |
2264 don't know what <ulink url="http://www.blinkenlights.de/">Blinkenlights</ulink> | |
12401 | 2265 or its successor |
2266 <ulink url="http://www.blinkenlights.de/arcade/">Arcade</ulink> | |
2267 are, find it out. Although this is most probably the least used video output | |
2268 driver, without a doubt it is the coolest <application>MPlayer</application> | |
2269 has to offer. Just watch some of the | |
2270 <ulink url="http://www.blinkenlights.de/video.en.html">Blinkenlights documentation videos</ulink>. | |
2271 On the Arcade video you can see the Blinkenlights output driver in | |
2272 action at 00:07:50. | |
9675 | 2273 </para> |
13912
c66b1514ce5b
Remove pointless devices section, make video and audio top level sections.
diego
parents:
13908
diff
changeset
|
2274 </sect2> |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2275 </sect1> |
9675 | 2276 |
20862 | 2277 |
2278 <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> | |
2279 | |
2280 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2281 <sect1 id="tvout"> |
9675 | 2282 <title>TV-out support</title> |
2283 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2284 <sect2 id="tvout-mga-g400"> |
9675 | 2285 <title>Matrox G400 cards</title> |
2286 | |
2287 <para> | |
2288 Under Linux you have two methods to get G400 TV out working: | |
2289 </para> | |
2290 | |
2291 <important> | |
2292 <para> | |
2293 for Matrox G450/G550 TV-out instructions, please see the next section! | |
2294 </para> | |
2295 </important> | |
2296 | |
2297 <variablelist> | |
2298 <varlistentry> | |
2299 <term>XFree86</term> | |
21521 | 2300 <listitem> |
2301 <para> | |
12349 | 2302 Using the driver and the HAL module, available from the <ulink |
2303 url="http://www.matrox.com">Matrox site</ulink>. This will give you X | |
9675 | 2304 on the TV. |
21521 | 2305 </para> |
2306 <para> | |
9675 | 2307 <emphasis role="bold">This method doesn't give you accelerated playback</emphasis> |
21521 | 2308 as under Windows! The second head has only YUV framebuffer, the |
2309 <emphasis>BES</emphasis> (Back End Scaler, the YUV scaler on | |
2310 G200/G400/G450/G550 cards) doesn't work on it! The windows driver somehow | |
2311 workarounds this, probably by using the 3D engine to zoom, and the YUV | |
2312 framebuffer to display the zoomed image. If you really want to use X, use | |
2313 the <option>-vo x11 -fs -zoom</option> options, but it will be | |
2314 <emphasis role="bold">SLOW</emphasis>, and has | |
2315 <emphasis role="bold">Macrovision</emphasis> copy protection enabled | |
9675 | 2316 (you can "workaround" Macrovision using this |
13977 | 2317 <ulink url="http://avifile.sf.net/mgamacro.pl">perl script</ulink>). |
21521 | 2318 </para> |
2319 </listitem> | |
9675 | 2320 </varlistentry> |
2321 <varlistentry> | |
2322 <term>Framebuffer</term> | |
20862 | 2323 <listitem> |
2324 <para> | |
9675 | 2325 Using the <emphasis role="bold">matroxfb modules</emphasis> in the 2.4 |
2326 kernels. 2.2 kernels don't have the TVout feature in them, thus unusable | |
21521 | 2327 for this. You have to enable ALL matroxfb-specific feature during |
2328 compilation (except MultiHead), and compile them into | |
2329 <emphasis role="bold">modules</emphasis>! | |
9675 | 2330 You'll also need I2C enabled. |
2331 </para> | |
2332 | |
2333 <procedure> | |
2334 <step><para> | |
11499 | 2335 Enter <filename class="directory">TVout</filename> and type |
2336 <command>./compile.sh</command>. Install | |
11521 | 2337 <filename>TVout/matroxset/matroxset</filename> |
2338 somewhere into your <envar>PATH</envar>. | |
20862 | 2339 </para></step> |
9675 | 2340 <step><para> |
11499 | 2341 If you don't have <command>fbset</command> installed, put |
11521 | 2342 <filename>TVout/fbset/fbset</filename> |
2343 somewhere into your <envar>PATH</envar>. | |
20862 | 2344 </para></step> |
9675 | 2345 <step><para> |
11499 | 2346 If you don't have <command>con2fb</command> installed, put |
11521 | 2347 <filename>TVout/con2fb/con2fb</filename> |
2348 somewhere into your <envar>PATH</envar>. | |
20862 | 2349 </para></step> |
10254 | 2350 <step><para> |
21521 | 2351 Then enter into the <filename class="directory">TVout/</filename> |
2352 directory in the <application>MPlayer</application> source, and execute | |
9675 | 2353 <filename>./modules</filename> as root. Your text-mode console will |
2354 enter into framebuffer mode (no way back!). | |
20862 | 2355 </para></step> |
9675 | 2356 <step><para> |
2357 Next, EDIT and run the <filename>./matroxtv</filename> script. This will | |
2358 present you to a very simple menu. Press <keycap>2</keycap> and | |
2359 <keycap>Enter</keycap>. Now you should have the same picture on your | |
10111 | 2360 monitor, and TV. If the TV (PAL by default) |
9675 | 2361 picture has some weird stripes on it, the script wasn't able to set the |
2362 resolution correctly (to 640x512 by default). Try other resolutions | |
2363 from the menu and/or experiment with fbset. | |
20862 | 2364 </para></step> |
9675 | 2365 <step><para> |
2366 Yoh. Next task is to make the cursor on tty1 (or whatever) to | |
2367 disappear, and turn off screen blanking. Execute the following | |
2368 commands: | |
12815 | 2369 |
9675 | 2370 <screen> |
2371 echo -e '\033[?25l' | |
2372 setterm -blank 0<!-- | |
2373 --></screen> | |
2374 or | |
2375 <screen> | |
2376 setterm -cursor off | |
2377 setterm -blank 0<!-- | |
2378 --></screen> | |
2379 | |
2380 You possibly want to put the above into a script, and also clear the | |
2381 screen. To turn the cursor back: | |
2382 <screen>echo -e '\033[?25h'</screen> or | |
2383 <screen>setterm -cursor on</screen> | |
20862 | 2384 </para></step> |
9675 | 2385 <step><para> |
2386 Yeah kewl. Start movie playing with | |
2387 <screen> | |
2388 mplayer -vo mga -fs -screenw 640 -screenh 512 <replaceable>filename</replaceable><!-- | |
2389 --></screen> | |
12815 | 2390 |
9675 | 2391 (If you use X, now change to matroxfb with for example |
21720 | 2392 <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.) |
9675 | 2393 Change <literal>640</literal> and <literal>512</literal> if you set |
2394 the resolution to other... | |
21521 | 2395 </para></step> |
9675 | 2396 <step><para> |
2397 <emphasis role="bold">Enjoy the ultra-fast ultra-featured Matrox TV | |
2398 output (better than Xv)!</emphasis> | |
20862 | 2399 </para></step> |
9675 | 2400 </procedure> |
2401 </listitem> | |
2402 </varlistentry> | |
2403 </variablelist> | |
2404 | |
21521 | 2405 <formalpara><title>Building a Matrox TV-out cable</title> |
9675 | 2406 <para> |
2407 No one takes any responsibility, nor guarantee for any damage caused | |
2408 by this documentation. | |
2409 </para> | |
2410 </formalpara> | |
2411 | |
21521 | 2412 <formalpara><title>Cable for G400</title> |
9675 | 2413 <para> |
2414 The CRTC2 connector's fourth pin is the composite video signal. The | |
2415 ground are the sixth, seventh and eighth pins. (info contributed | |
20535 | 2416 from Balázs Rácz) |
9675 | 2417 </para> |
2418 </formalpara> | |
2419 | |
21521 | 2420 <formalpara><title>Cable for G450</title> |
9675 | 2421 <para> |
2422 The CRTC2 connector's first pin is the composite video signal. The | |
2423 ground are the fifth, sixth, seventh, and fifteenth (5, 6, 7, 15) | |
20535 | 2424 pins. (info contributed from Balázs Kerekes) |
9675 | 2425 </para> |
2426 </formalpara> | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2427 </sect2> |
9675 | 2428 |
20862 | 2429 <!-- ********** --> |
2430 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2431 <sect2 id="tv-out_matrox_g450"> |
9675 | 2432 <title>Matrox G450/G550 cards</title> |
20862 | 2433 |
9675 | 2434 <para> |
2435 TV output support for these cards has only been recently introduced, and is | |
21521 | 2436 not yet in the mainstream kernel. |
2437 Currently the <emphasis role="bold">mga_vid</emphasis> module can't be used | |
2438 AFAIK, because the G450/G550 driver works only in one configuration: the first | |
2439 CRTC chip (with much more features) on the first display (on monitor), | |
2440 and the second CRTC (no <emphasis role="bold">BES</emphasis> - for | |
9675 | 2441 explanation on BES, please see the G400 section above) on TV. So you can only |
21521 | 2442 use <application>MPlayer</application>'s <emphasis>fbdev</emphasis> output |
2443 driver at the present. | |
9675 | 2444 </para> |
2445 | |
2446 <para> | |
2447 The first CRTC can't be routed to the second head currently. The author of the | |
2448 kernel matroxfb driver - Petr Vandrovec - will maybe make support for this, by | |
2449 displaying the first CRTC's output onto both of the heads at once, as currently | |
2450 recommended for G400, see the section above. | |
2451 </para> | |
2452 | |
2453 <para> | |
12349 | 2454 The necessary kernel patch and the detailed HOWTO is downloadable from |
9948 | 2455 <ulink url="http://www.bglug.ca/matrox_tvout/"/> |
9675 | 2456 </para> |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2457 </sect2> |
9675 | 2458 |
20862 | 2459 <!-- ********** --> |
9675 | 2460 |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2461 <sect2 id="tvout-ati"> |
9675 | 2462 <title>ATI cards</title> |
2463 | |
21521 | 2464 <formalpara><title>PREAMBLE</title> |
9675 | 2465 <para> |
2466 Currently ATI doesn't want to support any of its TV-out chips under Linux, | |
2467 because of their licensed Macrovision technology. | |
2468 </para> | |
2469 </formalpara> | |
2470 | |
2471 <itemizedlist> | |
2472 <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
|
2473 <listitem><para> |
9675 | 2474 <emphasis role="bold">ATI Mach64</emphasis>: |
12349 | 2475 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
|
2476 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2477 <listitem><para> |
9675 | 2478 <emphasis role="bold">ASIC Radeon VIVO</emphasis>: |
12349 | 2479 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
|
2480 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2481 <listitem><para> |
9675 | 2482 <emphasis role="bold">Radeon</emphasis> and <emphasis role="bold">Rage128</emphasis>: |
2483 supported by <application>MPlayer</application>! | |
2484 Check <link linkend="vesa">VESA driver</link> and | |
2485 <link linkend="vidix">VIDIX</link> sections. | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2486 </para></listitem> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2487 <listitem><para> |
9675 | 2488 <emphasis role="bold">Rage Mobility P/M, Radeon, Rage 128, Mobility M3/M4</emphasis>: |
21521 | 2489 supported by |
2490 <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
|
2491 </para></listitem> |
9675 | 2492 </itemizedlist> |
2493 | |
2494 <para> | |
2495 On other cards, just use the <link linkend="vesa">VESA</link> driver, | |
2496 without VIDIX. Powerful CPU is needed, though. | |
2497 </para> | |
2498 | |
2499 <para> | |
2500 Only thing you need to do - <emphasis role="bold">Have the TV connector | |
2501 plugged in before booting your PC</emphasis> since video BIOS initializes | |
2502 itself only once during POST procedure. | |
2503 </para> | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2504 </sect2> |
9675 | 2505 |
20862 | 2506 <!-- ********** --> |
9675 | 2507 |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2508 <sect2 id="tvout-nvidia"> |
10111 | 2509 <title>nVidia</title> |
20862 | 2510 |
9675 | 2511 <para> |
21521 | 2512 First, you MUST download the closed-source drivers from |
2513 <ulink url="http://nvidia.com"/>. | |
2514 I will not describe the installation and configuration process because it does | |
2515 not cover the scope of this documentation. | |
9675 | 2516 </para> |
2517 | |
2518 <para> | |
2519 After XFree86, XVideo, and 3D acceleration is properly working, edit your | |
2520 card's Device section in the <filename>XF86Config</filename> file, according | |
2521 to the following example (adapt for your card/TV): | |
2522 | |
2523 <programlisting> | |
2524 Section "Device" | |
2525 Identifier "GeForce" | |
2526 VendorName "ASUS" | |
2527 BoardName "nVidia GeForce2/MX 400" | |
2528 Driver "nvidia" | |
2529 #Option "NvAGP" "1" | |
2530 Option "NoLogo" | |
2531 Option "CursorShadow" "on" | |
2532 | |
2533 Option "TwinView" | |
2534 Option "TwinViewOrientation" "Clone" | |
2535 Option "MetaModes" "1024x768,640x480" | |
2536 Option "ConnectedMonitor" "CRT, TV" | |
2537 Option "TVStandard" "PAL-B" | |
2538 Option "TVOutFormat" "Composite" | |
2539 EndSection | |
2540 </programlisting> | |
2541 </para> | |
2542 | |
2543 <para> | |
2544 Of course the important thing is the TwinView part. | |
2545 </para> | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2546 </sect2> |
11264 | 2547 |
20862 | 2548 <!-- ********** --> |
2549 | |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2550 <sect2 id="tvout-neomagic"> |
13189 | 2551 <title>NeoMagic</title> |
20862 | 2552 |
11264 | 2553 <para> |
13189 | 2554 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
|
2555 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
|
2556 <itemizedlist> |
17559 | 2557 <listitem><para> |
12757
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2558 <emphasis role="bold">Analog encoder chip</emphasis>: |
17559 | 2559 It has been reported that reliable TV out can be obtained by using |
2560 <option>-vo fbdev</option> or <option>-vo fbdev2</option>. | |
2561 You need to have vesafb compiled in your kernel and pass | |
2562 the following parameters on the kernel command line: | |
2563 <option>append="video=vesafb:ywrap,mtrr" vga=791</option>. | |
2564 You should start <application>X</application>, then switch to console mode | |
21720 | 2565 with e.g. |
2566 <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>. | |
17559 | 2567 If you fail to start <application>X</application> before running |
2568 <application>MPlayer</application> from the console, the video | |
2569 becomes slow and choppy (explanations are welcome). | |
2570 Login to your console, then initiate the following command: | |
2571 | |
2572 <screen>clear; mplayer -vo fbdev -zoom -cache 8192 dvd://</screen> | |
2573 | |
2574 Now you should see the movie running in console mode filling up about | |
21720 | 2575 half your laptop's LCD screen. To switch to TV hit |
2576 <keycombo><keycap>Fn</keycap><keycap>F5</keycap></keycombo> three times. | |
17559 | 2577 Tested on a Tecra 8000, 2.6.15 kernel with vesafb, ALSA v1.0.10. |
20862 | 2578 </para></listitem> |
2579 <listitem> | |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2580 <para> |
12757
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2581 <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
|
2582 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
|
2583 </para><para> |
12757
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2584 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
|
2585 <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
|
2586 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
|
2587 </para> |
12757
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2588 <itemizedlist> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2589 <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
|
2590 <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
|
2591 </itemizedlist> |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2592 <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
|
2593 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
|
2594 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
|
2595 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
|
2596 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
|
2597 </para> |
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2598 <para> |
12757
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2599 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
|
2600 blacklevel, flickfilter are implemented. |
21725
e4cd9d683286
Massive <simpara> -> <para>, as no <simpara>'s are actually needed.
torinthiel
parents:
21720
diff
changeset
|
2601 </para> |
12757
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2602 </listitem> |
8bcd91d9efd1
Neomagic TV out support docs by Rudolf Marek <MAREKR2@cs.felk.cvut.cz>
diego
parents:
12578
diff
changeset
|
2603 </itemizedlist> |
11264 | 2604 </para> |
9675 | 2605 </sect2> |
13912
c66b1514ce5b
Remove pointless devices section, make video and audio top level sections.
diego
parents:
13908
diff
changeset
|
2606 </sect1> |
17321
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2607 |
7f9fcf5245a0
Improve overall structure by adding a few top-level chapters so that
diego
parents:
15894
diff
changeset
|
2608 </chapter> |