Mercurial > mplayer.hg
annotate DOCS/video.html @ 6981:3bc485948088
HTML fixes, no content change.
| author | diego |
|---|---|
| date | Sun, 11 Aug 2002 22:27:08 +0000 |
| parents | 916f62dd0910 |
| children | 83a386e88f9e |
| rev | line source |
|---|---|
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 1612 | 2 <HTML> |
|
4982
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4920
diff
changeset
|
3 |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4920
diff
changeset
|
4 <HEAD> |
|
6882
f3f87f6bf5cf
Added a uniform title: something - MPlayer - The Movie Player for Linux.
diego
parents:
6732
diff
changeset
|
5 <TITLE>Video - MPlayer - The Movie Player for Linux</TITLE> |
| 6391 | 6 <LINK REL="stylesheet" TYPE="text/css" HREF="default.css"> |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
7 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> |
|
4982
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4920
diff
changeset
|
8 </HEAD> |
|
6cb9d9a1716d
HTML: different font handling - idea from new hp dezign
gabucino
parents:
4920
diff
changeset
|
9 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
10 <BODY> |
| 1704 | 11 |
| 1612 | 12 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
13 <P><B><A NAME="video">2.3.1 Video output devices</A></B></P> |
| 1612 | 14 |
| 15 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
16 <P><B><A NAME="mtrr">2.3.1.1 Setting up MTRR</A></B></P> |
| 1612 | 17 |
| 1946 | 18 <P>It is VERY recommended to check if the MTRR registers are set up properly, |
| 6960 | 19 because they can give a big performance boost.</P> |
| 1946 | 20 |
| 6960 | 21 <P>Do a '<CODE>cat /proc/mtrr</CODE>':</P> |
| 1946 | 22 |
| 23 <P><CODE> | |
| 6960 | 24 --($:~)-- cat /proc/mtrr<BR> |
| 25 reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9<BR> | |
| 6974 | 26 reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1</CODE></P> |
| 1946 | 27 |
| 6599 | 28 <P>It's right, shows my Matrox G400 with 16MB memory. I did this from |
| 6960 | 29 XFree 4.x.x , which sets up MTRR registers automatically.</P> |
| 1946 | 30 |
| 6960 | 31 <P>If nothing worked, you have to do it manually. First, you have to find the |
| 32 base address. You have 3 ways to find it:</P> | |
| 1612 | 33 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
34 <UL> |
| 6960 | 35 <LI>from X11 startup messages, for example: |
| 36 <P><CODE>(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000<BR> | |
| 37 (--) SVGA: Linear framebuffer at 0xD8000000</CODE></P></LI> | |
| 38 <LI>from /proc/pci (use lspci -v command): | |
| 39 <P> | |
| 40 <CODE>01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525</CODE> | |
| 41 <CODE>Memory at d8000000 (32-bit, prefetchable)</CODE> | |
| 42 </P></LI> | |
| 43 <LI>from mga_vid kernel driver messages (use dmesg): | |
| 44 <P><CODE>mga_mem_base = d8000000</CODE></P></LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
45 </UL> |
| 1612 | 46 |
| 1682 | 47 <P>Then let's find the memory size. This is very easy, just convert video ram |
| 6960 | 48 size to hexadecimal, or use this table:</P> |
| 1612 | 49 |
| 1682 | 50 <TABLE BORDER=0> |
| 6974 | 51 <TR><TD> </TD><TD>1 MB</TD><TD WIDTH="10%"></TD><TD>0x100000</TD></TR> |
| 52 <TR><TD></TD><TD>2 MB</TD><TD></TD><TD>0x200000</TD></TR> | |
| 53 <TR><TD></TD><TD>4 MB</TD><TD></TD><TD>0x400000</TD></TR> | |
| 54 <TR><TD></TD><TD>8 MB</TD><TD></TD><TD>0x800000</TD></TR> | |
| 55 <TR><TD></TD><TD>16 MB</TD><TD></TD><TD>0x1000000</TD></TR> | |
| 56 <TR><TD></TD><TD>32 MB</TD><TD></TD><TD>0x2000000</TD></TR> | |
| 1682 | 57 </TABLE> |
| 1612 | 58 |
| 59 | |
| 6599 | 60 <P>You know base address and memory size, let's setup MTRR registers! |
| 6960 | 61 For example, for the Matrox card above (base=0xd8000000) with 32MB |
| 62 ram (size=0x2000000) just execute:</P> | |
| 1612 | 63 |
| 64 | |
| 1682 | 65 <P><CODE> echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr</CODE></P> |
| 1612 | 66 |
| 67 | |
| 6599 | 68 <P>Not all CPUs support MTRRs. For example older K6-2's [around 266MHz, |
| 6960 | 69 stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat |
| 70 /proc/cpuinfo</CODE>' to check it').</P> | |
| 1612 | 71 |
| 6974 | 72 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
73 <P><B><A NAME="xv">2.3.1.2 Xv</A></B></P> |
| 1612 | 74 |
| 1682 | 75 <P>Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines |
| 6960 | 76 using the XVideo extension. This is what the option '-vo xv' uses. Also, |
| 77 this is driver supports adjusting brightness/contrast/hue/etc (unless you use | |
| 78 the old, slow DirectShow DivX codec, which supports it everywhere), see the | |
| 79 man page.</P> | |
| 4498 | 80 |
| 81 <P>In order to make this work, be sure to check the following:</P> | |
| 6960 | 82 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
83 <UL> |
| 6960 | 84 <LI>You have to use XFree86 4.0.2 or newer (former versions don't have |
| 85 XVideo)</LI> | |
| 86 <LI>Your card actually supports hardware acceleration (modern cards do)</LI> | |
| 87 <LI>X loads the XVideo extension, it's something like this: | |
| 1612 | 88 |
| 6960 | 89 <P><CODE> (II) Loading extension XVideo</CODE></P> |
| 90 | |
| 91 <P>in /var/log/XFree86.0.log</P> | |
| 1612 | 92 |
| 6960 | 93 <P>NOTE: this loads only the XFree86's extension. In a good install, this |
| 94 is always loaded, and doesn't mean that the _card's_ XVideo support is | |
| 95 loaded!</P> | |
| 96 </LI> | |
| 97 <LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the | |
| 98 part of the XFree86 distribution. It should display a long text, similar | |
| 99 to this: | |
| 100 <PRE> | |
| 1612 | 101 X-Video Extension version 2.2 |
| 102 screen #0 | |
| 103 Adaptor #0: "Savage Streams Engine" | |
| 104 number of ports: 1 | |
| 105 port base: 43 | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
106 operations supported: PutImage |
| 1612 | 107 supported visuals: |
| 108 depth 16, visualID 0x22 | |
| 109 depth 16, visualID 0x23 | |
| 110 number of attributes: 5 | |
| 111 (...) | |
| 112 Number of image formats: 7 | |
| 113 id: 0x32595559 (YUY2) | |
| 114 guid: 59555932-0000-0010-8000-00aa00389b71 | |
| 115 bits per pixel: 16 | |
| 116 number of planes: 1 | |
| 117 type: YUV (packed) | |
| 118 id: 0x32315659 (YV12) | |
| 119 guid: 59563132-0000-0010-8000-00aa00389b71 | |
| 120 bits per pixel: 12 | |
| 121 number of planes: 3 | |
| 122 type: YUV (planar) | |
| 123 (...etc...) | |
| 6960 | 124 </PRE> |
| 125 <P>It must support YUY2 packed, and YV12 planar pixel formats to be | |
| 126 usable with <B>MPlayer</B>.</P> | |
| 127 </LI> | |
| 128 <LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support. | |
| 129 ./configure prints this.</LI> | |
| 6974 | 130 </UL> |
| 1612 | 131 |
| 1682 | 132 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
133 <P><B><A NAME="xv_3dfx">2.3.1.2.1 3dfx cards</A></B></P> |
| 1612 | 134 |
| 6960 | 135 <P>Older 3dfx drivers were known to have problems with XVideo acceleration, it |
| 136 didn't support either YUY2 or YV12, and so. Verify that you have XFree86 | |
| 137 version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous versions, | |
| 138 including 4.1.0 <B>crashes with YV12</B>! If you experience strange effects | |
| 139 using -vo xv, try SDL (it has XVideo too) and see if it helps. Check the | |
| 140 <A HREF="#sdl">SDL section</A> for details.</P> | |
| 1612 | 141 |
| 6960 | 142 <P><B>OR</B>, try the NEW -vo tdfxfb driver! See the |
| 143 <A HREF="#tdfxfb">tdfxfb</A> section!</P> | |
| 1612 | 144 |
| 2865 | 145 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
146 <P><B><A NAME="xv_s3">2.3.1.2.2 S3 cards</A></B></P> |
| 1682 | 147 |
| 148 <P>S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3 | |
| 6960 | 149 or greater (in case of image problems, try 16bpp). As for S3 Virge.. there is |
| 150 xv support, but the card itself is very slow, so you better sell it.</P> | |
| 1682 | 151 |
| 6960 | 152 <P><B>NOTE</B>: Savage cards have a slow YV12 image displaying capability (it |
| 153 needs to do YV12->YUY2 conversion, because the Savage hardware can't display | |
| 154 YV12). So when this documentation says at some point "this has YV12 output | |
| 155 use this, it's faster", it's not sure. Try | |
| 156 <A HREF="http://www.mplayerhq.hu/MPlayer/contrib/Savage-driver/savage_drv.o.mmx2.bz2">this | |
| 157 driver</A>, it uses MMX2 for this task and is faster than the native X | |
| 158 driver.</P> | |
| 2865 | 159 |
| 160 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
161 <P><B><A NAME="xv_nvidia">2.3.1.2.3 nVidia cards</A></B></P> |
| 1612 | 162 |
| 6960 | 163 <P>nVidia isn't a very good choice under Linux (according to nVidia, this is |
| 164 <A HREF="users_against_developers.html#nvidia">not true</A>).. You'll have to | |
| 165 use the binary closed-source nVidia driver, available at nVidia's web site. | |
| 166 The standard XFree86 driver doesn't support XVideo for these cards, due to | |
| 167 nVidia's closed sources/specifications.</P> | |
| 1612 | 168 |
| 3290 | 169 <P>As far as I know the latest XFree86 driver contains XVideo support for |
| 6960 | 170 GeForce 2 and 3.</P> |
| 3290 | 171 |
| 6599 | 172 <P>Riva128 cards don't have XVideo support even with the nVidia driver :( |
| 6960 | 173 Complain to nVidia.</P> |
| 1612 | 174 |
| 175 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
176 <P><B><A NAME="xv_ati">2.3.1.2.4 ATI cards</A></B></P> |
| 1612 | 177 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
178 <UL> |
| 6960 | 179 <LI>The <A HREF="http://www.linuxvideo.org/gatos">GATOS driver</A> (which you |
| 180 should use, unless you have Rage128 or Radeon) has VSYNC enabled by | |
| 181 default. It means that decoding speed (!) is synced to the monitor's | |
| 182 refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or | |
| 183 set refresh rate to n*(fps of the movie) Hz.</LI> | |
| 184 <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version | |
| 185 4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can | |
| 186 happily get <B>accelerated</B> display, with or without <B>TV output</B>, and | |
| 187 no libraries or X are needed. Read <A HREF="#vidix">Vidix</A> section.</LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
188 </UL> |
| 1612 | 189 |
| 190 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
191 <P><B><A NAME="xv_neomagic">2.3.1.2.5 NeoMagic cards</A></B></P> |
|
1922
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
192 |
|
4920
089485d69edd
added notes about enhanced Neomagic and Savage4 drivers
gabucino
parents:
4908
diff
changeset
|
193 <P>These cards can be found in many laptops. Unfortunately, the driver in |
|
089485d69edd
added notes about enhanced Neomagic and Savage4 drivers
gabucino
parents:
4908
diff
changeset
|
194 X 4.2.0 can't do Xv, but we have a modified, Xv-capable driver for you. |
|
089485d69edd
added notes about enhanced Neomagic and Savage4 drivers
gabucino
parents:
4908
diff
changeset
|
195 <A HREF="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/neomagic_drv.o.4.2.0.bz2">Download from here</A>. |
| 5359 | 196 Driver provided by Stefan Seyfried.</P> |
| 5378 | 197 |
| 6960 | 198 <P>To allow playback of DVD sized content change your XF86Config like this:</P> |
| 5378 | 199 |
| 6974 | 200 <P>Section "Device"<BR> |
| 6960 | 201 <I>[...]</I><BR> |
| 202 Driver "neomagic"<BR> | |
| 203 <B>Option "OverlayMem" "829440"</B><BR> | |
| 204 <I>[...]</I><BR> | |
| 6974 | 205 EndSection</P> |
|
1922
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
206 |
| 5378 | 207 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
208 <P><B><A NAME="xv_trident">2.3.1.2.6 Trident cards</A></B></P> |
| 3794 | 209 |
| 210 <P>If you want to use xv with a trident card, provided that it doesn't | |
| 6960 | 211 work with 4.1.0, try the latest CVS of XFree or wait for XFree 4.2.0. |
| 212 The latest CVS adds support for fullscreen xv support with the | |
| 213 Cyberblade XP card.</P> | |
|
1922
5f0e4310dd4d
NeoMagic stuff added (legyen egyszer gyereknap...)
gabucino
parents:
1920
diff
changeset
|
214 |
| 6974 | 215 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
216 <P><B><A NAME="dga">2.3.1.3 DGA</A></B></P> |
| 1612 | 217 |
| 6974 | 218 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
219 <P><B><A NAME="dga_summary">2.3.1.3.1 Summary</A></B></P> |
| 1612 | 220 |
| 6960 | 221 <P>This document tries to explain in some words what DGA is in general and what |
| 222 the DGA video output driver for <B>MPlayer</B> can do (and what it | |
| 223 can't).</P> | |
| 1612 | 224 |
| 225 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
226 <P><B><A NAME="dga_whatis">2.3.1.3.2 What is DGA</A></B></P> |
| 1612 | 227 |
| 1682 | 228 <P>DGA is short for Direct Graphics Access and is a means for a program to |
| 6960 | 229 bypass the X-Server and directly modifying the framebuffer memory. |
| 230 Technically spoken this happens by mapping the framebuffer memory into | |
| 231 the memory range of your process. This is allowed by the kernel only | |
| 232 if you have superuser privileges. You can get these either by logging in | |
| 233 as root or by setting the SUID bit on the <B>MPlayer</B> executable (NOT | |
| 234 recommended!).</P> | |
| 1612 | 235 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
236 <P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was |
| 6960 | 237 introduced with XFree 4.0.1.</P> |
| 1612 | 238 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
239 <P>DGA1 provides only direct framebuffer access as described above. For |
| 6960 | 240 switching the resolution of the video signal you have to rely on the |
| 241 XVidMode extension.</P> | |
| 1612 | 242 |
| 1682 | 243 <P>DGA2 incorporates the features of XVidMode extension and also allows |
| 6960 | 244 switching the depth of the display. So you may, although basically |
| 245 running a 32 bit depth X server, switch to a depth of 15 bits and vice | |
| 246 versa. </P> | |
| 1612 | 247 |
| 1682 | 248 <P>However DGA has some drawbacks. It seems it is somewhat dependent on the |
| 6960 | 249 graphics chip you use and on the implementation of the X server's video |
| 250 driver that controls this chip. So it does not work on every system ...</P> | |
| 1612 | 251 |
| 252 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
253 <P><B><A NAME="dga_installation">2.3.1.3.3 Installing DGA support for MPlayer</A></B></P> |
| 1682 | 254 |
| 255 <P>First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:</P> | |
| 256 | |
| 257 <P> <CODE>(II) Loading extension XFree86-DGA</CODE></P> | |
| 258 | |
| 6960 | 259 <P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! <B>MPlayer</B>'s DGA |
| 260 driver is autodetected on ./configure, or you can force it with | |
| 261 --enable-dga.</P> | |
| 1612 | 262 |
| 1682 | 263 <P>If the driver couldn't switch to a smaller resolution, experiment with |
| 6960 | 264 switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that |
| 265 the movie fits in. There is no converter right now.. :(</P> | |
| 1612 | 266 |
| 6960 | 267 <P>Become ROOT. DGA needs root access to be able to write directly video |
| 268 memory. If you want to run it as user, then install <B>MPlayer</B> SUID | |
| 269 root:</P> | |
| 1612 | 270 |
| 1682 | 271 <P><CODE> |
| 6960 | 272 chown root /usr/local/bin/mplayer<BR> |
| 273 chmod 750 /usr/local/bin/mplayer<BR> | |
| 274 chmod +s /usr/local/bin/mplayer</CODE></P> | |
| 1612 | 275 |
| 1682 | 276 <P>Now it works as a simple user, too.</P> |
| 1612 | 277 |
| 1682 | 278 <P><B>!!!! BUT STAY TUNED !!!!</B><BR> |
| 6960 | 279 This is a <B>BIG</B> security risk! Never do this on a server or on a |
| 280 computer can be accessed by more people than only you because they can gain | |
| 281 root privileges through SUID root <B>MPlayer</B>.<BR> | |
| 282 <B>!!!! SO YOU HAVE BEEN WARNED ... !!!!</B></P> | |
| 1682 | 283 |
| 284 <P>Now use '-vo dga' option, and there you go! (hope so:) | |
| 6960 | 285 You should also try if the '-vo sdl:dga' option works for you! It's much |
| 286 faster!!!</P> | |
| 1682 | 287 |
| 6974 | 288 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
289 <P><B><A NAME="dga_resolution">2.3.1.3.4 Resolution switching</A></B></P> |
| 1682 | 290 |
| 6960 | 291 <P>The DGA driver allows for switching the resolution of the output signal. |
| 292 This avoids the need for doing (slow) software scaling and at the same time | |
| 293 provides a fullscreen image. Ideally it would switch to the exact resolution | |
| 294 (except for honoring aspect ratio) of the video data, but the X server only | |
| 295 allows switching to resolutions predefined in | |
| 296 <CODE>/etc/X11/XF86Config</CODE> (<CODE>/etc/X11/XF86Config-4</CODE> for | |
| 297 XFree 4.0.X respectively). Those are defined by so-called modelines and | |
| 298 depend on the capabilities of your video hardware. The X server scans this | |
| 299 config file on startup and disables the modelines not suitable for your | |
| 300 hardware. You can find out which modes survive with the X11 log file. It can | |
| 301 be found at: | |
| 302 <CODE>/var/log/XFree86.0.log</CODE>.</P> | |
| 303 | |
| 1682 | 304 <P>See appendix A for some sample modeline definitions.</P> |
| 305 | |
| 6974 | 306 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
307 <P><B><A NAME="dga_mplayer">2.3.1.3.5 DGA & MPlayer</A></B></P> |
| 1612 | 308 |
| 6960 | 309 <P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to |
| 310 make use of it (-vo sdl:dga) and within the DGA driver (-vo dga). The above | |
| 311 said is true for both; in the following sections I'll explain how the DGA | |
| 312 driver for <B>MPlayer</B> works.</P> | |
| 1612 | 313 |
| 6974 | 314 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
315 <P><B><A NAME="dga_features">2.3.1.3.6 Features of the DGA driver</A></B></P> |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
316 |
| 1682 | 317 <P>The DGA driver is invoked by specifying -vo dga at the command line. |
| 6960 | 318 The default behavior is to switch to a resolution matching the original |
| 319 resolution of the video as close as possible. It deliberately ignores the | |
| 320 -vm and -fs switches (enabling of video mode switching and fullscreen) - | |
| 321 it always tries to cover as much area of your screen as possible by switching | |
| 322 the video mode, thus refraining to use a single additional cycle of your CPU | |
| 323 to scale the image. | |
| 324 If you don't like the mode it chooses you may force it to choose the mode | |
| 325 matching closest the resolution you specify by -x and -y. | |
| 326 By providing the -v option, the DGA driver will print, among a lot of other | |
| 327 things, a list of all resolutions supported by your current XF86-Config | |
| 328 file. | |
| 329 Having DGA2 you may also force it to use a certain depth by using the -bpp | |
| 330 option. Valid depths are 15, 16, 24 and 32. It depends on your hardware | |
| 331 whether these depths are natively supported or if a (possibly slow) | |
| 332 conversion has to be done.</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
333 |
|
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
334 <P>If you should be lucky enough to have enough offscreen memory left to |
| 6960 | 335 put a whole image there, the DGA driver will use doublebuffering, which |
| 336 results in much smoother movie replaying. It will tell you whether double- | |
| 337 buffering is enabled or not.</P> | |
| 1612 | 338 |
| 1682 | 339 <P>Doublebuffering means that the next frame of your video is being drawn in |
| 6960 | 340 some offscreen memory while the current frame is being displayed. When the |
| 341 next frame is ready, the graphics chip is just told the location in memory | |
| 342 of the new frame and simply fetches the data to be displayed from there. | |
| 343 In the meantime the other buffer in memory will be filled again with new | |
| 344 video data.</P> | |
| 1682 | 345 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
346 <P>Doublebuffering may be switched on by using the option -double and may be |
| 6960 | 347 disabled with -nodouble. Current default option is to disable |
| 348 doublebuffering. When using the DGA driver, onscreen display (OSD) only | |
| 349 works with doublebuffering enabled. However, enabling doublebuffering may | |
| 350 result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of | |
| 351 CPU time!) depending on the implementation of DGA for your hardware.</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
352 |
| 1682 | 353 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
354 <P><B><A NAME="dga_speed">2.3.1.3.7 Speed issues</A></B></P> |
| 1682 | 355 |
| 356 <P>Generally spoken, DGA framebuffer access should be at least as fast as using | |
| 6960 | 357 the X11 driver with the additional benefit of getting a fullscreen image. |
| 358 The percentage speed values printed by <B>MPlayer</B> have to be interpreted | |
| 359 with some care, as for example, with the X11 driver they do not include the | |
| 360 time used by the X-Server needed for the actual drawing. Hook a terminal to a | |
| 361 serial line of your box and start top to see what is really going on in your | |
| 362 box...</P> | |
| 1682 | 363 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
364 <P>Generally spoken, the speedup done by using DGA against 'normal' use of X11 |
| 6960 | 365 highly depends on your graphics card and how well the X-Server module for it |
| 366 is optimized.</P> | |
| 1682 | 367 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
368 <P>If you have a slow system, better use 15 or 16bit depth since they require |
| 6960 | 369 only half the memory bandwidth of a 32 bit display.</P> |
| 1612 | 370 |
| 6960 | 371 <P>Using a depth of 24bit is even a good idea if your card natively just |
| 372 supports 32 bit depth since it transfers 25% less data compared to the 32/32 | |
| 373 mode.</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
374 |
| 6599 | 375 <P>I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2 |
| 6960 | 376 CPUs might work at 400 MHZ and above.</P> |
| 1612 | 377 |
| 6974 | 378 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
379 <P><B><A NAME="dga_bugs">2.3.1.3.8 Known bugs</A></B></P> |
| 1682 | 380 |
| 6599 | 381 <P>Well, according to some developers of XFree, DGA is quite a beast. They |
| 6960 | 382 tell you better not to use it. Its implementation is not always flawless |
| 383 with every chipset driver for XFree out there.</P> | |
| 1612 | 384 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
385 <UL> |
| 6960 | 386 <LI>With XFree 4.0.3 and nv.o there is a bug resulting in strange |
| 387 colors.</LI> | |
| 388 <LI>ATI driver requires to switch mode back more than once after finishing | |
| 389 using of DGA.</LI> | |
| 390 <LI>Some drivers simply fail to switch back to normal resolution (use | |
| 391 Ctrl-Alt-Keypad +, - to switch back manually).</LI> | |
| 392 <LI>Some drivers simply display strange colors.</LI> | |
| 393 <LI>Some drivers lie about the amount of memory they map into the process's | |
| 394 address space, thus vo_dga won't use doublebuffering (SIS?).</LI> | |
| 395 <LI>some drivers seem to fail to report even a single valid mode. In this | |
| 396 case the DGA driver will crash telling you about a nonsense mode of | |
| 397 100000x100000 or the like ...</LI> | |
| 398 <LI>OSD only works with doublebuffering enabled.</LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
399 </UL> |
| 1682 | 400 |
| 6974 | 401 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
402 <P><B><A NAME="dga_future">2.3.1.3.9 Future work</A></B></P> |
| 1682 | 403 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
404 <UL> |
| 6960 | 405 <LI>use of the new X11 render interface for OSD</LI> |
| 406 <LI>where is my TODO list ???? :-(((</LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
407 </UL> |
| 1612 | 408 |
| 409 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
410 <P><B><A NAME="dga_modelines">2.3.1.3.A Some modelines</A></B></P> |
| 1612 | 411 |
| 1682 | 412 <PRE> |
| 1612 | 413 Section "Modes" |
| 414 Identifier "Modes[0]" | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
415 Modeline "800x600" 40 800 840 968 1056 600 601 605 628 |
| 1612 | 416 Modeline "712x600" 35.0 712 740 850 900 400 410 412 425 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
417 Modeline "640x480" 25.175 640 664 760 800 480 491 493 525 |
| 1612 | 418 Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan |
| 419 Modeline "352x288" 25.10 352 368 416 432 288 296 290 310 | |
| 420 Modeline "352x240" 15.750 352 368 416 432 240 244 246 262 Doublescan | |
| 421 Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan | |
| 422 EndSection | |
| 1682 | 423 </PRE> |
| 1612 | 424 |
| 6599 | 425 <P>These entries work fine with my Riva128 chip, using nv.o X server driver |
| 6960 | 426 module.</P> |
| 1612 | 427 |
| 428 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
429 <P><B><A NAME="dga_bug_reports">2.3.1.3.B Bug Reports</A></B></P> |
| 1612 | 430 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
431 <P>If you experience troubles with the DGA driver please feel free to file |
| 6960 | 432 a bug report to me (e-mail address below). Please start <B>MPlayer</B> with |
| 433 the -v option and include all lines in the bug report that start with | |
| 434 vo_dga:</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
435 |
|
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
436 <P>Please do also include the version of X11 you are using, the graphics card |
| 6960 | 437 and your CPU type. The X11 driver module (defined in XF86-Config) might |
| 438 also help. Thanks!</P> | |
| 1612 | 439 |
| 1682 | 440 <P><I>Acki (acki@acki-netz.de, www.acki-netz.de)</I></P> |
| 1612 | 441 |
| 442 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
443 <P><B><A NAME="sdl">2.3.1.4 SDL</A></B></P> |
| 1612 | 444 |
| 6583 | 445 <P>SDL (Simple Directmedia Layer) is basically a unified video/audio |
| 3988 | 446 interface. Programs that use it know only about SDL, and not about what video |
| 447 or audio driver does SDL actually use. For example a Doom port using SDL can | |
| 448 run on svgalib, aalib, X, fbdev, and others, you only have to specify the | |
| 449 (for example) video driver to use with the SDL_VIDEODRIVER environment | |
| 450 variable. Well, in theory.</P> | |
| 451 | |
| 452 <P>With <B>MPlayer</B>, we used its X11 driver's software scaler ability for | |
| 453 cards/drivers that doesn't support XVideo, until we made our own (faster, | |
| 454 nicer) software scaler. Also we used its aalib output, but now we have ours | |
| 455 which is more comfortable. Its DGA mode was better than ours, until | |
| 456 recently. Get it now? :)</P> | |
| 457 | |
| 458 <P>It also helps with some buggy drivers/cards if the video is jerky | |
| 459 (not slow system problem), or audio is lagging.</P> | |
| 460 | |
| 5119 | 461 <P>SDL video output supports displaying subtitles under the movie, on the (if |
| 462 present) black bar.</P> | |
| 463 | |
| 1682 | 464 <P>Here are some notes about SDL out in <B>MPlayer</B>.</P> |
| 1612 | 465 |
| 6974 | 466 <TABLE BORDER=0> |
| 467 <TR><TD COLSPAN=4><P><B>There are several command line switches for SDL:</B></P></TD></TR> | |
| 468 <TR><TD> </TD><TD><CODE>-vo sdl:name</CODE></TD><TD> </TD><TD> | |
| 469 specifies sdl video driver to use (i.e.. aalib, dga, x11)</TD></TR> | |
| 470 <TR><TD></TD><TD><CODE>-ao sdl:name</CODE></TD><TD></TD><TD>specifies sdl audio driver to use (i.e.. dsp, | |
| 471 esd, arts)</TD></TR> | |
| 472 <TR><TD></TD><TD><CODE>-noxv</CODE></TD><TD></TD><TD>disables XVideo hardware acceleration</TD></TR> | |
| 473 <TR><TD></TD><TD><CODE>-forcexv</CODE></TD><TD></TD><TD>tries to force XVideo acceleration</TD></TR> | |
| 1612 | 474 |
| 6974 | 475 <TR><TD COLSPAN=4><P><B>SDL Keys:</B></P></TD></TR> |
| 476 <TR><TD></TD><TD><CODE>F</CODE></TD><TD></TD><TD>toggles fullscreen/windowed mode</TD></TR> | |
| 477 <TR><TD></TD><TD><CODE>C</CODE></TD><TD></TD><TD>cycles available fullscreen modes</TD></TR> | |
| 478 <TR><TD></TD><TD><CODE>W/S</CODE></TD><TD></TD><TD>mappings for * and / (mixer control)</TD></TR> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
479 </TABLE> |
| 1612 | 480 |
| 1682 | 481 <P><B>KNOWN BUGS:</B></P> |
| 6960 | 482 |
| 483 <UL> | |
| 484 <LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa!) | |
| 485 It's bug in SDL, I can't change it (tested with SDL 1.2.1).</LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
486 </UL> |
| 1612 | 487 |
| 6974 | 488 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
489 <P><B><A NAME="svgalib">2.3.1.5 SVGAlib</A></B></P> |
| 1682 | 490 |
| 6499 | 491 <P><B><U>Installation</U></B><BR> |
| 492 You'll have to install svgalib and its development package in order for | |
| 493 <B>MPlayer</B> build its SVGAlib driver (autodetected, but can be forced), | |
| 494 and don't forget to edit /etc/vga/libvga.config to suit your card & | |
| 495 monitor.</P> | |
| 496 | |
| 497 <P><B><U>Notes</U></B><BR> | |
| 498 Be sure not to use the -fs switch, since it toggles the usage of the software | |
| 499 scaler, and it's slow. If you really need it, use the <CODE>-sws 4</CODE> | |
| 500 option which will produce bad quality, but is somewhat faster.</P> | |
| 501 | |
| 502 <P><B><U>EGA (4bpp) support</U></B><BR> | |
| 503 SVGAlib incorporates EGAlib, and <B>MPlayer</B> has the possibility to | |
| 504 display any movie in 16 colors, thus usable in the following sets:</P> | |
| 1612 | 505 |
| 6499 | 506 <UL> |
| 507 <LI>EGA card with EGA monitor: 320x200x4bpp, 640x200x4bpp, 640x350x4bpp</LI> | |
| 508 <LI>EGA card with CGA monitor: 320x200x4bpp, 640x200x4bpp</LI> | |
| 509 </UL> | |
| 510 | |
| 511 <P>The bpp (bits per pixel) value must be set to 4 by hand:<BR> | |
| 512 <CODE>-bpp 4</CODE><BR> | |
| 513 The movie probably must be scaled down to fit in EGA mode:<BR> | |
| 514 <CODE>-vop scale=640:350</CODE> or<BR> | |
| 515 <CODE>-vop scale=320:200</CODE><BR> | |
| 516 For that we need fast but bad quality scaling routine:<BR> | |
| 517 <CODE>-sws 4</CODE><BR> | |
| 518 Maybe automatic aspect correction has to be shut off:<BR> | |
| 6974 | 519 <CODE>-noaspect</CODE></P> |
| 6499 | 520 |
| 1612 | 521 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
522 <P><B><A NAME="fbdev">2.3.1.6 Framebuffer output (FBdev)</A></B></P> |
| 1682 | 523 |
| 524 <P>Whether to build the FBdev target is autodetected during ./configure . | |
| 6960 | 525 Read the framebuffer documentation in the kernel sources |
| 526 (Documentation/fb/*) for info on how to enable it, etc..!</P> | |
| 1612 | 527 |
| 1682 | 528 <P>If your card doesn't support VBE 2.0 standard (older ISA/PCI |
| 6960 | 529 cards, such as S3 Trio64), only VBE 1.2 (or older?): |
| 530 Well, VESAfb is still available, but you'll have to load SciTech Display | |
| 531 Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or | |
| 532 whatever. And don't forget to register your UniVBE ;))</P> | |
| 1612 | 533 |
| 1682 | 534 <P>The FBdev output takes some additional parameters above the others:</P> |
| 1612 | 535 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
536 <TABLE BORDER=0> |
| 6974 | 537 <TR><TD> </TD><TD><CODE>-fb</CODE></TD><TD> </TD><TD> |
| 538 specify the framebuffer device to use (/dev/fb0)</TD></TR> | |
| 539 <TR><TD></TD><TD><CODE>-fbmode</CODE></TD><TD></TD><TD>mode name to use (according to /etc/fb.modes)</TD></TR> | |
| 540 <TR><TD></TD><TD><CODE>-fbmodeconfig</CODE></TD><TD></TD><TD> config file of modes (default /etc/fb.modes)</TD></TR> | |
| 541 <TR><TD></TD><TD><CODE>-monitor_hfreq</CODE></TD><TD></TD><TD ROWSPAN=3>IMPORTANT values, see example.conf</TD></TR> | |
| 542 <TR><TD></TD><TD><CODE>-monitor_vfreq</CODE></TD><TD></TD></TR> | |
| 543 <TR><TD></TD><TD><CODE>-monitor_dotclock</CODE></TD><TD></TD></TR> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
544 </TABLE> |
| 1612 | 545 |
| 1682 | 546 <P>If you want to change to a specific mode, then use</P> |
| 1612 | 547 |
| 1682 | 548 <P><CODE> mplayer -vm -fbmode (NameOfMode) filename</CODE></P> |
| 1612 | 549 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
550 <UL> |
| 6960 | 551 <LI><B>-vm</B> alone will choose the most suitable mode from /etc/fb.modes. |
| 552 Can be used together with -x and -y options too. The -flip option is | |
| 553 supported only if the movie's pixel format matches the video mode's pixel | |
| 554 format. Pay attention to the bpp value, fbdev driver tries to use the | |
| 555 current, or if you specify the -bpp option, then that.</LI> | |
| 556 <LI><B>-zoom</B> option isn't supported (software scaling is slow). -fs | |
| 557 option isn't supported. You can't use 8bpp (or less) modes.</LI> | |
| 558 <LI>you possibly want to turn the cursor off: <CODE>echo -e | |
| 559 '\033[?25l'</CODE> or <CODE>setterm -cursor off</CODE><BR> | |
| 560 and the screen saver: <CODE>setterm -blank 0</CODE><BR> | |
| 561 To turn the cursor back on: <CODE>echo -e '\033[?25h'</CODE> | |
| 562 or <CODE>setterm -cursor on</CODE></LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
563 </UL> |
| 1612 | 564 |
| 1682 | 565 <P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer, |
| 6960 | 566 and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P> |
| 1612 | 567 |
| 6974 | 568 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
569 <P><B><A NAME="mga_vid">2.3.1.7 Matrox framebuffer (mga_vid)</A></B></P> |
| 1612 | 570 |
| 1992 | 571 <P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler) |
| 6960 | 572 support, the mga_vid kernel driver. It's active developed by me (A'rpi), and |
| 573 it has hardware VSYNC support with triple buffering. It works on both | |
| 574 framebuffer console and under X.</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
575 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
576 <P><B>WARNING</B>: on non-Linux systems, use <A HREF="#vidix">VIDIX</A> for |
|
4505
fdeee8424d90
on non-Linux use Vidix instead of mga_vid kernelmodule
gabucino
parents:
4504
diff
changeset
|
577 mga_vid !!!</P> |
|
fdeee8424d90
on non-Linux use Vidix instead of mga_vid kernelmodule
gabucino
parents:
4504
diff
changeset
|
578 |
| 1682 | 579 <P>To use it, you first have to compile mga_vid.o:</P> |
| 1612 | 580 |
| 1682 | 581 <P><CODE> cd drivers<BR> |
| 6960 | 582 make</CODE></P> |
| 1612 | 583 |
| 1682 | 584 <P>Then create /dev/mga_vid device:</P> |
| 1612 | 585 |
| 1682 | 586 <P><CODE> mknod /dev/mga_vid c 178 0</CODE></P> |
| 1612 | 587 |
| 1682 | 588 <P>and load the driver with</P> |
| 589 | |
| 590 <P><CODE> insmod mga_vid.o</CODE></P> | |
| 1612 | 591 |
| 1682 | 592 <P>You should verify the memory size detection using the 'dmesg' command. If |
| 6960 | 593 it's bad, use the mga_ram_size option (rmmod mga_vid first), specify card's |
| 594 memory size in MB:</P> | |
| 1612 | 595 |
| 1682 | 596 <P><CODE> insmod mga_vid.o mga_ram_size=16</CODE></P> |
| 1612 | 597 |
|
3664
f3a20477f042
added "copy mga_vid to /lib/modules" to install instructions
gabucino
parents:
3583
diff
changeset
|
598 <P>To make it load/unload automatically when needed, first insert the following line |
| 6960 | 599 at the end of /etc/modules.conf:</P> |
| 1612 | 600 |
| 1682 | 601 <P><CODE> alias char-major-178 mga_vid</CODE></P> |
| 1612 | 602 |
|
3664
f3a20477f042
added "copy mga_vid to /lib/modules" to install instructions
gabucino
parents:
3583
diff
changeset
|
603 <P>Then copy the <CODE>mga_vid.o</CODE> module to the appropriate place under |
|
f3a20477f042
added "copy mga_vid to /lib/modules" to install instructions
gabucino
parents:
3583
diff
changeset
|
604 <CODE>/lib/modules/<kernel version>/somewhere</CODE>.</P> |
|
f3a20477f042
added "copy mga_vid to /lib/modules" to install instructions
gabucino
parents:
3583
diff
changeset
|
605 |
| 1682 | 606 <P>Then run</P> |
| 1612 | 607 |
| 1682 | 608 <P><CODE> depmod -a</CODE></P> |
| 1612 | 609 |
| 1682 | 610 <P>Now you have to (re)compile <B>MPlayer</B>, ./configure will detect /dev/mga_vid |
| 6960 | 611 and build the 'mga' driver. Using it from <B>MPlayer</B> goes by '-vo mga' if |
| 612 you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.</P> | |
| 1682 | 613 |
| 2108 | 614 <P>The mga_vid driver cooperates with Xv.</P> |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
615 |
| 4504 | 616 <P>The <CODE>/dev/mga_vid</CODE> device file can be read (for example by |
| 617 <CODE>cat /dev/mga_vid</CODE>) for some info, and written for brightness | |
| 6960 | 618 change: <CODE>echo "brightness=120" > /dev/mga_vid</CODE></P> |
| 4504 | 619 |
| 1612 | 620 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
621 <P><B><A NAME="sis_vid">2.3.1.8 SiS 6326 framebuffer (sis_vid)</A></B></P> |
| 1682 | 622 |
| 623 <P>SiS 6326 YUV Framebuffer driver -> sis_vid kernel driver</P> | |
| 1612 | 624 |
| 1682 | 625 <P>Its interface should be compatible with the mga_vid, but the driver was not |
| 6960 | 626 updated after the mga_vid changes, so it's outdated now. Volunteers |
| 627 needed to test it and bring the code up-to-date.</P> | |
| 1612 | 628 |
| 6974 | 629 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
630 <P><B><A NAME="tdfxfb">2.3.1.9 3dfx YUV support (tdfxfb)</A></B></P> |
| 1612 | 631 |
| 1992 | 632 <P>This driver uses the kernel's tdfx framebuffer driver to play movies with |
| 6960 | 633 YUV acceleration. You'll need a kernel with tdfxfb support, and recompile |
| 634 with <CODE>./configure --enable-tdfxfb</CODE></P> | |
| 1612 | 635 |
| 6974 | 636 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
637 <P><B><A NAME="opengl">2.3.1.10 OpenGL output</A></B></P> |
| 1612 | 638 |
| 6309 | 639 <P><B>MPlayer</B> supports displaying movies using OpenGL, but if your |
| 6960 | 640 platform/driver supports xv as should be the case on a PC with Linux, use xv |
| 641 instead, OpenGL performance is considerably worse. If you have an X11 | |
| 642 implementation without xv support, OpenGL is a viable alternative.</P> | |
| 6309 | 643 |
| 644 <P>Unfortunately not all drivers support this feature. The Utah-GLX drivers | |
| 6960 | 645 (for XFree86 3.3.6) support it for all cards. See |
| 646 <A HREF="http://utah-glx.sourceforge.net">http://utah-glx.sourceforge.net</A> | |
| 647 for details about how to install it.</P> | |
| 1612 | 648 |
| 6309 | 649 <P>XFree86(DRI) >= 4.0.3 supports OpenGL with Matrox and Radeon cards, >= 4.2 |
| 6960 | 650 supports Rage128. See |
| 651 <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> | |
| 652 for download and installation instructions.</P> | |
| 1612 | 653 |
| 6974 | 654 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
655 <P><B><A NAME="aalib">2.3.1.11 AAlib - text mode displaying</A></B></P> |
| 1612 | 656 |
| 1682 | 657 <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful |
| 6960 | 658 ASCII renderer. There are LOTS of programs already supporting it, like Doom, |
| 659 Quake, etc. <B>MPlayer</B> contains a very usable driver for it. | |
| 660 If ./configure detects aalib installed, the aalib libvo driver will be | |
| 661 built.</P> | |
| 1612 | 662 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
663 <TABLE BORDER=0> |
| 6974 | 664 <TR><TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD></TR> |
| 665 <TR><TD> </TD><TD><CODE>1</CODE></TD><TD> </TD><TD>decrease contrast</TD></TR> | |
| 666 <TR><TD></TD><TD><CODE>2</CODE></TD><TD></TD><TD>increase contrast</TD></TR> | |
| 667 <TR><TD></TD><TD><CODE>3</CODE></TD><TD></TD><TD>decrease brightness</TD></TR> | |
| 668 <TR><TD></TD><TD><CODE>4</CODE></TD><TD></TD><TD>increase brightness</TD></TR> | |
| 669 <TR><TD></TD><TD><CODE>5</CODE></TD><TD></TD><TD>switch fast rendering on/off</TD></TR> | |
| 670 <TR><TD></TD><TD><CODE>6</CODE></TD><TD></TD><TD>set dithering mode (none, error distribution, Floyd Steinberg)</TD></TR> | |
| 671 <TR><TD></TD><TD><CODE>7</CODE></TD><TD></TD><TD>invert image</TD></TR> | |
| 672 <TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and <B>MPlayer</B> control)</TD></TR> | |
| 1612 | 673 |
| 6974 | 674 <TR><TD COLSPAN=4><P><B>The following command line options can be used:</B></P></TD></TR> |
| 675 <TR><TD></TD><TD><CODE>-aaosdcolor=V</CODE></TD><TD></TD><TD>change OSD color</TD></TR> | |
| 676 <TR><TD></TD><TD><CODE>-aasubcolor=V</CODE></TD><TD></TD><TD>change subtitle color</TD></TR> | |
| 677 <TR><TD COLSPAN=3></TD><TD><P><I>where V can be: (0/normal, 1/dark, 2/bold, | |
| 678 3/bold font, 4/reverse, 5/special)</I></P></TD></TR> | |
| 679 <TR><TD COLSPAN=4><P><B>AAlib itself provides a large sum of options. | |
| 680 Here are some important:</B></P></TD></TR> | |
| 681 <TR><TD></TD><TD><CODE>-aadriver</CODE></TD><TD></TD><TD>set recommended aa driver (X11, curses, Linux)</TD></TR> | |
| 682 <TR><TD></TD><TD><CODE>-aaextended</CODE></TD><TD></TD><TD>use all 256 characters</TD></TR> | |
| 683 <TR><TD></TD><TD><CODE>-aaeight</CODE></TD><TD></TD><TD>use eight bit ASCII</TD></TR> | |
| 684 <TR><TD></TD><TD><CODE>-aahelp</CODE></TD><TD></TD><TD>prints out all aalib options</TD></TR> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
685 </TABLE> |
| 1682 | 686 |
| 687 <P>NOTE: the rendering is very CPU intensive, especially when using AA-on-X | |
| 6960 | 688 (using aalib on X), and it's least CPU intensive on standard, |
| 689 non-framebuffer console. Use SVGATextMode to set up a big textmode, | |
| 690 then enjoy! (secondary head Hercules cards rock :)) (anyone can enhance | |
| 691 fbdev to do conversion/dithering to hgafb? Would be neat :)</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
692 |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
693 <P>Use the <CODE>-framedrop</CODE> option if your computer isn't fast enough to |
| 6960 | 694 render all frames!</P> |
| 1612 | 695 |
| 6960 | 696 <P>Playing on terminal you'll get better speed and quality using the Linux |
| 697 driver, not curses (-aadriver linux). But therefore you need write access on | |
| 698 /dev/vcsa<terminal>! That isn't autodetected by aalib, but vo_aa tries | |
| 699 to find the best mode. See | |
| 700 <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> | |
| 701 for further tuning issues.</P> | |
| 1612 | 702 |
| 2471 | 703 |
| 6960 | 704 <P><B><A NAME="vesa">2.3.1.12. VESA - output to VESA BIOS</A></B></P> |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
705 |
| 6960 | 706 <P>This driver was designed and introduced as a <B>generic driver</B> for any |
| 707 video card which has VESA VBE 2.0 compatible BIOS. Another advantage of this | |
| 708 driver is that it tries to force TV output on.<BR> | |
| 709 <B>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998</B> (Page | |
| 710 70) says:</P> | |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
711 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
712 <BLOCKQUOTE> |
| 6974 | 713 <B>Dual-Controller Designs</B><BR> |
| 6960 | 714 VBE 3.0 supports the dual-controller design by assuming that since both |
| 715 controllers are typically provided by the same OEM, under control of a | |
| 716 single BIOS ROM on the same graphics card, it is possible to hide the fact | |
| 717 that two controllers are indeed present from the application. This has the | |
| 718 limitation of preventing simultaneous use of the independent controllers, | |
| 719 but allows applications released before VBE 3.0 to operate normally. The | |
| 720 VBE Function 00h (Return Controller Information) returns the combined | |
| 721 information of both controllers, including the combined list of available | |
| 722 modes. When the application selects a mode, the appropriate controller is | |
| 723 activated. Each of the remaining VBE functions then operates on the active | |
| 724 controller. | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
725 </BLOCKQUOTE> |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
726 |
| 6960 | 727 <P>So you have chances to get working TV-out by using this driver.<BR> |
| 728 (I guess that TV-out frequently is standalone head or standalone output | |
| 729 at least.)</P> | |
| 730 | |
| 731 <P><B>What are pluses:</B><BR> | |
| 732 - You have chances to watch movies <B>if Linux even doesn't know</B> your | |
| 733 video hardware.<BR> | |
| 734 - You don't need to have installed any graphics' related things on your Linux | |
| 735 (like X11 (aka XFree86), fbdev and so on). This driver can be run from | |
| 736 <B>text-mode</B>.<BR> | |
| 737 - You have chances to get <B>working TV-out</B>. (It's known at least for | |
| 738 ATI's cards).<BR> | |
| 739 - This driver calls <B>int 10h</B> handler thus it's not an emulator - it | |
| 740 calls <B>real</B> things of <B>real</B> BIOS in <B>real</B>-mode. (Finely - | |
| 741 in vm86 mode).<BR> | |
| 742 - You can use Vidix with it, thus getting accelerated video display | |
| 6974 | 743 <B>AND</B> TV output at the same time! (recommended for ATI cards)</P> |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
744 |
| 6960 | 745 <P><B>What are minuses:</B><BR> |
| 746 - It works only on <B>x86 systems</B>.<BR> | |
| 747 - It can be used only by <B>ROOT</B>.<BR> | |
| 6974 | 748 - Currently it's available only for <B>Linux</B>.</P> |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
749 |
| 6960 | 750 <P>Don't use this driver with <B>GCC 2.96</B>! It won't work!</P> |
| 3141 | 751 |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
752 <TABLE BORDER=0> |
| 6974 | 753 <TR><TD COLSPAN=4><P><B>These switches of command line currently are available for VESA:</B></P></TD></TR> |
| 754 <TR><TD> </TD><TD VALIGN="top"><CODE>-vo vesa:opts</CODE></TD><TD></TD> | |
| 755 <TD>currently recognized: <B>dga</B> to force dga mode and <B>nodga</B> to | |
| 756 disable dga mode. Note: you may omit these parameters to enable <B>autodetect</B> | |
| 757 of dga mode. (In the future also will specify mode parameters such as refresh | |
| 758 rate, interlacing, doublescan and so on. Samples: i43, 85, d100)</TD></TR> | |
| 759 <TR><TD></TD><TD VALIGN="top"><CODE>-screenw, -screenh, -bpp</CODE></TD><TD></TD><TD>force userdefined mode</TD></TR> | |
| 760 <TR><TD></TD><TD VALIGN="top"><CODE>-x, -y</CODE></TD><TD></TD><TD>set userdefined prescaling</TD></TR> | |
| 761 <TR><TD></TD><TD VALIGN="top"><CODE>-zoom</CODE></TD><TD></TD><TD>enables userdefined prescaling</TD></TR> | |
| 762 <TR><TD></TD><TD VALIGN="top"><CODE>-fs</CODE></TD><TD></TD><TD>scales image to fullscreen</TD></TR> | |
| 763 <TR><TD></TD><TD VALIGN="top"><CODE>-fs -zoom</CODE></TD><TD></TD><TD>scales userdefined prescaling to fullscreen</TD></TR> | |
| 764 <TR><TD></TD><TD VALIGN="top"><CODE>-double</CODE></TD><TD></TD><TD>enables | |
| 765 double buffering mode. (Available only in DGA mode). Should be slower of | |
| 766 single buffering, but has no flickering effects.</TD></TR> | |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
767 </TABLE> |
|
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
768 |
| 6960 | 769 <P><B>Known problems and workaround:</B><BR> |
| 770 - If you have installed <B>NLS</B> font on your Linux box and run VESA driver | |
| 771 from text-mode then after terminating <B>MPlayer</B> you will have <B>ROM | |
| 772 font</B> loaded instead of national. You can load national font again by | |
| 773 using <B><I>setsysfont</I></B> utility from for example Mandrake | |
| 774 distribution.<BR> | |
| 775 (<B>Hint</B>: The same utility is used for localization of fbdev).<BR> | |
| 776 - Some <B>Linux graphics drivers</B> don't update active <B>BIOS mode</B> in | |
| 777 DOS memory. So if you have such problem - always use VESA driver only from | |
| 778 <B>text-mode</B>. Otherwise text-mode (#03) will be activated anyway and | |
| 779 you will need restart your computer.<BR> | |
| 780 - Often after terminating VESA driver you get <B>black screen</B>. To return | |
| 781 your screen to original state - simply switch to other console (by pressing | |
| 782 <B>Alt-Fx</B>) then switch to your previous console by the same way.<BR> | |
| 783 - To get <B>working TV-out</B> you need have plugged TV-connector in before | |
| 784 booting your PC since video BIOS initializes itself only once during POST | |
| 6974 | 785 procedure.</P> |
|
2448
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
786 |
|
1e56c3381d55
'vesa' vo driver added. By Nick Kurshev. (spellchecked, fixed, mplayerdoxized)
gabucino
parents:
2408
diff
changeset
|
787 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
788 <P><B><A NAME="x11">2.3.1.13 X11</A></B></P> |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
789 |
|
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
790 <P>Avoid if possible. Outputs to X11 (uses shared memory extension), with no |
| 6960 | 791 hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but still |
| 792 slow) software scaling, use the options <CODE>-fs -zoom</CODE>. Most cards | |
| 793 have hardware scaling support, use the <CODE>-vo xv</CODE> output for them, | |
| 794 or <CODE>-vo xmga</CODE> for Matroxes.</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
795 |
| 6960 | 796 <P>The problem is that most cards' driver doesn't support hardware acceleration |
| 797 on the second head/TV. In those cases, you see green/blue colored window | |
| 798 instead of the movie. This is where this driver comes in handy, but you need | |
| 799 powerful CPU to use software scaling. Don't use the SDL driver's software | |
| 800 output+scaler, it has worse image quality!</P> | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
801 |
| 6960 | 802 <P>Software scaling is very slow, you better try changing video modes instead. |
| 803 It's very simple. See the <A HREF="#dga_modelines">DGA section's modelines</A>, | |
| 804 and insert them into your XF86Config.</P> | |
| 805 | |
| 3290 | 806 <UL> |
| 807 <LI>If you have XFree86 4.x.x - use the <CODE>-vm</CODE> option. It will | |
| 6960 | 808 change to a resolution your movie fits in. If it doesn't:</LI> |
| 3290 | 809 <LI>With XFree86 3.x.x - you have to cycle through available resolutions |
| 810 with the <B>CTRL-ALT-plus</B> and <B>minus</B> keys.</LI> | |
| 811 </UL> | |
| 812 | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
813 <P>If you can't find the modes you inserted, browse XFree86's output. Some |
| 6960 | 814 drivers can't use low pixelclocks that are needed for low resolution |
| 815 video modes.</P> | |
| 3290 | 816 |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
817 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
818 <P><B><A NAME="vidix">2.3.1.14 VIDIX</A></B></P> |
| 4199 | 819 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
820 <P><B>WHAT IS VIDIX?</B></P> |
| 4199 | 821 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
822 <P>VIDIX is the abbreviation for <B>VID</B>eo <B>I</B>nterface for |
|
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
823 *ni<B>X</B>.<BR> |
| 4199 | 824 VIDIX was designed and introduced as an interface for fast user-space drivers |
| 6583 | 825 providing such video performance as mga_vid does for Matrox cards. It's |
| 826 also very portable.</P> | |
| 4199 | 827 |
| 828 <P>This interface was designed as an attempt to fit existing video acceleration | |
| 6583 | 829 interfaces (known as mga_vid, rage128_vid, radeon_vid, pm3_vid) into a fixed scheme. It |
| 4199 | 830 provides highlevel interface to chips which are known as BES (BackEnd |
| 831 scalers) or OV (Video Overlays). It doesn't provide lowlevel interface to | |
| 832 things which are known as graphics servers. (I don't want to compete with X11 | |
| 833 team in graphics mode switching). I.e. main goal of this interface is to | |
| 6974 | 834 maximize the speed of video playback.</P> |
| 4199 | 835 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
836 <P><B>USAGE</B></P> |
| 4199 | 837 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
838 <UL> |
| 4199 | 839 <LI>You can use standalone video output driver: <CODE>-vo xvidix</CODE><BR> |
| 840 This driver was developed as X11's front end to VIDIX technology. It | |
| 6599 | 841 requires X server and can work only under X server.</LI> |
| 4199 | 842 <LI>You can use VIDIX subdevice which was applied to several video output |
| 843 drivers, such as:<BR> | |
| 6583 | 844 <CODE>-vo vesa:vidix</CODE> (<B>LINUX ONLY</B>) and <CODE>-vo fbdev:vidix</CODE></LI> |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
845 </UL> |
| 6974 | 846 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
847 Indeed it doesn't matter which video output driver is used with <B>VIDIX</B>. |
| 4199 | 848 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
849 <P><B>REQUIREMENTS</B></P> |
| 4199 | 850 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
851 <UL> |
|
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
852 <LI>video card should be in graphics mode (I write <B>should</B> simply |
| 4199 | 853 because I tested it in text mode - it works but has awful output ;) Use |
| 854 AAlib for that).<BR> | |
| 855 <I>Note: Everyone can try this trick by commenting out mode switching in | |
| 856 vo_vesa driver.</I></LI> | |
| 857 <LI><B>MPlayer</B>'s video output driver should know active video mode and be | |
| 858 able to tell to VIDIX subdevice some video characteristics of server.</LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
859 </UL> |
| 6974 | 860 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
861 I hope that probably every video output driver of <B>MPlayer</B> will |
|
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
862 recognize <CODE>:vidix</CODE> subdevice. |
| 4199 | 863 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
864 <P><B>USAGE METHODS</B></P> |
| 4199 | 865 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
866 <P>When VIDIX is used as <B>subdevice</B> (<CODE>-vo vesa:vidix</CODE>) then |
| 4199 | 867 video mode configuration is performed by video output device |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
868 (<B>vo_server</B> in short). Therefore you can pass into command line of |
| 4199 | 869 <B>MPlayer</B> the same keys as for vo_server. In addition it understands |
| 870 <CODE>-double</CODE> key as globally visible parameter. (I recommend using | |
| 871 this key with VIDIX at least for ATI's card).<BR> | |
| 6960 | 872 As for <CODE>-vo xvidix</CODE>: currently it recognizes the following |
| 6974 | 873 options: <CODE>-fs -zoom -x -y -double</CODE>.</P> |
| 4199 | 874 |
| 875 <P>Also you can specify VIDIX's driver directly as third subargument in command | |
| 6960 | 876 line:<BR> |
| 4199 | 877 <BR> |
| 878 <code>mplayer -vo xvidix:mga_vid.so -fs -zoom -double | |
| 879 file.avi</code><BR> | |
| 880 or<BR> | |
| 881 <code>mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp | |
| 882 32 file.avi</code><BR> | |
| 883 <BR> | |
| 884 But it's dangerous, and you shouldn't do that. In this case given driver will | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
885 be forced and result is unpredictable (it may <B>freeze</B> your |
| 4339 | 886 computer). You should do that ONLY if you are absolutely sure it will work, |
| 887 and <B>MPlayer</B> doesn't do it automatically. Please tell about it to the | |
| 888 developers. The Right Way is to use VIDIX without arguments to enable driver | |
| 6974 | 889 autodetection.</P> |
| 4199 | 890 |
| 6974 | 891 <P>VIDIX is very new technology and it's extremely possible that on your system |
| 4199 | 892 (OS=abc CPU=xyz) it won't work. In this case only solution for you it's port |
| 893 it (mainly libdha). But there is hope that it will work on those systems | |
| 6974 | 894 where X11 does.</P> |
| 4199 | 895 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
896 <P>And the last <B>WARNING</B>: (un)fortunately you <B>MUST</B> have |
|
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
897 <B>ROOT</B> privileges to use VIDIX due to direct hardware access. At least |
| 6974 | 898 set the <B>SUID</B> bit on the <B>MPlayer</B> executable.</P> |
| 4199 | 899 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
900 <P><B>VIDEO EQUALIZER</B></P> |
| 4496 | 901 |
| 6974 | 902 <P>This is a video equalizer implemented especially for VIDIX. You can use |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
903 it either with <B>1-8</B> keys as described in the man page, or |
| 4506 | 904 by command line arguments. <B>MPlayer</B> recognizes the |
| 6974 | 905 following options:</P> |
| 4496 | 906 |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
907 <TABLE> |
| 6974 | 908 <TR><TD> </TD><TD VALIGN="top"><CODE>-brightness</CODE></TD><TD> </TD> |
| 909 <TD>Adjust <B>BRIGHTNESS</B> of video output. It's not equal to brightness | |
| 910 adjusting on monitor panel or on TV. It changes intensity of RGB components of | |
| 911 video signal from black to white screen.</TD></TR> | |
| 912 <TR><TD></TD><TD VALIGN="top"><CODE>-contrast</CODE></TD><TD></TD> | |
| 913 <TD>Adjust <B>CONTRAST</B> of video output. Works in similar manner as | |
| 914 brightness.</TD></TR> | |
| 915 <TR><TD></TD><TD VALIGN="top"><CODE>-saturation</CODE></TD> | |
| 916 <TD></TD><TD>Adjust <B>SATURATION</B> of video output. You can get grayscale | |
| 917 output with this option.</TD></TR> | |
| 918 <TR><TD></TD><TD VALIGN="top"><CODE>-hue</CODE></TD> | |
| 919 <TD></TD><TD>Adjust <B>HUE</B> of video signal. You can get colored negative | |
| 920 of image with this option.</TD></TR> | |
| 921 <TR><TD></TD><TD VALIGN="top"><CODE>-red_intensity</CODE></TD> | |
| 922 <TD></TD><TD>Adjust intensity of <B>RED</B> component of video signal.</TD></TR> | |
| 923 <TR><TD></TD><TD VALIGN="top"><CODE>-green_intensity</CODE></TD> | |
| 924 <TD></TD><TD>Adjust intensity of <B>GREEN</B> component of video signal.</TD></TR> | |
| 925 <TR><TD></TD><TD VALIGN="top"><CODE>-blue_intensity</CODE></TD> | |
| 926 <TD></TD><TD>Adjust intensity of <B>BLUE</B> component of video signal.</TD></TR> | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
927 </TABLE> |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
928 |
| 6974 | 929 <P>Each parameter can accept values from <B>-1000</B> to <B>+1000</B>.<BR> |
| 930 Default value for each parameter is <B>0</B>.</P> | |
| 931 | |
| 932 <P><B>Note:</B> Not every driver provides support for each of those parameters. | |
| 6599 | 933 Currently only <B>radeon_vid.so</B> provides full support for video equalizing. |
| 6974 | 934 Other drivers only partly support these options.</P> |
| 935 | |
| 4496 | 936 <P><B>Examples:</B><BR> |
| 937 <CODE>mplayer -vo vesa:vidix -brightness -300 -contrast 200 | |
| 938 filename.avi</CODE><BR> | |
| 939 or<BR> | |
| 940 <CODE>mplayer -vo xvidix -red_intensity -50 -saturation 400 -hue 300 | |
| 6974 | 941 filename.vob</CODE></P> |
| 4496 | 942 |
|
2956
f6b51da0a50d
DOXized and applied Nick's radeon_vid patch. Nick, should I update
gabucino
parents:
2883
diff
changeset
|
943 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
944 <P><B><A NAME="zr">2.3.1.15 Zr</A></B></P> |
| 4339 | 945 |
| 946 <P>This is a display-driver (<CODE>-vo zr</CODE>) for a number of MJPEG | |
| 6960 | 947 capture/playback cards (tested for DC10+ and Buz, and it should work for the |
| 948 LML33, the DC10). The driver works by encoding the frame to jpeg and then | |
| 949 sending it to the card. For the jpeg encoding <B>libavcodec</B> is | |
| 950 used, and required.</P> | |
| 4339 | 951 |
| 952 <P>This driver talks to the kernel driver available at | |
| 6960 | 953 <A HREF="http://mjpeg.sourceforge.net">http://mjpeg.sourceforge.net</A>, so |
| 954 you must get it working first. Then recompile <B>MPlayer</B> with | |
| 955 <CODE>--enable-zr</CODE>.</P> | |
| 4339 | 956 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
957 Some remarks: |
| 4339 | 958 <UL> |
| 4360 | 959 <LI>don't start or stop XawTV on the playback device during playback, |
| 960 it will crash your computer. It is, however, fine to <B>FIRST</B> start | |
| 961 XawTV, <B>THEN</B> start <B>MPlayer</B>, wait for <B>MPlayer</B> to finish | |
| 962 and <B>THEN</B> stop XawTV.</LI> | |
| 6599 | 963 <LI>this driver adds <CODE>-zr*</CODE> command line options. The explanation |
| 4339 | 964 of these options can be viewed with <CODE>-zrhelp</CODE>. It is possible to |
| 6599 | 965 crop the input frame (cut borders to make it fit or to enhance performance) |
| 4339 | 966 and to do other things.</LI> |
| 4360 | 967 <LI>the driver takes data in YV12 and YUY2 format, this means that some |
| 968 codecs won't work. Some old VfW (Video for Windows) codecs, for example, | |
| 6599 | 969 are incompatible with this driver. The error message that you will see is: |
| 4360 | 970 <CODE>Sorry, selected video_out device is incompatible with this codec. |
| 971 </CODE></LI> | |
| 972 <LI>OSD is currently not supported, so you won't see | |
| 973 subtitles.</LI> | |
| 4339 | 974 </UL> |
| 975 | |
| 976 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
977 <P><B><A NAME="dvb">2.3.1.16 DVB</A></B></P> |
| 6729 | 978 |
| 979 <P><B>MPlayer</B> supports cards with the Siemens DVB chipset from vendors like | |
| 6960 | 980 Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB drivers are |
| 981 available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you | |
| 982 want to do software transcoding you should have at least a 1GHz CPU.</P> | |
| 6729 | 983 |
| 984 <P>Configure should detect your DVB card. If it did not, force detection with | |
| 985 | |
| 986 <PRE> | |
| 987 ./configure --enable-dvb | |
| 988 </PRE> | |
| 989 | |
| 990 <P>If you have ost headers at a non-standard path, set the path with</P> | |
| 991 | |
| 992 <PRE> | |
| 993 ./configure --with-extraincdir=<DVB source directory>/ost/include | |
| 994 </PRE> | |
| 995 | |
| 996 <P>Then compile and install as usual.</P> | |
| 997 | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
998 <P><B>USAGE</B></P> |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
999 |
| 6729 | 1000 <P>Hardware decoding (playing standard MPEG1/2 files) can be done with this |
| 6960 | 1001 command:</P> |
| 6729 | 1002 |
| 1003 <PRE> | |
| 1004 mplayer -ao mpegpes -vo mpegpes file.mpg|vob | |
| 1005 </PRE> | |
| 1006 | |
| 1007 <P>Software decoding or transcoding different formats to MPEG1 can be achieved | |
| 6960 | 1008 using a command like this:</P> |
| 6729 | 1009 |
| 1010 <PRE> | |
| 1011 mplayer -ao mpegpes -vo mpegpes -vop lavc yourfile.ext | |
| 1012 mplayer -ao mpegpes -vo mpegpes -vop fame,expand yourfile.ext | |
| 1013 </PRE> | |
| 1014 | |
| 1015 <P>Note that DVB cards only support heights 288 and 576 for PAL or 240 and 480 | |
| 6960 | 1016 for NTSC. You <B>must</B> rescale for other heights by adding |
| 1017 <CODE>scale=width:height</CODE> with the width and height you want to the | |
| 1018 <CODE>-vop</CODE> option. DVB cards accept various widths, like 720, 704, | |
| 1019 640, 512, 480, 352 etc and do hardware scaling in horizontal direction, so | |
| 1020 you do not need to scale horizontally in most cases. For a 512x384 (aspect | |
| 1021 4:3) DivX try:</P> | |
| 6729 | 1022 |
| 1023 <PRE> | |
| 1024 mplayer -ao mpegpes -vo mpegpes -vop lavc,scale=512:576 | |
| 1025 </PRE> | |
| 1026 | |
| 1027 <P>If you have a widescreen movie and you do not want to scale it to full height, | |
| 6960 | 1028 you can use the <CODE>expand=w:h</CODE> plugin to add black bands. To view a |
| 1029 640x384 DivX, try:</P> | |
| 6729 | 1030 |
| 1031 <PRE> | |
| 1032 mplayer -ao mpegpes -vo mpegpes -vop lavc,expand=640:576 file.avi | |
| 1033 </PRE> | |
| 1034 | |
| 1035 <P>If your CPU is too slow for a full size 720x576 DivX, try downscaling:</P> | |
| 1036 | |
| 1037 <PRE> | |
| 1038 mplayer -ao mpegpes -vo mpegpes -vop lavc,scale=352:576 file.avi | |
| 1039 </PRE> | |
| 1040 | |
| 1041 <P>If speed does not improve, try vertical downscaling, too:</P> | |
| 1042 | |
| 1043 <PRE> | |
| 1044 mplayer -ao mpegpes -vo mpegpes -vop lavc,scale=352:288 file.avi | |
| 1045 </PRE> | |
| 1046 | |
| 1047 <P>For OSD and subtitles use the expand feature of the OSD plugin. So, instead | |
| 6960 | 1048 of <CODE>expand=w:h</CODE> or <CODE>expand=w:h:x:y</CODE>, use |
| 1049 <CODE>expand=w:h:x:y:1</CODE> (the 5th parameter <CODE>:1</CODE> at the end | |
| 1050 will enable OSD rendering). You may want to move the image up a bit to get a | |
| 1051 bigger black zone for subtitles. You may also want to move subtitles up, if | |
| 1052 they are outside your TV screen, use the <CODE>-subpos <0-100></CODE> switch | |
| 1053 to adjust this (<CODE>-subpos 80</CODE> is a good choice).</P> | |
| 6729 | 1054 |
| 1055 <P>In order to play non-25fps movies on a PAL TV or with a slow CPU, add the | |
| 6960 | 1056 <CODE>-framedrop</CODE> option.</P> |
| 6729 | 1057 |
| 1058 <P>To keep the aspect ratio of DivX files and get the optimal scaling parameters | |
| 6960 | 1059 (hardware horizontal scaling and software vertical scaling while keeping the |
| 1060 right aspect ratio), use the new dvbscale plugin:</P> | |
| 6729 | 1061 |
| 1062 <PRE> | |
| 1063 for 3:4 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale | |
| 1064 for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024 | |
| 1065 </PRE> | |
| 1066 | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1067 <P><B>FUTURE</B></P> |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1068 |
| 6729 | 1069 <P>If you have questions or want to hear feature announcements and take part in |
| 6960 | 1070 discussions on this subject, join our |
| 1071 <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</A> | |
| 1072 mailing list. Please remember that the list language is English.</P> | |
| 6729 | 1073 |
| 1074 <P>In the future you may expect the ability to display OSD and subtitles using | |
| 6960 | 1075 the native OSD feature of DVB cards, as well as more fluent playback of |
| 1076 non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial | |
| 1077 decompression).</P> | |
| 6729 | 1078 |
| 4496 | 1079 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
1080 <P><B><A NAME="dxr3">2.3.1.17 DXR3</A></B></P> |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1081 |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1082 <P><B>MPlayer</B> supports hardware accelerated playback with the Creative DXR3 |
| 6960 | 1083 and Sigma Designs Hollywood Plus cards.</P> |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1084 |
| 6960 | 1085 <P>First of all you will need properly installed DXR3/H+ drivers, version |
| 1086 0.12.0 or later. You can find the drivers and installation instructions at | |
| 1087 the <A HREF="http://dxr3.sourceforge.net/">DXR3 & Hollywood Plus for | |
| 1088 Linux</A> site. Configure should detect your card automatically, compilation | |
| 1089 should go without any problems.</P> | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1090 |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1091 <P><B>USAGE</B></P> |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1092 |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1093 <TABLE> |
| 6974 | 1094 <TR><TD> </TD><TD VALIGN="top"><CODE>-vo dxr3:<noprebuf>:<codec>:<device></CODE></TD><TD> </TD> |
| 1095 <TD>Where <CODE><noprebuf></CODE> specifies turning off prebuffering. | |
| 1096 This is done automatically on Athlons. If playback is out of sync try | |
| 1097 disabling prebuffering. If noprebuf is left out prebuffering is enabled | |
| 1098 (except on Athlons). | |
| 1099 <BR> | |
| 1100 <CODE><codec></CODE> = fame/avcodec, avcodec produces better quality | |
| 1101 output, but fame is faster for those of you with slow machines. The default is | |
| 1102 to use libavcodec. Note that you need libavcodec properly installed (read | |
| 1103 DOCS/codecs.html). | |
| 1104 <BR> | |
| 1105 <CODE><device></CODE> = device number to use if you have more than one | |
| 1106 em8300 card. | |
| 1107 <BR> | |
| 1108 Any of these options may be left out, but they must be specified in this | |
| 1109 order, i.e. <CODE>dxr3:fame</CODE> works, <CODE>dxr3:1</CODE> works, but | |
| 1110 <CODE>dxr3:1:avcodec</CODE> will not.</TD></TR> | |
| 1111 <TR><TD></TD><TD VALIGN="top"><CODE>-ao oss:/dev/em8300_ma-X</CODE></TD> | |
| 1112 <TD></TD><TD>For audio output, where <CODE>X</CODE> is the device number | |
| 1113 (0 if one card).</TD></TR> | |
| 1114 <TR><TD></TD><TD VALIGN="top"><CODE>-ac hwac3</CODE></TD> | |
| 1115 <TD></TD><TD>For digital instead of analog audio output.</TD></TR> | |
| 1116 <TR><TD></TD><TD VALIGN="top"><CODE>-vc mpegpes</CODE></TD> | |
| 1117 <TD></TD><TD>Force hardware acceleration, only works with MPEG1/2.</TD></TR> | |
| 1118 <TR><TD></TD><TD VALIGN="top"><CODE>-aop list=resample:fout=xxxxx</CODE></TD> | |
| 1119 <TD></TD><TD>If sample rate is below 44100Hz, select either 44100Hz or 48000Hz | |
| 1120 depending on which one matches closest. I.e. if the movie uses 22050Hz use | |
| 1121 44100Hz as 44100 / 2 = 22050, if it is 24000Hz use 48000Hz as 48000 / 2 = 24000 | |
| 1122 and so on. This does not work with digital audio output | |
| 1123 (<CODE>-ac hwac3</CODE>).</TD></TR> | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1124 </TABLE> |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1125 |
| 6981 | 1126 <P><B>Overlay</B></P> |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1127 |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1128 <P>To get overlay run dxr3view that comes with the em8300 package before |
| 6960 | 1129 starting <B>MPlayer</B>. You can set various options in dxr3view by pressing |
| 1130 <CODE>T</CODE> while holding the mouse cursor above the window.</P> | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1131 |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1132 <P><B>MPEG1, MPEG2, VCD and DVD Notes</B></P> |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1133 |
| 6960 | 1134 <P>MPEG1/2 content should now automatically be detected by <B>MPlayer</B> and |
| 1135 it will use the hardware acceleration of the DXR3 to play it. If not, you can | |
| 1136 force it to hardware acceleration with <CODE>-vc mpegpes</CODE>. Also, if you | |
| 1137 plan to use any postprocessing filters you must use <CODE>-vc | |
| 1138 mpeg12</CODE>.</P> | |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1139 |
| 6960 | 1140 <P>In some instances, subtitles may not appear properly in sync with the A/V |
| 1141 stream when using hardware decoding (<CODE>-vc mpegpes</CODE>). This is a | |
| 1142 known bug. The em8300 will also improperly handle subtitles that are too big, | |
| 1143 and may hang for a second or two. At this time, the only workaround is to use | |
| 6981 | 1144 <CODE>-vc mpeg12</CODE> when viewing DVDs with subtitles.</P> |
|
6732
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1145 |
|
8460a77203de
DXR3 moved to video.html. TOC updated, added <CODE> where appropiate.
diego
parents:
6729
diff
changeset
|
1146 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
1147 <P><B><A NAME="tv-out">2.3.1.A TV-out support</A></B></P> |
| 1612 | 1148 |
| 6974 | 1149 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
1150 <P><B><A NAME="tv-out_matrox">2.3.1.A.1 Matrox G400 cards</A></B></P> |
| 1612 | 1151 |
| 6960 | 1152 <P>Under Linux you have 2 methods to get G400 TV out working:</P> |
| 5116 | 1153 |
| 1154 <P><B>IMPORTANT:</B> Only Matrox G400DH/G400MAX has TV-out support under Linux, others (G450, G550) has <B>NOT!</B></P> | |
| 2309 | 1155 |
| 2486 | 1156 <UL> |
| 1157 <LI><B>XFree86</B>: using the driver and the HAL module, available from | |
| 1158 <A HREF="http://www.matrox.com">Matrox's site</A>. This will give you X on | |
| 1159 the TV.<BR> <B>This method doesn't give you accelerated playback</B> as | |
| 1160 under Windoze! The second head has only YUV framebuffer, the <I>BES</I> | |
| 1161 (Back End Scaler, the YUV scaler on G200/G400/G450/G550 cards) doesn't work | |
| 1162 on it! The windows driver somehow workarounds this, probably by using the | |
| 1163 3D engine to zoom, and the YUV framebuffer to display the zoomed | |
|
2848
33c32f3d9f1f
many small updates, fixes (some/more to be completed soon)
gabucino
parents:
2747
diff
changeset
|
1164 image. If you really want to use X, use the <CODE>-vo x11 -fs -zoom</CODE> |
| 6599 | 1165 options, but it will be <B>SLOW</B>, and has <B>Macrovision</B> copy protection |
| 4177 | 1166 enabled (you can "workaround" Macrovision using |
| 1167 <A HREF="http://avifile.sourceforge.net/mgamacro.pl">this</A> perl | |
| 1168 script.</LI> | |
| 2486 | 1169 <LI><B>Framebuffer</B>: using the <B>matroxfb modules</B> in the 2.4 kernels. |
| 1170 2.2 kernels don't have the TVout feature in them, thus unusable for this. | |
| 3030 | 1171 You have to enable ALL matroxfb-specific feature during compilation (except |
| 5713 | 1172 MultiHead), and compile them into <B>modules</B>! You'll also need I2C |
| 1173 enabled. | |
| 2486 | 1174 <UL> |
| 1175 <LI> | |
| 1176 Enter <CODE>TVout/matroxset</CODE> and type <CODE>make</CODE>. Install | |
| 1177 <CODE>matroxset</CODE> into somewhere in your PATH.</LI> | |
| 1178 <LI> | |
| 1179 If you don't have <CODE>fbset</CODE> installed, enter | |
| 1180 <CODE>TVout/fbset</CODE> and type <CODE>make</CODE>. Install | |
| 1181 <CODE>fbset</CODE> into somewhere in your PATH.</LI> | |
| 1182 <LI> | |
| 1183 Then enter into the <CODE>TVout/</CODE> directory in the <B>MPlayer</B> | |
| 1184 source, and execute <CODE>./modules</CODE> as root. Your text-mode console | |
| 1185 will enter into framebuffer mode (no way back!).</LI> | |
| 1186 <LI>Next, run the <CODE>./matroxtv</CODE> script. This will present you | |
| 1187 to a very simple menu. Press <B>2</B> and <B>ENTER</B>. Now you should | |
| 1188 have the same picture on your monitor, and TV. The <B>3.</B> option | |
| 1189 will turn on independent display, but then you <B>can't use X</B>! If | |
| 6960 | 1190 the TV (PAL!) picture has some weird stripes on it, the script wasn't able to |
| 2486 | 1191 set the resolution correctly (to 640x512 by default). Use other menu |
| 1192 items randomly and it'll be OK :)</LI> | |
| 1193 </UL> | |
| 1194 | |
| 6974 | 1195 <P>Yoh. Next task is to make the cursor on tty1 (or whatever) to disappear, |
| 2486 | 1196 and turn off screen blanking. Execute the following commands:</P> |
| 1197 | |
| 6974 | 1198 <P><CODE>echo -e '\033[?25l'</CODE> or <CODE>setterm -cursor off<BR> |
| 1199 setterm -blank 0</CODE></P> | |
| 2486 | 1200 |
| 6974 | 1201 <P>You possibly want to put the above into a script, and also clear |
| 6960 | 1202 the screen.. To turn the cursor back:<BR><CODE>echo -e '\033[?25h'</CODE> |
| 6974 | 1203 or <CODE>setterm -cursor on</CODE></P> |
| 2486 | 1204 |
| 1205 <P>Yeah kewl. Start movie playing with <CODE>mplayer -vo mga -fs -screenw 640 | |
| 1206 -screenh 512 <filename></CODE><BR> | |
| 6960 | 1207 (if you use X, now change to matroxfb with for example CTRL-ALT-F1!)<BR> |
| 2486 | 1208 Change 640x512 if you set the resolution to other..<BR> |
| 6974 | 1209 <B>Enjoy the ultra-fast ultra-featured Matrox TV output (better than Xv)!</B></P> |
| 2486 | 1210 </LI> |
| 1211 </UL> | |
| 2309 | 1212 |
| 1213 | |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
1214 <P><B><A NAME="tv-out_ati">2.3.1.A.2 ATI cards</A></B></P> |
| 2206 | 1215 |
| 6974 | 1216 <P><B><U>PREAMBLE</U></B><BR> |
| 6960 | 1217 Currently ATI doesn't want to support any of its TV-out chips under Linux, |
| 1218 because of their licensed Macrovision technology.</P> | |
| 6583 | 1219 |
| 1220 <P><B><U>ATI CARDS TV-OUT STATUS ON LINUX</U></B></P> | |
| 2206 | 1221 |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
1222 <UL> |
| 6960 | 1223 <LI><B>ATI Mach64</B>: supported by |
| 1224 <A HREF="http://gatos.sf.net">gatos</A>.</LI> | |
| 1225 <LI><B>ASIC Radeon VIVO</B>: supported by | |
| 1226 <A HREF="http://gatos.sf.net">gatos</A>.</LI> | |
| 1227 <LI><B>Radeon</B> and <B>Rage128</B>: supported by <B>MPlayer</B>! | |
| 1228 Check <a href="#vesa">VESA driver</a> and <A HREF="#2.3.1.15">Vidix</A> | |
| 1229 sections.</LI> | |
|
6435
d0d74f9d8d4a
Background now set by CSS, added doctype and charset.
diego
parents:
6393
diff
changeset
|
1230 </UL> |
| 2206 | 1231 |
| 6974 | 1232 <P>On other cards, just use the <a href="#vesa">VESA driver</a>, without |
| 1233 VIDIX. Powerful CPU is needed, though.</P> | |
| 2206 | 1234 |
| 6583 | 1235 <P>Only thing you need to do - <B>have TV connector plugged in before |
| 1236 booting your PC</B> since video BIOS initializes itself only once during | |
| 6974 | 1237 POST procedure.</P> |
| 2206 | 1238 |
|
2472
487f5bbb38ae
link to tomi ollila's voodoo3 tvout text. if he has interest to integrate
gabucino
parents:
2471
diff
changeset
|
1239 |
|
6906
3274d0725fde
Changed all link names from the section number to a sensible label.
diego
parents:
6882
diff
changeset
|
1240 <P><B><A NAME="tv-out_voodoo">2.3.1.A.3 Voodoo 3</A></B></P> |
|
2472
487f5bbb38ae
link to tomi ollila's voodoo3 tvout text. if he has interest to integrate
gabucino
parents:
2471
diff
changeset
|
1241 |
| 6974 | 1242 <P>Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>.</P> |
|
2472
487f5bbb38ae
link to tomi ollila's voodoo3 tvout text. if he has interest to integrate
gabucino
parents:
2471
diff
changeset
|
1243 |
| 1612 | 1244 </BODY> |
| 1245 </HTML> |