Mercurial > mplayer.hg
comparison DOCS/video.html @ 4177:cab4ac1467e4
many small updates
author | gabucino |
---|---|
date | Tue, 15 Jan 2002 17:04:01 +0000 |
parents | a5c59d8637a9 |
children | bcaf75e384d8 |
comparison
equal
deleted
inserted
replaced
4176:116abdd0aed1 | 4177:cab4ac1467e4 |
---|---|
253 | 253 |
254 | 254 |
255 <P><B><A NAME=2.3.1.2.4>2.3.1.2.4. ATI cards</A></B></P> | 255 <P><B><A NAME=2.3.1.2.4>2.3.1.2.4. ATI cards</A></B></P> |
256 | 256 |
257 <P> | 257 <P> |
258 <LI>The <A HREF="http://www.linuxvideo.org/gatos">GATOS driver</A> (which you should use) has VSYNC enabled by default. It means that decoding speed | 258 <LI>The <A HREF="http://www.linuxvideo.org/gatos">GATOS driver</A> (which you |
259 (!) is synced to the monitor's refresh rate. If playing seems to be slow, try | 259 should use, unless you have Rage128 or Radeon) has VSYNC enabled by default. It |
260 disabling VSYNC somehow, or set refresh rate to n*(fps of the movie) Hz.</LI> | 260 means that decoding speed (!) is synced to the monitor's refresh rate. If |
261 playing seems to be slow, try disabling VSYNC somehow, or set refresh rate to | |
262 n*(fps of the movie) Hz.</LI> | |
261 | 263 |
262 <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version | 264 <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version |
263 4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can | 265 4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can |
264 happily get <B>accelerated</B> display, with or without <B>TV output</B>, and | 266 happily get <B>accelerated</B> display, with or without <B>TV output</B>, and |
265 no libraries or X are needed. Read <a href=#2.3.1.12>VESA driver</a> and <A | 267 no libraries or X are needed. Read <a href=#2.3.1.12>VESA driver</a> and <A |
897 (Back End Scaler, the YUV scaler on G200/G400/G450/G550 cards) doesn't work | 899 (Back End Scaler, the YUV scaler on G200/G400/G450/G550 cards) doesn't work |
898 on it! The windows driver somehow workarounds this, probably by using the | 900 on it! The windows driver somehow workarounds this, probably by using the |
899 3D engine to zoom, and the YUV framebuffer to display the zoomed | 901 3D engine to zoom, and the YUV framebuffer to display the zoomed |
900 image. If you really want to use X, use the <CODE>-vo x11 -fs -zoom</CODE> | 902 image. If you really want to use X, use the <CODE>-vo x11 -fs -zoom</CODE> |
901 options, but it will be <B>SLOW</B>, and has <B>Macrovision</B> copyprotection | 903 options, but it will be <B>SLOW</B>, and has <B>Macrovision</B> copyprotection |
902 enabled.</LI> | 904 enabled (you can "workaround" Macrovision using |
905 <A HREF="http://avifile.sourceforge.net/mgamacro.pl">this</A> perl | |
906 script.</LI> | |
903 <LI><B>Framebuffer</B>: using the <B>matroxfb modules</B> in the 2.4 kernels. | 907 <LI><B>Framebuffer</B>: using the <B>matroxfb modules</B> in the 2.4 kernels. |
904 2.2 kernels don't have the TVout feature in them, thus unusable for this. | 908 2.2 kernels don't have the TVout feature in them, thus unusable for this. |
905 You have to enable ALL matroxfb-specific feature during compilation (except | 909 You have to enable ALL matroxfb-specific feature during compilation (except |
906 MultiHead), and compile them into <B>modules</B>! | 910 MultiHead), and compile them into <B>modules</B>! |
907 <UL> | 911 <UL> |