[Mplayer-cvslog] CVS: main/DOCS codecs.html,1.76,1.77 documentation.html,1.286,1.287 encoding.html,1.54,1.55 formats.html,1.39,1.40 sound.html,1.46,1.47 users_against_developers.html,1.26,1.27 video.html,1.87,1.88
Diego Biurrun CVS
diego at mplayerhq.hu
Sun Aug 11 20:27:42 CEST 2002
Update of /cvsroot/mplayer/main/DOCS
In directory mail:/var/tmp.root/cvs-serv25760
Modified Files:
codecs.html documentation.html encoding.html formats.html
sound.html users_against_developers.html video.html
Log Message:
Another big batch of cosmetics *only*.
2 character indentation everywhere, 2 blank lines before new sections.
The docs should now have a nice and uniform look.
Index: codecs.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/codecs.html,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- codecs.html 10 Aug 2002 20:26:43 -0000 1.76
+++ codecs.html 11 Aug 2002 18:27:38 -0000 1.77
@@ -15,8 +15,8 @@
<P><B><A NAME="video_codecs">2.2.1 Video codecs</A></B></P>
-<P>See the <A HREF="http://www.mplayerhq.hu/DOCS/codecs-status.html">codec status table</A> for the complete,
-daily generated list!!!</P>
+<P>See the <A HREF="http://www.mplayerhq.hu/DOCS/codecs-status.html">codec status table</A>
+ for the complete, daily generated list!!!</P>
<P>The most important ones above all:</P>
<UL>
@@ -34,13 +34,14 @@
<LI>RealVideo 1.0 codec from libavcodec, and RealVideo 2.0, 3.0 codecs using
RealPlayer libraries</LI>
<LI>native decoder for HuffYUV</LI>
- <LI>Various old simple RLE-like formats</LI>
+ <LI>various old simple RLE-like formats</LI>
</UL>
<P>If you have a Win32 codec not listed here which is not supported yet, please
read the <A HREF="#importing">codec importing HOWTO</A> and help us add support
for it!</P>
+
<P><B><A NAME="divx">2.2.1.1 DivX4/DivX5</A></B></P>
<P>This section contains information about the DivX4 and DivX5 codecs of
@@ -73,13 +74,13 @@
<P>DivX4Linux works in two modes:</P>
<TABLE BORDER=0>
-<TR><TD> </TD><TD VALIGN=top><CODE>-vc odivx</CODE></TD><TD> </TD>
-<TD>Uses the codec in OpenDivX fashion. In this case it
-produces YV12 images in its own buffer, and <B>MPlayer</B> does colorspace
-conversion via libvo. (<B>FAST, RECOMMENDED!</B>)</TD></TR>
-<TR><TD></TD><TD VALIGN=top><CODE>-vc divx4</CODE></TD><TD></TD>
-<TD>Uses the colorspace conversion of the codec.
-In this mode you can use YUY2/UYVY, too. (<B>SLOW</B>)</TD></TR>
+ <TR><TD> </TD><TD VALIGN=top><CODE>-vc odivx</CODE></TD><TD> </TD>
+ <TD>Uses the codec in OpenDivX fashion. In this case it
+ produces YV12 images in its own buffer, and <B>MPlayer</B> does colorspace
+ conversion via libvo. (<B>FAST, RECOMMENDED!</B>)</TD></TR>
+ <TR><TD></TD><TD VALIGN=top><CODE>-vc divx4</CODE></TD><TD></TD>
+ <TD>Uses the colorspace conversion of the codec.
+ In this mode you can use YUY2/UYVY, too. (<B>SLOW</B>)</TD></TR>
</TABLE>
<P>The <CODE>-vc odivx</CODE> method is usually faster, due to the fact that it
@@ -95,7 +96,7 @@
<P><B><A NAME="libavcodec">2.2.1.2 FFmpeg DivX/libavcodec</A></B></P>
<P><A HREF="http://ffmpeg.sourceforge.net">FFmpeg</A> contains an
- <B>opensource</B> codec package, which is capable of decoding video streams
+ <B>open source</B> codec package, which is capable of decoding video streams
encoded with
H263/MJPEG/RV10/DivX3/DivX4/DivX5/MP41/MP42/WMV1
codecs. Not only some of them can be encoded with, but it also offers higher
@@ -143,24 +144,22 @@
<UL>
<LI>Download the codecs you wish to use from the
- <A HREF="http://xanim.va.pubnix.com">XAnim site</A>. The <B>3ivx</B> codec
- is not there, but at the <A HREF="http://www.3ivx.com">3ivx site</A>.</LI>
-
+ <A HREF="http://xanim.va.pubnix.com">XAnim site</A>. The <B>3ivx</B> codec
+ is not there, but at the <A HREF="http://www.3ivx.com">3ivx site</A>.</LI>
<LI>Use the <CODE>--with-xanimlibdir</CODE> option to tell configure where
- to find the XAnim codecs. By default, it looks for them at
- <CODE>/usr/local/lib/xanim/mods, /usr/lib/xanim/mods and /usr/lib/xanim</CODE>.
- Alternatively you can set the environment variable <I>XANIM_MOD_DIR</I> to
- the directory of the XAnim codecs.</LI>
-
+ to find the XAnim codecs. By default, it looks for them at
+ <CODE>/usr/local/lib/xanim/mods, /usr/lib/xanim/mods and /usr/lib/xanim</CODE>.
+ Alternatively you can set the environment variable <I>XANIM_MOD_DIR</I> to
+ the directory of the XAnim codecs.</LI>
<LI>Rename/symlink the files, cutting out the architecture stuff, so they will
- have filenames like these: <CODE>vid_cvid.xa, vid_h263.xa, vid_iv50.xa</CODE>
-
+ have filenames like these: <CODE>vid_cvid.xa, vid_h263.xa, vid_iv50.xa</CODE>.</LI>
</UL>
<P>XAnim is video codec family number 10, so you may want to use the <CODE>-vfm 10</CODE>
option to tell <B>MPlayer</B> to use them if possible.</P>
-<P>Tested codecs include: <B>Indeo 3.2</B>, <B>4.1</B>, <B>5.0</B>, <B>CVID</B>, <B>3ivX</B>, <B>h263</B>.</P>
+<P>Tested codecs include: <B>Indeo 3.2</B>, <B>4.1</B>, <B>5.0</B>, <B>CVID</B>,
+ <B>3ivX</B>, <B>h263</B>.</P>
<P><B><A NAME="vivo_video">2.2.1.4 VIVO video</A></B></P>
@@ -203,6 +202,7 @@
<P><B><A NAME="realvideo">2.2.1.8 RealVideo</A></B></P>
<B>MPlayer</B> supports decoding all versions of RealVideo:
+
<UL>
<LI>RealVideo 1.0 (fourcc RV10) - en/decoding supported by <B>libavcodec</B></LI>
<LI>RealVideo 2.0 (fourcc RV20) - decoding supported by <B>RealPlayer libraries</B></LI>
@@ -231,35 +231,38 @@
have the same origin.</P>
<P><B>Advantages:</B></P>
- <UL>
- <LI>open source</LI>
- <LI>its API is compatible with DivX4 so adding support for
- it is easy</LI>
- <LI>2-pass encoding support</LI>
- <LI>nice encoding quality, higher speed than DivX4 (you can optimize it for
- your box while compiling)</LI>
- </UL>
+
+<UL>
+ <LI>open source</LI>
+ <LI>its API is compatible with DivX4 so adding support for
+ it is easy</LI>
+ <LI>2-pass encoding support</LI>
+ <LI>nice encoding quality, higher speed than DivX4 (you can optimize it for
+ your box while compiling)</LI>
+</UL>
<P><B>Disadvantages:</B></P>
- <UL>
- <LI>currently it does not properly <B>decode</B> all DivX/DivX4 files (no problem as libavcodec can play them)</LI>
- <LI>you have to choose between DivX4 <B>OR</B> XViD support at
- compiletime</LI>
- <LI>under development</LI>
- </UL>
+
+<UL>
+ <LI>currently it does not properly <B>decode</B> all DivX/DivX4 files (no problem as libavcodec can play them)</LI>
+ <LI>you have to choose between DivX4 <B>OR</B> XViD support at
+ compiletime</LI>
+ <LI>under development</LI>
+</UL>
<P><B>Installation:</B> It is currently available only from CVS. Here are the
download and installation instructions:</P>
- <OL>
- <LI><CODE>cvs -z3 -d:pserver:anonymous at cvs.xvid.org:/xvid login</CODE></LI>
- <LI><CODE>cvs -z3 -d:pserver:anonymous at cvs.xvid.org:/xvid co xvidcore</CODE></LI>
- <LI><CODE>cd xvidcore/build/generic</CODE></LI>
- <LI>Edit <CODE>Makefile.linux</CODE> to fit your needs.</LI>
- <LI><CODE>make -f Makefile.linux</CODE></LI>
- <LI>Get <CODE>encore2.h</CODE> and <CODE>decore.h</CODE> from the DivX4Linux
- package, and copy them to <CODE>/usr/local/include/</CODE>.</LI>
- <LI>Recompile <B>MPlayer</B> with <CODE>--with-xvidcore=/path/to/libcore.a</CODE>.</LI>
- </OL>
+
+<OL>
+ <LI><CODE>cvs -z3 -d:pserver:anonymous at cvs.xvid.org:/xvid login</CODE></LI>
+ <LI><CODE>cvs -z3 -d:pserver:anonymous at cvs.xvid.org:/xvid co xvidcore</CODE></LI>
+ <LI><CODE>cd xvidcore/build/generic</CODE></LI>
+ <LI>Edit <CODE>Makefile.linux</CODE> to fit your needs.</LI>
+ <LI><CODE>make -f Makefile.linux</CODE></LI>
+ <LI>Get <CODE>encore2.h</CODE> and <CODE>decore.h</CODE> from the DivX4Linux
+ package, and copy them to <CODE>/usr/local/include/</CODE>.</LI>
+ <LI>Recompile <B>MPlayer</B> with <CODE>--with-xvidcore=/path/to/libcore.a</CODE>.</LI>
+</OL>
<P><B><A NAME="sorenson">2.2.1.10 Sorenson</A></B></P>
@@ -268,14 +271,16 @@
able to decode the first version (SVQ1) with a native decoder.</P>
<P><B>Advantages:</B></P>
- <UL>
- <LI>Fast, even old Macintosh machines were able to decode it.</LI>
- </UL>
+
+<UL>
+ <LI>Fast, even old Macintosh machines were able to decode it.</LI>
+</UL>
<P><B>Disadvantages:</B></P>
- <UL>
- <LI>SVQ3 is still not reverse engineered.</LI>
- </UL>
+
+<UL>
+ <LI>SVQ3 is still not reverse engineered.</LI>
+</UL>
<P><B>Installation:</B> it's compiled and usable per default.</P>
@@ -283,6 +288,7 @@
<P><B><A NAME="audio_codecs">2.2.2 Audio codecs</A></B></P>
<P>The most important audio codecs above all:<BR></P>
+
<UL>
<LI>MPEG layer 2, and layer 3 (MP3) audio (<B>native</B> code, with
MMX/SSE/3DNow! optimization)</LI>
@@ -356,6 +362,7 @@
<P><B><A NAME="realaudio">2.2.2.5 RealAudio</A></B></P>
<B>MPlayer</B> supports decoding nearly all versions of RealAudio:
+
<UL>
<LI>RealAudio DNET - decoding supported by <B>liba52</B></LI>
<LI>RealAudio Cook - decoding supported by <B>RealPlayer libraries</B></LI>
@@ -368,30 +375,32 @@
<P><B><A NAME="importing">2.2.3 Win32 codec importing HOWTO</A></B></P>
+
<P><B><A NAME="importing_vfw">2.2.3.1 VFW codecs</A></B></P>
<P>VFW (Video for Windows) is the old Video API for Windows. Its codecs have
-the .DLL or (rarely) .DRV extension.
-If <B>MPlayer</B> fails at playing your AVI with this kind of message:</P>
+ the .DLL or (rarely) .DRV extension.
+ If <B>MPlayer</B> fails at playing your AVI with this kind of message:</P>
<P> <CODE>UNKNOWN video codec: HFYU (0x55594648)</CODE></P>
<P>It means your AVI is encoded with a codec which has the HFYU fourcc (HFYU =
-HuffYUV codec, DIV3 = DivX Low Motion, etc...). Now that you know this, you
-have to find out which DLL Windows loads in order to play this file. In our
-case, the <CODE>system.ini</CODE> contains this information in a line that reads:</P>
+ HuffYUV codec, DIV3 = DivX Low Motion, etc...). Now that you know this, you
+ have to find out which DLL Windows loads in order to play this file. In our
+ case, the <CODE>system.ini</CODE> contains this information in a line that
+ reads:</P>
<P> <CODE>VIDC.HFYU=huffyuv.dll</CODE></P>
<P>So you need the <CODE>huffyuv.dll</CODE> file. Note that the audio codecs are
-specified by the MSACM prefix:</P>
+ specified by the MSACM prefix:</P>
<P> <CODE>msacm.l3acm=L3codeca.acm</CODE></P>
-<P>This is the MP3 codec.
-Now that you have all the necessary information (fourcc, codec file, sample AVI),
-submit your codec support request by mail, and upload these files to the FTP site:</P>
+<P>This is the MP3 codec. Now that you have all the necessary information
+ (fourcc, codec file, sample AVI), submit your codec support request by mail,
+ and upload these files to the FTP site:</P>
<P> <CODE>ftp://ftp.mplayerhq.hu/MPlayer/incoming/[codecname]/</CODE></P>
@@ -399,34 +408,37 @@
<P><B><A NAME="importing_directshow">2.2.3.2 DirectShow codecs</A></B></P>
<P>DirectShow is the newer Video API, which is even worse than its predecessor.
-Things are harder with DirectShow, since</P>
+ Things are harder with DirectShow, since</P>
+
<UL>
-<LI><CODE>system.ini</CODE> does not contain the needed information, instead it
-is stored in the registry and
-<LI>we need the GUID of the codec.
+ <LI><CODE>system.ini</CODE> does not contain the needed information, instead it
+ is stored in the registry and
+ <LI>we need the GUID of the codec.
</UL>
<P>Take a deep breath and start searching the registry...</P>
+
<UL>
-<LI>Start <CODE>regedit</CODE>.
-<LI>Press <CODE>Ctrl-f</CODE>, disable the first two checkboxes, and enable the
-third. Type in the fourcc of the codec (e.g. TM20).
-<LI>You should see a field which contains the path and the filename
-(e.g. <CODE>C:\WINDOWS\SYSTEM\TM20DEC.AX</CODE>).
-<LI>Now that you have the file, we need the GUID. Try searching again, but
-now search for the codec's name, not the fourcc. Its name can be acquired
-when Media Player is playing the file, by checking File->Properties->Advanced.
-If not, you are out of luck. Try guessing (e.g. search for TrueMotion).
-<LI>If the GUID is found you should see a FriendlyName and a CLSID
-field. Write down the 16 byte CLSID, this is the GUID we need.
+ <LI>Start <CODE>regedit</CODE>.
+ <LI>Press <CODE>Ctrl-f</CODE>, disable the first two checkboxes, and enable
+ the third. Type in the fourcc of the codec (e.g. TM20).
+ <LI>You should see a field which contains the path and the filename
+ (e.g. <CODE>C:\WINDOWS\SYSTEM\TM20DEC.AX</CODE>).
+ <LI>Now that you have the file, we need the GUID. Try searching again, but
+ now search for the codec's name, not the fourcc. Its name can be acquired
+ when Media Player is playing the file, by checking File -> Properties
+ -> Advanced.
+ If not, you are out of luck. Try guessing (e.g. search for TrueMotion).
+ <LI>If the GUID is found you should see a FriendlyName and a CLSID
+ field. Write down the 16 byte CLSID, this is the GUID we need.
</UL>
<P><B>Note:</B> If searching fails, try enabling all the checkboxes. You may have
-false hits, but you may get lucky...</P>
+ false hits, but you may get lucky...</P>
<P>Now that you have all the necessary information (fourcc, GUID, codec file,
-sample AVI), submit your codec support request by mail, and upload these files
-to the FTP site:</P>
+ sample AVI), submit your codec support request by mail, and upload these files
+ to the FTP site:</P>
<P> <CODE>ftp://ftp.mplayerhq.hu/MPlayer/incoming/[codecname]/</CODE></P>
Index: documentation.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/documentation.html,v
retrieving revision 1.286
retrieving revision 1.287
diff -u -r1.286 -r1.287
--- documentation.html 11 Aug 2002 15:49:42 -0000 1.286
+++ documentation.html 11 Aug 2002 18:27:38 -0000 1.287
@@ -9,14 +9,15 @@
<BODY>
-<CENTER><B>MPlayer - Movie Player for LINUX (C) 2000-2002 Arpad Gereoffy (A'rpi/ESP-team)</B><BR>
-<BR><A HREF="http://www.mplayerhq.hu">http://www.mplayerhq.hu</A><BR><BR>
-[ English ]
-<A HREF="Hungarian/documentation.html">[ Hungarian ]</A>
-<A HREF="German/documentation.html">[ German ]</A>
-<A HREF="French/documentation.html">[ French ]</A>
-<A HREF="Polish/documentation.html">[ Polish ]</A>
-<A HREF="Italian/documentation.html">[ Italian ]</A>
[...2108 lines suppressed...]
<P>First note: options -fs -vm and -zoom are just recommendations, not (yet)
-supported by all drivers. So it isn't a bug if it doesn't work.
-Only a few driver supports scaling/zooming, don't expect this from x11 or dga.</P>
+ supported by all drivers. So it isn't a bug if it doesn't work.
+ Only a few driver supports scaling/zooming, don't expect this from x11 or dga.</P>
<P>OSD/sub flickering:<BR>
-- x11 driver: sorry, it can't be fixed now<BR>
-- xv driver: use -double option</P>
+ - x11 driver: sorry, it can't be fixed now<BR>
+ - xv driver: use -double option</P>
<P>Green image using mga_vid (-vo mga / -vo xmga):<BR>
-- mga_vid misdetected your card's RAM amount, reload it using mga_ram_size option<BR>
-</P>
+ - mga_vid misdetected your card's RAM amount, reload it using mga_ram_size option</P>
</BODY>
</HTML>
Index: encoding.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/encoding.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- encoding.html 10 Aug 2002 20:26:43 -0000 1.54
+++ encoding.html 11 Aug 2002 18:27:38 -0000 1.55
@@ -12,6 +12,7 @@
<P><B><A NAME="encoding">2.4 Encoding with MEncoder</A></B></P>
+
<P><B><A NAME="overview">2.4.1 Overview</A></B></P>
<P><B>MEncoder</B> (<B>MPlayer</B>'s Movie Encoder) is a simple movie encoder,
@@ -22,6 +23,7 @@
<B>PCM</B>/<B>MP3</B>/<B>VBR MP3</B> audio. Also has powerful plugin system
for video manipulation.</P>
+
<P><B><A NAME="compilation">2.4.2 Compilation</A></B></P>
<UL>
@@ -55,6 +57,7 @@
<P>You are ready. As you probably know, other encoding tools need the
<I>avifile</I> library installed. <B>MEncoder</B> doesn't need it at all.</P>
+
<P><B><A NAME="features">2.4.3 MEncoder features</A></B></P>
<UL>
@@ -86,6 +89,7 @@
<LI>audio encoding from v4l (DONE for FreeBSD ?)</LI>
</UL>
+
<P><B><A NAME="2pass">2.4.3.1 Encoding 2 or 3-pass DivX4</A></B></P>
<P><U><B>2-pass encoding:</B></U> the name comes from the fact that this method
@@ -113,34 +117,34 @@
audio is encoded only once, unlike in 2-pass mode. The schematics:</P>
<TABLE>
-<TR>
- <TD> <CODE>rm frameno.avi</CODE></TD>
- <TD> <B>remove conflicting temporary file</B></TD>
-</TR>
-<TR>
- <TD> <CODE>mencoder <file/DVD> -ovc frameno -o
+ <TR>
+ <TD><CODE>rm frameno.avi</CODE></TD>
+ <TD><B>remove conflicting temporary file</B></TD>
+ </TR>
+ <TR>
+ <TD><CODE>mencoder <file/DVD> -ovc frameno -o
frameno.avi</CODE></TD>
- <TD> <B><U>First pass:</U> an audio-only avi file will be created, containing
- ONLY the requested audio stream. Don't forget <CODE>-lameopts</CODE>, if
- you need to set it. If you were encoding a long movie, MEncoder prints
- the recommended bitrate values for 650Mb, 700Mb, and 800Mb destination
- sizes, after this pass finishes.</B></TD>
-</TR>
-<TR>
- <TD> <CODE>mencoder <file/DVD> -oac copy -pass 1
+ <TD><B><U>First pass:</U> an audio-only avi file will be created, containing
+ ONLY the requested audio stream. Don't forget <CODE>-lameopts</CODE>, if
+ you need to set it. If you were encoding a long movie, MEncoder prints
+ the recommended bitrate values for 650Mb, 700Mb, and 800Mb destination
+ sizes, after this pass finishes.</B></TD>
+ </TR>
+ <TR>
+ <TD><CODE>mencoder <file/DVD> -oac copy -pass 1
-ovc divx4 -divx4opts br=<bitrate></CODE></TD>
- <TD> <B><U>Second pass:</U> alias the first pass of DivX4 video encoding.
- Optionally specify the video bitrate MEncoder printed at the end of the
- previous pass.</B></TD>
-</TR>
-<TR>
- <TD> <CODE>mencoder <file/DVD> -oac copy -pass 2
+ <TD><B><U>Second pass:</U> alias the first pass of DivX4 video encoding.
+ Optionally specify the video bitrate MEncoder printed at the end of the
+ previous pass.</B></TD>
+ </TR>
+ <TR>
+ <TD><CODE>mencoder <file/DVD> -oac copy -pass 2
-ovc divx4 -divx4opts br=<bitrate></CODE></TD>
- <TD> <B><U>Third pass:</U> alias the second pass of DivX4 video encoding.
- Optionally specify the video bitrate MEncoder printed at the end of the
- previous pass. In this pass, audio from <CODE>frameno.avi</CODE> will be
- inserted into the destination file.. and it's all ready!</B></TD>
-</TR>
+ <TD><B><U>Third pass:</U> alias the second pass of DivX4 video encoding.
+ Optionally specify the video bitrate MEncoder printed at the end of the
+ previous pass. In this pass, audio from <CODE>frameno.avi</CODE> will be
+ inserted into the destination file.. and it's all ready!</B></TD>
+ </TR>
</TABLE>
<P><B>Example for 3-pass encoding:</B></P>
@@ -153,8 +157,7 @@
mencoder -dvd 2
-lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 1<BR>
mencoder -dvd 2
- -lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 2</CODE>
-</P>
+ -lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 2</CODE></P>
<P><U><B>2 or 3-pass encoding using internal libavcodec controller:</B></U>
Optionally you can use libavcodec's internal 2 or 3-pass mode, it may give
@@ -177,6 +180,7 @@
movie.avi</CODE></LI>
</UL>
+
<P><B><A NAME="rescaling">2.4.3.2 Rescaling movies</A></B></P>
<P>Often the need to resize movie images' size emerges. Its reasons can be many,
@@ -265,8 +269,7 @@
<P><B>Explanation of the process</B></P>
<P><B>MEncoder</B> <I>decodes</I> the input image(s) with <CODE>libjpeg</CODE>
- (when decoding PNGs, it will use <B>libpng</B>).
-</P>
+ (when decoding PNGs, it will use <B>libpng</B>).</P>
<P><B>MEncoder</B> then feeds the decoded image to the chosen video compressor
(DivX4, Xvid, ffmpeg msmpeg4, etc...). Watch for the PNG decoder, as
@@ -349,116 +352,118 @@
<P>NOTE: for all available options, <B>read the man page!</B></P>
-<P>
- As <B>MEncoder</B> is built on the same codebase as <B>MPlayer</B>, there
+<P>As <B>MEncoder</B> is built on the same codebase as <B>MPlayer</B>, there
are many <B>MPlayer</B> options that have function in <B>MEncoder</B> too!
See, you can use <CODE>-sid</CODE> to rip a DVD with subtitles, or
- <CODE>-noidx</CODE> to disregard buggy index of input AVI. <B>Be smart!</B>
-</P>
+ <CODE>-noidx</CODE> to disregard buggy index of input AVI. <B>Be smart!</B></P>
<TABLE BORDER=1>
-<TR>
- <TD> <CODE>-ss</CODE> time</TD>
- <TD> start encoding from the given time (can start only from keyframes!)
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-endpos</CODE> time</TD>
- <TD> stop encoding at the given time. See the man page for examples!
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-o</CODE> filename</TD>
- <TD> specify output filename
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-sws</CODE> 0-2</TD>
- <TD> type of scaling method<BR>
- 0 - fast bilinear<BR>
- 1 - bilinear<BR>
- 2 - bicubic (best quality)<BR>
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-ovc</CODE> codecname</TD>
- <TD> Encode with the given codec (codec names are from codecs.conf). Examples:<BR>
- <B>help</B> - get list of available codecs<BR>
- <B>rawrgb</B> - ?<BR>
- <B>copy</B> - no encoding, just copy the stream (only from AVI/ASF now)<BR>
- <B>divx4</B> - encode to DivX4<BR>
- <B>lavc</B> - encode with a codec from libavcodec<BR>
- <B>vfw</B> - encode with a Windows DLL<BR>
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-oac</CODE> codecname</TD>
- <TD> Encode with the given codec (codec names are from codecs.conf). Examples:<BR>
- <B>help</B> - get list of available codecs<BR>
- <B>copy</B> - no encoding, just copy the stream (only from AVI/ASF now)<BR>
- <B>pcm</B> - encode to uncompressed PCM<BR>
- <B>mp3lame</B> - encode to MP3 (using Lame)<BR>
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-mf</CODE> multifile options</TD>
- <TD> Used when encoding from multiple JPEG files. Its sub-options are:<BR>
- <B>on</B> - turns on multifile support<BR>
- <B>w</B>=<value> - width of the output file<BR>
- <B>h</B>=<value> - height of the output file<BR>
- <B>fps</B>=<value> - fps of the output file<BR>
- <B>type</B>=<value> - type of input files (available types: <CODE>jpeg</CODE>, <CODE>png</CODE>)<BR>
- </TD>
-</TR>
-
-<TR>
- <TD> <CODE>-divx4opts</CODE></TD>
- <TD> If encoding to DivX4, you can specify its parameters here, like:<BR>
- <CODE>-divx4opts br=1800:deinterlace:key=250</CODE><BR>
- Common options: <B>(for full list, check the man page!)</B><BR>
- <B>help</B> - get help<BR>
- <B>br</B>=<value> - specify bitrate in kbit <4-16000> or bit <16001-24000000><BR>
- <B>q</B>=<value> - quality (1-fastest, 5-best - default 5)<BR>
- <B>key</B>=<value> - keyframe interval<BR>
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-lavcopts</CODE></TD>
- <TD> If encoding with libavcodec, you can specify its parameters here, like:<BR>
- <CODE>-lavcopts vcodec=msmpeg4:vbitrate=1800:vhq:keyint=250</CODE><BR>
- Common options: <B>(for full list, check the man page!)</B><BR>
- <B>help</B> - get help<BR>
- <B>vcodec</B>=<value> - select videocodec (for the full list, see the libavcodec section above)<BR>
- <B>vbitrate</B>=<value> - specify bitrate in kbit <4-16000> or bit <16001-24000000><BR>
- <B>vhq</B> - high quality<BR>
- <B>keyint</B>=<value> - keyframe interval<BR>
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-lameopts</CODE></TD>
- <TD> If encoding to MP3 with libmp3lame, you can specify its parameters here, like:<BR>
- <CODE>-lameopts q=3</CODE><BR>
- <CODE>-lameopts br=192:cbr</CODE><BR>
- Common options: <B>(for full list, check the man page!)</B><BR>
- <B>help</B> - get help<BR>
- <B>cbr</B> - select <B>CBR</B> MP3 (default is <B>VBR</B>)<BR>
- <B>br</B>=<value> - specify bitrate in kbit <0-1024> (this is for <B>CBR</B> only!)<BR>
- <B>q</B>=<value> - quality (0-highest, 9-fastest - default 0) (this is for <B>VBR</B> only!)<BR>
- <B>vbr</B>=<value> - VBR sub-mode (3-ABR, best quality/speed) (this is for <B>VBR</B> only!)<BR>
- </TD>
-</TR>
-<TR>
- <TD> <CODE>-vobsubout</CODE> basename</TD>
- <TD> Specify the basename for the output <CODE>.idx</CODE> and <CODE>.sub</CODE> files. This turns off subtitle rendering on the encoded movie.</TD>
-</TR>
-<TR>
- <TD> <CODE>-vobsuboutindex</CODE> index</TD>
- <TD> Specify the index of the subtitles in the output files. Defaults to 0.</TD>
-</TR>
-<TR>
- <TD> <CODE>-vobsuboutid</CODE> langid</TD>
- <TD> Specify the language two letter code for the subtitles. This overrides what is read from the DVD or the <CODE>.ifo</CODE> file.</TD>
-</TR>
+ <TR>
+ <TD><CODE>-ss</CODE> time</TD>
+ <TD>start encoding from the given time (can start only from keyframes!)
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-endpos</CODE> time</TD>
+ <TD>stop encoding at the given time. See the man page for examples!
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-o</CODE> filename</TD>
+ <TD>specify output filename
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-sws</CODE> 0-2</TD>
+ <TD>type of scaling method<BR>
+ 0 - fast bilinear<BR>
+ 1 - bilinear<BR>
+ 2 - bicubic (best quality)<BR>
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-ovc</CODE> codecname</TD>
+ <TD>Encode with the given codec (codec names are from codecs.conf). Examples:<BR>
+ <B>help</B> - get list of available codecs<BR>
+ <B>rawrgb</B> - ?<BR>
+ <B>copy</B> - no encoding, just copy the stream (only from AVI/ASF now)<BR>
+ <B>divx4</B> - encode to DivX4<BR>
+ <B>lavc</B> - encode with a codec from libavcodec<BR>
+ <B>vfw</B> - encode with a Windows DLL<BR>
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-oac</CODE> codecname</TD>
+ <TD>Encode with the given codec (codec names are from codecs.conf). Examples:<BR>
+ <B>help</B> - get list of available codecs<BR>
+ <B>copy</B> - no encoding, just copy the stream (only from AVI/ASF now)<BR>
+ <B>pcm</B> - encode to uncompressed PCM<BR>
+ <B>mp3lame</B> - encode to MP3 (using Lame)<BR>
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-mf</CODE> multifile options</TD>
+ <TD>Used when encoding from multiple JPEG files. Its sub-options are:<BR>
+ <B>on</B> - turns on multifile support<BR>
+ <B>w</B>=<value> - width of the output file<BR>
+ <B>h</B>=<value> - height of the output file<BR>
+ <B>fps</B>=<value> - fps of the output file<BR>
+ <B>type</B>=<value> - type of input files (available types:
+ <CODE>jpeg</CODE>, <CODE>png</CODE>)<BR>
+ </TD>
+ </TR>
+
+ <TR>
+ <TD><CODE>-divx4opts</CODE></TD>
+ <TD>If encoding to DivX4, you can specify its parameters here, like:<BR>
+ <CODE>-divx4opts br=1800:deinterlace:key=250</CODE><BR>
+ Common options: <B>(for full list, check the man page!)</B><BR>
+ <B>help</B> - get help<BR>
+ <B>br</B>=<value> - specify bitrate in kbit <4-16000>
+ or bit <16001-24000000><BR>
+ <B>q</B>=<value> - quality (1-fastest, 5-best - default 5)<BR>
+ <B>key</B>=<value> - keyframe interval<BR>
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-lavcopts</CODE></TD>
+ <TD>If encoding with libavcodec, you can specify its parameters here, like:<BR>
+ <CODE>-lavcopts vcodec=msmpeg4:vbitrate=1800:vhq:keyint=250</CODE><BR>
+ Common options: <B>(for full list, check the man page!)</B><BR>
+ <B>help</B> - get help<BR>
+ <B>vcodec</B>=<value> - select videocodec (for the full list, see the libavcodec section above)<BR>
+ <B>vbitrate</B>=<value> - specify bitrate in kbit <4-16000> or bit <16001-24000000><BR>
+ <B>vhq</B> - high quality<BR>
+ <B>keyint</B>=<value> - keyframe interval<BR>
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-lameopts</CODE></TD>
+ <TD>If encoding to MP3 with libmp3lame, you can specify its parameters here, like:<BR>
+ <CODE>-lameopts q=3</CODE><BR>
+ <CODE>-lameopts br=192:cbr</CODE><BR>
+ Common options: <B>(for full list, check the man page!)</B><BR>
+ <B>help</B> - get help<BR>
+ <B>cbr</B> - select <B>CBR</B> MP3 (default is <B>VBR</B>)<BR>
+ <B>br</B>=<value> - specify bitrate in kbit <0-1024> (this is for <B>CBR</B> only!)<BR>
+ <B>q</B>=<value> - quality (0-highest, 9-fastest - default 0) (this is for <B>VBR</B> only!)<BR>
+ <B>vbr</B>=<value> - VBR sub-mode (3-ABR, best quality/speed) (this is for <B>VBR</B> only!)<BR>
+ </TD>
+ </TR>
+ <TR>
+ <TD><CODE>-vobsubout</CODE> basename</TD>
+ <TD>Specify the basename for the output <CODE>.idx</CODE> and <CODE>.sub</CODE>
+ files. This turns off subtitle rendering on the encoded movie.</TD>
+ </TR>
+ <TR>
+ <TD><CODE>-vobsuboutindex</CODE> index</TD>
+ <TD>Specify the index of the subtitles in the output files. Defaults to 0.</TD>
+ </TR>
+ <TR>
+ <TD><CODE>-vobsuboutid</CODE> langid</TD>
+ <TD>Specify the language two letter code for the subtitles. This overrides
+ what is read from the DVD or the <CODE>.ifo</CODE> file.</TD>
+ </TR>
</TABLE>
<P><B><A NAME="examples">2.4.6 Examples</A></B></P>
Index: formats.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/formats.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- formats.html 10 Aug 2002 20:26:43 -0000 1.39
+++ formats.html 11 Aug 2002 18:27:38 -0000 1.40
@@ -19,8 +19,7 @@
<P>You see, a <B>codec</B> is not the same as a <B>file format</B>.<BR>
Examples of video <B>codecs</B> are: MPEG1, MPEG2, DivX, Indeo5, 3ivx.<BR>
- Examples of file <B>formats</B> are: MPG, AVI, ASF.<BR>
-</P>
+ Examples of file <B>formats</B> are: MPG, AVI, ASF.</P>
<P>In theory, you can put an OpenDivX video and MP3 audio into an <B>MPG</B>
format file. However, most players will not play it, since they expect MPEG1
@@ -72,7 +71,7 @@
supports one video stream and 0 to 99 audio streams. File size is limited to
2GB, but there exists an extension allowing bigger files called
<B>OpenDMS</B>. Microsoft currently strongly discourages its use and
- encourages ASF/WMV. Not that anybody cares.<BR>
+ encourages ASF/WMV. Not that anybody cares.</P>
<P>There is a hack that allows AVI files to contain an Ogg Vorbis audio
stream, but makes them incompatible with standard AVI. <B>MPlayer</B>
@@ -194,8 +193,7 @@
format used by the <A HREF="http://mjpeg.sf.net">mjpegtools programs</A>.
You can grab, produce, filter or encode video in this format using these
tools. The file format is really a sequence of uncompressed YUV 4:2:0
- images.
-</P>
+ images.</P>
<P><B><A NAME="film">2.1.1.10 FILM files</A></B></P>
Index: sound.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/sound.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- sound.html 10 Aug 2002 20:26:43 -0000 1.46
+++ sound.html 11 Aug 2002 18:27:38 -0000 1.47
@@ -13,24 +13,21 @@
<P><B><A NAME="audio">2.3.2 Audio output devices</A></B></P>
<P><B>MPlayer</B>'s audio interface is called <I>libao2</I>. It currently
-contains these drivers:</P>
+ contains these drivers:</P>
<TABLE BORDER=0>
-
-<TR><TD COLSPAN=4><P><B>General:</B></P></TD></TR>
-
-<TR><TD> </TD><TD VALIGN=top>oss</TD><TD> </TD><TD>OSS (ioctl) driver (supports hardware AC3 passthrough)</TD></TR>
-<TR><TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD>SDL driver (supports up/downsampling, <B>ESD</B>, <B>ARTS</B> etc)</TD></TR>
-<TR><TD></TD><TD VALIGN=top>nas</TD><TD></TD><TD>NAS (Network Audio System) driver</TD></TR>
-<TR><TD></TD><TD VALIGN=top>alsa5</TD><TD></TD><TD>native ALSA 0.5 driver</TD></TR>
-<TR><TD></TD><TD VALIGN=top>alsa9</TD><TD></TD><TD>native ALSA 0.9 driver (supports hardware AC3 passthrough)</TD></TR>
-<TR><TD></TD><TD VALIGN=top>sun</TD><TD></TD><TD>SUN audio driver (<CODE>/dev/audio</CODE>) for BSD and Solaris8 users</TD></TR>
-<TR><TD></TD><TD VALIGN=top>arts</TD><TD></TD><TD>native ARTS driver (mostly for KDE users)</TD></TR>
-
+ <TR><TD COLSPAN=4><P><B>General:</B></P></TD></TR>
+ <TR><TD> </TD><TD VALIGN=top>oss</TD><TD> </TD><TD>OSS (ioctl) driver (supports hardware AC3 passthrough)</TD></TR>
+ <TR><TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD>SDL driver (supports up/downsampling, <B>ESD</B>, <B>ARTS</B> etc)</TD></TR>
+ <TR><TD></TD><TD VALIGN=top>nas</TD><TD></TD><TD>NAS (Network Audio System) driver</TD></TR>
+ <TR><TD></TD><TD VALIGN=top>alsa5</TD><TD></TD><TD>native ALSA 0.5 driver</TD></TR>
+ <TR><TD></TD><TD VALIGN=top>alsa9</TD><TD></TD><TD>native ALSA 0.9 driver (supports hardware AC3 passthrough)</TD></TR>
+ <TR><TD></TD><TD VALIGN=top>sun</TD><TD></TD><TD>SUN audio driver (<CODE>/dev/audio</CODE>) for BSD and Solaris8 users</TD></TR>
+ <TR><TD></TD><TD VALIGN=top>arts</TD><TD></TD><TD>native ARTS driver (mostly for KDE users)</TD></TR>
</TABLE>
<P>Fact is, Linux sound card drivers have compatibility problems.
-It <B>may</B> take a while to find your optimal settings.</P>
+ It <B>may</B> take a while to find your optimal settings.</P>
<UL>
<LI>If you have an OSS driver, first try <CODE>-ao oss</CODE> (this is the
@@ -55,70 +52,70 @@
<P><B><A NAME="experiences">2.3.2.1 Sound Card experiences, recommendations</A></B></P>
<TABLE BORDER=0 WIDTH="100%">
-<TR><TD COLSPAN=3><B>VIA onboard chipset (via82cxxx) 48kHz only</B></TD><TR>
-<TD></TD><TD>Driver:</TD><TD> from <A HREF="http://sourceforge.net/project/showfiles.php?group_id=3242&release_id=59602">here</A></TD><TR>
+ <TR><TD COLSPAN=3><B>VIA onboard chipset (via82cxxx) 48kHz only</B></TD><TR>
+ <TD></TD><TD>Driver:</TD><TD> from <A HREF="http://sourceforge.net/project/showfiles.php?group_id=3242&release_id=59602">here</A></TD><TR>
-<TD COLSPAN=3><B>Aureal Vortex 2</B></TD><TR>
-<TD> </TD><TD>OSS:</TD><TD>no driver</TD><TR>
-<TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>no driver</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
-<TD></TD><TD>Driver:</TD><TD><A HREF="http://aureal.sourceforge.net">aureal.sourceforge.net</A></TD><TR>
-<TD></TD><TD>Driver2:</TD><TD> from <A HREF="http://makacs.poliod.hu/~pontscho/aureal/au88xx-1.1.3.tar.bz2">here</A><BR>
-(<I>buffer size increased to 32k</I>)</TD><TR>
-
-<TD COLSPAN=3><B>GUS PnP</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>no driver</TD><TR>
-<TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>OK</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
-
-<TD COLSPAN=3><B>SB Live!</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>Analog OK, SP/DIF not working</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>Both OK</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>192</TD><TR>
-
-<TD COLSPAN=3><B>SB AWE 64</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>max 44kHz</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>48kHz sounds bad</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
-
-<TD COLSPAN=3><B>Gravis UltraSound ACE</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>not OK</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>OK</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>44</TD><TR>
-
-<TD COLSPAN=3><B>Gravis UltraSound MAX</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>OK</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
-
-<TD COLSPAN=3><B>ESS 688</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>OK</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
-
-<TD COLSPAN=3><B>C-Media cards (which ones?)</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>not OK (hissing) (?)</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>?</TD><TR>
-
-<TD COLSPAN=3><B>Yamaha cards (*ymf*)</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>not OK (?) (maybe <CODE>-ao sdl</CODE>)</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>OK only with ALSA 0.5 with OSS emulation <B>AND</B> <CODE>-ao sdl</CODE> (!) (?)</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>?</TD><TR>
-
-<TD COLSPAN=3><B>Cards with envy24 chips (like Terratec EWS88MT)</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>?</TD><TR>
-<TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>?</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>?</TD><TR>
-
-<TD COLSPAN=3><B>PC Speaker or DAC</B></TD><TR>
-<TD></TD><TD>OSS:</TD><TD>OK (Use the SDL driver: <CODE>-ao sdl</CODE>)</TD><TR>
-<TD></TD><TD>ALSA:</TD><TD>no driver</TD><TR>
-<TD></TD><TD>Max kHz:</TD><TD>The driver emulates 44.1, maybe more.</TD><TR>
-<TD></TD><TD>Driver:</TD><TD><A HREF="ftp://ftp.infradead.org/pub/pcsp">ftp://ftp.infradead.org/pub/pcsp</A></TD>
+ <TD COLSPAN=3><B>Aureal Vortex 2</B></TD><TR>
+ <TD> </TD><TD>OSS:</TD><TD>no driver</TD><TR>
+ <TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>no driver</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
+ <TD></TD><TD>Driver:</TD><TD><A HREF="http://aureal.sourceforge.net">aureal.sourceforge.net</A></TD><TR>
+ <TD></TD><TD>Driver2:</TD><TD> from <A HREF="http://makacs.poliod.hu/~pontscho/aureal/au88xx-1.1.3.tar.bz2">here</A><BR>
+ (<I>buffer size increased to 32k</I>)</TD><TR>
+
+ <TD COLSPAN=3><B>GUS PnP</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>no driver</TD><TR>
+ <TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
+
+ <TD COLSPAN=3><B>SB Live!</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>Analog OK, SP/DIF not working</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>Both OK</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>192</TD><TR>
+
+ <TD COLSPAN=3><B>SB AWE 64</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>max 44kHz</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>48kHz sounds bad</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
+
+ <TD COLSPAN=3><B>Gravis UltraSound ACE</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>not OK</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>44</TD><TR>
+
+ <TD COLSPAN=3><B>Gravis UltraSound MAX</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
+
+ <TD COLSPAN=3><B>ESS 688</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR>
+
+ <TD COLSPAN=3><B>C-Media cards (which ones?)</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>not OK (hissing) (?)</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>?</TD><TR>
+
+ <TD COLSPAN=3><B>Yamaha cards (*ymf*)</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>not OK (?) (maybe <CODE>-ao sdl</CODE>)</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>OK only with ALSA 0.5 with OSS emulation <B>AND</B> <CODE>-ao sdl</CODE> (!) (?)</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>?</TD><TR>
+
+ <TD COLSPAN=3><B>Cards with envy24 chips (like Terratec EWS88MT)</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>?</TD><TR>
+ <TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>?</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>?</TD><TR>
+
+ <TD COLSPAN=3><B>PC Speaker or DAC</B></TD><TR>
+ <TD></TD><TD>OSS:</TD><TD>OK (Use the SDL driver: <CODE>-ao sdl</CODE>)</TD><TR>
+ <TD></TD><TD>ALSA:</TD><TD>no driver</TD><TR>
+ <TD></TD><TD>Max kHz:</TD><TD>The driver emulates 44.1, maybe more.</TD><TR>
+ <TD></TD><TD>Driver:</TD><TD><A HREF="ftp://ftp.infradead.org/pub/pcsp">ftp://ftp.infradead.org/pub/pcsp</A></TD>
</TABLE>
<UL>
@@ -144,28 +141,23 @@
card. They are enabled using the <CODE>-aop</CODE> switch which takes a
<CODE>list=plugin1,plugin2,...</CODE> argument. The <CODE>list</CODE> argument
is required and determines which plugins should be used and in which order they
- should be executed. Example:
-</P>
+ should be executed. Example:</P>
<P> <CODE>mplayer media.avi -aop list=resample,format</CODE></P>
<P>would run the sound through the resampling plugin followed by the format
- plugin.
-</P>
+ plugin.</P>
<P>The plugins can also have switches that change their behavior. These
switches are explained in detail in the sections below. A plugin will execute
using default settings if its switches are omitted. Here is an example of how
- to use plugins in combination with plugin specific switches:
-</P>
+ to use plugins in combination with plugin specific switches:</P>
<P> <CODE>mplayer media.avi -aop
- list=resample,format:fout=44100:format=0x8</CODE>
-</P>
+ list=resample,format:fout=44100:format=0x8</CODE></P>
<P>would set the output frequency of the resample plugin to 44100Hz and the
- output format of the format plugin to AFMT_U8.
-</P>
+ output format of the format plugin to AFMT_U8.</P>
<P>Currently audio plugins can not be used in <B>MEncoder</B>.</P>
@@ -179,26 +171,26 @@
the sample frequency explicitly. This plugin has one switch:
<CODE>fout</CODE> which is used for setting the desired output sample
frequency. It defaults to 48kHz, and is given in
- <Hz>.
-</P>
+ <Hz>.</P>
<P>Usage:<BR>
- <CODE>mplayer media.avi -aop list=resample:fout=<required
+ <CODE>mplayer media.avi -aop list=resample:fout=<required
frequency in Hz, like 44100></CODE></P>
<P>Note that the output frequency should not be scaled up from the default value.
Scaling up will cause the audio and video streams to be played in slow motion
in addition to audio distortion.</P>
+
<P><B><A NAME="surround_decoding">2.3.2.2.2 Surround Sound decoding</A></B></P>
<P><B>MPlayer</B> has an audio plugin that can decode matrix encoded
-surround sound. Dolby Surround is an example of a matrix encoded format.
-Many files with 2 channel audio actually contain matrixed surround sound.
-To use this feature you need a sound card supporting at least 4 channels.</P>
+ surround sound. Dolby Surround is an example of a matrix encoded format.
+ Many files with 2 channel audio actually contain matrixed surround sound.
+ To use this feature you need a sound card supporting at least 4 channels.</P>
<P>Usage:<BR>
- <CODE>mplayer media.avi -aop list=surround</CODE></P>
+ <CODE>mplayer media.avi -aop list=surround</CODE></P>
<P><B><A NAME="format">2.3.2.2.3 Sample format converter</A></B></P>
@@ -209,13 +201,11 @@
has one switch, <CODE>format</CODE>, which can be set to one of the numbers
found in <CODE>libao2/afmt.h</CODE>. This plugin is hardly ever needed and is
intended for advanced users. Keep in mind that this plugin only changes the
- sample format and not the sample frequency or the number of channels.
-</P>
+ sample format and not the sample frequency or the number of channels.</P>
<P>Usage:<BR>
<CODE>mplayer media.avi -aop
- list=format:format=<required output format></CODE>
-</P>
+ list=format:format=<required output format></CODE></P>
<P><B><A NAME="delay">2.3.2.2.4 Delay</A></B></P>
@@ -241,33 +231,28 @@
external amplifier connected to the computer (this is almost always
the case), the noise level can be minimized by adjusting the master
level and the volume knob on the amplifier until the hissing noise
- in the background is gone.
-</P>
+ in the background is gone.</P>
<P>Usage:<BR>
<CODE>mplayer media.avi -aop
- list=volume:volume=<0-255></CODE>
-</P>
+ list=volume:volume=<0-255></CODE></P>
<P>This plugin also has compressor or "soft-clipping" capabilities.
Compression can be used if the dynamic range of the sound is very
high or if the dynamic range of the loudspeakers is very
low. Be aware that this feature creates distortion and should be
- considered a last resort.
-</P>
+ considered a last resort.</P>
<P>Usage:<BR>
<CODE>mplayer media.avi -aop
- list=volume:softclip</CODE>
-</P>
+ list=volume:softclip</CODE></P>
<P><B><A NAME="extrastereo">2.3.2.2.6 Extrastereo</A></B></P>
<P>This plugin (linearly) increases the difference between left and right
channels (like the XMMS extrastereo plugin) which gives some sort of "live"
- effect to playback.
-</P>
+ effect to playback.</P>
<P>Usage:<BR>
<CODE>mplayer media.avi -aop list=extrastereo</CODE><BR>
Index: users_against_developers.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/users_against_developers.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- users_against_developers.html 4 Aug 2002 22:13:09 -0000 1.26
+++ users_against_developers.html 11 Aug 2002 18:27:38 -0000 1.27
@@ -13,65 +13,66 @@
<P><B>In medias res</B></P>
<P>There are two major topics which always cause huge dispute and flame on the
-<A HREF="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</A>
-mailing list. Number one is the topic of the</P>
+ <A HREF="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</A>
+ mailing list. Number one is the topic of the</P>
-<P><A NAME=gcc><B>GCC 2.96 series</B></A></P>
+
+<P><A NAME="gcc"><B>GCC 2.96 series</B></A></P>
<P><B>The background:</B> The GCC <B>2.95</B> series is an official GNU release
-and version 2.95.3 of GCC is the most bug-free in that series.
-We have never noticed compilation problems that we could trace to gcc-2.95.3.
-Starting with Red Hat Linux 7.0, <B>Red Hat</B> included a heavily
-patched CVS version of GCC in their distribution and named it <B>2.96</B>. Red
-Hat included this version in the distribution because GCC 3.0 was not finished at
-the time, and they needed a compiler that worked well on all of their supported
-platforms, including IA64 and s390. The Linux distributor <B>Mandrake</B>
-also followed Red Hat's example and started shipping GCC 2.96 with their
-Linux-Mandrake 8.0 series. </P>
-
-<P><B>The statements:</B> The GCC team disclaimed any link with GCC 2.96 and issued an
-<A HREF="http://gcc.gnu.org/gcc-2.96.html">official response</A> to GCC 2.96.
-Many developers around the world began having problems with GCC 2.96, and
-started recommending other compilers. Examples are
-<A HREF="http://www.apachelabs.org/apr-mbox/200106.mbox/%3c20010623194228.C25512@ebuilt.com%3e">Apache</A>,
-<A HREF="http://www.mysql.com/downloads/mysql-3.23.html">MySQL</A>,
-<A HREF="http://avifile.sourceforge.net/news-old1.htm">avifile</A> and
-<A HREF="http://www.winehq.com/news/?view=92#RH 7.1 gcc fixes compiler bug">Wine</A>.
-Other interesting links are
-<A HREF="http://www.realtimelinux.org/archives/rtai/20017/0144.html">Real time Linux</A>,
-<A HREF="http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html">
-Linux kernel news flash about kernel 2.4.17</A> and
-<A HREF="http://www.voy.com/3516/572.html">Voy Forum</A>.
-<B>MPlayer</B> also suffered from intermittent problems that were all solved by
-switching to a different version of GCC. Several projects started implementing
-workarounds for some of the 2.96 issues, but we refused to fix other people's
-bugs, especially since some workarounds may imply a performance penalty.</P>
+ and version 2.95.3 of GCC is the most bug-free in that series.
+ We have never noticed compilation problems that we could trace to gcc-2.95.3.
+ Starting with Red Hat Linux 7.0, <B>Red Hat</B> included a heavily
+ patched CVS version of GCC in their distribution and named it <B>2.96</B>. Red
+ Hat included this version in the distribution because GCC 3.0 was not finished
+ at the time, and they needed a compiler that worked well on all of their
+ supported platforms, including IA64 and s390. The Linux distributor
+ <B>Mandrake</B> also followed Red Hat's example and started shipping GCC 2.96
+ with their Linux-Mandrake 8.0 series.</P>
+
+<P><B>The statements:</B> The GCC team disclaimed any link with GCC 2.96 and
+ issued an <A HREF="http://gcc.gnu.org/gcc-2.96.html">official response</A> to
+ GCC 2.96. Many developers around the world began having problems with GCC 2.96,
+ and started recommending other compilers. Examples are
+ <A HREF="http://www.apachelabs.org/apr-mbox/200106.mbox/%3c20010623194228.C25512@ebuilt.com%3e">Apache</A>,
+ <A HREF="http://www.mysql.com/downloads/mysql-3.23.html">MySQL</A>,
+ <A HREF="http://avifile.sourceforge.net/news-old1.htm">avifile</A> and
+ <A HREF="http://www.winehq.com/news/?view=92#RH 7.1 gcc fixes compiler bug">Wine</A>.
+ Other interesting links are
+ <A HREF="http://www.realtimelinux.org/archives/rtai/20017/0144.html">Real time Linux</A>,
+ <A HREF="http://www.atnf.csiro.au/people/rgooch/linux/docs/kernel-newsflash.html">
+ Linux kernel news flash about kernel 2.4.17</A> and
+ <A HREF="http://www.voy.com/3516/572.html">Voy Forum</A>.
+ <B>MPlayer</B> also suffered from intermittent problems that were all solved by
+ switching to a different version of GCC. Several projects started implementing
+ workarounds for some of the 2.96 issues, but we refused to fix other people's
+ bugs, especially since some workarounds may imply a performance penalty.</P>
<P>You can read about the other side of the story
-<A HREF="http://www.bero.org/gcc296.html">here</A>.
-GCC 2.96 does not allow | (pipe) characters in assembler comments
-because it supports Intel as well as AT&T Syntax and the | character is a
-symbol in the Intel variant. The problem is that it <B>silently</B> ignores the
-whole assembler block. This is supposedly fixed now, GCC prints a warning instead
-of skipping the block.</P>
+ <A HREF="http://www.bero.org/gcc296.html">here</A>.
+ GCC 2.96 does not allow | (pipe) characters in assembler comments
+ because it supports Intel as well as AT&T Syntax and the | character is a
+ symbol in the Intel variant. The problem is that it <B>silently</B> ignores the
+ whole assembler block. This is supposedly fixed now, GCC prints a warning instead
+ of skipping the block.</P>
<P><B>The present:</B> Red Hat says that GCC 2.96-85 and above is fixed. The
-situation has indeed improved, yet we still see problem reports on our
-mailing lists that disappear with a different compiler. In any case it does not
-matter any longer. Hopefully a maturing GCC 3.x will solve the issue for good.
-If you want to compile with 2.96 give the <CODE>--disable-gcc-checking</CODE>
-flag to configure. Remember that you are on your own and <B>do not report any
-bugs</B>. If you do, you will only get banned from our mailing list because
-we have had more than enough flame wars over GCC 2.96. Please let the matter rest.</P>
+ situation has indeed improved, yet we still see problem reports on our
+ mailing lists that disappear with a different compiler. In any case it does not
+ matter any longer. Hopefully a maturing GCC 3.x will solve the issue for good.
+ If you want to compile with 2.96 give the <CODE>--disable-gcc-checking</CODE>
+ flag to configure. Remember that you are on your own and <B>do not report any
+ bugs</B>. If you do, you will only get banned from our mailing list because
+ we have had more than enough flame wars over GCC 2.96. Please let the matter rest.</P>
<P>If you have problems with GCC 2.96, you can get 2.96-85 packages from the
-Red Hat <A HREF="ftp://updates.redhat.com">ftp server</A>, or just go for the
-3.0.4 packages offered for version 7.2 and later. You can also get gcc-3.1
-packages (unofficial, but working fine)
-<A HREF="ftp://people.redhat.com/jakub/gcc3/3.1-1/">here</A> and you can
-install them along the gcc-2.96 you already have. MPlayer will detect it and
-use 3.1 instead of 2.96. If you do not want to or cannot use the binary
-packages, here is how you can compile GCC 3.1 from source:</P>
+ Red Hat <A HREF="ftp://updates.redhat.com">ftp server</A>, or just go for the
+ 3.0.4 packages offered for version 7.2 and later. You can also get gcc-3.1
+ packages (unofficial, but working fine)
+ <A HREF="ftp://people.redhat.com/jakub/gcc3/3.1-1/">here</A> and you can
+ install them along the gcc-2.96 you already have. MPlayer will detect it and
+ use 3.1 instead of 2.96. If you do not want to or cannot use the binary
+ packages, here is how you can compile GCC 3.1 from source:</P>
<UL>
<LI>Go to the <A HREF="http://gcc.gnu.org/mirrors.html">GCC mirrors page</A>
@@ -95,92 +96,94 @@
<CODE>make install</CODE></LI>
</UL>
-<P><A NAME=binary><B>Binary distribution of MPlayer</B></A></P>
+
+<P><A NAME="binary"><B>Binary distribution of MPlayer</B></A></P>
<P>This was the second big problem but has been solved as of version
-0.90-pre1. <B>MPlayer</B> previously contained source from the OpenDivX project,
-which disallows binary redistribution. This code has been removed and you are now
-welcome to create binary packages as you see fit.</P>
+ 0.90-pre1. <B>MPlayer</B> previously contained source from the OpenDivX project,
+ which disallows binary redistribution. This code has been removed and you are now
+ welcome to create binary packages as you see fit.</P>
<P>Another impediment to binary redistribution was compiletime optimizations
-for CPU architecture. <B>MPlayer</B> now supports runtime CPU detection
-(specify the <CODE>--enable-runtime-cpudetection</CODE> option when
-compiling). It is disabled by default because it implies a small speed
-sacrifice, it is now possible to create binaries that run on different
-members of the Intel CPU family.</P>
+ for CPU architecture. <B>MPlayer</B> now supports runtime CPU detection
+ (specify the <CODE>--enable-runtime-cpudetection</CODE> option when
+ compiling). It is disabled by default because it implies a small speed
+ sacrifice, it is now possible to create binaries that run on different
+ members of the Intel CPU family.</P>
-<P><A NAME=nvidia><B>nVidia</B></A></P>
+
+<P><A NAME="nvidia"><B>nVidia</B></A></P>
<P>We dislike the fact that <A HREF="http://www.nvidia.com">nVidia</A>
- only provides binary drivers (for use with XFree86), which are often buggy.
-We have had many reports on
-<A HREF="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</A>
-about problems related to these closed-source drivers
-and their poor quality, instability and poor user and expert support.
-Here is an example from the
-<A HREF="http://www.nvnews.net/forum/showthread.php?s=fda5725bc2151e29453b2da3bd5d2930&threadid=14306">
-nVidia Linux Forum</A>.
-Many of these problems/issues keep appearing repeatedly.
-We have been contacted by nVidia lately, and they said these bugs
-do not exist, instability is caused by bad AGP chips, and they received
-no reports of driver bugs (like the purple line). So if you have a
-problem with your nVidia card, you are advised to update the nVidia driver
-and/or buy a new motherboard or ask nVidia to supply open-source drivers.
-In any case, if you are using the nVidia binary drivers and facing driver related problems,
-please be aware that you will receive very little help from our side because we have
-little power to help in this matter.</P>
+ only provides binary drivers (for use with XFree86), which are often buggy.
+ We have had many reports on
+ <A HREF="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</A>
+ about problems related to these closed-source drivers
+ and their poor quality, instability and poor user and expert support.
+ Here is an example from the
+ <A HREF="http://www.nvnews.net/forum/showthread.php?s=fda5725bc2151e29453b2da3bd5d2930&threadid=14306">
+ nVidia Linux Forum</A>.
+ Many of these problems/issues keep appearing repeatedly.
+ We have been contacted by nVidia lately, and they said these bugs
+ do not exist, instability is caused by bad AGP chips, and they received
+ no reports of driver bugs (like the purple line). So if you have a
+ problem with your nVidia card, you are advised to update the nVidia driver
+ and/or buy a new motherboard or ask nVidia to supply open-source drivers.
+ In any case, if you are using the nVidia binary drivers and facing driver related problems,
+ please be aware that you will receive very little help from our side because we have
+ little power to help in this matter.</P>
+
<P><A NAME="barr"><B>Joe Barr</B></A></P>
<P>Joe Barr became infamous by writing a less than favorable
-<A HREF="http://www.linuxworld.com/site-stories/2001/1214.mplayer.html">
-<B>MPlayer</B> review</A>. He found <B>MPlayer</B> hard to install, but then
-again he is not very fond of
-<A HREF="http://www.linuxworld.com/linuxworld/lw-2000-06/lw-06-exam.html">reading documentation</A>.
-He also concluded that the developers were unfriendly and the documentation
-incomplete and insulting. You be the judge.
-He went on to mention <B>MPlayer</B> negatively in his
-<A HREF="http://www.linuxworld.com/site-stories/2001/1227.predictions.html">10 Linux predictions for 2002</A>
-In a followup
-<A HREF="http://www.linuxworld.com/site-stories/2002/0125.xine.html">review of xine</A>
-he continued stirring up controversy. Ironically at the end of that article he
-quotes his exchange with Günter Bartsch, the original author of xine, that
-perfectly summarizes the whole situation:</P>
+ <A HREF="http://www.linuxworld.com/site-stories/2001/1214.mplayer.html">
+ <B>MPlayer</B> review</A>. He found <B>MPlayer</B> hard to install, but then
+ again he is not very fond of
+ <A HREF="http://www.linuxworld.com/linuxworld/lw-2000-06/lw-06-exam.html">reading documentation</A>.
+ He also concluded that the developers were unfriendly and the documentation
+ incomplete and insulting. You be the judge.
+ He went on to mention <B>MPlayer</B> negatively in his
+ <A HREF="http://www.linuxworld.com/site-stories/2001/1227.predictions.html">10 Linux predictions for 2002</A>
+ In a followup
+ <A HREF="http://www.linuxworld.com/site-stories/2002/0125.xine.html">review of xine</A>
+ he continued stirring up controversy. Ironically at the end of that article he
+ quotes his exchange with Günter Bartsch, the original author of xine, that
+ perfectly summarizes the whole situation:</P>
<BLOCKQUOTE>
-However, he also went on to say that he was "surprised" by my column about
-Mplayer and thought it was unfair, reminding me that it is a free software
-project. "If you don't like it," Bartsch said, "you're free not to use it."
+ However, he also went on to say that he was "surprised" by my column about
+ Mplayer and thought it was unfair, reminding me that it is a free software
+ project. "If you don't like it," Bartsch said, "you're free not to use it."
</BLOCKQUOTE>
<P>He does not reply to our mails. His editor does not reply to our mails.
-Here are some quotes from different people about Joe Barr, so you can form your
-own opinion:</P>
+ Here are some quotes from different people about Joe Barr, so you can form your
+ own opinion:</P>
<P>Marc Rassbach has <A HREF="http://daily.daemonnews.org/view_story.php3?story_id=2102">something to say</A>
-about the man
-</P>
+ about the man.</P>
<BLOCKQUOTE>
-You may all remember the LinuxWorld 2000, when he claimed that Linus T said
-that 'FreeBSD is just a handful of programmers'. Linus said NOTHING of the
-sort. When Joe was called on this, his reaction was to call BSD supporters
-assholes and jerks.
+ You may all remember the LinuxWorld 2000, when he claimed that Linus T said
+ that 'FreeBSD is just a handful of programmers'. Linus said NOTHING of the
+ sort. When Joe was called on this, his reaction was to call BSD supporters
+ assholes and jerks.
</BLOCKQUOTE>
<P>A <A HREF="http://www.mplayerhq.hu/pipermail/mplayer-users/2001-December/009118.html">quote</A>
-from Robert Munro on the
-<A HREF="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</A>
-mailing list:</P>
+ from Robert Munro on the
+ <A HREF="http://mplayerhq.hu/pipermail/mplayer-users/">mplayer-users</A>
+ mailing list:</P>
<BLOCKQUOTE>
-<P>He's interesting, but not good at avoiding, um... controversy. Joe Barr
-used to be one of the regulars on Will Zachmann's Canopus forum on Compuserve,
-years ago. He was an OS/2 advocate then (I was an OS/2 fan too).<P>
-
-<P>He used to go over-the-top, flaming people, and I suspect he had some hard
-times, then. He's mellowed some, judging by his columns recently. Moderately
-subtle humor was not his mode in those earlier days, not at all.</P>
+ <P>He's interesting, but not good at avoiding, um... controversy. Joe Barr
+ used to be one of the regulars on Will Zachmann's Canopus forum on Compuserve,
+ years ago. He was an OS/2 advocate then (I was an OS/2 fan too).<P>
+
+ <P>He used to go over-the-top, flaming people, and I suspect he had some hard
+ times, then. He's mellowed some, judging by his columns recently. Moderately
+ subtle humor was not his mode in those earlier days, not at all.</P>
</BLOCKQUOTE>
</HTML>
Index: video.html
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/video.html,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -r1.87 -r1.88
--- video.html 10 Aug 2002 20:26:43 -0000 1.87
+++ video.html 11 Aug 2002 18:27:38 -0000 1.88
@@ -23,8 +23,7 @@
<P><CODE>
--($:~)-- cat /proc/mtrr<BR>
reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9<BR>
- reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<BR>
-</CODE></P>
+ reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1</CODE></P>
<P>It's right, shows my Matrox G400 with 16MB memory. I did this from
XFree 4.x.x , which sets up MTRR registers automatically.</P>
@@ -49,12 +48,12 @@
size to hexadecimal, or use this table:</P>
<TABLE BORDER=0>
-<TR><TD> </TD><TD>1 MB</TD><TD WIDTH="10%"></TD><TD>0x100000</TD></TR>
-<TR><TD></TD><TD>2 MB</TD><TD></TD><TD>0x200000</TD></TR>
-<TR><TD></TD><TD>4 MB</TD><TD></TD><TD>0x400000</TD></TR>
-<TR><TD></TD><TD>8 MB</TD><TD></TD><TD>0x800000</TD></TR>
-<TR><TD></TD><TD>16 MB</TD><TD></TD><TD>0x1000000</TD></TR>
-<TR><TD></TD><TD>32 MB</TD><TD></TD><TD>0x2000000</TD></TR>
+ <TR><TD> </TD><TD>1 MB</TD><TD WIDTH="10%"></TD><TD>0x100000</TD></TR>
+ <TR><TD></TD><TD>2 MB</TD><TD></TD><TD>0x200000</TD></TR>
+ <TR><TD></TD><TD>4 MB</TD><TD></TD><TD>0x400000</TD></TR>
+ <TR><TD></TD><TD>8 MB</TD><TD></TD><TD>0x800000</TD></TR>
+ <TR><TD></TD><TD>16 MB</TD><TD></TD><TD>0x1000000</TD></TR>
+ <TR><TD></TD><TD>32 MB</TD><TD></TD><TD>0x2000000</TD></TR>
</TABLE>
@@ -70,6 +69,7 @@
stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat
/proc/cpuinfo</CODE>' to check it').</P>
+
<P><B><A NAME="xv">2.3.1.2 Xv</A></B></P>
<P>Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines
@@ -94,11 +94,9 @@
is always loaded, and doesn't mean that the _card's_ XVideo support is
loaded!</P>
</LI>
-
<LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the
part of the XFree86 distribution. It should display a long text, similar
to this:
-
<PRE>
X-Video Extension version 2.2
screen #0
@@ -124,16 +122,14 @@
type: YUV (planar)
(...etc...)
</PRE>
-
<P>It must support YUY2 packed, and YV12 planar pixel formats to be
usable with <B>MPlayer</B>.</P>
</LI>
-
<LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support.
./configure prints this.</LI>
-
</UL>
+
<P><B><A NAME="xv_3dfx">2.3.1.2.1 3dfx cards</A></B></P>
<P>Older 3dfx drivers were known to have problems with XVideo acceleration, it
@@ -185,7 +181,6 @@
default. It means that decoding speed (!) is synced to the monitor's
refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or
set refresh rate to n*(fps of the movie) Hz.</LI>
-
<LI>Radeon VE - currently only XFree86 CVS has driver for this card, version
4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can
happily get <B>accelerated</B> display, with or without <B>TV output</B>, and
@@ -202,14 +197,12 @@
<P>To allow playback of DVD sized content change your XF86Config like this:</P>
-<P>
- Section "Device"<BR>
+<P>Section "Device"<BR>
<I>[...]</I><BR>
Driver "neomagic"<BR>
<B>Option "OverlayMem" "829440"</B><BR>
<I>[...]</I><BR>
- EndSection
-</P>
+ EndSection</P>
<P><B><A NAME="xv_trident">2.3.1.2.6 Trident cards</A></B></P>
@@ -219,8 +212,10 @@
The latest CVS adds support for fullscreen xv support with the
Cyberblade XP card.</P>
+
<P><B><A NAME="dga">2.3.1.3 DGA</A></B></P>
+
<P><B><A NAME="dga_summary">2.3.1.3.1 Summary</A></B></P>
<P>This document tries to explain in some words what DGA is in general and what
@@ -278,10 +273,8 @@
chmod 750 /usr/local/bin/mplayer<BR>
chmod +s /usr/local/bin/mplayer</CODE></P>
-
<P>Now it works as a simple user, too.</P>
-
<P><B>!!!! BUT STAY TUNED !!!!</B><BR>
This is a <B>BIG</B> security risk! Never do this on a server or on a
computer can be accessed by more people than only you because they can gain
@@ -292,6 +285,7 @@
You should also try if the '-vo sdl:dga' option works for you! It's much
faster!!!</P>
+
<P><B><A NAME="dga_resolution">2.3.1.3.4 Resolution switching</A></B></P>
<P>The DGA driver allows for switching the resolution of the output signal.
@@ -309,6 +303,7 @@
<P>See appendix A for some sample modeline definitions.</P>
+
<P><B><A NAME="dga_mplayer">2.3.1.3.5 DGA & MPlayer</A></B></P>
<P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to
@@ -316,6 +311,7 @@
said is true for both; in the following sections I'll explain how the DGA
driver for <B>MPlayer</B> works.</P>
+
<P><B><A NAME="dga_features">2.3.1.3.6 Features of the DGA driver</A></B></P>
<P>The DGA driver is invoked by specifying -vo dga at the command line.
@@ -379,6 +375,7 @@
<P>I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2
CPUs might work at 400 MHZ and above.</P>
+
<P><B><A NAME="dga_bugs">2.3.1.3.8 Known bugs</A></B></P>
<P>Well, according to some developers of XFree, DGA is quite a beast. They
@@ -401,6 +398,7 @@
<LI>OSD only works with doublebuffering enabled.</LI>
</UL>
+
<P><B><A NAME="dga_future">2.3.1.3.9 Future work</A></B></P>
<UL>
@@ -439,7 +437,6 @@
and your CPU type. The X11 driver module (defined in XF86-Config) might
also help. Thanks!</P>
-
<P><I>Acki (acki at acki-netz.de, www.acki-netz.de)</I></P>
@@ -466,23 +463,19 @@
<P>Here are some notes about SDL out in <B>MPlayer</B>.</P>
-
-
<TABLE BORDER=0>
-<TR><TD COLSPAN=4><P><B>There are several command line switches for SDL:</B></P></TD></TR>
-<TR><TD> </TD><TD><CODE>-vo sdl:name</CODE></TD><TD> </TD><TD>
-specifies sdl video driver to use (i.e.. aalib, dga, x11)</TD></TR>
-<TR><TD></TD><TD><CODE>-ao sdl:name</CODE></TD><TD></TD><TD>specifies sdl audio driver to use (i.e.. dsp,
-esd, arts)</TD></TR>
-<TR><TD></TD><TD><CODE>-noxv</CODE></TD><TD></TD><TD>disables XVideo hardware acceleration</TD></TR>
-<TR><TD></TD><TD><CODE>-forcexv</CODE></TD><TD></TD><TD>tries to force XVideo acceleration</TD></TR>
-
-<TR><TD COLSPAN=4><P><B>SDL Keys:</B></P></TD></TR>
-
-<TR><TD></TD><TD><CODE>F</CODE></TD><TD></TD><TD>toggles fullscreen/windowed mode</TD></TR>
-<TR><TD></TD><TD><CODE>C</CODE></TD><TD></TD><TD>cycles available fullscreen modes</TD></TR>
-<TR><TD></TD><TD><CODE>W/S</CODE></TD><TD></TD><TD>mappings for * and / (mixer control)</TD></TR>
-
+ <TR><TD COLSPAN=4><P><B>There are several command line switches for SDL:</B></P></TD></TR>
+ <TR><TD> </TD><TD><CODE>-vo sdl:name</CODE></TD><TD> </TD><TD>
+ specifies sdl video driver to use (i.e.. aalib, dga, x11)</TD></TR>
+ <TR><TD></TD><TD><CODE>-ao sdl:name</CODE></TD><TD></TD><TD>specifies sdl audio driver to use (i.e.. dsp,
+ esd, arts)</TD></TR>
+ <TR><TD></TD><TD><CODE>-noxv</CODE></TD><TD></TD><TD>disables XVideo hardware acceleration</TD></TR>
+ <TR><TD></TD><TD><CODE>-forcexv</CODE></TD><TD></TD><TD>tries to force XVideo acceleration</TD></TR>
+
+ <TR><TD COLSPAN=4><P><B>SDL Keys:</B></P></TD></TR>
+ <TR><TD></TD><TD><CODE>F</CODE></TD><TD></TD><TD>toggles fullscreen/windowed mode</TD></TR>
+ <TR><TD></TD><TD><CODE>C</CODE></TD><TD></TD><TD>cycles available fullscreen modes</TD></TR>
+ <TR><TD></TD><TD><CODE>W/S</CODE></TD><TD></TD><TD>mappings for * and / (mixer control)</TD></TR>
</TABLE>
<P><B>KNOWN BUGS:</B></P>
@@ -492,6 +485,7 @@
It's bug in SDL, I can't change it (tested with SDL 1.2.1).</LI>
</UL>
+
<P><B><A NAME="svgalib">2.3.1.5 SVGAlib</A></B></P>
<P><B><U>Installation</U></B><BR>
@@ -522,8 +516,7 @@
For that we need fast but bad quality scaling routine:<BR>
<CODE>-sws 4</CODE><BR>
Maybe automatic aspect correction has to be shut off:<BR>
- <CODE>-noaspect</CODE><BR>
-</P>
+ <CODE>-noaspect</CODE></P>
<P><B><A NAME="fbdev">2.3.1.6 Framebuffer output (FBdev)</A></B></P>
@@ -541,13 +534,13 @@
<P>The FBdev output takes some additional parameters above the others:</P>
<TABLE BORDER=0>
-<TR><TD> </TD><TD><CODE>-fb</CODE></TD><TD> </TD><TD>
-specify the framebuffer device to use (/dev/fb0)</TD></TR>
-<TR><TD></TD><TD><CODE>-fbmode</CODE></TD><TD></TD><TD>mode name to use (according to /etc/fb.modes)</TD></TR>
-<TR><TD></TD><TD><CODE>-fbmodeconfig</CODE></TD><TD></TD><TD> config file of modes (default /etc/fb.modes)</TD></TR>
-<TR><TD></TD><TD><CODE>-monitor_hfreq</CODE></TD><TD></TD><TD ROWSPAN=3>IMPORTANT values, see example.conf</TD></TR>
-<TR><TD></TD><TD><CODE>-monitor_vfreq</CODE></TD><TD></TD></TR>
-<TR><TD></TD><TD><CODE>-monitor_dotclock</CODE></TD><TD></TD></TR>
+ <TR><TD> </TD><TD><CODE>-fb</CODE></TD><TD> </TD><TD>
+ specify the framebuffer device to use (/dev/fb0)</TD></TR>
+ <TR><TD></TD><TD><CODE>-fbmode</CODE></TD><TD></TD><TD>mode name to use (according to /etc/fb.modes)</TD></TR>
+ <TR><TD></TD><TD><CODE>-fbmodeconfig</CODE></TD><TD></TD><TD> config file of modes (default /etc/fb.modes)</TD></TR>
+ <TR><TD></TD><TD><CODE>-monitor_hfreq</CODE></TD><TD></TD><TD ROWSPAN=3>IMPORTANT values, see example.conf</TD></TR>
+ <TR><TD></TD><TD><CODE>-monitor_vfreq</CODE></TD><TD></TD></TR>
+ <TR><TD></TD><TD><CODE>-monitor_dotclock</CODE></TD><TD></TD></TR>
</TABLE>
<P>If you want to change to a specific mode, then use</P>
@@ -572,6 +565,7 @@
<P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer,
and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P>
+
<P><B><A NAME="mga_vid">2.3.1.7 Matrox framebuffer (mga_vid)</A></B></P>
<P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)
@@ -632,12 +626,14 @@
updated after the mga_vid changes, so it's outdated now. Volunteers
needed to test it and bring the code up-to-date.</P>
+
<P><B><A NAME="tdfxfb">2.3.1.9 3dfx YUV support (tdfxfb)</A></B></P>
<P>This driver uses the kernel's tdfx framebuffer driver to play movies with
YUV acceleration. You'll need a kernel with tdfxfb support, and recompile
with <CODE>./configure --enable-tdfxfb</CODE></P>
+
<P><B><A NAME="opengl">2.3.1.10 OpenGL output</A></B></P>
<P><B>MPlayer</B> supports displaying movies using OpenGL, but if your
@@ -655,6 +651,7 @@
<A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A>
for download and installation instructions.</P>
+
<P><B><A NAME="aalib">2.3.1.11 AAlib - text mode displaying</A></B></P>
<P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful
@@ -664,29 +661,27 @@
built.</P>
<TABLE BORDER=0>
-<TR><TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD></TR>
-<TR><TD> </TD><TD><CODE>1</CODE></TD><TD> </TD><TD>decrease contrast</TD></TR>
-<TR><TD></TD><TD><CODE>2</CODE></TD><TD></TD><TD>increase contrast</TD></TR>
-<TR><TD></TD><TD><CODE>3</CODE></TD><TD></TD><TD>decrease brightness</TD></TR>
-<TR><TD></TD><TD><CODE>4</CODE></TD><TD></TD><TD>increase brightness</TD></TR>
-<TR><TD></TD><TD><CODE>5</CODE></TD><TD></TD><TD>switch fast rendering on/off</TD></TR>
-<TR><TD></TD><TD><CODE>6</CODE></TD><TD></TD><TD>set dithering mode (none, error distribution, Floyd Steinberg)</TD></TR>
-<TR><TD></TD><TD><CODE>7</CODE></TD><TD></TD><TD>invert image</TD></TR>
-<TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and <B>MPlayer</B> control)</TD></TR>
-
-<TR><TD COLSPAN=4><P><B>The following command line options can be used:</B></P></TD></TR>
-
-<TR><TD></TD><TD><CODE>-aaosdcolor=V</CODE></TD><TD></TD><TD>change OSD color</TD></TR>
-<TR><TD></TD><TD><CODE>-aasubcolor=V</CODE></TD><TD></TD><TD>change subtitle color</TD></TR>
-<TR><TD COLSPAN=3></TD><TD><P><I>where V can be: (0/normal, 1/dark, 2/bold, 3/bold font, 4/reverse, 5/special)</I></P></TD></TR>
-
-<TR><TD COLSPAN=4><P><B>AAlib itself provides a large sum of options.
-Here are some important:</B></P></TD></TR>
-
-<TR><TD></TD><TD><CODE>-aadriver</CODE></TD><TD></TD><TD>set recommended aa driver (X11, curses, Linux)</TD></TR>
-<TR><TD></TD><TD><CODE>-aaextended</CODE></TD><TD></TD><TD>use all 256 characters</TD></TR>
-<TR><TD></TD><TD><CODE>-aaeight</CODE></TD><TD></TD><TD>use eight bit ASCII</TD></TR>
-<TR><TD></TD><TD><CODE>-aahelp</CODE></TD><TD></TD><TD>prints out all aalib options</TD></TR>
+ <TR><TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD></TR>
+ <TR><TD> </TD><TD><CODE>1</CODE></TD><TD> </TD><TD>decrease contrast</TD></TR>
+ <TR><TD></TD><TD><CODE>2</CODE></TD><TD></TD><TD>increase contrast</TD></TR>
+ <TR><TD></TD><TD><CODE>3</CODE></TD><TD></TD><TD>decrease brightness</TD></TR>
+ <TR><TD></TD><TD><CODE>4</CODE></TD><TD></TD><TD>increase brightness</TD></TR>
+ <TR><TD></TD><TD><CODE>5</CODE></TD><TD></TD><TD>switch fast rendering on/off</TD></TR>
+ <TR><TD></TD><TD><CODE>6</CODE></TD><TD></TD><TD>set dithering mode (none, error distribution, Floyd Steinberg)</TD></TR>
+ <TR><TD></TD><TD><CODE>7</CODE></TD><TD></TD><TD>invert image</TD></TR>
+ <TR><TD></TD><TD><CODE>a</CODE></TD><TD></TD><TD>toggles between aa and <B>MPlayer</B> control)</TD></TR>
+
+ <TR><TD COLSPAN=4><P><B>The following command line options can be used:</B></P></TD></TR>
+ <TR><TD></TD><TD><CODE>-aaosdcolor=V</CODE></TD><TD></TD><TD>change OSD color</TD></TR>
+ <TR><TD></TD><TD><CODE>-aasubcolor=V</CODE></TD><TD></TD><TD>change subtitle color</TD></TR>
+ <TR><TD COLSPAN=3></TD><TD><P><I>where V can be: (0/normal, 1/dark, 2/bold,
+ 3/bold font, 4/reverse, 5/special)</I></P></TD></TR>
+ <TR><TD COLSPAN=4><P><B>AAlib itself provides a large sum of options.
+ Here are some important:</B></P></TD></TR>
+ <TR><TD></TD><TD><CODE>-aadriver</CODE></TD><TD></TD><TD>set recommended aa driver (X11, curses, Linux)</TD></TR>
+ <TR><TD></TD><TD><CODE>-aaextended</CODE></TD><TD></TD><TD>use all 256 characters</TD></TR>
+ <TR><TD></TD><TD><CODE>-aaeight</CODE></TD><TD></TD><TD>use eight bit ASCII</TD></TR>
+ <TR><TD></TD><TD><CODE>-aahelp</CODE></TD><TD></TD><TD>prints out all aalib options</TD></TR>
</TABLE>
<P>NOTE: the rendering is very CPU intensive, especially when using AA-on-X
@@ -715,7 +710,7 @@
70) says:</P>
<BLOCKQUOTE>
-<B>Dual-Controller Designs</B><BR>
+ <B>Dual-Controller Designs</B><BR>
VBE 3.0 supports the dual-controller design by assuming that since both
controllers are typically provided by the same OEM, under control of a
single BIOS ROM on the same graphics card, it is possible to hide the fact
@@ -745,26 +740,30 @@
calls <B>real</B> things of <B>real</B> BIOS in <B>real</B>-mode. (Finely -
in vm86 mode).<BR>
- You can use Vidix with it, thus getting accelerated video display
- <B>AND</B> TV output at the same time! (recommended for ATI cards)
-</P>
+ <B>AND</B> TV output at the same time! (recommended for ATI cards)</P>
<P><B>What are minuses:</B><BR>
- It works only on <B>x86 systems</B>.<BR>
- It can be used only by <B>ROOT</B>.<BR>
- - Currently it's available only for <B>Linux</B>.<BR>
-</P>
+ - Currently it's available only for <B>Linux</B>.</P>
<P>Don't use this driver with <B>GCC 2.96</B>! It won't work!</P>
<TABLE BORDER=0>
-<TR><TD COLSPAN=4><P><B>These switches of command line currently are available for VESA:</B></P></TD></TR>
-<TR><TD> </TD><TD VALIGN="top"><CODE>-vo vesa:opts</CODE></TD><TD></TD><TD>currently recognized: <B>dga</B> to force dga mode and <B>nodga</B> to disable dga mode. Note: you may omit these parameters to enable <B>autodetect</B> of dga mode. (In the future also will specify mode parameters such as refresh rate, interlacing, doublescan and so on. Samples: i43, 85, d100)</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-screenw, -screenh, -bpp</CODE></TD><TD></TD><TD>force userdefined mode</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-x, -y</CODE></TD><TD></TD><TD>set userdefined prescaling</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-zoom</CODE></TD><TD></TD><TD>enables userdefined prescaling</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-fs</CODE></TD><TD></TD><TD>scales image to fullscreen</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-fs -zoom</CODE></TD><TD></TD><TD>scales userdefined prescaling to fullscreen</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-double</CODE></TD><TD></TD><TD>enables double buffering mode. (Available only in DGA mode). Should be slower of single buffering, but has no flickering effects.</TD></TR>
+ <TR><TD COLSPAN=4><P><B>These switches of command line currently are available for VESA:</B></P></TD></TR>
+ <TR><TD> </TD><TD VALIGN="top"><CODE>-vo vesa:opts</CODE></TD><TD></TD>
+ <TD>currently recognized: <B>dga</B> to force dga mode and <B>nodga</B> to
+ disable dga mode. Note: you may omit these parameters to enable <B>autodetect</B>
+ of dga mode. (In the future also will specify mode parameters such as refresh
+ rate, interlacing, doublescan and so on. Samples: i43, 85, d100)</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-screenw, -screenh, -bpp</CODE></TD><TD></TD><TD>force userdefined mode</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-x, -y</CODE></TD><TD></TD><TD>set userdefined prescaling</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-zoom</CODE></TD><TD></TD><TD>enables userdefined prescaling</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-fs</CODE></TD><TD></TD><TD>scales image to fullscreen</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-fs -zoom</CODE></TD><TD></TD><TD>scales userdefined prescaling to fullscreen</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-double</CODE></TD><TD></TD><TD>enables
+ double buffering mode. (Available only in DGA mode). Should be slower of
+ single buffering, but has no flickering effects.</TD></TR>
</TABLE>
<P><B>Known problems and workaround:</B><BR>
@@ -783,8 +782,7 @@
<B>Alt-Fx</B>) then switch to your previous console by the same way.<BR>
- To get <B>working TV-out</B> you need have plugged TV-connector in before
booting your PC since video BIOS initializes itself only once during POST
- procedure.
-</P>
+ procedure.</P>
<P><B><A NAME="x11">2.3.1.13 X11</A></B></P>
@@ -833,8 +831,7 @@
scalers) or OV (Video Overlays). It doesn't provide lowlevel interface to
things which are known as graphics servers. (I don't want to compete with X11
team in graphics mode switching). I.e. main goal of this interface is to
- maximize the speed of video playback.
-</P>
+ maximize the speed of video playback.</P>
<P><B>USAGE</B></P>
@@ -846,6 +843,7 @@
drivers, such as:<BR>
<CODE>-vo vesa:vidix</CODE> (<B>LINUX ONLY</B>) and <CODE>-vo fbdev:vidix</CODE></LI>
</UL>
+
Indeed it doesn't matter which video output driver is used with <B>VIDIX</B>.
<P><B>REQUIREMENTS</B></P>
@@ -859,6 +857,7 @@
<LI><B>MPlayer</B>'s video output driver should know active video mode and be
able to tell to VIDIX subdevice some video characteristics of server.</LI>
</UL>
+
I hope that probably every video output driver of <B>MPlayer</B> will
recognize <CODE>:vidix</CODE> subdevice.
@@ -871,8 +870,7 @@
<CODE>-double</CODE> key as globally visible parameter. (I recommend using
this key with VIDIX at least for ATI's card).<BR>
As for <CODE>-vo xvidix</CODE>: currently it recognizes the following
- options: <CODE>-fs -zoom -x -y -double</CODE>.<BR>
-</P>
+ options: <CODE>-fs -zoom -x -y -double</CODE>.</P>
<P>Also you can specify VIDIX's driver directly as third subargument in command
line:<BR>
@@ -888,68 +886,59 @@
computer). You should do that ONLY if you are absolutely sure it will work,
and <B>MPlayer</B> doesn't do it automatically. Please tell about it to the
developers. The Right Way is to use VIDIX without arguments to enable driver
- autodetection.
-</P>
+ autodetection.</P>
-<P>
- VIDIX is very new technology and it's extremely possible that on your system
+<P>VIDIX is very new technology and it's extremely possible that on your system
(OS=abc CPU=xyz) it won't work. In this case only solution for you it's port
it (mainly libdha). But there is hope that it will work on those systems
- where X11 does.
-</P>
+ where X11 does.</P>
<P>And the last <B>WARNING</B>: (un)fortunately you <B>MUST</B> have
<B>ROOT</B> privileges to use VIDIX due to direct hardware access. At least
- set the <B>SUID</B> bit on the <B>MPlayer</B> executable.
-</P>
+ set the <B>SUID</B> bit on the <B>MPlayer</B> executable.</P>
<P><B>VIDEO EQUALIZER</B></P>
-<P>
- This is a video equalizer implemented especially for VIDIX. You can use
+<P>This is a video equalizer implemented especially for VIDIX. You can use
it either with <B>1-8</B> keys as described in the man page, or
by command line arguments. <B>MPlayer</B> recognizes the
- following options:
-</P>
+ following options:</P>
<TABLE>
-<TR><TD> </TD><TD VALIGN="top"><CODE>-brightness</CODE></TD><TD> </TD>
- <TD>Adjust <B>BRIGHTNESS</B> of video output. It's not equal to brightness
- adjusting on monitor panel or on TV. It changes intensity of RGB components of
- video signal from black to white screen.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-contrast</CODE></TD><TD></TD>
- <TD>Adjust <B>CONTRAST</B> of video output. Works in similar manner as
- brightness.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-saturation</CODE></TD>
- <TD></TD><TD>Adjust <B>SATURATION</B> of video output. You can get grayscale
- output with this option.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-hue</CODE></TD>
- <TD></TD><TD>Adjust <B>HUE</B> of video signal. You can get colored negative
- of image with this option.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-red_intensity</CODE></TD>
- <TD></TD><TD>Adjust intensity of <B>RED</B> component of video signal.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-green_intensity</CODE></TD>
- <TD></TD><TD>Adjust intensity of <B>GREEN</B> component of video signal.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-blue_intensity</CODE></TD>
- <TD></TD><TD>Adjust intensity of <B>BLUE</B> component of video signal.</TD></TR>
+ <TR><TD> </TD><TD VALIGN="top"><CODE>-brightness</CODE></TD><TD> </TD>
+ <TD>Adjust <B>BRIGHTNESS</B> of video output. It's not equal to brightness
+ adjusting on monitor panel or on TV. It changes intensity of RGB components of
+ video signal from black to white screen.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-contrast</CODE></TD><TD></TD>
+ <TD>Adjust <B>CONTRAST</B> of video output. Works in similar manner as
+ brightness.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-saturation</CODE></TD>
+ <TD></TD><TD>Adjust <B>SATURATION</B> of video output. You can get grayscale
+ output with this option.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-hue</CODE></TD>
+ <TD></TD><TD>Adjust <B>HUE</B> of video signal. You can get colored negative
+ of image with this option.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-red_intensity</CODE></TD>
+ <TD></TD><TD>Adjust intensity of <B>RED</B> component of video signal.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-green_intensity</CODE></TD>
+ <TD></TD><TD>Adjust intensity of <B>GREEN</B> component of video signal.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-blue_intensity</CODE></TD>
+ <TD></TD><TD>Adjust intensity of <B>BLUE</B> component of video signal.</TD></TR>
</TABLE>
-<P>
- Each parameter can accept values from <B>-1000</B> to <B>+1000</B>.<BR>
- Default value for each parameter is <B>0</B>.
-</P>
-<P>
- <B>Note:</B> Not every driver provides support for each of those parameters.
+<P>Each parameter can accept values from <B>-1000</B> to <B>+1000</B>.<BR>
+ Default value for each parameter is <B>0</B>.</P>
+
+<P><B>Note:</B> Not every driver provides support for each of those parameters.
Currently only <B>radeon_vid.so</B> provides full support for video equalizing.
- Other drivers only partly support these options.
-</P>
+ Other drivers only partly support these options.</P>
+
<P><B>Examples:</B><BR>
<CODE>mplayer -vo vesa:vidix -brightness -300 -contrast 200
filename.avi</CODE><BR>
or<BR>
<CODE>mplayer -vo xvidix -red_intensity -50 -saturation 400 -hue 300
- filename.vob</CODE>
-</P>
+ filename.vob</CODE></P>
<P><B><A NAME="zr">2.3.1.15 Zr</A></B></P>
@@ -1102,36 +1091,36 @@
<P><B>USAGE</B></P>
<TABLE>
-<TR><TD> </TD><TD VALIGN="top"><CODE>-vo dxr3:<noprebuf>:<codec>:<device></CODE></TD><TD> </TD>
- <TD>Where <CODE><noprebuf></CODE> specifies turning off prebuffering.
- This is done automatically on Athlons. If playback is out of sync try
- disabling prebuffering. If noprebuf is left out prebuffering is enabled
- (except on Athlons).
- <BR>
- <CODE><codec></CODE> = fame/avcodec, avcodec produces better quality
- output, but fame is faster for those of you with slow machines. The default is
- to use libavcodec. Note that you need libavcodec properly installed (read
- DOCS/codecs.html).
- <BR>
- <CODE><device></CODE> = device number to use if you have more than one
- em8300 card.
- <BR>
- Any of these options may be left out, but they must be specified in this
- order, i.e. <CODE>dxr3:fame</CODE> works, <CODE>dxr3:1</CODE> works, but
- <CODE>dxr3:1:avcodec</CODE> will not.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-ao oss:/dev/em8300_ma-X</CODE></TD>
- <TD></TD><TD>For audio output, where <CODE>X</CODE> is the device number
- (0 if one card).</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-ac hwac3</CODE></TD>
- <TD></TD><TD>For digital instead of analog audio output.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-vc mpegpes</CODE></TD>
- <TD></TD><TD>Force hardware acceleration, only works with MPEG1/2.</TD></TR>
-<TR><TD></TD><TD VALIGN="top"><CODE>-aop list=resample:fout=xxxxx</CODE></TD>
- <TD></TD><TD>If sample rate is below 44100Hz, select either 44100Hz or 48000Hz
- depending on which one matches closest. I.e. if the movie uses 22050Hz use
- 44100Hz as 44100 / 2 = 22050, if it is 24000Hz use 48000Hz as 48000 / 2 = 24000
- and so on. This does not work with digital audio output
- (<CODE>-ac hwac3</CODE>).</TD></TR>
+ <TR><TD> </TD><TD VALIGN="top"><CODE>-vo dxr3:<noprebuf>:<codec>:<device></CODE></TD><TD> </TD>
+ <TD>Where <CODE><noprebuf></CODE> specifies turning off prebuffering.
+ This is done automatically on Athlons. If playback is out of sync try
+ disabling prebuffering. If noprebuf is left out prebuffering is enabled
+ (except on Athlons).
+ <BR>
+ <CODE><codec></CODE> = fame/avcodec, avcodec produces better quality
+ output, but fame is faster for those of you with slow machines. The default is
+ to use libavcodec. Note that you need libavcodec properly installed (read
+ DOCS/codecs.html).
+ <BR>
+ <CODE><device></CODE> = device number to use if you have more than one
+ em8300 card.
+ <BR>
+ Any of these options may be left out, but they must be specified in this
+ order, i.e. <CODE>dxr3:fame</CODE> works, <CODE>dxr3:1</CODE> works, but
+ <CODE>dxr3:1:avcodec</CODE> will not.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-ao oss:/dev/em8300_ma-X</CODE></TD>
+ <TD></TD><TD>For audio output, where <CODE>X</CODE> is the device number
+ (0 if one card).</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-ac hwac3</CODE></TD>
+ <TD></TD><TD>For digital instead of analog audio output.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-vc mpegpes</CODE></TD>
+ <TD></TD><TD>Force hardware acceleration, only works with MPEG1/2.</TD></TR>
+ <TR><TD></TD><TD VALIGN="top"><CODE>-aop list=resample:fout=xxxxx</CODE></TD>
+ <TD></TD><TD>If sample rate is below 44100Hz, select either 44100Hz or 48000Hz
+ depending on which one matches closest. I.e. if the movie uses 22050Hz use
+ 44100Hz as 44100 / 2 = 22050, if it is 24000Hz use 48000Hz as 48000 / 2 = 24000
+ and so on. This does not work with digital audio output
+ (<CODE>-ac hwac3</CODE>).</TD></TR>
</TABLE>
<P><B>Overlay</B><P>
@@ -1157,6 +1146,7 @@
<P><B><A NAME="tv-out">2.3.1.A TV-out support</A></B></P>
+
<P><B><A NAME="tv-out_matrox">2.3.1.A.1 Matrox G400 cards</A></B></P>
<P>Under Linux you have 2 methods to get G400 TV out working:</P>
@@ -1202,35 +1192,28 @@
items randomly and it'll be OK :)</LI>
</UL>
- <P>
- Yoh. Next task is to make the cursor on tty1 (or whatever) to disappear,
+ <P>Yoh. Next task is to make the cursor on tty1 (or whatever) to disappear,
and turn off screen blanking. Execute the following commands:</P>
- <P>
- <CODE>echo -e '\033[?25l'</CODE> or <CODE>setterm -cursor off<BR>
- setterm -blank 0</CODE>
- </P>
+ <P><CODE>echo -e '\033[?25l'</CODE> or <CODE>setterm -cursor off<BR>
+ setterm -blank 0</CODE></P>
- <P>
- You possibly want to put the above into a script, and also clear
+ <P>You possibly want to put the above into a script, and also clear
the screen.. To turn the cursor back:<BR><CODE>echo -e '\033[?25h'</CODE>
- or <CODE>setterm -cursor on</CODE>
- </P>
+ or <CODE>setterm -cursor on</CODE></P>
<P>Yeah kewl. Start movie playing with <CODE>mplayer -vo mga -fs -screenw 640
-screenh 512 <filename></CODE><BR>
(if you use X, now change to matroxfb with for example CTRL-ALT-F1!)<BR>
Change 640x512 if you set the resolution to other..<BR>
- <B>Enjoy the ultra-fast ultra-featured Matrox TV output (better than Xv)!</B>
- </P>
+ <B>Enjoy the ultra-fast ultra-featured Matrox TV output (better than Xv)!</B></P>
</LI>
</UL>
<P><B><A NAME="tv-out_ati">2.3.1.A.2 ATI cards</A></B></P>
-<P>
-<B><U>PREAMBLE</U></B><BR>
+<P><B><U>PREAMBLE</U></B><BR>
Currently ATI doesn't want to support any of its TV-out chips under Linux,
because of their licensed Macrovision technology.</P>
@@ -1246,22 +1229,17 @@
sections.</LI>
</UL>
-<P>
- On other cards, just use the <a href="#vesa">VESA driver</a>, without
- VIDIX. Powerful CPU is needed, though.
-</P>
+<P>On other cards, just use the <a href="#vesa">VESA driver</a>, without
+ VIDIX. Powerful CPU is needed, though.</P>
<P>Only thing you need to do - <B>have TV connector plugged in before
booting your PC</B> since video BIOS initializes itself only once during
- POST procedure.
-</P>
+ POST procedure.</P>
<P><B><A NAME="tv-out_voodoo">2.3.1.A.3 Voodoo 3</A></B></P>
-<P>
- Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>.
-</P>
+<P>Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>.</P>
</BODY>
</HTML>
More information about the MPlayer-cvslog
mailing list