|
1612
|
1 <HTML>
|
|
1704
|
2 <BODY BGCOLOR=white>
|
|
|
3
|
|
|
4 <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>
|
|
1612
|
5
|
|
1682
|
6 <P><B><A NAME=2.2.1>2.2.1. Video output devices</A></B></P>
|
|
1612
|
7
|
|
1682
|
8 <TABLE BORDER=0>
|
|
|
9
|
|
|
10 <TD COLSPAN=4><P><B>General:</B></P></TD><TR>
|
|
1612
|
11
|
|
1682
|
12 <TD> </TD><TD VALIGN=top>x11</TD><TD> </TD><TD>X11 with optional SHM extension</TD><TR>
|
|
|
13 <TD></TD><TD VALIGN=top>xv</TD><TD></TD><TD>X11 using overlays with the Xvideo extension (hardware YUV & scaling)</TD><TR>
|
|
|
14 <TD></TD><TD VALIGN=top>gl</TD><TD></TD><TD>OpenGL renderer, so far works only with:
|
|
|
15 <UL><LI>all cards with Utah-GLX
|
|
|
16 <LI>Matrox cards with X/DRI >=4.0.3
|
|
|
17 <LI>Radeon with X/DRI CVS</UL></TD><TR>
|
|
|
18 <TD></TD><TD VALIGN=top>dga</TD><TD></TD><TD>X11 DGA extension</TD><TR>
|
|
|
19 <TD></TD><TD VALIGN=top>fbdev</TD><TD></TD><TD>Output to general framebuffers</TD><TR>
|
|
|
20 <TD></TD><TD VALIGN=top>svga</TD><TD></TD><TD>Output to SVGAlib</TD><TR>
|
|
|
21 <TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD>
|
|
|
22 <CODE>1.1.7:</CODE> supports software scaling<BR>
|
|
|
23 <CODE>1.1.8:</CODE> supports Xvideo (hardware scaling/fullscreen)<BR>
|
|
|
24 <CODE>1.2.0:</CODE> supports AAlib (-vo aa is very recommended, see below!)</TD><TR>
|
|
|
25 <TD></TD><TD VALIGN=top>ggi</TD><TD></TD><TD>similar to SDL</TD><TR>
|
|
|
26 <TD></TD><TD VALIGN=top>aa</TD><TD></TD><TD>textmode rendering with AAlib</TD><TR>
|
|
|
27
|
|
|
28 <TD COLSPAN=4><P><B>Card specific:</B></P></TD><TR>
|
|
1612
|
29
|
|
1682
|
30 <TD> </TD><TD VALIGN=top>mga</TD><TD> </TD><TD>Matrox G200/G400 hardware YUV overlay via the mga_vid device</TD><TR>
|
|
|
31 <TD></TD><TD VALIGN=top>xmga</TD><TD></TD><TD>Matrox G200/G400 overlay (mga_vid) in X11 window<BR>
|
|
|
32 (<I>Xv emulation on X 3.3.x!</I>)</TD><TR>
|
|
|
33 <TD></TD><TD VALIGN=top>syncfb</TD><TD></TD><TD>Matrox G400 YUV support on framebuffer (obsoleted, use mga/xmga)</TD><TR>
|
|
|
34 <TD></TD><TD VALIGN=top>3dfx</TD><TD></TD><TD>Voodoo2/3 hardware YUV (/dev/3dfx) support (not yet tested, maybe
|
|
|
35 broken)</TD><TR>
|
|
|
36
|
|
|
37 <TD COLSPAN=4><P><B>Special:</B></P></TD><TR>
|
|
1612
|
38
|
|
1682
|
39 <TD> </TD><TD VALIGN=top>png</TD><TD> </TD><TD>PNG files output (use -z switch to set compression)</TD><TR>
|
|
|
40 <TD></TD><TD VALIGN=top>pgm</TD><TD></TD><TD>PGM files output (for testing purposes or ffmpeg encoding)</TD><TR>
|
|
|
41 <TD></TD><TD VALIGN=top>md5</TD><TD></TD><TD>MD5sum output (for MPEG conformance tests)</TD><TR>
|
|
|
42 <TD></TD><TD VALIGN=top>odivx</TD><TD></TD><TD>OpenDivX AVI File writer (use -br to set encoding bitrate)</TD><TR>
|
|
|
43 <TD></TD><TD VALIGN=top>null</TD><TD></TD><TD>Null output (for speed tests/benchmarking)</TD><TR>
|
|
|
44 </TABLE>
|
|
1612
|
45
|
|
1682
|
46 <P>NOTE: <I>check the following subsections for details and requirements!</I></P>
|
|
1612
|
47
|
|
|
48
|
|
1682
|
49 <P><B><A NAME=2.2.1.1>2.2.1.1. MTRR</A></B></P>
|
|
1612
|
50
|
|
1682
|
51 <P>It is VERY recommended to set MTRR registers up properly, because they can
|
|
|
52 give a big performance boost. First you have to find the base address.
|
|
|
53 You have 3 ways to find it:</P>
|
|
1612
|
54
|
|
1682
|
55 <P><UL>
|
|
|
56 <LI>from X11 startup messages, for example:
|
|
|
57 <P><CODE>(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000<BR>
|
|
|
58 (--) SVGA: Linear framebuffer at 0xD8000000</CODE></P>
|
|
|
59 <LI>from /proc/pci (use lspci -v command):
|
|
|
60 <P><TABLE>
|
|
|
61 <TD VALIGN=top><CODE>01:00.0</CODE></TD><TD><CODE>VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525</CODE></TD><TR>
|
|
|
62 <TD></TD><TD><CODE>Memory at d8000000 (32-bit, prefetchable)</CODE></TD><TR>
|
|
|
63 </TABLE></P></CODE>
|
|
|
64 <LI>from mga_vid kernel driver messages (use dmesg):
|
|
|
65 <P><CODE>mga_mem_base = d8000000</CODE></P>
|
|
|
66 </UL></P>
|
|
1612
|
67
|
|
1682
|
68 <P>Then let's find the memory size. This is very easy, just convert video ram
|
|
|
69 size to hexadecimal, or use this table:</P>
|
|
1612
|
70
|
|
1682
|
71 <TABLE BORDER=0>
|
|
|
72 <TD> </TD><TD>1 MB</TD><TD WIDTH=10%></TD><TD>0x100000</TD><TR>
|
|
|
73 <TD></TD><TD>2 MB</TD><TD></TD><TD>0x200000</TD><TR>
|
|
|
74 <TD></TD><TD>4 MB</TD><TD></TD><TD>0x400000</TD><TR>
|
|
|
75 <TD></TD><TD>8 MB</TD><TD></TD><TD>0x800000</TD><TR>
|
|
|
76 <TD></TD><TD>16 MB</TD><TD></TD><TD>0x1000000</TD><TR>
|
|
|
77 <TD></TD><TD>32 MB</TD><TD></TD><TD>0x2000000</TD><TR>
|
|
|
78 </TABLE>
|
|
1612
|
79
|
|
|
80
|
|
1682
|
81 <P>You know base address and memory size, let's setup mtrr registers!
|
|
|
82 For example, for the Matrox card above (base=0xd8000000) with 32MB
|
|
|
83 ram (size=0x2000000) just execute:</P>
|
|
1612
|
84
|
|
|
85
|
|
1682
|
86 <P><CODE> echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr</CODE></P>
|
|
1612
|
87
|
|
|
88
|
|
1682
|
89 <P>Not all CPUs support MTRRs. For example older K6-2's [around 266Mhz,
|
|
|
90 stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat /proc/cpuinfo</CODE>'
|
|
1686
|
91 to check it</CODE>').</P>
|
|
1612
|
92
|
|
1682
|
93 <P><B><A NAME=2.2.1.2>2.2.1.2. Xv</A></B></P>
|
|
1612
|
94
|
|
1682
|
95 <P>Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines
|
|
|
96 using the XVideo extension. This is what the option '-vo xv' uses.
|
|
|
97 In order to make this work, be sure to check the following:</P>
|
|
|
98 <P><UL>
|
|
|
99 <LI>You have to use XFree86 4.0.2 or newer (former versions don't have XVideo)
|
|
|
100 <LI>Your card actually supports harware acceleration (modern cards do)
|
|
|
101 <LI>X loads the XVideo extension, it's something like this:
|
|
1612
|
102
|
|
1682
|
103 <P><CODE> (II) Loading extension XVideo</CODE></P>
|
|
|
104 <P>in /var/log/XFree86.0.log</P>
|
|
1612
|
105
|
|
1682
|
106 <P>NOTE: this loads only the XFree86's extension. In a good install, this is
|
|
|
107 always loaded, and doesn't mean that the _card's_ XVideo support is loaded!</P>
|
|
1612
|
108
|
|
1682
|
109 <LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the
|
|
|
110 part of the XFree86 distribution. It should display a long text, similar
|
|
|
111 to this:
|
|
|
112 <PRE>
|
|
1612
|
113 X-Video Extension version 2.2
|
|
|
114 screen #0
|
|
|
115 Adaptor #0: "Savage Streams Engine"
|
|
|
116 number of ports: 1
|
|
|
117 port base: 43
|
|
|
118 operations supported: PutImage
|
|
|
119 supported visuals:
|
|
|
120 depth 16, visualID 0x22
|
|
|
121 depth 16, visualID 0x23
|
|
|
122 number of attributes: 5
|
|
|
123 (...)
|
|
|
124 Number of image formats: 7
|
|
|
125 id: 0x32595559 (YUY2)
|
|
|
126 guid: 59555932-0000-0010-8000-00aa00389b71
|
|
|
127 bits per pixel: 16
|
|
|
128 number of planes: 1
|
|
|
129 type: YUV (packed)
|
|
|
130 id: 0x32315659 (YV12)
|
|
|
131 guid: 59563132-0000-0010-8000-00aa00389b71
|
|
|
132 bits per pixel: 12
|
|
|
133 number of planes: 3
|
|
|
134 type: YUV (planar)
|
|
|
135 (...etc...)
|
|
1682
|
136 </PRE>
|
|
1612
|
137
|
|
1682
|
138 <P>It must support YUY2 packed, and YV12 planar pixel formats to be
|
|
|
139 usable with <B>MPlayer</B>.</P>
|
|
1612
|
140
|
|
1682
|
141 <LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support.
|
|
|
142 ./configure prints this.
|
|
1612
|
143
|
|
1682
|
144 </UL></P>
|
|
|
145
|
|
|
146 <P><B><A NAME=2.2.1.2.1>2.2.1.2.1. 3dfx cards</A></B></P>
|
|
1612
|
147
|
|
1682
|
148 <P>Older 3dfx drivers were known to have problems with XVideo acceleration,
|
|
|
149 it didn't support either YUY2 or YV12, and so. Verify that you have
|
|
|
150 XFree86 version 4.1.0 or greater, it works ok. Alternatively, you can use
|
|
|
151 <A HREF="http://dri.sourceforge.net">DRI</A> cvs.
|
|
|
152 If you experience strange effects using -vo xv, try SDL (it has XVideo too)
|
|
|
153 and see if it helps. Check the <A HREF="#2.2.1.4">SDL section</A> for details.</P>
|
|
1612
|
154
|
|
|
155
|
|
1682
|
156 <P><B><A NAME=2.2.1.2.2>2.2.1.2.2. S3 cards</A></B></P>
|
|
|
157
|
|
|
158 <P>S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3
|
|
|
159 or greater. As for S3 Virge.. sell it.</P>
|
|
|
160
|
|
|
161 <P><B><A NAME=2.2.1.2.3>2.2.1.2.3. nVidia cards</A></B></P>
|
|
1612
|
162
|
|
1682
|
163 <P>nVidia isn't a very good choice under Linux.. You'll have to use the
|
|
|
164 binary nVidia driver, available at nVidia's website. The standard X
|
|
|
165 driver doesn't support XVideo for these cards, due to nVidia's closed
|
|
|
166 sources/specifications.</P>
|
|
1612
|
167
|
|
1682
|
168 <P><UL><LI>Riva128 cards don't have XVideo support even with the nvidia driver :(
|
|
|
169 Complain to NVidia.</UL></P>
|
|
1612
|
170
|
|
|
171
|
|
1682
|
172 <P><B><A NAME=2.2.1.2.4>2.2.1.2.4. ATI cards</A></B></P>
|
|
1612
|
173
|
|
1682
|
174 <P>The GATOS driver has VSYNC enabled by default. It means that decoding speed
|
|
|
175 (!) is synced to the monitor's refresh rate. If playing seems to be slow, try
|
|
|
176 disabling VSYNC somehow, or set refresh rate to n*(fps of the movie) Hz.</P>
|
|
1612
|
177
|
|
|
178
|
|
1682
|
179 <P><B><A NAME=2.2.1.3>2.2.1.3. DGA</A></B></P>
|
|
1612
|
180
|
|
1682
|
181 <P><B><A NAME=2.2.1.3.1>2.2.1.3.1. Summary</A></B></P>
|
|
1612
|
182
|
|
1682
|
183 <P>This document tries to explain in some words what DGA is in general and
|
|
|
184 what the DGA video output driver for mplayer can do (and what it can't).</P>
|
|
1612
|
185
|
|
|
186
|
|
1682
|
187 <P><B><A NAME=2.2.1.3.2>2.2.1.3.2. What is DGA</A></B></P>
|
|
1612
|
188
|
|
1682
|
189 <P>DGA is short for Direct Graphics Access and is a means for a program to
|
|
|
190 bypass the X-Server and directly modifying the framebuffer memory.
|
|
|
191 Technically spoken this happens by mapping the framebuffer memory into
|
|
|
192 the memory range of your process. This is allowed by the kernel only
|
|
|
193 if you have superuser privileges. You can get these either by logging in
|
|
|
194 as root or by setting the suid bit on the mplayer excecutable (NOT
|
|
|
195 recommended!).</P>
|
|
1612
|
196
|
|
1682
|
197 <P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was
|
|
|
198 introduced with XFree 4.0.1.</P>
|
|
1612
|
199
|
|
1682
|
200 <P>DGA1 provides only direct framebuffer access as described above. For
|
|
|
201 switching the resolution of the video signal you have to rely on the
|
|
|
202 XVidMode extension.</P>
|
|
1612
|
203
|
|
1682
|
204 <P>DGA2 incorporates the features of XVidMode extension and also allows
|
|
|
205 switching the depth of the display. So you may, although basically
|
|
|
206 running a 32 bit depth XServer, switch to a depth of 15 bits and vice
|
|
|
207 versa. </P>
|
|
1612
|
208
|
|
1682
|
209 <P>However DGA has some drawbacks. It seems it is somewhat dependent on the
|
|
|
210 graphics chip you use and on the implementation of the XServer's video
|
|
|
211 driver that controls this chip. So it does not work on every system ...</P>
|
|
1612
|
212
|
|
|
213
|
|
1682
|
214 <P><B><A NAME=2.2.1.3.3>2.2.1.3.3. Installing DGA support for MPlayer</A></B></P>
|
|
|
215
|
|
|
216 <P>First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:</P>
|
|
|
217
|
|
|
218 <P> <CODE>(II) Loading extension XFree86-DGA</CODE></P>
|
|
|
219
|
|
|
220 <P>See, XFree86 4.0.x or greater is VERY RECOMMENDED!
|
|
|
221 <B>MPlayer</B>'s DGA driver is autodetected on ./configure, or you can force it
|
|
|
222 with --enable-dga.</P>
|
|
1612
|
223
|
|
1682
|
224 <P>If the driver couldn't switch to a smaller resolution, experiment with
|
|
|
225 switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that
|
|
|
226 the movie fits in. There is no converter right now.. :(</P>
|
|
1612
|
227
|
|
1682
|
228 <P>Become ROOT. DGA needs root access to be able to write directly video memory.
|
|
|
229 If you want to run it as user, then install <B>MPlayer</B> SUID root:</P>
|
|
1612
|
230
|
|
1682
|
231 <P><CODE>
|
|
|
232 <CODE>chown root /usr/local/bin/mplayer<BR>
|
|
1686
|
233 chmod 750 /usr/local/bin/mplayer<BR>
|
|
|
234 chmod +s /usr/local/bin/mplayer</CODE></P>
|
|
1612
|
235
|
|
|
236
|
|
1682
|
237 <P>Now it works as a simple user, too.</P>
|
|
1612
|
238
|
|
|
239
|
|
1682
|
240 <P><B>!!!! BUT STAY TUNED !!!!</B><BR>
|
|
|
241 This is a <B>BIG</B> security risk! Never do this on a server or on a computer
|
|
|
242 can be accessed by more people than only you because they can gain root
|
|
|
243 privilegies through suid root mplayer.<BR>
|
|
|
244 <B>!!!! SO YOU HAVE BEEN WARNED ... !!!!</B></P>
|
|
|
245
|
|
|
246 <P>Now use '-vo dga' option, and there you go! (hope so:)
|
|
|
247 You should also try if the '-vo sdl:dga' option works for you! It's much
|
|
|
248 faster!!!</P>
|
|
|
249
|
|
|
250 <P><B><A NAME=2.2.1.3.4>2.2.1.3.4. Resolution switching</A></B></P>
|
|
|
251
|
|
|
252 <P>The DGA driver allows for switching the resolution of the output signal.
|
|
|
253 This avoids the need for doing (slow) software scaling and at the same
|
|
|
254 time provides a fullscreen image. Ideally it would switch to the exact
|
|
|
255 resolution (except for honouring aspect ratio) of the video data, but the
|
|
1686
|
256 XServer only allows switching to resolutions predefined in
|
|
1682
|
257 <CODE>/etc/X11/XF86Config</CODE> (<CODE>/etc/X11/XF86Config-4</CODE> for XFree 4.0.X respectively).
|
|
|
258 Those are defined by so-called modelines and depend on the capabilites
|
|
|
259 of your video hardware. The XServer scans this config file on startup and
|
|
|
260 disables the modelines not suitable for your hardware. You can find
|
|
|
261 out which modes survive with the X11 log file. It can be found at:
|
|
|
262 <CODE>/var/log/XFree86.0.log</CODE>.</P>
|
|
|
263 <P>See appendix A for some sample modeline definitions.</P>
|
|
|
264
|
|
|
265 <P><B><A NAME=2.2.1.3.5>2.2.1.3.5. DGA & MPlayer</A></B></P>
|
|
1612
|
266
|
|
1682
|
267 <P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to make
|
|
|
268 use of it (-vo sdl:dga) and within the DGA driver (-vo dga).
|
|
|
269 The above said is true for both; in the following sections I'll explain
|
|
|
270 how the DGA driver for <B>MPlayer</B> works.</P>
|
|
1612
|
271
|
|
1682
|
272 <P><B><A NAME=2.2.1.3.6>2.2.1.3.6. Features of the DGA driver</A></B></P>
|
|
|
273
|
|
|
274 <P>The DGA driver is invoked by specifying -vo dga at the command line.
|
|
|
275 The default behaviour is to switch to a resolution matching the original
|
|
|
276 resolution of the video as close as possible. It deliberately ignores the
|
|
|
277 -vm and -fs switches (enabling of video mode switching and fullscreen) -
|
|
|
278 it always tries to cover as much area of your screen as possible by switching
|
|
|
279 the video mode, thus refraining to use a single additional cycle of your CPU
|
|
|
280 to scale the image.
|
|
|
281 If you don't like the mode it chooses you may force it to choose the mode
|
|
|
282 matching closest the resolution you specify by -x and -y.
|
|
|
283 By providing the -v option, the DGA driver will print, among a lot of other
|
|
|
284 things, a list of all resolutions supported by your current XF86-Config
|
|
|
285 file.
|
|
|
286 Having DGA2 you may also force it to use a certain depth by using the -bpp
|
|
|
287 option. Valid depths are 15, 16, 24 and 32. It depends on your hardware
|
|
|
288 whether these depths are natively supported or if a (possibly slow)
|
|
|
289 conversion has to be done.</P>
|
|
|
290
|
|
|
291 <P>If you should be lucky enough to have enough offscreen memory left to
|
|
|
292 put a whole image there, the DGA driver will use doublebuffering, which
|
|
|
293 results in much smoother movie replaying. It will tell you whether double-
|
|
|
294 buffering is enabled or not.</P>
|
|
1612
|
295
|
|
1682
|
296 <P>Doublebuffering means that the next frame of your video is being drawn in
|
|
|
297 some offscreen memory while the current frame is being displayed. When the
|
|
|
298 next frame is ready, the graphics chip is just told the location in memory
|
|
|
299 of the new frame and simply fetches the data to be displayed from there.
|
|
|
300 In the meantime the other buffer in memory will be filled again with new
|
|
|
301 video data.</P>
|
|
|
302
|
|
|
303 Doublebuffering may be switched on by using the option -double and may be
|
|
|
304 disabled with -nodouble. Current default option is to disable
|
|
|
305 doublebuffering. When using the DGA driver, onscreen display (OSD) only
|
|
|
306 works with doublebuffering enabled. However, enabling doublebuffering may
|
|
|
307 result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of
|
|
|
308 CPU time!) depending on the implementation of DGA for your hardware.</P>
|
|
|
309
|
|
|
310
|
|
|
311 <P><B><A NAME=2.2.1.3.7>2.2.1.3.7. Speed issues</A></B></P>
|
|
|
312
|
|
|
313 <P>Generally spoken, DGA framebuffer access should be at least as fast as using
|
|
|
314 the X11 driver with the additional benefit of getting a fullscreen image.
|
|
|
315 The percentage speed values printed by mplayer have to be interpreted with
|
|
|
316 some care, as for example, with the X11 driver they do not include the time
|
|
|
317 used by the X-Server needed for the actual drawing. Hook a terminal to a
|
|
|
318 serial line of your box and start top to see what is really going on in your
|
|
|
319 box ...</P>
|
|
|
320
|
|
|
321 <P>Generally spoken, the speedup done by using DGA against 'normal' use of X11
|
|
|
322 highly depends on your graphics card and how well the X-Server module for it
|
|
|
323 is optimized.</P>
|
|
|
324
|
|
|
325 <P>If you have a slow system, better use 15 or 16bit depth since they require
|
|
|
326 only half the memory bandwidth of a 32 bit display.</P>
|
|
1612
|
327
|
|
1682
|
328 <P>Using a depth of 24bit is even a good idea if your card natively just supports
|
|
|
329 32 bit depth since it transfers 25% less data compared to the 32/32 mode.</P>
|
|
|
330
|
|
|
331 <P>I've seen some avi files already be replayed on a Pentium MMX 266. AMD K6-2
|
|
|
332 CPUs might work at 400 MHZ and above.</P>
|
|
1612
|
333
|
|
1682
|
334 <P><B><A NAME=2.2.1.3.8>2.2.1.3.8. Known bugs</A></B></P>
|
|
|
335
|
|
|
336 <P>Well, according to some developpers of XFree, DGA is quite a beast. They
|
|
|
337 tell you better not to use it. Its implementation is not always flawless
|
|
|
338 with every chipset driver for XFree out there.</P>
|
|
1612
|
339
|
|
1682
|
340 <P><UL>
|
|
|
341 <LI>with XFree 4.0.3 and nv.o there is a bug resulting in strange colors
|
|
|
342 <LI>ATI driver requires to switch mode back more than once after finishing
|
|
|
343 using of DGA
|
|
|
344 <LI>some drivers simply fail to switch back to normal resolution (use
|
|
|
345 Ctrl-Alt-Keypad +, - to switch back manually)
|
|
|
346 <LI>some drivers simply display strange colors
|
|
|
347 <LI>some drivers lie about the amount of memory they map into the process's
|
|
|
348 address space, thus vo_dga won't use doublebuffering (SIS?)
|
|
|
349 <LI>some drivers seem to fail to report even a single valid mode. In this
|
|
|
350 case the DGA driver will crash telling you about a nonsense mode of
|
|
|
351 100000x100000 or the like ...
|
|
|
352 <LI>OSD only works with doublebuffering enabled
|
|
|
353 </UL></P>
|
|
|
354
|
|
|
355 <P><B><A NAME=2.2.1.3.9>2.2.1.3.9. Future work</A></B></P>
|
|
|
356
|
|
|
357 <P><UL><LI>use of the new X11 render interface for OSD
|
|
|
358 <LI>where is my TODO list ???? :-(((</UL></P>
|
|
1612
|
359
|
|
|
360
|
|
1682
|
361 <P><B><A NAME=2.2.1.3.A>2.2.1.3.A. Some modelines</A></B></P>
|
|
1612
|
362
|
|
1682
|
363 <PRE>
|
|
1612
|
364 Section "Modes"
|
|
|
365 Identifier "Modes[0]"
|
|
|
366 Modeline "800x600" 40 800 840 968 1056 600 601 605 628
|
|
|
367 Modeline "712x600" 35.0 712 740 850 900 400 410 412 425
|
|
|
368 Modeline "640x480" 25.175 640 664 760 800 480 491 493 525
|
|
|
369 Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan
|
|
|
370 Modeline "352x288" 25.10 352 368 416 432 288 296 290 310
|
|
|
371 Modeline "352x240" 15.750 352 368 416 432 240 244 246 262 Doublescan
|
|
|
372 Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan
|
|
|
373 EndSection
|
|
1682
|
374 </PRE>
|
|
1612
|
375
|
|
1682
|
376 <P>These entries work fine with my Riva128 chip, using nv.o XServer driver
|
|
|
377 module.</P>
|
|
1612
|
378
|
|
|
379
|
|
1682
|
380 <P><B><A NAME=2.2.1.3.B>2.2.1.3.B. Bug Reports</A></B></P>
|
|
1612
|
381
|
|
1682
|
382 <P>If you experience troubles with the DGA driver please feel free to file
|
|
|
383 a bug report to me (e-mail address below). Please start mplayer with the
|
|
|
384 -v option and include all lines in the bug report that start with vo_dga:</P>
|
|
|
385
|
|
|
386 <P>Please do also include the version of X11 you are using, the graphics card
|
|
|
387 and your CPU type. The X11 driver module (defined in XF86-Config) might
|
|
|
388 also help. Thanks!</P>
|
|
1612
|
389
|
|
1682
|
390
|
|
|
391 <P><I>Acki (acki@acki-netz.de, www.acki-netz.de)</I></P>
|
|
1612
|
392
|
|
|
393
|
|
1682
|
394 <P><B><A NAME=2.2.1.4>2.2.1.4. SDL</A></B></P>
|
|
1612
|
395
|
|
1682
|
396 <P>Here are some notes about SDL out in <B>MPlayer</B>.</P>
|
|
1612
|
397
|
|
|
398
|
|
|
399
|
|
1682
|
400 <P><TABLE BORDER=0>
|
|
|
401 <TD COLSPAN=4><P><B>There are several commandline switches for SDL:</B></P></TD><TR>
|
|
|
402 <TD> </TD><TD>-vo sdl:name</TD><TD> </TD><TD>
|
|
|
403 specifies sdl video driver to use (ie. aalib, dga, x11)</TD><TR>
|
|
|
404 <TD></TD><TD>-ao sdl:name</TD><TD></TD><TD>specifies sdl audio driver to use (ie. dsp,
|
|
|
405 esd, arts)</TD><TR>
|
|
|
406 <TD></TD><TD>-noxv</TD><TD></TD><TD>disables Xvideo hardware acceleration</TD><TR>
|
|
|
407 <TD></TD><TD>-forcexv</TD><TD></TD><TD>tries to force Xvideo acceleration</TD><TR>
|
|
1612
|
408
|
|
1682
|
409 <TD COLSPAN=4><P><B>SDL Keys:</B></P></TD><TR>
|
|
1612
|
410
|
|
1682
|
411 <TD></TD><TD>F</TD><TD></TD><TD>toggles fullscreen/windowed mode</TD><TR>
|
|
|
412 <TD></TD><TD>C</TD><TD></TD><TD>cycles available fullscreen modes</TD><TR>
|
|
|
413 <TD></TD><TD>W/S</TD><TD></TD><TD>mappings for * and / (mixer control)</TD><TR>
|
|
1612
|
414
|
|
1682
|
415 </TABLE></P>
|
|
1612
|
416
|
|
1682
|
417 <P><B>KNOWN BUGS:</B></P>
|
|
|
418 <P><UL><LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa !)
|
|
|
419 It's bug in SDL, I can't change it (tested with SDL 1.2.1).
|
|
|
420 </UL></P>
|
|
1612
|
421
|
|
1682
|
422 <P><B><A NAME=2.2.1.5>2.2.1.5. SVGAlib</A></B></P>
|
|
|
423
|
|
|
424 <P>If you don't have X, you can use the SVGAlib target! Be sure not to use the
|
|
|
425 -fs switch, since it toggles the usage of the software scaler, and it's
|
|
|
426 SLOOOW now, unless you have a real fast CPU (and/or MTRR?). :(</P>
|
|
1612
|
427
|
|
1682
|
428 <P>Of course you'll have to install svgalib and its development package in
|
|
|
429 order for <B>MPlayer</B> build its SVGAlib driver (autodetected, but can be
|
|
|
430 forced), and don't forget to edit /etc/vga/libvga.config to suit your
|
|
|
431 card & monitor.</P>
|
|
1612
|
432
|
|
1682
|
433 <P><B><A NAME=2.2.1.6>2.2.1.6. Framebuffer output (FBdev)</A></B></P>
|
|
|
434
|
|
|
435 <P>Whether to build the FBdev target is autodetected during ./configure .
|
|
|
436 Read the framebuffer documentation in the kernel sources
|
|
|
437 (Documentation/fb/*) for info on how to enable it, etc.. !</P>
|
|
1612
|
438
|
|
1682
|
439 <P>If your card doesn't support VBE 2.0 standard (older ISA/PCI
|
|
|
440 cards, such as S3 Trio64), only VBE 1.2 (or older?) :
|
|
|
441 Well, VESAfb is still available, but you'll have to load SciTech Display
|
|
|
442 Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or
|
|
|
443 whatever. And don't forget to register your UniVBE ;))</P>
|
|
1612
|
444
|
|
1682
|
445 <P>The FBdev output takes some additional parameters above the others:</P>
|
|
1612
|
446
|
|
1682
|
447 <P><TABLE BORDER=0>
|
|
|
448 <TD> </TD><TD>-fb</TD><TD> </TD><TD>
|
|
|
449 specify the framebuffer device to use (/dev/fd0)</TD><TR>
|
|
|
450 <TD></TD><TD>-fbmode</TD><TD></TD><TD>mode name to use (according to /etc/fb.modes)</TD><TR>
|
|
|
451 <TD></TD><TD>-fbmodeconfig</TD><TD></TD><TD> config file of modes (default /etc/fb.modes)</TD><TR>
|
|
|
452 <TD></TD><TD>-monitor_hfreq</TD><TD></TD><TD ROWSPAN=3>IMPORTANT values, see example.conf</TD><TR>
|
|
|
453 <TD></TD><TD>-monitor_vfreq</TD><TD></TD><TR>
|
|
|
454 <TD></TD><TD>-monitor_dotclock</TD><TD></TD><TR>
|
|
|
455 </TABLE></P>
|
|
1612
|
456
|
|
1682
|
457 <P>If you want to change to a specific mode, then use</P>
|
|
1612
|
458
|
|
1682
|
459 <P><CODE> mplayer -vm -fbmode (NameOfMode) filename</CODE></P>
|
|
1612
|
460
|
|
1682
|
461 <P><UL><LI><B>-vm</B> alone will choose the most suitable mode from /etc/fb.modes . Can be
|
|
|
462 used together with -x and -y options too. The -flip option is supported only
|
|
|
463 if the movie's pixel format matches the video mode's pixel format.
|
|
|
464 Pay attention to the bpp value, fbdev driver tries to use the current,
|
|
|
465 or if you specify the -bpp option, then that.
|
|
|
466 <LI><B>-zoom</B> option isn't supported (software scaling is slow). -fs option
|
|
|
467 isn't supported. You can't use 8bpp (or less) modes.</UL></P>
|
|
1612
|
468
|
|
1682
|
469 <P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer,
|
|
|
470 and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P>
|
|
1612
|
471
|
|
1682
|
472 <P><B><A NAME=2.2.1.7>2.2.1.7. Matrox framebuffer (mga_vid)</A></B></P>
|
|
1612
|
473
|
|
1682
|
474 <P>This section is about the Matrox G200/G400/G450 BES (Back-End Scaler)
|
|
|
475 support, the mga_vid kernel driver. It's active developed by me (A'rpi), and
|
|
|
476 it has hardware VSYNC support with triple buffering. It works on both
|
|
|
477 framebuffer console and under X.</P>
|
|
|
478
|
|
|
479 <P>To use it, you first have to compile mga_vid.o:</P>
|
|
1612
|
480
|
|
1682
|
481 <P><CODE> cd drivers<BR>
|
|
|
482 make</CODE></P>
|
|
1612
|
483
|
|
1682
|
484 <P>Then create /dev/mga_vid device:</P>
|
|
1612
|
485
|
|
1682
|
486 <P><CODE> mknod /dev/mga_vid c 178 0</CODE></P>
|
|
1612
|
487
|
|
1682
|
488 <P>and load the driver with</P>
|
|
|
489
|
|
|
490 <P><CODE> insmod mga_vid.o</CODE></P>
|
|
1612
|
491
|
|
1682
|
492 <P>You should verify the memory size detection using the 'dmesg' command. If
|
|
|
493 it's bad, use the mga_ram_size option (rmmod mga_vid first), specify card's
|
|
|
494 memory size in MB:</P>
|
|
1612
|
495
|
|
1682
|
496 <P><CODE> insmod mga_vid.o mga_ram_size=16</CODE></P>
|
|
1612
|
497
|
|
1682
|
498 <P>To make it load/unload automatically when needed, insert the following line
|
|
|
499 at the end of /etc/modules.conf:</P>
|
|
1612
|
500
|
|
1682
|
501 <P><CODE> alias char-major-178 mga_vid</CODE></P>
|
|
1612
|
502
|
|
1682
|
503 <P>Then run</P>
|
|
1612
|
504
|
|
1682
|
505 <P><CODE> depmod -a</CODE></P>
|
|
1612
|
506
|
|
1682
|
507 <P>Now you have to (re)compile <B>MPlayer</B>, ./configure will detect /dev/mga_vid
|
|
|
508 and build the 'mga' driver. Using it from <B>MPlayer</B> goes by '-vo mga' if
|
|
|
509 you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.</P>
|
|
|
510
|
|
|
511 <P>Note: '-vo xmga' works under XFree86 4.x.x, but it conflicts with the Xv
|
|
|
512 driver, so avoid using both. If you messed up Xv with mga, try running
|
|
|
513 <B>MPlayer</B> with '-vo mga' . It should fix Xv.</P>
|
|
1612
|
514
|
|
|
515
|
|
1682
|
516 <P><B><A NAME=2.2.1.8>2.2.1.8. SiS 6326 framebuffer (sis_vid)</A></B></P>
|
|
|
517
|
|
|
518 <P>SiS 6326 YUV Framebuffer driver -> sis_vid kernel driver</P>
|
|
1612
|
519
|
|
1682
|
520 <P>Its interface should be compatible with the mga_vid, but the driver was not
|
|
|
521 updated after the mga_vid changes, so it's outdated now. Volunteers
|
|
|
522 needed to test it and bring the code up-to-date.</P>
|
|
1612
|
523
|
|
1682
|
524 <P><B><A NAME=2.2.1.9>2.2.1.9. 3dfx YUV support</A></B></P>
|
|
1612
|
525
|
|
1682
|
526 <P>3dfx has native YUV+scaler support, using /dev/3dfx (tdfx.o driver?)
|
|
|
527 The /dev/3dfx kernel driver exists only for 2.2.x kernels, for use with
|
|
|
528 Glide 2.x Linux ports. It's not tested with <B>MPlayer</B>, and so no more
|
|
|
529 supported. Volunteers needed to test it and bring the code up-to-date.</P>
|
|
1612
|
530
|
|
1682
|
531 <P><B><A NAME=2.2.1.10>2.2.1.10. OpenGL output</A></B></P>
|
|
1612
|
532
|
|
1682
|
533 <P><B>MPlayer</B> support displaying movies using OpenGL. Unfortunately, not all
|
|
|
534 drivers support this ability. For example the Utah-GLX drivers
|
|
|
535 (for XFree86 3.3.6) have it, with all cards.
|
|
|
536 See <A HREF="http://utah-glx.sourceforge.net">http://utah-glx.sourceforge.net</A>
|
|
|
537 for details about how to install it.</P>
|
|
1612
|
538
|
|
1682
|
539 <P>XFree86(DRI) >= 4.0.3 supports it only with Matrox, and Radeon cards.
|
|
|
540 See <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> for download,
|
|
|
541 and installation instructions.</P>
|
|
1612
|
542
|
|
1682
|
543 <P><B><A NAME=2.2.1.11>2.2.1.11. AAlib - text mode displaying</B></P>
|
|
1612
|
544
|
|
1682
|
545 <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful
|
|
|
546 ASCII renderer. There are LOTS of programs already supporting it, like Doom,
|
|
|
547 Quake, etc. MPlayer contains a very usable driver for it.
|
|
|
548 If ./configure detects aalib installed, the aalib libvo driver will be built.</P>
|
|
1612
|
549
|
|
1682
|
550 <P><TABLE BORDER=0>
|
|
|
551 <TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD><TR>
|
|
|
552 <TD> </TD><TD>1</TD><TD> </TD><TD>decrease contrast</TD><TR>
|
|
|
553 <TD></TD><TD>2</TD><TD></TD><TD>increase contrast</TD><TR>
|
|
|
554 <TD></TD><TD>3</TD><TD></TD><TD>decrease brightness</TD><TR>
|
|
|
555 <TD></TD><TD>4</TD><TD></TD><TD>increase brightness</TD><TR>
|
|
|
556 <TD></TD><TD>5</TD><TD></TD><TD>switch fast rendering on/off</TD><TR>
|
|
|
557 <TD></TD><TD>6</TD><TD></TD><TD>set dithering mode (none, error distribution, floyd steinberg)</TD><TR>
|
|
|
558 <TD></TD><TD>7</TD><TD></TD><TD>invert image</TD><TR>
|
|
|
559 <TD></TD><TD>a</TD><TD></TD><TD>toggles between aa and mplayer control)</TD><TR>
|
|
|
560
|
|
|
561 <TD COLSPAN=4><P><B>The following command line options can be used:</B></P></TD><TR>
|
|
1612
|
562
|
|
1682
|
563 <TD></TD><TD>-aaosdcolor=V</TD><TD></TD><TD>change osd color</TD><TR>
|
|
|
564 <TD></TD><TD>-aasubcolor=V</TD><TD></TD><TD>change subtitle color</TD><TR>
|
|
|
565 <TD COLSPAN=3></TD><TD><P><I>where V can be: (0/normal, 1/dark, 2/bold, 3/boldfont, 4/reverse, 5/special)</P></TD><TR>
|
|
1612
|
566
|
|
1682
|
567 <TD COLSPAN=4><P><B>AAlib itselves provides a large sum of options.
|
|
|
568 Here are some important:</P></B></TD><TR>
|
|
|
569
|
|
|
570 <TD></TD><TD>-aadriver</TD><TD></TD><TD>set recommended aa driver (X11, curses, linux)</TD><TR>
|
|
|
571 <TD></TD><TD>-aaextended</TD><TD></TD><TD>use all 256 characters</TD><TR>
|
|
|
572 <TD></TD><TD>-aaeight</TD><TD></TD><TD>use eight bit ascii</TD><TR>
|
|
|
573 <TD></TD><TD>-aahelp</TD><TD></TD><TD>prints out all aalib options</TD><TR>
|
|
|
574 </TABLE></P>
|
|
|
575
|
|
|
576 <P>NOTE: the rendering is very CPU intensive, especially when using AA-on-X
|
|
|
577 (using aalib on X), and it's least CPU intensive on standard,
|
|
|
578 non-framebuffer console. Use SVGATextMode to set up a big textmode,
|
|
|
579 then enjoy! (secondary head Hercules cards rock :)) (anyone can enhance
|
|
|
580 bdev to do conversion/dithering to hgafb? Would be neat :)</P>
|
|
1612
|
581
|
|
1682
|
582 <P>Use the -framedrop option if your comp isn't fast enough to render all frames!</P>
|
|
1612
|
583
|
|
1682
|
584 <P>Playing on terminal you'll get better speed and quality using the linux driver, not
|
|
|
585 curses (-aadriver linux). But therefore you need write access on /dev/vcsa<terminal>!
|
|
|
586 That isn't autodetected by aalib, bu vo_aa tries to find the best mode.
|
|
1731
|
587 See <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> for further tuning issues.</P>
|
|
1612
|
588
|
|
1682
|
589 <P><B><A NAME=2.2.1.A>2.2.1.A. TV-out support</A></B></P>
|
|
1612
|
590
|
|
1682
|
591 <P><B><A NAME=2.2.1.A.1>2.2.1.A.1. Matrox cards</A></B></P>
|
|
1612
|
592
|
|
1682
|
593 <P><I> What I'd love to see in mplayer is the the same feature that I see in my
|
|
|
594 windows box. When I start a movie in windows (in a window or in full screen)
|
|
|
595 the movie is also redirected to the tv-out and I can also see it full screen
|
|
|
596 on my tv. I love this feature and was wondering how hard it would be to add
|
|
|
597 such a feature to mplayer.</I></P>
|
|
1612
|
598
|
|
1682
|
599 <P>It's a driver limitation. BES (Back-End Scaler, it's the overlay generator
|
|
|
600 and YUV scaling engine of G200/G400/G450 cards) works only with CRTC1.
|
|
|
601 Normally, CRTC1 (textmode, every bpp gfx and BES) is routed to HEAD1,
|
|
|
602 and CRTC2 (only 16/32bpp gfx) is routed to HEAD2 (TV-out).</P>
|
|
1612
|
603
|
|
1682
|
604 <P>Under linux, you have two choices to get TV-out working:</P>
|
|
1612
|
605
|
|
1682
|
606 <P><UL>
|
|
|
607 <LI>Using X 4.0.x + the HAL driver from matrox, so you'll get dual-head
|
|
|
608 support, and you'll be able to redirect second output to the TV.
|
|
|
609 Unfortunately it has Macrovision encryption enabled, so it will
|
|
|
610 only work on directly-connected TV, no through VCR.
|
|
|
611 Other problem is that Xv doesn't work on the second head.
|
|
|
612 (I don't know how Windows solve it, maybe it swaps the CRTCs between
|
|
|
613 the heads, or just uses YUV framebuffer of second DAC with some trick)
|
|
|
614 <LI>Using matroxfb with dual-head support enabled (2.4.x kernels).
|
|
|
615 You'll be able to get a framebuffer console (using CRTC2, so it's
|
|
|
616 slow), and TV-out (using CRTC1, with BES support).
|
|
|
617 You have to forget X while using this kind of TV-out! :(
|
|
|
618 </UL></P>
|
|
1612
|
619
|
|
1682
|
620 <P>Follow these instructions:</P>
|
|
1612
|
621
|
|
1682
|
622 <P><UL>
|
|
|
623 <LI>Compile all the matrox-related things to modules in the kernel.
|
|
|
624 (you MUST compile them to modules, at least I couldn't get them
|
|
|
625 working built-in yet)
|
|
|
626 [reboot to new kernel & install modules, but don't load them yet!]
|
|
|
627 <P><CODE>
|
|
|
628 cd TVout<BR>
|
|
|
629 ./compile.sh</CODE></P>
|
|
|
630 <LI>Run the 'modules' script from the TV-out directory of mplayer.
|
|
|
631 It will switch your console to framebuffer.
|
|
|
632 Change to tty1 (ALT+F1)!
|
|
|
633 Now run the script 'independent', it will set up your tty's:
|
|
|
634 <P>tty 1,2: fb console, CRTC2, head 1 (monitor)<BR>
|
|
|
635 tty 3,4,5...: framebuffer+BES, CRTC1, head 2 (TV-out)</P>
|
|
|
636 You should run the scripts TV-* and Mon-* to set up resolutions:
|
|
|
637 <P>change to tty1 (ALT+F1), and run Mon-* (one of them)<BR>
|
|
|
638 change to tty3 (ALT+F3) and then back to tty1 (ALT+F1)</P>
|
|
|
639 (this change will select tty3 on /dev/fb1 - tricky)<BR>
|
|
|
640 <P>run TV-* (one of them)</P>
|
|
|
641 (now you'll get a console on your PAL TV - don't know about NTSC)
|
|
|
642 <P>Now if you start mplayer (on tty1), the picture will show up on
|
|
|
643 the tty3, so you'll see it on your TV or second monitor.</P>
|
|
|
644 </UL></P>
|
|
1612
|
645
|
|
1682
|
646 <P>Yes, it is a bit 'hack' now. But I'm waiting for the marvel
|
|
|
647 project to be finished, it will provide real TV-out drivers, I hope.</P>
|
|
1612
|
648
|
|
1682
|
649 <P>My current problem is that BES is working only with CRTC1. So picture
|
|
|
650 will always shown up on head routed to CRTC1 (normaly the monitor),
|
|
|
651 so i have to swap CRTC's, but this way your console will framebuffer
|
|
|
652 (CRTC2 can't do text-mode) and a bit slow (no acceleration). :(</P>
|
|
1612
|
653
|
|
1682
|
654 <P><I>Anyway i also just get monochrome output on the tv ...</I>
|
|
|
655 Maybe you have NTSC TV? Or just didn't run one of TV-* scripts.</P>
|
|
1612
|
656
|
|
|
657 </BODY>
|
|
|
658 </HTML>
|
