Mercurial > mplayer.hg
comparison DOCS/video.html @ 7367:5b0baab4c4fd
Numbering corrected.
author | diego |
---|---|
date | Tue, 10 Sep 2002 22:10:06 +0000 |
parents | cc40fdbb0154 |
children | 2c13297f0b80 |
comparison
equal
deleted
inserted
replaced
7366:892ebabb04e2 | 7367:5b0baab4c4fd |
---|---|
622 <P>The <CODE>/dev/mga_vid</CODE> device file can be read (for example by | 622 <P>The <CODE>/dev/mga_vid</CODE> device file can be read (for example by |
623 <CODE>cat /dev/mga_vid</CODE>) for some info, and written for brightness | 623 <CODE>cat /dev/mga_vid</CODE>) for some info, and written for brightness |
624 change: <CODE>echo "brightness=120" > /dev/mga_vid</CODE></P> | 624 change: <CODE>echo "brightness=120" > /dev/mga_vid</CODE></P> |
625 | 625 |
626 | 626 |
627 <H4><A NAME="tdfxfb">2.3.1.9 3dfx YUV support (tdfxfb)</A></H4> | 627 <H4><A NAME="tdfxfb">2.3.1.8 3dfx YUV support (tdfxfb)</A></H4> |
628 | 628 |
629 <P>This driver uses the kernel's tdfx framebuffer driver to play movies with | 629 <P>This driver uses the kernel's tdfx framebuffer driver to play movies with |
630 YUV acceleration. You'll need a kernel with tdfxfb support, and recompile | 630 YUV acceleration. You'll need a kernel with tdfxfb support, and recompile |
631 with <CODE>./configure --enable-tdfxfb</CODE></P> | 631 with <CODE>./configure --enable-tdfxfb</CODE></P> |
632 | 632 |
633 | 633 |
634 <H4><A NAME="opengl">2.3.1.10 OpenGL output</A></H4> | 634 <H4><A NAME="opengl">2.3.1.9 OpenGL output</A></H4> |
635 | 635 |
636 <P><B>MPlayer</B> supports displaying movies using OpenGL, but if your | 636 <P><B>MPlayer</B> supports displaying movies using OpenGL, but if your |
637 platform/driver supports xv as should be the case on a PC with Linux, use xv | 637 platform/driver supports xv as should be the case on a PC with Linux, use xv |
638 instead, OpenGL performance is considerably worse. If you have an X11 | 638 instead, OpenGL performance is considerably worse. If you have an X11 |
639 implementation without xv support, OpenGL is a viable alternative.</P> | 639 implementation without xv support, OpenGL is a viable alternative.</P> |
647 4.2.0 or later supports Rage128. See | 647 4.2.0 or later supports Rage128. See |
648 <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> | 648 <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> |
649 for download and installation instructions.</P> | 649 for download and installation instructions.</P> |
650 | 650 |
651 | 651 |
652 <H4><A NAME="aalib">2.3.1.11 AAlib - text mode displaying</A></H4> | 652 <H4><A NAME="aalib">2.3.1.10 AAlib - text mode displaying</A></H4> |
653 | 653 |
654 <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful | 654 <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful |
655 ASCII renderer. There are LOTS of programs already supporting it, like Doom, | 655 ASCII renderer. There are LOTS of programs already supporting it, like Doom, |
656 Quake, etc. <B>MPlayer</B> contains a very usable driver for it. | 656 Quake, etc. <B>MPlayer</B> contains a very usable driver for it. |
657 If ./configure detects aalib installed, the aalib libvo driver will be | 657 If ./configure detects aalib installed, the aalib libvo driver will be |
711 to find the best mode. See | 711 to find the best mode. See |
712 <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> | 712 <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> |
713 for further tuning issues.</P> | 713 for further tuning issues.</P> |
714 | 714 |
715 | 715 |
716 <H4><A NAME="vesa">2.3.1.12 VESA - output to VESA BIOS</A></H4> | 716 <H4><A NAME="vesa">2.3.1.11 VESA - output to VESA BIOS</A></H4> |
717 | 717 |
718 <P>This driver was designed and introduced as a <B>generic driver</B> for any | 718 <P>This driver was designed and introduced as a <B>generic driver</B> for any |
719 video card which has VESA VBE 2.0 compatible BIOS. Another advantage of this | 719 video card which has VESA VBE 2.0 compatible BIOS. Another advantage of this |
720 driver is that it tries to force TV output on.<BR> | 720 driver is that it tries to force TV output on.<BR> |
721 <B>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998</B> (Page | 721 <B>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998</B> (Page |
815 booting your PC since video BIOS initializes itself only once during POST | 815 booting your PC since video BIOS initializes itself only once during POST |
816 procedure.</LI> | 816 procedure.</LI> |
817 </UL> | 817 </UL> |
818 | 818 |
819 | 819 |
820 <H4><A NAME="x11">2.3.1.13 X11</A></H4> | 820 <H4><A NAME="x11">2.3.1.12 X11</A></H4> |
821 | 821 |
822 <P>Avoid if possible. Outputs to X11 (uses shared memory extension), with no | 822 <P>Avoid if possible. Outputs to X11 (uses shared memory extension), with no |
823 hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but still | 823 hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but still |
824 slow) software scaling, use the options <CODE>-fs -zoom</CODE>. Most cards | 824 slow) software scaling, use the options <CODE>-fs -zoom</CODE>. Most cards |
825 have hardware scaling support, use the <CODE>-vo xv</CODE> output for them, | 825 have hardware scaling support, use the <CODE>-vo xv</CODE> output for them, |
845 <P>If you can't find the modes you inserted, browse XFree86's output. Some | 845 <P>If you can't find the modes you inserted, browse XFree86's output. Some |
846 drivers can't use low pixelclocks that are needed for low resolution | 846 drivers can't use low pixelclocks that are needed for low resolution |
847 video modes.</P> | 847 video modes.</P> |
848 | 848 |
849 | 849 |
850 <H4><A NAME="vidix">2.3.1.14 VIDIX</A></H4> | 850 <H4><A NAME="vidix">2.3.1.13 VIDIX</A></H4> |
851 | 851 |
852 <P>VIDIX is the abbreviation for <B>VID</B>eo <B>I</B>nterface for | 852 <P>VIDIX is the abbreviation for <B>VID</B>eo <B>I</B>nterface for |
853 *ni<B>X</B>.<BR> | 853 *ni<B>X</B>.<BR> |
854 VIDIX was designed and introduced as an interface for fast user-space drivers | 854 VIDIX was designed and introduced as an interface for fast user-space drivers |
855 providing such video performance as mga_vid does for Matrox cards. It's | 855 providing such video performance as mga_vid does for Matrox cards. It's |
978 or<BR> | 978 or<BR> |
979 <CODE>mplayer -vo xvidix -red_intensity -50 -saturation 400 -hue 300 | 979 <CODE>mplayer -vo xvidix -red_intensity -50 -saturation 400 -hue 300 |
980 filename.vob</CODE></P> | 980 filename.vob</CODE></P> |
981 | 981 |
982 | 982 |
983 <H4><A NAME="zr">2.3.1.15 Zr</A></H4> | 983 <H4><A NAME="zr">2.3.1.14 Zr</A></H4> |
984 | 984 |
985 <P>This is a display-driver (<CODE>-vo zr</CODE>) for a number of MJPEG | 985 <P>This is a display-driver (<CODE>-vo zr</CODE>) for a number of MJPEG |
986 capture/playback cards (tested for DC10+ and Buz, and it should work for the | 986 capture/playback cards (tested for DC10+ and Buz, and it should work for the |
987 LML33 and the original DC10). The driver works by encoding the frame to jpeg | 987 LML33 and the original DC10). The driver works by encoding the frame to jpeg |
988 and then sending it to the card. For the jpeg encoding <B>libavcodec</B> is | 988 and then sending it to the card. For the jpeg encoding <B>libavcodec</B> is |
1062 <P>Finally an important remark: Do not start or stop XawTV on the playback | 1062 <P>Finally an important remark: Do not start or stop XawTV on the playback |
1063 device during playback, it will crash your computer. It is, however, fine to | 1063 device during playback, it will crash your computer. It is, however, fine to |
1064 <B>FIRST</B> start XawTV, <B>THEN</B> start <B>MPlayer</B>, wait for | 1064 <B>FIRST</B> start XawTV, <B>THEN</B> start <B>MPlayer</B>, wait for |
1065 <B>MPlayer</B> to finish and <B>THEN</B> stop XawTV.</P> | 1065 <B>MPlayer</B> to finish and <B>THEN</B> stop XawTV.</P> |
1066 | 1066 |
1067 <H4><A NAME="dvb">2.3.1.16 DVB</A></H4> | 1067 |
1068 <H4><A NAME="dvb">2.3.1.15 DVB</A></H4> | |
1068 | 1069 |
1069 <P><B>MPlayer</B> supports cards with the Siemens DVB chipset from vendors like | 1070 <P><B>MPlayer</B> supports cards with the Siemens DVB chipset from vendors like |
1070 Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB drivers are | 1071 Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB drivers are |
1071 available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you | 1072 available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you |
1072 want to do software transcoding you should have at least a 1GHz CPU.</P> | 1073 want to do software transcoding you should have at least a 1GHz CPU.</P> |
1165 the native OSD feature of DVB cards, as well as more fluent playback of | 1166 the native OSD feature of DVB cards, as well as more fluent playback of |
1166 non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial | 1167 non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial |
1167 decompression).</P> | 1168 decompression).</P> |
1168 | 1169 |
1169 | 1170 |
1170 <H4><A NAME="dxr3">2.3.1.17 DXR3/Hollywood+</A></H4> | 1171 <H4><A NAME="dxr3">2.3.1.16 DXR3/Hollywood+</A></H4> |
1171 | 1172 |
1172 <P><B>MPlayer</B> supports hardware accelerated playback with the Creative DXR3 | 1173 <P><B>MPlayer</B> supports hardware accelerated playback with the Creative DXR3 |
1173 and Sigma Designs Hollywood Plus cards. These cards both use the em8300 MPEG | 1174 and Sigma Designs Hollywood Plus cards. These cards both use the em8300 MPEG |
1174 decoder chip from Sigma Designs.</P> | 1175 decoder chip from Sigma Designs.</P> |
1175 | 1176 |