Update of /cvsroot/mplayer/main/DOCS In directory mail:/var/tmp.root/cvs-serv9467 Modified Files: bugreports.html cd-dvd.html codecs.html documentation.html formats.html sound.html video.html Log Message: 95% cosmetics (only paragraph reformatting, joe: ctrl-k-j :)) 5% useful new stuff (not significant.. only in documentation.html) (?) Index: bugreports.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/bugreports.html,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- bugreports.html 25 Jul 2002 02:38:20 -0000 1.31 +++ bugreports.html 1 Aug 2002 20:47:46 -0000 1.32 @@ -14,47 +14,48 @@ <P><B>How to report bugs?</B></P> <P>First of all please try the latest CVS version of <B>MPlayer</B> as your bug -might already be fixed there. CVS instructions can be found at the bottom of -<A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A>.</P> + might already be fixed there. CVS instructions can be found at the bottom of + <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A>.</P> -<P>If this did not help please refer to <A HREF="documentation.html#D">Appendix D</A> -and the rest of the documentation. If your problem is not known or not solvable by -our instructions, then please report the bug.</P> +<P>If this did not help please refer to <A HREF="documentation.html#D">Appendix + D</A> and the rest of the documentation. If your problem is not known or not + solvable by our instructions, then please report the bug.</P> <P>If you feel have the necessary skills you are invited to have a go at fixing -the bug yourself. Or maybe you already did that? Please read -<A HREF="tech/patches.txt">this short document</A> to find out how to get your -code included in <B>MPlayer</B>. The people on the -<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> -mailing list can assist you if you have questions.</P> + the bug yourself. Or maybe you already did that? Please read + <A HREF="tech/patches.txt">this short document</A> to find out how to get + your code included in <B>MPlayer</B>. The people on the + <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> + mailing list can assist you if you have questions.</P> <P><B>Where to report bugs?</B></P> <P>Subscribe to the mplayer-users mailing list:<BR> -    <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> -and send your bug report to:<BR> -    <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> +     <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> + and send your bug report to:<BR> +     <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> <P>The language of this list is <B>English</B>. Please follow the standard -<A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and -<B>do not send HTML mail</B> to any of our mailing lists. You will only get -ignored or banned. Also note that we will not individually CC (carbon-copy) -people so it is a good idea to subscribe to actually receive your answer.</P> - -<P>Please do not send bug reports privately to individual developers. This is -community work and thus there might be several people interested in it. -Also sometimes other users already experienced your troubles and have a -solution in hand how to circumvent a problem even if it is a bug in <B>MPlayer</B> -code.</P> + <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and + <B>do not send HTML mail</B> to any of our mailing lists. You will only get + ignored or banned. Also note that we will not individually CC (carbon-copy) + people so it is a good idea to subscribe to actually receive your answer.</P> + +<P>Please do not send bug reports privately to individual developers. This is + community work and thus there might be several people interested in it. Also + sometimes other users already experienced your troubles and have a solution + in hand how to circumvent a problem even if it is a bug in <B>MPlayer</B> + code.</P> <P>Please describe your problem in as much detail as possible. Do a little -detective work to narrow down the circumstances under which the problem occurs. -Does the bug only show up in certain situations? Is it specific to certain files -or file types? Does it occur with only one codec or is it codec independent? -Can you reproduce it with all output drivers? The more information you provide -the better are our chances at fixing your problem. Please do not forget to -also include the valuable information requested below, we will probably be -unable to properly diagnose your bug otherwise.</P> + detective work to narrow down the circumstances under which the problem + occurs. Does the bug only show up in certain situations? Is it specific to + certain files or file types? Does it occur with only one codec or is it codec + independent? Can you reproduce it with all output drivers? The more + information you provide the better are our chances at fixing your problem. + Please do not forget to also include the valuable information requested + below, we will probably be unable to properly diagnose your bug + otherwise.</P> <P><B>What to report?</B></P> @@ -64,7 +65,7 @@ <LI>Your Linux distribution or operating system e.g.: <UL> <LI>Red Hat 7.1</LI> - <LI>Slackware 7.0 + devel packs from 7.1 ...</LI> + <LI>Slackware 7.0 + devel packs from 7.1...</LI> </UL> </LI> <LI>kernel version:<BR> @@ -135,38 +136,38 @@ <P><B>For playback problems</B></P> <P>Please include the output of <B>MPlayer</B> at verbosity level 1, but -remember to <B>not truncate the output</B> when you paste it into your mail. The -developers need all of the messages to properly diagnose a problem. You can -direct the output into a file like this:</P> + remember to <B>not truncate the output</B> when you paste it into your mail. + The developers need all of the messages to properly diagnose a problem. You + can direct the output into a file like this:</P> <P><CODE>    mplayer -v [options] [filename] &> mplayer.log</CODE></P> <P>If your problem is specific to one or more files, then please upload the -offender(s) to:</P> + offender(s) to:</P> <P>    <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> -<P>Also upload a small text file having the same base name as your file -with a .txt extension. Describe the problem you are having with the -particular file there and include your email address as well as the output -of <B>MPlayer</B> at verbosity level 1.<BR> -Usually the first 1-5 MB of a file are enough to reproduce the problem, -but to be sure we ask you to: -<P><CODE>    dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> - -<P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and -write it to <STRONG>'small-file'</STRONG>.<BR> -Then try again on this small file and if the bug still shows up -your sample is sufficient for us.<BR> -Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, -and send only the path/filename of the file on the FTP-server.<BR> -If the file is accessible on the net, then sending the -<STRONG>exact</STRONG> URL is sufficient.</P> +<P>Also upload a small text file having the same base name as your file with a + .txt extension. Describe the problem you are having with the particular file + there and include your email address as well as the output of <B>MPlayer</B> + at verbosity level 1.<BR> + Usually the first 1-5 MB of a file are enough to reproduce the problem, but + to be sure we ask you to: + <P><CODE>    dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> +</P> + +<P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and + write it to <STRONG>'small-file'</STRONG>.<BR> Then try again on this small + file and if the bug still shows up your sample is sufficient for us.<BR> + Please <STRONG>do not ever</STRONG> send such files via mail! Upload it, and + send only the path/filename of the file on the FTP-server.<BR> If the file is + accessible on the net, then sending the <STRONG>exact</STRONG> URL is + sufficient.</P> <P><B>For crashes</B></P> <P>If you have a core dump of the crash continue reading the next paragraph, -otherwise skip it.</P> + otherwise skip it.</P> <P><B>How to extract meaningful information from a core dump</B></P> @@ -187,14 +188,18 @@ <P>    <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> <P><B>How to conserve information about a reproducible crash</B></P> + <P>Recompile <B>MPlayer</B> with debugging code enabled:</P> + <P><CODE>    ./configure --enable-debug=3<BR> -    make</CODE></P> +     make</CODE></P> + and then run <B>MPlayer</B> within gdb using: + <P><CODE>    gdb mplayer</CODE></P> <P>You are now within gdb. Type:</P> -<P><CODE>    run -v [options-to-mplayer] filename</code></P> +<P><CODE>    run -v [options-to-mplayer] filename</CODE></P> and reproduce your crash. As soon as you did it, gdb will return you to the command line prompt where you have to enter <P><CODE>    bt<BR> @@ -203,25 +208,26 @@ <P><B>General note</B></P> -<P>If something is quite big (logs for instance) then it is better to upload -it to the FTP server in a compressed format (gzip and bzip preferred) and -include only the path and filename in your bug report.</P> +<P>If something is quite big (logs for instance) then it is better to upload it + to the FTP server in a compressed format (gzip and bzip preferred) and + include only the path and filename in your bug report.</P> <P><B>I know what I am doing...</B></P> <P>If you created a proper bug report following the steps above and you are -confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken file, -you have already read the documentation and you could not find a solution, -your sound drivers are OK, then you might want to subscribe to the -mplayer-advusers list and send your bug report there to get a better and -faster answer.<BR><BR> -Please be advised that if you post newbie questions or questions answered -in the manual there, you will be ignored or flamed instead of getting an -appropriate answer.<BR> -So do not flame us and subscribe to -advusers only if you really know -what you are doing and feel like being an advanced <B>MPlayer</B> user or -developer. If you meet these criteria it should not be difficult to find -out how to subscribe... + confident it is a bug in <B>MPlayer</B>, not a compiler problem or broken + file, you have already read the documentation and you could not find a + solution, your sound drivers are OK, then you might want to subscribe to the + mplayer-advusers list and send your bug report there to get a better and + faster answer.<BR><BR> + + Please be advised that if you post newbie questions or questions answered in + the manual there, you will be ignored or flamed instead of getting an + appropriate answer.<BR> + So do not flame us and subscribe to -advusers only if you really know what + you are doing and feel like being an advanced <B>MPlayer</B> user or + developer. If you meet these criteria it should not be difficult to find out + how to subscribe... </P> </BODY> Index: cd-dvd.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/cd-dvd.html,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- cd-dvd.html 13 Jun 2002 00:15:32 -0000 1.30 +++ cd-dvd.html 1 Aug 2002 20:47:46 -0000 1.31 @@ -14,38 +14,39 @@ <P>Playing standard Video CDs:</P> <P> -mplayer -vcd <I>trackno</I> [-cdrom-device device]<BR><BR> -Examples:<BR> -mplayer -vcd 1<BR> -mplayer -fs -vcd 2 -cdrom-device /dev/hdc<BR> + mplayer -vcd <I>trackno</I> [-cdrom-device device]<BR><BR> + + Examples:<BR> + mplayer -vcd 1<BR> + mplayer -fs -vcd 2 -cdrom-device /dev/hdc<BR> </P> <P> -Notes:<BR> -- Do NOT mount VCD disks and play DAT files directly! It may work under windows -but won't work under linux. You have to play them directly, with the -vcd -option!<BR> -- VCD disks usually have 2 tracks: a data track (containing autostart windows -playback program, karaoke data etc) and a mode-2 track (the movie), so try --vcd 2 first!<BR> -- the default VCD device is /dev/cdrom. if your device differs, then you have -to make a symlink, or specify it in command line! + Notes:<BR> + - Do NOT mount VCD disks and play DAT files directly! It may work under + windows but won't work under linux. You have to play them directly, with + the <CODE>-vcd</CODE> option!<BR> + - VCD disks usually have 2 tracks: a data track (containing autostart windows + playback program, karaoke data etc) and a mode-2 track (the movie), so try + <CODE>-vcd 2</CODE> first!<BR> + - the default VCD device is /dev/cdrom. if your device differs, then you have + to make a symlink, or specify it in command line! </P> <P>From Linux documentation:</P> -<P>Some CDROM drives are capable of changing their head-speed. There are several -reasons for changing the speed of a CDROM drive. Badly pressed CDROMs may -benefit from less-than-maximum head rate. Modern CDROM drives can obtain very -high head rates (up to 24-times is common). It has been reported that these -drives can make reading errors at these high speeds, reducing the speed can -prevent data loss in these circumstances. Finally, some of these drives can -make an annoyingly loud noise, which a lower speed may reduce.</P> - -<P>The recommended way to do it is with a program called 'setcd' . It's kinda -old, but won't be too hard to find on the Net. (UPDATE : new hdparm -has an option for this !) -Use it with :</P> +<P>Some CDROM drives are capable of changing their head-speed. There are + several reasons for changing the speed of a CDROM drive. Badly pressed CDROMs + may benefit from less-than-maximum head rate. Modern CDROM drives can obtain + very high head rates (up to 24-times is common). It has been reported that + these drives can make reading errors at these high speeds, reducing the speed + can prevent data loss in these circumstances. Finally, some of these drives + can make an annoyingly loud noise, which a lower speed may reduce.</P> + +<P>The recommended way to do it is with a program called 'setcd'. It's kinda + old, but won't be too hard to find on the Net. (UPDATE: new hdparm has an + option for this!) + Use it with:</P> <P>    <CODE>setcd -x [speed] [cdrom device]</CODE></P> @@ -58,15 +59,15 @@ <P>    <CODE>echo file_readahead:2000000 >/proc/ide/[cdrom device]/settings</CODE></P> <P>for 2MB prefetched reading from the file (it's useful for scratched CDROMs). -It's recommended that you tuneup your CDROM drive also with hdparm:</P> + It's recommended that you tuneup your CDROM drive also with hdparm:</P> <P>    <CODE>hdparm -d1 -a8 -u1 (cdrom device)</CODE></P> <P>to enable using DMA access, readahead, and IRQ unmasking. -(if you don't understand these, *read the hdparm man page*)</P> + (if you don't understand these, *read the hdparm man page*)</P> -<P>Please refer to "<CODE>/proc/ide/[cdrom device]/settings</CODE>" for fine-tuning your -CDROM.</P> +<P>Please refer to "<CODE>/proc/ide/[cdrom device]/settings</CODE>" for + fine-tuning your CDROM.</P> <P><B><A NAME=4.2>4.2. DVD playback</A></B></P> @@ -112,14 +113,14 @@ <TD>Enables DVD support and selects title.</TD><TR> <TD VALIGN=top>-chapter <chapter_id> </TD> <TD>Selects DVD chapter(s) to play (default: play from chapter 1). - Example : <CODE>-chapter 5-10</CODE> or <CODE>-chapter -9</CODE></TD><TR> + Example: <CODE>-chapter 5-10</CODE> or <CODE>-chapter -9</CODE></TD><TR> <TD VALIGN=top>-dvdangle <angle_id> </TD> <TD>Selects camera angle (default: 1)</TD><TR> <TD VALIGN=top>-alang <country code> </TD> <TD> The <CODE>country code</CODE> tells <B>MPlayer</B> which audio language(s) to prefer. For the list of available languages, add <CODE>-v</CODE> option after your DVD options, and browse the output.<BR> - For example :<BR> + For example:<BR>   <CODE>-alang hu,en</CODE> - first tries to find hungarian audio, and if not found, decode english audio.</TD><TR> <TD VALIGN=top>-slang <country code> </TD> @@ -127,7 +128,7 @@ which language(s) to prefer. For the list of available languages, add <CODE>-v</CODE> option after your DVD options, and browse the output.<BR> - For example :<BR> + For example:<BR>   <CODE>-slang hu,en</CODE> - first tries to display hungarian subtitles, and if not found, display english subtitles.</TD><TR> <TD VALIGN=top>-sid <subtitle_id> </TD> @@ -149,7 +150,7 @@ </TABLE> <P>Default device is <CODE>/dev/dvd</CODE>, you can change it in config.h -(compile time option), or you can specify it using the -dvd-device option : + (compile time option), or you can specify it using the -dvd-device option: </P> <P>    <CODE>mplayer -dvd 1 -dvd-device /dev/dvd</CODE></P> Index: codecs.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/codecs.html,v retrieving revision 1.73 retrieving revision 1.74 diff -u -r1.73 -r1.74 --- codecs.html 24 Jul 2002 01:56:08 -0000 1.73 +++ codecs.html 1 Aug 2002 20:47:46 -0000 1.74 @@ -19,53 +19,56 @@ <P>The most important ones above all:</P> <UL> -<LI>MPEG1 (VCD) and MPEG2 (DVD) video</LI> -<LI>native decoders for DivX ;-), OpenDivX (DivX4), DivX 5.01, 3ivX, M$ MPEG4 v1, v2 and other MPEG4 variants</LI> -<LI>native decoder for Windows Media Video 7 (WMV1), and Win32 DLL decoder for - Windows Media Video 8 (WMV2), both used in .wmv files</LI> -<LI><B>native Sorenson (SVQ1) decoder</B></LI> -<LI>Cinepak and Intel Indeo codecs (3.1,3.2,4.1,5.0)</LI> -<LI>MJPEG, AVID, VCR2, ASV2 and other hardware formats</LI> -<LI>VIVO 1.0, 2.0, I263 and other h263(+) variants</LI> -<LI>FLI/FLC</LI> -<LI>RealVideo 1.0 from ffmpeg, and RealVideo 2.0, 3.0 using RealPlayer - libraries</LI> -<LI>native decoder for HuffYUV</LI> -<LI>Various old simple RLE-like formats</LI> + <LI>MPEG1 (VCD) and MPEG2 (DVD) video</LI> + <LI>native decoders for DivX ;-), OpenDivX, DivX4, DivX5, + M$ MPEG4 v1, v2 and other MPEG4 variants</LI> + <LI>native decoder for Windows Media Video 7 (WMV1), and Win32 DLL decoder for + Windows Media Video 8 (WMV2), both used in .wmv files</LI> + <LI><B>native Sorenson (SVQ1) decoder</B></LI> + <LI>3ivx decoder</LI> + <LI>Cinepak and Intel Indeo codecs (3.1,3.2,4.1,5.0)</LI> + <LI>MJPEG, AVID, VCR2, ASV2 and other hardware formats</LI> + <LI>VIVO 1.0, 2.0, I263 and other h263(+) variants</LI> + <LI>FLI/FLC</LI> + <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> </UL> -<P>If you have a Win32 codec not listed here which is not supported yet, please read the -<A HREF="#2.2.3">codec importing HOWTO</A> and help us add support -for it!</P> +<P>If you have a Win32 codec not listed here which is not supported yet, please + read the <A HREF="#2.2.3">codec importing HOWTO</A> and help us add support + for it!</P> + <P><B><A NAME=2.2.1.1>2.2.1.1. DivX4/DivX5</A></B></P> -<P>This section contains information about the DivX4 codec of -<A HREF="http://www.projectmayo.com">Project Mayo</A>. Their first available alpha version was OpenDivX 4.0 -alpha 47 and 48. Support for this was included in <B>MPlayer</B> in the past, -and built by default. We also used its postprocessing code to optionally -enhance visual quality of MPEG1/2 movies. Now we use our own, for all file -types.</P> - -<P>The new generation of this codec is called DivX4Linux and can even decode -movies made with the infamous DivX codec! In addition it is much faster than the -native Win32 DivX DLLs but slower than libavcodec. -Hence its usage as a decoder is <B>DISCOURAGED</B>. However, it is useful for -encoding. One disadvantage of this codec is that it is currently closed source.</P> +<P>This section contains information about the DivX4 and DivX5 codecs of + <A HREF="http://www.projectmayo.com">Project Mayo</A>. Their first available + alpha version was OpenDivX 4.0 alpha 47 and 48. Support for this was included + in <B>MPlayer</B> in the past, and built by default. We also used its + postprocessing code to optionally enhance visual quality of MPEG1/2 movies. + Now we use our own, for all file types.</P> + +<P>The new generation of this codec is called DivX4 and can even decode + movies made with the infamous DivX codec! In addition it is much faster than + the native Win32 DivX DLLs but slower than libavcodec. Hence its usage as a + decoder is <B>DISCOURAGED</B>. However, it is useful for encoding. One + disadvantage of this codec is that it is currently closed source.</P> <P>The codec can be downloaded from one of the following URLs:</P> <P>    <A HREF="http://avifile.sourceforge.net">http://avifile.sourceforge.net</A><BR> -    <A HREF="http://divx.com">http://divx.com</A></P> +     <A HREF="http://divx.com">http://divx.com</A></P> <P>Unpack it, and run <CODE>./install.sh</CODE> as root.</P> <P><B>Note:</B> Do <B>not</B> forget adding <CODE>/usr/local/lib</CODE> to your -<CODE>/etc/ld.so.conf</CODE> and running <CODE>ldconfig</CODE>!</P> + <CODE>/etc/ld.so.conf</CODE> and running <CODE>ldconfig</CODE>!</P> <P><B>MPlayer</B> autodetects DivX4/DivX5 if it is properly installed, just -compile as usual. If it does not detect it, you did not install or configure -it correctly.</P> + compile as usual. If it does not detect it, you did not install or configure + it correctly.</P> <P>DivX4Linux works in two modes:</P> @@ -79,11 +82,11 @@ 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 transfers -image data in YV12 (planar YUV 4:2:0) format, thus requiring much less -bandwidth on the bus. For packed YUV modes (YUY2, UYVY) use the <CODE>-vc divx4</CODE> -method. For RGB modes the speed is the same, differing at best -according to your current color depth.</P> +<P>The <CODE>-vc odivx</CODE> method is usually faster, due to the fact that it + transfers image data in YV12 (planar YUV 4:2:0) format, thus requiring much + less bandwidth on the bus. For packed YUV modes (YUY2, UYVY) use the + <CODE>-vc divx4</CODE> method. For RGB modes the speed is the same, differing + at best according to your current color depth.</P> <P><B>Note:</B> If your <CODE>-vo</CODE> driver supports direct rendering, then <CODE>-vc divx4</CODE> may be faster or even the fastest solution.</P> @@ -91,21 +94,21 @@ <P><B><A NAME=2.2.1.2>2.2.1.2. FFmpeg DivX/libavcodec</A></B></P> -<P>Beginning with version 0.4.2, -<A HREF="http://ffmpeg.sourceforge.net">FFmpeg</A> contains an -<B>open source</B> DivX codec, which is compatible with traditional DivX. -<B>MPlayer</B> supports this codec, making it possible to <B>watch -DivX/DivX4/DivX5/MP41/MP42 movies on non-x86 platforms</B>. Furthermore it -offers higher decoding speed than the Win32 codecs or the original -DivX4 library!</P> - -<P>It also contains a lot of nice codecs, such as RealVideo 1.0, WMV7, - MJPEG, h263, h263+, etc.</P> - -<P>If you use an <B>MPlayer</B> release you have libavcodec right in the package, -just build as usual. If you use <B>MPlayer</B> from CVS you have to extract -libavcodec from the FFmpeg CVS tree as FFmpeg 0.4.5 does <B>not</B> work with -<B>MPlayer</B>. In order to achieve this do:</P> +<P><A HREF="http://ffmpeg.sourceforge.net">FFmpeg</A> contains an + <B>opensource</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 + speed than the Win32 codecs or the ProjectMayo DivX4/5 library!</P> + +<P>It contains a lot of nice codecs, especially important are the MPEG4 + variants: + DivX 3, DivX 4, DivX 5, Windows Media Video 7 (WMV1)</P> + +<P>If you use an <B>MPlayer</B> release you have libavcodec right in the + package, just build as usual. If you use <B>MPlayer</B> from CVS you have to + extract libavcodec from the FFmpeg CVS tree as FFmpeg 0.4.5 does <B>not</B> + work with <B>MPlayer</B>. In order to achieve this do:</P> <OL> <LI><CODE>cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg login</CODE></LI> @@ -118,8 +121,8 @@ </OL> <P><B>Note:</B> MPlayer from CVS does contain a libavcodec -subdirectory, but it does NOT contain the source for libavcodec! -You must follow the steps above to obtain the source for this library.</P> + subdirectory, but it does NOT contain the source for libavcodec! + You must follow the steps above to obtain the source for this library.</P> <P>With FFmpeg and my Matrox G400, I can view even the highest resolution DivX movies without dropped frames on my K6/2 500.</P> @@ -128,15 +131,15 @@ <P><B><A NAME=2.2.1.3>2.2.1.3. XAnim codecs</A></B></P> <P>Foreword:<BR> -Be advised that the XAnim binary codecs are packaged with a piece of text -claiming to be a legally binding software license which, besides other -restrictions, forbids the user to use the codecs in conjunction with any -program other than XAnim. However, the XAnim author has yet to bring legal -action against anyone for codec-related issues. + Be advised that the XAnim binary codecs are packaged with a piece of text + claiming to be a legally binding software license which, besides other + restrictions, forbids the user to use the codecs in conjunction with any + program other than XAnim. However, the XAnim author has yet to bring legal + action against anyone for codec-related issues. </P> <P><B>MPlayer</B> is capable of employing the XAnim codecs for decoding. Follow -the instructions to enable them:</P> + the instructions to enable them:</P> <UL> <LI>Download the codecs you wish to use from the @@ -155,7 +158,7 @@ </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> + 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> @@ -163,39 +166,38 @@ <P><B><A NAME=2.2.1.4>2.2.1.4. VIVO video</A></B></P> <P><B>MPlayer</B> can play Vivo (1.0 and 2.0) videos. The most suitable codec -for 1.0 files is FFmpeg's H263 decoder, you can use it with the <CODE>-vc -ffh263</CODE> option (default) (requires up-to-date libavcodec). For 2.0 files, use -the <CODE>ivvideo.dll</CODE> Win32 DLL file (from <A -HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/ivvideo.dll">here</A>), -and install it under <CODE>/usr/lib/win32</CODE> or wherever you store the -Win32 codecs. This latter codec does not support YV12 nor YUY2 only BGR modes, -restricting it to the X11 and OpenGL outputs. Hopefully ffh263 will support -VIVO 2.0 files in the future.</P> + for 1.0 files is FFmpeg's H263 decoder, you can use it with the <CODE>-vc + ffh263</CODE> option (default) (requires up-to-date libavcodec). For 2.0 + files, use the <CODE>ivvideo.dll</CODE> Win32 DLL file (from + <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/ivvideo.dll">here</A>), + and install it under <CODE>/usr/lib/win32</CODE> or wherever you store the + Win32 codecs. This latter codec does not support YV12 nor YUY2 only BGR + modes, restricting it to the X11 and OpenGL outputs. Hopefully ffh263 will + support VIVO 2.0 files in the future.</P> <P><B><A NAME=2.2.1.5>2.2.1.5. MPEG 1/2 video</A></B></P> -<P>MPEG1 and MPEG2 are decoded by the multiplatform native <B>libmpeg2</B> library, -whose source code is included in <B>MPlayer</B>. -We handle buggy MPEG 1/2 video files by catching sig11 (segmentation fault), -and quickly reinitializing the codec, continuing exactly from where the failure -occurred. -This recovery technique has no measurable speed penalty.</P> +<P>MPEG1 and MPEG2 are decoded by the multiplatform native <B>libmpeg2</B> + library, whose source code is included in <B>MPlayer</B>. We handle buggy + MPEG 1/2 video files by catching sig11 (segmentation fault), and quickly + reinitializing the codec, continuing exactly from where the failure occurred. + This recovery technique has no measurable speed penalty.</P> <P><B><A NAME=2.2.1.6>2.2.1.6. MS Video1</A></B></P> <P>This is a very old and very bad codec from Microsoft. In the past it was -decoded with the <CODE>msvidc32.dll</CODE> Win32 codec, now we have our own -open source implementation (by <A HREF="mailto:melanson@pcisys.net">Mike -Melanson</A>).</P> + decoded with the <CODE>msvidc32.dll</CODE> Win32 codec, now we have our own + open source implementation (by <A HREF="mailto:melanson@pcisys.net">Mike + Melanson</A>).</P> <P><B><A NAME=2.2.1.7>2.2.1.7. Cinepak CVID</A></B></P> <P><B>MPlayer</B> uses its own open source, multiplatform Cinepak decoder by -default. It supports YUV outputs, so that hardware scaling is possible if the -video output driver permits it.</P> + default. It supports YUV outputs, so that hardware scaling is possible if the + video output driver permits it.</P> <P><B><A NAME=2.2.1.8>2.2.1.8. RealVideo</A></B></P> @@ -209,12 +211,10 @@ <P>It is recommended to download and install RealPlayer8 or RealONE, because <B>MPlayer</B> can use their libraries to decode files with RealVideo 2.0 or - RealVideo 3.0 video. You may also just take the RealPlayer libraries from a - full installation and put them in a suitable directory like - <CODE>/usr/lib/real</CODE> or <CODE>$LIBDIR/real</CODE>. The <B>MPlayer</B> - configure script should detect the RealPlayer libraries there or in the - standard locations of a full installation. If it does not, tell configure - where to look with the <CODE>--with-reallibdir</CODE> switch.</P> + RealVideo 3.0 video. The <B>MPlayer</B> configure script should detect the + RealPlayer libraries in the standard locations of a full installation. If it + does not, tell configure where to look with the + <CODE>--with-reallibdir</CODE> switch.</P> <P><B>Note:</B> RealPlayer libraries currently <B>only work with Linux, FreeBSD, NetBSD and Cygwin on the x86 platform</B>!</P> @@ -284,14 +284,16 @@ <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> -<LI>MPEG layer 1 audio (<B>native</B> code, with libavcodec)</LI> -<LI>AC3 Dolby audio (<B>native</B> code, with MMX/SSE/3DNow! optimization)</LI> -<LI>Ogg Vorbis audio codec (<B>native</B> library)</LI> -<LI>Voxware audio (using DirectShow DLL)</LI> -<LI>alaw, msgsm, pcm and other simple old audio formats</LI> -<LI>VIVO audio (g723, Vivo Siren)</LI> -<LI>RealAudio: DNET (low bitrate AC3), Cook, Sipro</LI> + <LI>MPEG layer 2, and layer 3 (MP3) audio (<B>native</B> code, with + MMX/SSE/3DNow! optimization)</LI> + <LI>MPEG layer 1 audio (<B>native</B> code, with libavcodec)</LI> + <LI>AC3 Dolby audio (<B>native</B> code, with MMX/SSE/3DNow! + optimization)</LI> + <LI>Ogg Vorbis audio codec (<B>native</B> library)</LI> + <LI>Voxware audio (using DirectShow DLL)</LI> + <LI>alaw, msgsm, pcm and other simple old audio formats</LI> + <LI>VIVO audio (g723, Vivo Siren)</LI> + <LI>RealAudio: DNET (low bitrate AC3), Cook</LI> </UL> @@ -299,67 +301,66 @@ <P>This is the default decoder used for files with AC3 audio.</P> -<P>The AC3 decoder can create audio output mixes for 2, 4, or 6 -speakers. When configured for 6 speakers, this decoder provides -separate output of all the AC3 channels to the sound driver, -allowing for full "surround sound" experience without the external AC3 -decoder required to use the hwac3 codec.</P> - -<P>Use the <CODE>-channels</CODE> option to select the number of output channels. -Use <CODE>-channels 2</CODE> for a stereo downmix. For a 4 channel downmix (Left -Front, Right Front, Left Surround and Right Surround outputs), use -<CODE>-channels 4</CODE>. In this case, any center channel will be mixed -equally to the front channels. <CODE>-channels 6</CODE> will output all the AC3 -channels as they are encoded - in the order Left, Right, Left Surround, Right -Surround, Center and LFE.</P> +<P>The AC3 decoder can create audio output mixes for 2, 4, or 6 speakers. When + configured for 6 speakers, this decoder provides separate output of all the + AC3 channels to the sound driver, allowing for full "surround sound" + experience without the external AC3 decoder required to use the hwac3 + codec.</P> + +<P>Use the <CODE>-channels</CODE> option to select the number of output + channels. Use <CODE>-channels 2</CODE> for a stereo downmix. For a 4 + channel downmix (Left Front, Right Front, Left Surround and Right Surround + outputs), use <CODE>-channels 4</CODE>. In this case, any center channel will + be mixed equally to the front channels. <CODE>-channels 6</CODE> will output + all the AC3 channels as they are encoded - in the order Left, Right, Left + Surround, Right Surround, Center and LFE.</P> <P>The default number of output channels is 2.</P> -<P>To use more than 2 output channels, you will need to use OSS, and have a sound -card that supports the appropriate number of output channels via the -SNDCTL_DSP_CHANNELS ioctl. An example of a suitable driver is emu10k1 (used by -Soundblaster Live! cards) from August 2001 or newer (ALSA CVS is also supposed to -work).</P> +<P>To use more than 2 output channels, you will need to use OSS, and have a + sound card that supports the appropriate number of output channels via the + SNDCTL_DSP_CHANNELS ioctl. An example of a suitable driver is emu10k1 (used + by Soundblaster Live! cards) from August 2001 or newer (ALSA CVS is also + supposed to work).</P> <P><B><A NAME=2.2.2.2>2.2.2.2. Hardware AC3 decoding</A></B></P> -<P>You need an AC3 capable sound card, with digital out (SP/DIF). The -card's driver must properly support the AFMT_AC3 format (C-Media does). -Connect your AC3 decoder to the SP/DIF output, and use the <CODE>-ac hwac3</CODE> -option. It is experimental but known to work with C-Media cards and Soundblaster -Live! + ALSA (but not OSS) drivers.</P> +<P>You need an AC3 capable sound card, with digital out (SP/DIF). The card's + driver must properly support the AFMT_AC3 format (C-Media does). Connect + your AC3 decoder to the SP/DIF output, and use the <CODE>-ac hwac3</CODE> + option. It is experimental but known to work with C-Media cards and + Soundblaster Live! + ALSA (but not OSS) drivers.</P> <P><B><A NAME=2.2.2.3>2.2.2.3. libmad support</A></B></P> -<P><A HREF="http://mad.sourceforge.net">libmad</A> is a multiplatform MPEG audio -decoding library. It does not handle broken files well, and it sometimes has -problems with seeking.</P> +<P><A HREF="http://mad.sourceforge.net">libmad</A> is a multiplatform MPEG + audio decoding library. It does not handle broken files well, and it + sometimes has problems with seeking.</P> <P>To enable support, compile with the <CODE>--enable-mad</CODE> configure -option.</P> + option.</P> <P><B><A NAME=2.2.2.4>2.2.2.4. VIVO audio</A></B></P> <P>The audio codec used in VIVO files depends on whether it is a VIVO/1.0 or -VIVO/2.0 file. VIVO/1.0 files have <B>g.723</B> audio, and VIVO/2.0 files -have <B>Vivo Siren</B> audio. Both are supported. You can grab the g.723/Siren -Win32 DLL from -<A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/vivog723.acm">here</A>, -then copy it into the <CODE>/usr/lib/win32</CODE> directory.</P> + VIVO/2.0 file. VIVO/1.0 files have <B>g.723</B> audio, and VIVO/2.0 files + have <B>Vivo Siren</B> audio. Both are supported. You can grab the + g.723/Siren Win32 DLL from + <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/vivog723.acm">here</A>, + then copy it into the <CODE>/usr/lib/win32</CODE> directory.</P> <P><B><A NAME=2.2.2.5>2.2.2.5. RealAudio</A></B></P> -<B>MPlayer</B> supports decoding all versions of RealAudio: +<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> - <LI>RealAudio Sipro - decoding supported by <B>RealPlayer libraries</B></LI> + <LI>RealAudio Sipro - not yet supported</LI> </UL> - <P>On how to install RealPlayer libraries, see the <A HREF="formats.html#2.1.1.7">RealMedia file format</A> section.</P> Index: documentation.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/documentation.html,v retrieving revision 1.278 retrieving revision 1.279 diff -u -r1.278 -r1.279 --- documentation.html 30 Jul 2002 18:08:06 -0000 1.278 +++ documentation.html 1 Aug 2002 20:47:46 -0000 1.279 @@ -340,8 +340,8 @@ Mach64, Permedia3) too! Most of them supports software or hardware scaling, so you can enjoy movies in fullscreen. <B>MPlayer</B> supports displaying through some hardware MPEG -decoder boards, such as the <B><A HREF="DVB">DVB</A></B> and <B> <A -HREF="DXR3">DXR3/Hollywood+</A></B> ! And what about the nice big antialiased +decoder boards, such as the <B><A HREF="video.html#2.3.1.16">DVB</A></B> and +<B><A HREF="video.html#2.3.1.17">DXR3/Hollywood+</A></B>! And what about the nice big antialiased shaded subtitles (<B>10 supported types!!!</B>) with european/ISO 8859-1,2 (Hungarian, English, Czech, etc), Cyrillic, Korean fonts, and the onscreen display (OSD)?</P> @@ -393,7 +393,7 @@ <LI><B>MPlayer 0.18 "The BugCounter"</B> Jul 9, 2001<BR> 2 months since 0.17 and here's a new release.. Completed ASF support, more subtitle formats, introduced libao (similar to libvo but to audio), - even more stable than ever, and so on. It's a MUST !</LI> + even more stable than ever, and so on. It's a MUST!</LI> <LI><B>MPlayer 0.50 "The Faszom(C)ounter"</B> Oct 8, 2001<BR> Hmm. Release again. Tons of new features, beta GUI version, bugs fixed, new vo and ao drivers, ported to many systems, including opensource DivX @@ -402,7 +402,7 @@ MOV/VIVO/RM/FLI/NUV fileformats support, native CRAM, Cinepak, ADPCM codecs, and support for XAnim's binary codecs; DVD subtitles support, first release of MEncoder, TV grabbing, cache, liba52, countless fixes.</LI> -<LI><B>MPlayer 0.90 "?"</B> Jul? ??, 2002<BR> +<LI><B>MPlayer 0.90 "?"</B> Aug? ??, 2002<BR> </LI> </UL> @@ -461,61 +461,65 @@ <P><B>CODECS</B></P> <UL> -<LI><B>libavcodec</B> : If you want to use this DivX3/DivX4/DivX5/MP41/MP42/etc -codec, check the -<A HREF="codecs.html#2.2.1.2">2.2.1.2</A> section before compiling. Features :<BR> -<UL> - <LI>you can <B>gain DivX/DivX4/DivX5/MP41/MP42 playback on non-x86 - machines</B></LI> - <LI>RealVideo 1.0/VIVO/MJPEG/h263/others playing and encoding</LI> - <LI>this codec has the <B>greatest decoding speed</B> for DivX and DivX4/DivX5 -movies (even faster than the original DivX4 library itself) ! Recommended!</LI> +<LI><B>libavcodec</B>: This codec package is capable of decoding + H263/MJPEG/RV10/DivX3/DivX4/DivX5/MP41/MP42/WMV1 encoded video streams, on + multiple platforms. It is also known to be the fastest for this task. + Details can be found <A HREF="codecs.html#2.2.1.2">here</A>. Features:<BR> +<UL> + <LI>gain decoding of videos mentioned above, on non-x86 machines</B></LI> + <LI>encoding with most of the mentioned codecs</LI> + <LI>this codec is the <B>fastest codec available</B> for DivX/3/4/5 and other + MPEG4 types. Recommended!</LI> </UL> </LI> -<LI><B>Win32 codecs</B> : If you plan to use <B>MPlayer</B> on x86 -architecture, you will possibly need them. Download and unzip w32codecs.zip to -/usr/lib/win32 <B>BEFORE</B> compiling <B>MPlayer</B>, otherwise no Win32 -support will be compiled!<BR> -Note: the avifile project has similar codecs package, but it -differs from ours, so if you want to use all supported codecs, then use our -package! However, you can use our codecs package with avifile. Features:<BR> -<UL> - <LI>you need this if you want to play or encode for example movies recorded - with various hardware compressors, like tuner cards, digital cameras (example: DV, ATI VCR, MJPEG)</LI> - <LI>needed if you want to play <B>WMV8 movies</B>. Not needed for old - ASF's with MP41 or MP42 video (though VoxWare audio is frequent for these - files - it's done by the Win32 codec), or WMV7.</LI> -</UL> +<LI><B>Win32 codecs</B>: If you plan to use <B>MPlayer</B> on x86 + architecture, you will possibly need them. Download and unzip w32codecs.zip + to /usr/lib/win32 <B>BEFORE</B> compiling <B>MPlayer</B>, otherwise no Win32 + support will be compiled!<BR> + <B>Note</B>: the avifile project has similar codecs package, but it differs + from ours, so if you want to use all supported codecs, then use our package! + However, you can use our codecs package with avifile. Features:<BR> + <UL> + <LI>you need this if you want to play or encode for example movies recorded + with various hardware compressors, like tuner cards, digital cameras (example: DV, ATI VCR, MJPEG)</LI> + <LI>needed if you want to play <B>WMV8 movies</B>. Not needed for old + ASF's with MP41 or MP42 video (though VoxWare audio is frequent for these + files - it's done by the Win32 codec), or WMV7.</LI> + </UL> </LI> -<LI><B>DivX4/DivX5</B> : information about this codec is available in the -<A HREF="codecs.html#2.2.1.1">2.2.1.1</A> section. If you don't want to encode -with it, you possibly don't want this codec as <B>libavcodec</B> (see above) is -much faster than this.<BR> -Features: -<UL> - <LI>1 pass or 2 pass encoding with <A HREF="encoding.html">MEncoder</A></LI> - <LI>can play old <B>DivX3</B> movies much faster than the Win32 DLL but - slower than <B>libavcodec</B> !</LI> - <LI>it's closed-source, and only an x86 version is available.</LI> -</UL> +<LI><B>DivX4/DivX5</B>: information about this codec is available in the + <A HREF="codecs.html#2.2.1.1">2.2.1.1</A> section. You possibly don't want + this codec as <B>libavcodec</B> (see above) is much faster and has better + quality than this, for both decoding and encoding.<BR> + Features: + <UL> + <LI>1 pass or 2 pass encoding with + <A HREF="encoding.html">MEncoder</A></LI> + <LI>can play old <B>DivX3</B> movies much faster than the Win32 DLL but + slower than <B>libavcodec</B>!</LI> + <LI>it's closed-source, and only an x86 version is available.</LI> + </UL> </LI> -<LI><B>XviD</B> : Open source encoding alternative to Divx4Linux<BR> -Features: -<UL> - <LI>1 pass or 2 pass encoding with <A HREF="encoding.html">MEncoder</A></LI> - <LI>it's open-source, so not only an x86 version is available.</LI> - <LI>it's about 2 times faster than divx4 when encoding - about the same quality</LI> -</UL> +<LI><B>XviD</B>: Open source encoding alternative to Divx4Linux<BR> + Features: + <UL> + <LI>1 pass or 2 pass encoding with + <A HREF="encoding.html">MEncoder</A></LI> + <LI>it's open-source, so it's multiplatform.</LI> + <LI>it's about 2 times faster than DivX4 when encoding - about the same + quality</LI> + </UL> </LI> -<LI>The <A HREF="codecs.html#2.2.1.3">XAnim codecs</A> are the best (full screen, -hardware YUV zoom) for decoding <B>3ivx</B> and Indeo 3/4/5 movies, and some -old formats. And they are multiplatform, so this is the only way to play Indeo on -non-x86 platforms (well, apart from using XAnim:). But for example Cinepak -movies are best played with <B>MPlayer</B>'s own Cinepak decoder !</LI> +<LI>The <A HREF="codecs.html#2.2.1.3">XAnim codecs</A> are the best (full + screen, hardware YUV zoom) for decoding <B>3ivx</B> and Indeo 3/4/5 movies, + and some old formats. And they are multiplatform, so this is the only way to + play Indeo on non-x86 platforms (well, apart from using XAnim:). But for + example Cinepak movies are best played with <B>MPlayer</B>'s own Cinepak + decoder!</LI> <LI>For <B>Ogg Vorbis</B> audio decoding you need to install <CODE>libvorbis</CODE> properly. Use deb/rpm packages if available, or @@ -527,7 +531,6 @@ files with <B>RealVideo 2.0 and 3.0</B> video, and Sipro/Cook audio. See <A HREF="formats.html#2.1.1.7">RealMedia file format</A> section for installation instructions and more information!</LI> - </UL> <P><B>VIDEO CARDS</B></P> @@ -552,7 +555,7 @@ compiling <B>MPlayer</B>, otherwise no mga_vid support will be built. Also check out the <A HREF="video.html#2.3.1.A.1">Matrox TV-out</A> section. <U><B>If you are non-Linux user</B></U>, your only possibility is the Vidix - driver: read <A HREF="video.html#2.3.1.15">Vidix</A> documentation !</LI> + driver: read <A HREF="video.html#2.3.1.15">Vidix</A> documentation!</LI> <LI><B>3Dfx Voodoo3/Banshee cards</B>: please see the <A HREF="video.html#2.3.1.9">2.3.1.9</A> section in order to gain big @@ -569,19 +572,19 @@ section</A> of the TV-out documentation, to know if you card's TV-out is supported under Linux/MPlayer.</LI> -<LI><B>S3 cards</B>: the Savage and Virge/DX chips have hardware acceleration. Use as -new XFree86 version as possible, older drivers are buggy. Savage chips -have problems with YV12 display, see <A HREF="video.html#2.3.1.2.2">S3 Xv -section</A> for details. Older, Trio cards have no, or slow hardware -support.</LI> +<LI><B>S3 cards</B>: the Savage and Virge/DX chips have hardware acceleration. + Use as new XFree86 version as possible, older drivers are buggy. Savage chips + have problems with YV12 display, see <A HREF="video.html#2.3.1.2.2">S3 Xv + section</A> for details. Older, Trio cards have no, or slow hardware + support.</LI> <LI><B>nVidia cards</B>: very bad choice for video playing (nVidia has -<A HREF="users_against_developers.html#nvidia">different opinion</A>!). -nVidia's cards have very cheap and bad -quality chips. Moreover, <U>the built-in nVidia driver in XFree86 doesn't -contain support for hardware YUV acceleration for all nVidia cards !</U> -You have to download nVidia's closed-source drivers from nVidia.com. See -details in <A HREF="video.html#2.3.1.2.3">nVidia Xv driver</A> section.</LI> + <A HREF="users_against_developers.html#nvidia">different opinion</A>!). + nVidia's cards have very cheap and bad quality chips. Moreover, <U>the + built-in nVidia driver in XFree86 doesn't contain support for hardware YUV + acceleration for all nVidia cards!</U> You have to download nVidia's + closed-source drivers from nVidia.com. See details in <A + HREF="video.html#2.3.1.2.3">nVidia Xv driver</A> section.</LI> <LI><B>3DLabs GLINT R3 and Permedia3</B>: a Vidix driver is provided (pm3_vid). Please see the <A HREF="video.html#2.3.1.15">Vidix @@ -592,11 +595,12 @@ <LI>Try if the XFree86 driver (and your card) supports hardware acceleration. See the <A HREF="video.html#2.3.1.2">Xv section</A> for details.</LI> - <LI>If it doesn't, then your card's video features aren't supported under your OS :(<BR> - If it does hardware scaling under Windows, it doesn't mean it will do the same - under Linux or other OS, it depends on the drivers! Most manufacturers don't - make Linux drivers nor release chip specs - so you're unlucky if using their cards. - See next section: + <LI>If it doesn't, then your card's video features aren't supported under + your OS :(<BR> + If it does hardware scaling under Windows, it doesn't mean it will do the + same under Linux or other OS, it depends on the drivers! Most + manufacturers don't make Linux drivers nor release chip specs - so you're + unlucky using their cards. See the next section: </LI> </UL> </LI> @@ -606,57 +610,83 @@ <P> <B>Non-YUV cards</B></P> -<P> -Fullscreen playing can be achieved by either zooming -<B>by software</B> (use the option -zoom, but i warn you: this is slooow!), -or changing to a smaller video mode, for -example to 352x288. If you don't have YUV acceleration, this latter method is -the recommended one. Throughout <B>MPlayer</B>, <U>this behavior can -be switched on by using the <CODE>-vm</CODE> option</U> and with -the following drivers : +<P>Fullscreen playing can be achieved by either zooming <B>by software</B> (use + the option <CODE>-zoom</CODE> or <A HREF="#2.6.11"><CODE>-vop + scale</CODE></A>, but I warn you: this is SLOW!), or changing to a smaller + video mode, for example to 352x288. If you don't have YUV acceleration, this + latter method is the recommended one. Throughout <B>MPlayer</B>, <U>this + behavior can be switched on by using the <CODE>-vm</CODE> option</U> and with + the following drivers: </P> <UL> - <LI><B>using</B> XFree86 : see details in + <LI><B>using</B> XFree86: see details in <A HREF="video.html#2.3.1.3">DGA driver</A> and <A HREF="video.html#2.3.1.13">X11 driver</A> sections. DGA is recommended! Also try DGA via SDL, sometimes it's better.</LI> - <LI><B>not using</B> XFree86 : try the drivers in the following order : + <LI><B>not using</B> XFree86: try the drivers in the following order: <A HREF="video.html#2.3.1.12">vesa</A>, <A HREF="video.html#2.3.1.6">fbdev</A>, <A HREF="video.html#2.3.1.5">svgalib</A>, <A HREF="video.html#2.3.1.11">aalib</A>.</LI> </UL> +<P>Some cards:</P> + +<UL> + <LI><B>Cirrus Logic cards</B>: + <UL> + <LI>GD 7548: present on-board and tested in Compaq Armada 41xx notebook + series. + <UL> + <LI>XFree86 3: works in 8/16bpp modes. However, the driver is + dramatically slow, and very buggy in 16bpp.</LI> + <LI>XFree86 4: the Xserver freezes soon after start, unless + connected to a monitor.</LI> + <LI>FBdev: the card is only VBE 1.2 capable, so VESA framebuffer + can't be used. When tried to workaround with UniVBE, the + framebuffer was unusably full of debris.</LI> + <LI>VESA: the card is only VBE 1.2 capable, so VESA output can't be + used. Can't be workarounded with UniVBE.</LI> + <LI>SVGAlib: detects an older Cirrus chip. Usable with + <CODE>-bpp 8</CODE>. <B>Recommended</B>.</LI> + </UL> + </LI> + </UL> + </LI> +</UL> + + <P><B>SOUND CARDS</B></P> <UL> -<LI><B>Soundblaster Live!</B> : with this card you can use 4 or 6 (<B>5.1</B>) -channels AC3 decoding instead of 2. Read the -<A HREF="codecs.html#2.2.2.1">Software AC3 decoding</A> section. -For hardware AC3 passthrough you MUST use ALSA 0.9 oss emulation!</LI> +<LI><B>Soundblaster Live!</B>: with this card you can use 4 or 6 (<B>5.1</B>) + channels AC3 decoding instead of 2. Read the + <A HREF="codecs.html#2.2.2.1">Software AC3 decoding</A> section. + For hardware AC3 passthrough you MUST use ALSA 0.9 oss emulation!</LI> -<LI><B>C-Media with SP/DIF out</B> : hardware AC3 passthrough is possible +<LI><B>C-Media with SP/DIF out</B>: hardware AC3 passthrough is possible with these cards, see <A HREF="codecs.html#2.2.2.2">Hardware AC3 decoding</A> section.</LI> <LI><B>other cards'</B> features aren't supported by <B>MPlayer</B>. <U>It's very recommended to read the <A HREF="sound.html#2.3.2">sound card - section</A> !</U> + section</A>!</U></LI> </UL> <P><B>FEATURES</B></P> <UL> <LI>Decide if you need GUI. If you do, see the <A HREF="#1.4">1.4 section</A> -before compiling.</LI> + before compiling.</LI> <LI>If you want to install <B>MEncoder</B> (our great all-purpose encoder), -see the <A HREF="encoding.html#2.4">MEncoder section</A> .</LI> + see the <A HREF="encoding.html#2.4">MEncoder section</A>.</LI> -<LI>If you have a V4L compatible <B>TV tuner</B> card, and wish to watch/grab and -encode movies with <B>MPlayer</B>, read the <A HREF="#2.5">TV input</A> section.</LI> +<LI>If you have a V4L compatible <B>TV tuner</B> card, and wish to watch/grab + and encode movies with <B>MPlayer</B>, read the <A HREF="#2.5">TV input</A> + section.</LI> <LI>There are three timing methods in <B>MPlayer</B>. <UL> @@ -672,7 +702,7 @@ RTC frequency for normal users through the <CODE>/proc</CODE> filesystem. Use this command to enable RTC for normal users: <P> - <CODE>echo 1024 > /proc/sys/dev/rtc/max-user-freq</CODE> + <CODE>echo 1024 > /proc/sys/dev/rtc/max-user-freq</CODE> </P> If you do not have such a new kernel, you can also change one line in <CODE>drivers/char/rtc.c</CODE> and recompile your kernel. Find the @@ -702,9 +732,8 @@ </LI> </UL> -Note: <B>NEVER install a setuid root MPlayer binary on a -multiuser system!</B> It's a clear way for everyone to gain root. - +Note: <B>NEVER install a setuid root MPlayer binary on a multiuser system!</B> +It's a clear way for everyone to gain root. <P>Then build <B>MPlayer</B>:</P> @@ -715,29 +744,30 @@ </PRE> <P>At this point, <B>MPlayer</B> is ready to use. The directory -<CODE>$PREFIX/share/mplayer</CODE> contains the <CODE>codecs.conf</CODE> -file, which is used to tell the program all the codecs and their capabilities. -This file should always be kept uptodate together with the main binary !<BR> -Check if you have codecs.conf in your home directory (~/.mplayer/codecs.conf) -left from old MPlayer versions, and remove it!</P> + <CODE>$PREFIX/share/mplayer</CODE> contains the <CODE>codecs.conf</CODE> + file, which is used to tell the program all the codecs and their + capabilities. This file should always be kept uptodate together with the + main binary!<BR> Check if you have codecs.conf in your home directory + (~/.mplayer/codecs.conf) left from old MPlayer versions, and remove it!</P> <P><B>Debian users</B> can build a .deb package for themselves, it's very -simple. Just exec <CODE>fakeroot debian/rules binary</CODE> in <B>MPlayer</B>'s -root dir. Detailed instructions can be found <A HREF="documentation.html#6.1">here</A>.</P> + simple. Just exec <CODE>fakeroot debian/rules binary</CODE> in + <B>MPlayer</B>'s root dir. Detailed instructions can be found + <A HREF="documentation.html#6.1">here</A>.</P> <P><B>ALWAYS browse the output of <CODE>./configure</CODE></B>, and the -<CODE>configure.log</CODE> file, they contain information about what will be -built, and what will not. You may also want to view <CODE>config.h</CODE> and -<CODE>config.mak</CODE> files.<BR> -If you have some libraries installed, but not detected by <CODE>./configure</CODE>, -then check if you also have the proper header files (usually the -dev packages) -and their version matches. The <CODE>configure.log</CODE> file usually tells -you what is missing.</P> - -<P>Though not mandatory, the fonts should be installed in order to gain -OSD, and subtitle functionality. Download <CODE>mp-arial-iso-8859-*.zip</CODE> -and/or optional (if exists) language updates. It's VERY RECOMMENDED to check -<A HREF="#1.5">section 1.5</A> for details.</P> + <CODE>configure.log</CODE> file, they contain information about what will be + built, and what will not. You may also want to view <CODE>config.h</CODE> and + <CODE>config.mak</CODE> files.<BR> + If you have some libraries installed, but not detected by + <CODE>./configure</CODE>, then check if you also have the proper header files + (usually the -dev packages) and their version matches. The + <CODE>configure.log</CODE> file usually tells you what is missing.</P> + +<P>Though not mandatory, the fonts should be installed in order to gain OSD, + and subtitle functionality. Download <CODE>mp-arial-iso-8859-*.zip</CODE> + and/or optional (if exists) language updates. It's VERY RECOMMENDED to check + section <A HREF="#1.5">1.5</A> for details.</P> <PRE> mkdir ~/.mplayer/font @@ -750,86 +780,94 @@ <P><B><A NAME=1.4>1.4. What about the GUI?</A></B></P> <P>The GUI needs GTK (it isn't GTK, but the panels are). The skins are stored -in PNG format, so gtk, libpng (and their devel stuff) has to be installed. -You can build it by specifying <CODE>--enable-gui</CODE> during -<CODE>./configure</CODE>. Then, to turn on GUI mode, you either</P> -<UL> - <LI>use the <CODE>-gui</CODE> option</LI> - <LI>specify <CODE>gui=yes</CODE> in your config file</LI> - <LI><CODE>ln -s $PREFIX/bin/mplayer $PREFIX/bin/gmplayer</CODE> , - and call <CODE>gmplayer</CODE> instead. -</UL> + in PNG format, so gtk, libpng (and their devel stuff) has to be installed. + You can build it by specifying <CODE>--enable-gui</CODE> during + <CODE>./configure</CODE>. Then, to turn on GUI mode, you either</P> + <UL> + <LI>use the <CODE>-gui</CODE> option</LI> + <LI>specify <CODE>gui=yes</CODE> in your config file</LI> + <LI><CODE>ln -s $PREFIX/bin/mplayer $PREFIX/bin/gmplayer</CODE> , + and call <CODE>gmplayer</CODE> instead.</LI> + </UL> <P>HINT: use the middle button (on 2 button mice press left and right -simultaneously) for a popup GTK menu, with DVD playing option!</P> + simultaneously) for a popup GTK menu, with DVD playing option!</P> -<P>As <B>MPlayer</B> doesn't have a skin included, you have to download them -if you want to use the GUI. See the <A HREF="http://www.mplayerhq.hu/homepage/dload.html">download page</A>. -They should be extracted to the usual system-wide directory (<CODE>$PREFIX/share/mplayer/Skin</CODE>), -or to <CODE>$HOME/.mplayer/Skin</CODE> . <B>MPlayer</B> by default looks in -these directories for a <I>default</I> named directory, but you can use the -<CODE>-skin newskin</CODE> option, or the <CODE>skin=newskin</CODE> config file -directive to use the skin in <CODE>*/Skin/newskin</CODE> directory.</P> +<P>As <B>MPlayer</B> doesn't have a skin included, you have to download them if + you want to use the GUI. See the + <A HREF="http://www.mplayerhq.hu/homepage/dload.html">download page</A>. + They should be extracted to the usual system-wide directory + (<CODE>$PREFIX/share/mplayer/Skin</CODE>), or to + <CODE>$HOME/.mplayer/Skin</CODE>. <B>MPlayer</B> by default looks in these + directories for a directory named <I>default</I>, but you can use the + <CODE>-skin newskin</CODE> option, or the <CODE>skin=newskin</CODE> config + file directive to use the skin in <CODE>*/Skin/newskin</CODE> directory.</P> <P><B><A NAME=1.5>1.5. Subtitles and OSD</A></B></P> <P> -<B>MPlayer</B> can display subtitles along with movie files. Currently the following -formats are supported:</P> + <B>MPlayer</B> can display subtitles along with movie files. Currently the following + formats are supported:</P> <UL> -<LI>VobSub</LI> -<LI>Microdvd</LI> -<LI>SubRip</LI> -<LI>SubViewer</LI> -<LI>Sami</LI> -<LI>VPlayer</LI> -<LI>RT</LI> -<LI>SSA</LI> -<LI>MPsub</LI> -<LI>AQTitle</LI> + <LI>VobSub</LI> + <LI>Microdvd</LI> + <LI>SubRip</LI> + <LI>SubViewer</LI> + <LI>Sami</LI> + <LI>VPlayer</LI> + <LI>RT</LI> + <LI>SSA</LI> + <LI>MPsub</LI> + <LI>AQTitle</LI> </UL> + The command line options differ slightly for the different formats: <P> -<B>VobSub subtitles</B><BR> -VobSub subtitles consist of a big (some megabytes) .SUB file, and optional -.IDX and/or .IFO files.<BR> -Usage : if you have files like <CODE>sample.sub</CODE>, <CODE>sample.ifo</CODE>, -<CODE>sample.idx</CODE> - you have to pass the <CODE>-vobsub sample -vobsubid -<id></CODE> options (optionally with pathname, of course). The -<CODE>-vobsubid</CODE> option is like <CODE>-sid</CODE> for DVDs, you can -choose between subtitle tracks (languages) with it.</P> + <B>VobSub subtitles</B><BR> + VobSub subtitles consist of a big (some megabytes) .SUB file, and optional + .IDX and/or .IFO files.<BR> + Usage: if you have files like <CODE>sample.sub</CODE>, + <CODE>sample.ifo</CODE>, <CODE>sample.idx</CODE> - you have to pass the + <CODE>-vobsub sample -vobsubid + <id></CODE> options (optionally with pathname, of course). The + <CODE>-vobsubid</CODE> option is like <CODE>-sid</CODE> for DVDs, you can + choose between subtitle tracks (languages) with it.</P> <P> -<B>Other subtitles</B><BR> -The other formats consist of a single text file containing timing, placement -and text information.<BR> -Usage : if you have a file like <CODE>sample.txt</CODE>, you have to pass -the option <CODE>-sub sample.txt</CODE> (optionally with pathname, of course). + <B>Other subtitles</B><BR> + The other formats consist of a single text file containing timing, placement + and text information.<BR> + Usage: if you have a file like <CODE>sample.txt</CODE>, you have to pass the + option <CODE>-sub sample.txt</CODE> (optionally with pathname, of course). </P> <P> -<B>Adjusting subtitle timing and placement</B><BR> - -<CODE>-subdelay <sec></CODE> : Delays subtitles by <sec> seconds. Can be negative.<BR> -<CODE>-subfps <rate></CODE> : Specify frame/sec rate of subtitle file (float number)<BR> -<CODE>-subpos <0 - 100></CODE> : Specify the position of subtitles.<BR> + <B>Adjusting subtitle timing and placement</B><BR> + <CODE>-subdelay <sec></CODE>: Delays subtitles by <sec> seconds. + Can be negative.<BR> + <CODE>-subfps <rate></CODE>: Specify frame/sec rate of subtitle file + (float number)<BR> + <CODE>-subpos <0 - 100></CODE>: Specify the position of subtitles.<BR> </P> -<P> -If you experience a growing delay between the movie and the subtitles when using a MicroDVD -subtitle file, most likely the frame rate of the movie and the subtitle file are different.<BR> -Please note that the MicroDVD subtitle format uses absolute frame numbers for its -timing, and therefore the <CODE>-subfps</CODE> option cannot be used with this format. As -<B>MPlayer</B> has no way to guess the frame rate of the subtitle file, you have to manually -convert the frame rate. There is a little perl script in the <CODE>contrib</CODE> directory of -the MPlayer FTP site to do this conversion for you.</P> + +<P>If you experience a growing delay between the movie and the subtitles when + using a MicroDVD subtitle file, most likely the frame rate of the movie and + the subtitle file are different.<BR> Please note that the MicroDVD subtitle + format uses absolute frame numbers for its timing, and therefore the + <CODE>-subfps</CODE> option cannot be used with this format. As + <B>MPlayer</B> has no way to guess the frame rate of the subtitle file, you + have to manually convert the frame rate. There is a little perl script in the + <CODE>contrib</CODE> directory of the MPlayer FTP site to do this conversion + for you.</P> <P>About DVD subtitles, read the <A HREF="cd-dvd.html#4.2">DVD section</A>.</P> -<P><B>MPlayer</B> introduces a new subtitle format called <B>MPsub</B>. -It was designed by me (Gabucino). Basically its main feature is being -<I>dynamically</I> time-based (although it has frame-based mode too). Example (from -<A HREF="http://www.mplayerhq.hu/DOCS/tech/mpsub.sub">DOCS/tech/mpsub.sub</A>) : +<P><B>MPlayer</B> introduces a new subtitle format called <B>MPsub</B>. It was + designed by me (Gabucino). Basically its main feature is being + <I>dynamically</I> time-based (although it has frame-based mode too). Example + (from + <A HREF="tech/mpsub.sub">DOCS/tech/mpsub.sub</A>): </P> <P><CODE><I> @@ -846,64 +884,68 @@ Naboo was under an attack.<BR> </I></CODE></P> -<P>So you see, the main goal was to <B>make subtitle editing/timing/joining/cutting easy</B>. And, -if you - say - get an SSA subtitle but it's badly timed/delayed to your -version of the movie, you simply do a <CODE>mplayer dummy.avi -sub source.ssa --dumpmpsub</CODE> . A <CODE>dump.mpsub</CODE> file will be created in the -current directory, which will contain the source subtitle's text, but in -<B>MPsub</B> format. Then you can freely add/subtract seconds to/from the -subtitle.</P> - -<P>Subtitles are displayed with a technique called <B>'OSD', On Screen Display</B>. -OSD is used to display current time, volume bar, seek bar etc.</P> +<P>So you see, the main goal was to <B>make subtitle + editing/timing/joining/cutting easy</B>. And, if you - say - get an SSA + subtitle but it's badly timed/delayed to your version of the movie, you + simply do a <CODE>mplayer dummy.avi -sub source.ssa -dumpmpsub</CODE>. + A <CODE>dump.mpsub</CODE> file will be created in the current directory, + which will contain the source subtitle's text, but in <B>MPsub</B> format. + Then you can freely add/subtract seconds to/from the subtitle.</P> + +<P>Subtitles are displayed with a technique called <B>'OSD', On Screen + Display</B>. OSD is used to display current time, volume bar, seek bar + etc.</P> <P><B>INSTALLING OSD and SUB</B></P> <P>You need an <B>MPlayer</B> font package to be able to use OSD/SUB feature. -There are many ways to get it:</P> -<UL> + There are many ways to get it:</P> -<LI>download ready-to-use font packages from <B>MPlayer</B> site. -Note: currently available fonts are limited for iso 8859-1/2 support, -but there are some other (including Korean, Russian, 8859-8 etc) fonts -at contrib/font section of FTP, made by users. - -Font should have appropriate font.desc file which maps unicode font -positions to the actual code page of the subtitles text. Other solution -is to have subtitles encoded in utf8 encoding and use -utf8 option -or just name the subtitles file <video_name>.utf and have it in the same -dir as the video file. Recoding from different codepages to utf8 could be -done by using konwert (Debian) or iconv (Red Hat) programs.<BR> -Some URLs: <UL> - <LI><A HREF="ftp://ftp.mplayerhq.hu/MPlayer/releases/">ftp://ftp.mplayerhq.hu/MPlayer/releases/</A> - ISO fonts - <LI><A HREF="ftp://ftp.mplayerhq.hu/MPlayer/contrib/fonts/">ftp://ftp.mplayerhq.hu/MPlayer/contrib/fonts/</A> - various fonts by users - <LI><A HREF="http://realtime.ssu.ac.kr/~lethean/mplayer">http://realtime.ssu.ac.kr/~lethean/mplayer</A> - Korean fonts & RAW plugin -</UL> -</LI> + <LI>download ready-to-use font packages from <B>MPlayer</B> site. + Note: currently available fonts are limited for iso 8859-1/2 support, + but there are some other (including Korean, Russian, 8859-8 etc) fonts + at contrib/font section of FTP, made by users.<BR> + <BR> + Font should have appropriate font.desc file which maps unicode font + positions to the actual code page of the subtitles text. Other solution is + to have subtitles encoded in utf8 encoding and use <CODE>-utf8</CODE> + option or just name the subtitles file <video_name>.utf and have it + in the same dir as the video file. Recoding from different codepages to + utf8 could be done by using konwert (Debian) or iconv (Red Hat) + programs.<BR> + Some URLs: + <UL> + <LI><A HREF="ftp://ftp.mplayerhq.hu/MPlayer/releases/">ftp://ftp.mplayerhq.hu/MPlayer/releases/</A> - ISO fonts + <LI><A HREF="ftp://ftp.mplayerhq.hu/MPlayer/contrib/fonts/">ftp://ftp.mplayerhq.hu/MPlayer/contrib/fonts/</A> - various fonts by users + <LI><A HREF="http://realtime.ssu.ac.kr/~lethean/mplayer">http://realtime.ssu.ac.kr/~lethean/mplayer</A> - Korean fonts & RAW plugin + </UL> + </LI> -<LI>use the font generator tool at TOOLS/subfont-c -It's a complete tool to convert from TTF/Type1/etc font to mplayer font pkg. -(read TOOLS/subfont-c/README for details)</LI> + <LI>use the font generator tool at TOOLS/subfont-c + It's a complete tool to convert from TTF/Type1/etc font to mplayer font pkg. + (read TOOLS/subfont-c/README for details)</LI> -<LI>use the font generator GIMP plugin at TOOLS/subfont-GIMP -(note: you must have HSI RAW plugin too, see URL below)</LI> + <LI>use the font generator GIMP plugin at TOOLS/subfont-GIMP + (note: you must have HSI RAW plugin too, see URL below)</LI> </UL> <P>After that, UNZIP the file you downloaded to <CODE>~/.mplayer</CODE> or -<CODE>$PREFIX/share/mplayer</CODE>. Then rename or symlink one of them to -<CODE>font</CODE> (like : <CODE>ln -s ~/.mplayer/arial-24 -~/.mplayer/font</CODE>). Now you have to see a timer at the upper left corner -of the movie (switch it off with the "o" key).</P> + <CODE>$PREFIX/share/mplayer</CODE>. Then rename or symlink one of them to + <CODE>font</CODE> (like: <CODE>ln -s ~/.mplayer/arial-24 + ~/.mplayer/font</CODE>). Now you have to see a timer at the upper left corner + of the movie (switch it off with the "o" key).</P> <P>OSD has 3 states: (switch with 'o')</P> + <UL> - <LI>timer + volume bar + seek bar + subtitles (default) - <LI>volume bar + seek bar + subtitles - <LI>subtitles only + <LI>timer + volume bar + seek bar + subtitles (default)</LI> + <LI>volume bar + seek bar + subtitles</LI> + <LI>subtitles only</LI> </UL> -<P>You can change default behaviour by setting <CODE>osdlevel=</CODE> variable in config file.</P> +<P>You can change default behaviour by setting <CODE>osdlevel=</CODE> variable + in config file.</P> <P><B><A NAME=2>2. Features</A></B></P> @@ -1052,11 +1094,11 @@ </P> <P> -<B>Note:</B><BR> -If you have a TV card with an external audio device and get only a black -screen, although input works with xawtv or similar, then try to use the -<CODE>-noaudio</CODE> option. For the example above this would be:<BR> -<CODE>    mplayer -tv on:noaudio:driver=v4l:width=640:height=480:outfmt=i420 -vc rawi420 -vo xv</CODE> + <B>Note:</B><BR> + If you have a TV card with an external audio device and get only a black + screen, although input works with xawtv or similar, then try to use the + <CODE>-noaudio</CODE> option. For the example above this would be:<BR> + <CODE>    mplayer -tv on:noaudio:driver=v4l:width=640:height=480:outfmt=i420 -vc rawi420 -vo xv</CODE> </P> @@ -1435,7 +1477,7 @@ <P><B>Mouse</B></P> -<P>Note : mouse is only supported under X</P> +<P>Note: mouse is only supported under X</P> <UL> <LI>MOUSE_BTN0 (Left button)</LI> @@ -1449,7 +1491,7 @@ <P><B>Joystick</B></P> -<P>Note : joystick support must be enabled at compile time</P> +<P>Note: joystick support must be enabled at compile time</P> <UL> <LI>JOY_RIGHT or JOY_AXIS0_PLUS</LI> @@ -1589,7 +1631,7 @@ </PRE> <P>If you don't like the standard location for the lirc-config file (~/.lircrc) -use the -lircconf <filename> switch to specify another file.</P> + use the -lircconf <filename> switch to specify another file.</P> <P><B><A NAME=3.2.4>3.2.4. Slave mode</A></B></P> @@ -1603,17 +1645,19 @@ <P><B>MPlayer</B> can play files from network, using the HTTP or MMS protocol.</P> -<P>Playing goes by simply using adding the URL to the command line. <B>MPlayer</B> -also honors the http_proxy environment variable, and uses proxy if available. -Proxy usage can also be forced :</P> +<P>Playing goes by simply using adding the URL to the command line. + <B>MPlayer</B> also honors the http_proxy environment variable, and uses + proxy if available. Proxy usage can also be forced:</P> <P><CODE>mplayer http_proxy://proxy.micorsops.com:3128/http://micorsops.com:80/stream.asf</CODE></P> <P><B>MPlayer</B> can read from stdin (NOT named pipes). This can be for example -used to play from FTP:</P> + used to play from FTP:</P> + <P><CODE>  wget ftp://micorsops.com/something.avi -O - | mplayer -</CODE></P> <P>Note: it's also recommended to enable CACHE when playback from network:</P> + <P><CODE>  wget ftp://micorsops.com/something.avi -O - | mplayer -cache 8192 -</CODE></P> @@ -1629,7 +1673,7 @@ <P><B><A NAME=6.1>6.1. Debian packaging</A></B></P> <P>To build the package, get the cvs version, or .tgz and uncompress it, -and cd into programs directory:</P> + and cd into programs directory:</P> <PRE> cd main @@ -1637,7 +1681,7 @@ </PRE> <P>(... mplayer detects hardware/software, builds itself and.. ) -dpkg-deb: building package `mplayer' in `../mplayer_0.90-1_i386.deb'.</P> + dpkg-deb: building package `mplayer' in `../mplayer_0.90-1_i386.deb'.</P> <P>And now just become root, and:</P> @@ -1660,15 +1704,15 @@ <P><B><A NAME=6.2>6.2. FreeBSD</A></B></P> <P>To build the package you will need GNU make (gmake, /usr/ports/devel/gmake), -native BSD make will not work.</P> + native BSD make will not work.</P> <P>To run <B>MPlayer</B> you will need to re-compile the kernel with -"options USER_LDT" (unless you are running -CURRENT, where this is default). -If you have a CPU with SSE also use "options CPU_ENABLE_SSE" to use it -(FreeBSD-STABLE required, or use kernel patches).</P> + "options USER_LDT" (unless you are running -CURRENT, where this is default). + If you have a CPU with SSE also use "options CPU_ENABLE_SSE" to use it + (FreeBSD-STABLE required, or use kernel patches).</P> <P>If <B>MPlayer</B> complains about "CD-ROM Device '/dev/cdrom' not found!" make a -symbolic link: <CODE>ln -s /dev/(your_cdrom_device) /dev/cdrom</CODE></P> + symbolic link: <CODE>ln -s /dev/(your_cdrom_device) /dev/cdrom</CODE></P> <P>There's no DVD support for FreeBSD yet.</P> @@ -1677,22 +1721,22 @@ <P>MPlayer should work on Solaris 2.6 or newer.</P> <P>AVI file playback works best on Solaris x86, because you have the -option to use the win32 codecs on the x86 platform, or can use MMX/MMX2/3DNow/etc -instructions for MP3/DivX/DVD/whatever. On Solaris SPARC, -you'll find quite a few AVI files with non working video and/or -audio playback, because the video/audio codecs using the Win32 DLLs -are not available. However, <B>DivX/OpenDivX</B> movies should work, -when using libavcodec.</P> + option to use the win32 codecs on the x86 platform, or can use + MMX/MMX2/3DNow/etc instructions for MP3/DivX/DVD/whatever. On Solaris SPARC, + you'll find quite a few AVI files with non working video and/or audio + playback, because the video/audio codecs using the Win32 DLLs are not + available. However, <B>DivX/OpenDivX</B> movies should work, when using + libavcodec.</P> <P>On <B>UltraSPARC</B>s, <B>MPlayer</B> takes advantage of their <B>VIS</B> -extensions (equivalent to MMX), currently only in <I>libmpeg2</I>, -<I>libvo</I> and <I>libavcodec</I>, but not in mp3lib. You can watch a VOB file -on a 400MHz CPU. You'll need <A -HREF="http://www.sun.com/sparc/vis/mediaLib.html">mLib</A> installed.</P> + extensions (equivalent to MMX), currently only in <I>libmpeg2</I>, + <I>libvo</I> and <I>libavcodec</I>, but not in mp3lib. You can watch a VOB + file on a 400MHz CPU. You'll need + <A HREF="http://www.sun.com/sparc/vis/mediaLib.html">mLib</A> installed.</P> <P>To build the package you will need GNU make (gmake, /opt/sfw/gmake), native -Solaris make will not work. Typical error you get when building with Solaris' -make instead of GNU make:</P> + Solaris make will not work. Typical error you get when building with Solaris' + make instead of GNU make:</P> <PRE> % /usr/ccs/bin/make @@ -1700,21 +1744,20 @@ </PRE> <P>On Solaris SPARC, you need the GNU C/C++ Compiler; it does not matter -if GNU C/C++ compiler is configured with or without the GNU assembler.</P> + if GNU C/C++ compiler is configured with or without the GNU assembler.</P> -<P>On Solaris x86, you need the GNU assembler and the GNU C/C++ -compiler, configured to use the GNU assembler! The mplayer code on -the x86 platform makes heavy use of MMX, SSE and 3DNOW! -instructions that cannot be compiled using Sun's assembler -<CODE>/usr/ccs/bin/as</CODE>.</P> - -<P>The configure script tries to find out, which assembler program is -used by your "gcc" command (in case the autodetection fails, use -the "--as=/whereever/you/have/installed/gnu-as" option to tell the -configure script where it can find GNU "as" on your system).</P> +<P>On Solaris x86, you need the GNU assembler and the GNU C/C++ compiler, + configured to use the GNU assembler! The mplayer code on the x86 platform + makes heavy use of MMX, SSE and 3DNOW! instructions that cannot be compiled + using Sun's assembler <CODE>/usr/ccs/bin/as</CODE>.</P> + +<P>The configure script tries to find out, which assembler program is used by + your "gcc" command (in case the autodetection fails, use the + <CODE>--as=/whereever/you/have/installed/gnu-as</CODE> option to tell the + configure script where it can find GNU "as" on your system).</P> <P>Error message from configure on a Solaris x86 system using GCC -without GNU assembler:</P> + without GNU assembler:</P> <PRE> % configure @@ -1726,7 +1769,7 @@ <P>(Solution: Install and use a gcc configured with "--with-as=gas")</P> <P>Typical error you get when building with a GNU C compiler that does -not use GNU as:</P> + not use GNU as:</P> <PRE> % gmake @@ -1740,22 +1783,23 @@ </PRE> <P>For DVD support you must have the patched libcss installed. Patch: -<A HREF="http://www.tools.de/solaris/mplayer/">http://www.tools.de/solaris/mplayer/</A>.</P> + <A HREF="http://www.tools.de/solaris/mplayer/">http://www.tools.de/solaris/mplayer/</A>.</P> <P>Due to two bugs in Solaris 8 x86, you cannot reliably play DVDs using a -capacity >4GB:</P> + capacity >4GB:</P> <UL> -<LI>The sd(7D) driver on Solaris 8 x86 driver has bug when accessing a -disk block >4GB on a device using a logical blocksize != DEV_BSIZE -(i.e. CD-ROM and DVD media). Due to a 32bit int overflow, a disk -address modulo 4GB is accessed. -(<A HREF="http://groups.yahoo.com/group/solarisonintel/message/22516">http://groups.yahoo.com/group/solarisonintel/message/22516</A>) - -<LI>The similar bug is present in the hsfs(7FS) filesystem code (aka -ISO9660), hsfs currently does not support partitions/disks >4GB, -all data is accessed modulo 4GB -(<A HREF="http://groups.yahoo.com/group/solarisonintel/message/22592">http://groups.yahoo.com/group/solarisonintel/message/22592</A>) + <LI>The sd(7D) driver on Solaris 8 x86 driver has bug when accessing a disk + block >4GB on a device using a logical blocksize != DEV_BSIZE (i.e. CD-ROM + and DVD media). Due to a 32bit int overflow, a disk address modulo 4GB is + accessed. + (<A HREF="http://groups.yahoo.com/group/solarisonintel/message/22516">http://groups.yahoo.com/group/solarisonintel/message/22516</A>) + </LI> + <LI>The similar bug is present in the hsfs(7FS) filesystem code (aka + ISO9660), hsfs currently does not support partitions/disks >4GB, all data + is accessed modulo 4GB + (<A HREF="http://groups.yahoo.com/group/solarisonintel/message/22592">http://groups.yahoo.com/group/solarisonintel/message/22592</A>) + </LI> </UL> <P>On Solaris with an UltraSPARC CPU, you can get some extra speed by @@ -1780,7 +1824,7 @@ <P><B><A NAME=6.5>6.5. Silicon Graphics / IRIX</A></B></P> <P>Reported working. You'll probably have to use the <I>SGI</I> ao driver. -Anyone has closer info?</P> + Anyone has closer info?</P> <P><B><A NAME=6.6>6.6. QNX</A></B></P> @@ -1796,31 +1840,31 @@ <P><B><A NAME=6.7>6.7. OpenBSD</A></B></P> <P>To build the package you will need GNU make (gmake, -/usr/ports/devel/gmake), native BSD make will not work, and a recent -binutils (including objcopy).</P> + /usr/ports/devel/gmake), native BSD make will not work, and a recent + binutils (including objcopy).</P> -<P>Due to limitations in different versions of gas (relocation vs mmx), -you'll need to compile in two steps: First make sure that the -non-native as is first in PATH and do a '<CODE>gmake -k</CODE>', then make sure -that the native version is used and do '<CODE>gmake</CODE>'.</P> +<P>Due to limitations in different versions of gas (relocation vs mmx), you'll + need to compile in two steps: First make sure that the non-native as is first + in PATH and do a '<CODE>gmake -k</CODE>', then make sure that the native + version is used and do '<CODE>gmake</CODE>'.</P> <P>To use Win32 DLLs with <B>MPlayer</B> you will need to re-compile the -kernel with "<CODE>option USER_LDT</CODE>".</P> + kernel with "<CODE>option USER_LDT</CODE>".</P> <P>If <B>MPlayer</B> complains about not finding '/dev/cdrom' or -'/dev/dvd' make a symbolic link, e.g. <CODE>ln -s -/dev/rcd0c /dev/dvd</CODE></P> + '/dev/dvd' make a symbolic link, e.g. <CODE>ln -s + /dev/rcd0c /dev/dvd</CODE></P> <P>The not so hardcore hackers amongst us might want to use the ports -version (/usr/ports/x11/mplayer).</P> + version (/usr/ports/x11/mplayer).</P> -<P><A NAME="6.8"></A><B>6.8. Cygwin</B><BR> -</P> + +<P><A NAME="6.8"></A><B>6.8. Cygwin</B><BR></P> <P>You will have to go to the <B>MPlayer</B> directory, and copy or symlink -<CODE>etc/cygwin_inttypes.h</CODE> to <CODE>/usr/include/inttypes.h</CODE> to -make <B>MPlayer</B> compile. Otherwise it will complain about missing -<CODE>intypes.h</CODE>.</P> + <CODE>etc/cygwin_inttypes.h</CODE> to <CODE>/usr/include/inttypes.h</CODE> to + make <B>MPlayer</B> compile. Otherwise it will complain about missing + <CODE>intypes.h</CODE>.</P> <P><B><A NAME=A>Appendix A - Authors</A></B></P> Index: formats.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/formats.html,v retrieving revision 1.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- formats.html 24 Jul 2002 01:56:08 -0000 1.36 +++ formats.html 1 Aug 2002 20:47:46 -0000 1.37 @@ -12,21 +12,22 @@ <P><B><A NAME=2.1>2.1. Supported formats</A></B></P> <P>It is important to clarify a common mistake. When people see a file with a -<B>.AVI</B> extension, they immediately conclude that it is not an MPEG file. -That is not true. At least not entirely. Contrary to popular belief such a file -<B>can</B> contain MPEG1 video.</P> + <B>.AVI</B> extension, they immediately conclude that it is not an MPEG file. + That is not true. At least not entirely. Contrary to popular belief such a + file <B>can</B> contain MPEG1 video.</P> <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> + 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> -<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 video and MP2 audio (unlike <B>AVI</B>, <B>MPG</B> does not have the -necessary fields to describe its video and audio streams). -Or you might put MPEG1 video into an AVI file. <A HREF="http://ffmpeg.sourceforge.net">FFmpeg</A> -and <A HREF="encoding.html">MEncoder</A> can create these files.</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 + video and MP2 audio (unlike <B>AVI</B>, <B>MPG</B> does not have the + necessary fields to describe its video and audio streams). Or you might put + MPEG1 video into an AVI file. + <A HREF="http://ffmpeg.sourceforge.net">FFmpeg</A> and + <A HREF="encoding.html">MEncoder</A> can create these files.</P> @@ -38,38 +39,39 @@ <P>MPEG files come in different guises:</P> <UL> -<LI>MPG: This is the most <B>basic</B> form of the MPEG file formats. It contains -MPEG1 video, and MP2 (MPEG-1 layer 2) or rarely MP1 audio.</LI> -<LI>DAT: This is the very same format as MPG with a different extension. It is used -on <B>Video CD</B>s. Due to the way VCDs are created and Linux is designed, -DAT files cannot be played nor copied from VCDs as regular files. You have -to use the <CODE>-vcd</CODE> option to play the Video CD.</LI> -<LI>VOB: This is the MPEG file format on <B>DVD</B>s. It is the same as MPG, plus the -capability to contain subtitles or non-MPEG (AC3) audio. It contains encoded MPEG2 -video and usually AC3 audio, but DTS, MP2 and uncompressed LPCM are allowed, too.<BR> -<B>Read the <A HREF="cd-dvd.html#4.2">DVD section</A> !</B></LI> + <LI>MPG: This is the most <B>basic</B> form of the MPEG file formats. It + contains MPEG1 video, and MP2 (MPEG-1 layer 2) or rarely MP1 audio.</LI> + <LI>DAT: This is the very same format as MPG with a different extension. It + is used on <B>Video CD</B>s. Due to the way VCDs are created and Linux is + designed, DAT files cannot be played nor copied from VCDs as regular files. + You have to use the <CODE>-vcd</CODE> option to play the Video CD.</LI> + <LI>VOB: This is the MPEG file format on <B>DVD</B>s. It is the same as MPG, + plus the capability to contain subtitles or non-MPEG (AC3) audio. It + contains encoded MPEG2 video and usually AC3 audio, but DTS, MP2 and + uncompressed LPCM are allowed, too.<BR> <B>Read the <A + HREF="cd-dvd.html#4.2">DVD section</A>!</B></LI> </UL> <P>Series of frames form independent groups in MPEG files. This means that you -can cut/join an MPEG file with standard file tools (like <CODE>dd</CODE>, -<CODE>cut</CODE>), and it remains completely functional.</P> + can cut/join an MPEG file with standard file tools (like <CODE>dd</CODE>, + <CODE>cut</CODE>), and it remains completely functional.</P> -<P>One important feature of MPGs is that they have a field to describe -the aspect ratio of the video stream within. For example SVCDs have -480x480 resolution video, and in the header that field is set to 4:3, so that -it is played at 640x480. AVI files do not have this field, so they have to be -rescaled during encoding or played with the <CODE>-aspect</CODE> option.</P> +<P>One important feature of MPGs is that they have a field to describe the + aspect ratio of the video stream within. For example SVCDs have 480x480 + resolution video, and in the header that field is set to 4:3, so that it is + played at 640x480. AVI files do not have this field, so they have to be + rescaled during encoding or played with the <CODE>-aspect</CODE> option.</P> <P><B><A NAME=2.1.1.2>2.1.1.2. AVI files</A></B></P> -<P>Designed by Microsoft, <B>AVI (Audio Video Interleaved)</B> is a -widespread multipurpose format currently used mostly for DivX and DivX4 -video. It has many known drawbacks and shortcomings (for example in streaming). -It 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> +<P>Designed by Microsoft, <B>AVI (Audio Video Interleaved)</B> is a widespread + multipurpose format currently used mostly for DivX and DivX4 video. It has + many known drawbacks and shortcomings (for example in streaming). It + 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> <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> @@ -79,9 +81,9 @@ problem.</P> <P><B>Note:</B> DV cameras create raw DV streams that DV grabbing utilities -convert to two different types of AVI files. The AVI will then contain either -separate audio and video streams that <B>MPlayer</B> can play or the raw DV -stream for which support is under development.</P> + convert to two different types of AVI files. The AVI will then contain either + separate audio and video streams that <B>MPlayer</B> can play or the raw DV + stream for which support is under development.</P> <P>There are two kinds of AVI files:</P> <UL> @@ -109,32 +111,33 @@ </UL> <P>Any audio and video codec is allowed, but note that VBR audio is not well -supported by most players. The file format makes it possible to use VBR -audio, but most players expect CBR audio, thus they fail with VBR. VBR is -uncommon and the Microsoft AVI specs only describe CBR audio. Most AVI -encoders/multiplexers create bad files when using VBR audio. There are only -two known exceptions: NanDub and <A HREF="encoding.html">MEncoder</A>.</P> + supported by most players. The file format makes it possible to use VBR + audio, but most players expect CBR audio, thus they fail with VBR. VBR is + uncommon and the Microsoft AVI specs only describe CBR audio. Most AVI + encoders/multiplexers create bad files when using VBR audio. There are only + two known exceptions: NanDub and <A HREF="encoding.html">MEncoder</A>.</P> <P><B><A NAME=2.1.1.3>2.1.1.3. ASF/WMV files</A></B></P> <P>ASF (active streaming format) comes from Microsoft. They developed two -variants of ASF, v1.0 and v2.0. v1.0 is used by their media tools (Windows -Media Player and Windows Media Encoder) and is very secret. v2.0 is published -and patented :). Of course they differ, there is no compatibility at all (it is -just another legal game). <B>MPlayer</B> supports only v1.0, as nobody has ever seen -v2.0 files :). Note that ASF files nowadays come with the extension .WMA or -.WMV.</P> + variants of ASF, v1.0 and v2.0. v1.0 is used by their media tools (Windows + Media Player and Windows Media Encoder) and is very secret. v2.0 is published + and patented :). Of course they differ, there is no compatibility at all (it + is just another legal game). <B>MPlayer</B> supports only v1.0, as nobody has + ever seen v2.0 files :). Note that ASF files nowadays come with the extension + .WMA or .WMV.</P> <P><B><A NAME=2.1.1.4>2.1.1.4. QuickTime/MOV files</A></B></P> -<P>These formats were designed by Apple and can contain any codec, CBR or VBR. -They usually have a .QT or .MOV extension. Ever since the MPEG4 group chose -QuickTime as the recommended file format for MPEG4, their MOV files come with a -.MPG or .MP4 extension (Interestingly the video and audio streams in these -files are real MPG and AAC files. You can even extract them with the -<CODE>-dumpvideo</CODE> and <CODE>-dumpaudio</CODE> options.).</P> +<P>These formats were designed by Apple and can contain any codec, CBR or VBR. + They usually have a .QT or .MOV extension. Ever since the MPEG4 group chose + QuickTime as the recommended file format for MPEG4, their MOV files come with + an + .MPG or .MP4 extension (Interestingly the video and audio streams in these + files are real MPG and AAC files. You can even extract them with the + <CODE>-dumpvideo</CODE> and <CODE>-dumpaudio</CODE> options.).</P> <P><B>Note:</B> Most new QuickTime files use <B>Sorenson</B> video and QDesign Music audio. See our <A HREF="codecs.html#2.2.1.10">Sorenson</A> codec @@ -143,26 +146,26 @@ <P><B><A NAME=2.1.1.5>2.1.1.5. VIVO files</A></B></P> -<P><B>MPlayer</B> happily demuxes VIVO file formats. The biggest disadvantage of -the format is that it has no index block, nor a fixed packet size or sync bytes -and most files lack even keyframes, so forget seeking!</P> +<P><B>MPlayer</B> happily demuxes VIVO file formats. The biggest disadvantage + of the format is that it has no index block, nor a fixed packet size or sync + bytes and most files lack even keyframes, so forget seeking!</P> <P>The video codec of VIVO/1.0 files is standard <B>h.263</B>. The video codec -of VIVO/2.0 files is a modified, nonstandard <B>h.263v2</B>. The audio is the same, -it may be <B>g.723</B> (standard), or <B>Vivo Siren</B>.</P> + of VIVO/2.0 files is a modified, nonstandard <B>h.263v2</B>. The audio is the + same, it may be <B>g.723</B> (standard), or <B>Vivo Siren</B>.</P> -<P>See the <A HREF="codecs.html#2.2.1.4">VIVO video codec</A> -and <A HREF="codecs.html#2.2.2.4">VIVO audio codec</A> sections for installation -instructions.</P> +<P>See the <A HREF="codecs.html#2.2.1.4">VIVO video codec</A> and + <A HREF="codecs.html#2.2.2.4">VIVO audio codec</A> sections for installation + instructions.</P> <P><B><A NAME=2.1.1.6>2.1.1.6. FLI files</A></B></P> -<P><B>FLI</B> is a very old file format used by Autodesk Animator, but it is -a common file format for short animations on the net. <B>MPlayer</B> demuxes -and decodes FLI movies and is even able to seek within them (useful when -looping with the <CODE>-loop</CODE> option). FLI files do not have keyframes, so the picture -will be messy for a short time after seeking.</P> +<P><B>FLI</B> is a very old file format used by Autodesk Animator, but it is a + common file format for short animations on the net. <B>MPlayer</B> demuxes + and decodes FLI movies and is even able to seek within them (useful when + looping with the <CODE>-loop</CODE> option). FLI files do not have keyframes, + so the picture will be messy for a short time after seeking.</P> <P><B><A NAME=2.1.1.7>2.1.1.7. RealMedia (RM) files</A></B></P> @@ -177,19 +180,20 @@ <P><B><A NAME=2.1.1.8>2.1.1.8. NuppelVideo files</A></B></P> <P><A HREF="http://mars.tuwien.ac.at/~roman/nuppelvideo">NuppelVideo</A> -is a TV grabber tool (AFAIK:). <B>MPlayer</B> can read its .NUV -files (only NuppelVideo 5.0). Those files can contain uncompressed YV12, -YV12+RTJpeg compressed, YV12 RTJpeg+lzo compressed, and YV12+lzo compressed -frames. <B>MPlayer</B> decodes them all (and also <B>encodes</B> them with -<B>MEncoder</B> to DivX/etc!). Seeking works.</P> + is a TV grabber tool (AFAIK:). <B>MPlayer</B> can read its .NUV files (only + NuppelVideo 5.0). Those files can contain uncompressed YV12, YV12+RTJpeg + compressed, YV12 RTJpeg+lzo compressed, and YV12+lzo compressed frames. + <B>MPlayer</B> decodes them all (and also <B>encodes</B> them with + <B>MEncoder</B> to DivX/etc!). Seeking works.</P> <P><B><A NAME=2.1.1.9>2.1.1.9. yuv4mpeg files</A></B></P> -<P><A HREF="http://mjpeg.sourceforge.net">yuv4mpeg / yuv4mpeg2</A> is -a file 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><A HREF="http://mjpeg.sourceforge.net">yuv4mpeg / yuv4mpeg2</A> is a file + 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> @@ -223,10 +227,10 @@ <P><B><A NAME=2.1.2.1>2.1.2.1. MP3 files</A></B></P> <P>You may have problems playing certain MP3 files that <B>MPlayer</B> will -misdetect as MPEGs and play incorrectly or not at all. This cannot be fixed -without dropping support for certain broken MPEG files and thus will remain -like this for the foreseeable future. The <CODE>-demuxer</CODE> flag described -in the manpage may help you in these cases.</P> + misdetect as MPEGs and play incorrectly or not at all. This cannot be fixed + without dropping support for certain broken MPEG files and thus will remain + like this for the foreseeable future. The <CODE>-demuxer</CODE> flag + described in the manpage may help you in these cases.</P> <P><B><A NAME=2.1.2.2>2.1.2.2. WAV files</A></B></P> Index: sound.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/sound.html,v retrieving revision 1.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- sound.html 28 Jun 2002 06:07:46 -0000 1.42 +++ sound.html 1 Aug 2002 20:47:46 -0000 1.43 @@ -32,22 +32,24 @@ 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 default). -If you experience glitches, halts or anything out of the ordinary, try -<CODE>-ao sdl</CODE> (NOTE: you need to have SDL libraries and header files -installed). The SDL audio driver helps in a lot of cases and also supports ESD, -ARTS, and up/downsampling. (ESD is the sound daemon from GNOME, ARTS is from KDE.)</LI> -<LI>If you have ALSA version 0.5, then you almost always have to use <CODE>-ao alsa5</CODE> , -since ALSA 0.5 has buggy OSS emulation code, and will <B>crash MPlayer</B> with -a message like this:<BR> -<CODE>DEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer!</CODE></LI> -<LI>If you have ALSA version 0.9 you may choose between <CODE>-ao oss</CODE> and -<CODE>-ao sdl</CODE>. You can also use <CODE>-ao alsa9</CODE>. It works, but -there may be problems like lost sync and disappearing audio.</LI> + <LI>If you have an OSS driver, first try <CODE>-ao oss</CODE> (this is the + default). If you experience glitches, halts or anything out of the + ordinary, try <CODE>-ao sdl</CODE> (NOTE: you need to have SDL libraries + and header files installed). The SDL audio driver helps in a lot of cases + and also supports ESD, ARTS, and up/downsampling. (ESD is the sound daemon + from GNOME, ARTS is from KDE.)</LI> + <LI>If you have ALSA version 0.5, then you almost always have to use + <CODE>-ao alsa5</CODE> , since ALSA 0.5 has buggy OSS emulation code, and + will <B>crash MPlayer</B> with a message like this:<BR> + <CODE>DEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer!</CODE></LI> + <LI>If you have ALSA version 0.9 you may choose between <CODE>-ao oss</CODE> + and <CODE>-ao sdl</CODE>. You can also use <CODE>-ao alsa9</CODE>. It + works, but there may be problems like lost sync and disappearing + audio.</LI> </UL> <P>On <B>Solaris/FreeBSD</B> systems, use the SUN audio driver with the -<CODE>-ao sun</CODE> option, otherwise neither video nor audio will work.</P> + <CODE>-ao sun</CODE> option, otherwise neither video nor audio will work.</P> <P><B><A NAME=2.3.2.1>2.3.2.1. Sound Card experiences, recommendations</A></B></P> @@ -119,17 +121,18 @@ </TABLE> <UL> -<LI>On Linux, a 2.4.x kernel is highly recommended. Kernel 2.2 is not tested.</LI> -<LI>If sound clicks when playing from CD-ROM, turn on IRQ unmasking, e.g. - <CODE>hdparm -u1 /dev/cdrom</CODE> (<CODE>man hdparm</CODE>). This is - generally beneficial and described more detailed in the - <A HREF="cd-dvd.html#4.1">CD-ROM section</A>.</LI> -<LI>Sharing your sound card with another application like XMMS is <B>strongly discouraged</B>! - If the other sound application is using ESD, start <B>MPlayer</B> with the <CODE>-vo sdl:esd</CODE> option - to combine both sound streams! In fact, the option <CODE>-vo sdl:esd</CODE> could be used with ESD - even when playing <B>Mplayer</B> alone.</LI> -<LI>Feedback to this document is welcome. Please tell us how <B>MPlayer</B> and - your sound card(s) worked together.</LI> + <LI>On Linux, a 2.4.x kernel is highly recommended. Kernel 2.2 is not tested.</LI> + <LI>If sound clicks when playing from CD-ROM, turn on IRQ unmasking, e.g. + <CODE>hdparm -u1 /dev/cdrom</CODE> (<CODE>man hdparm</CODE>). This is + generally beneficial and described more detailed in the <A + HREF="cd-dvd.html#4.1">CD-ROM section</A>.</LI> + <LI>Sharing your sound card with another application like XMMS is <B>strongly + discouraged</B>! If the other sound application is using ESD, start + <B>MPlayer</B> with the <CODE>-vo sdl:esd</CODE> option to combine both + sound streams! In fact, the option <CODE>-vo sdl:esd</CODE> could be used + with ESD even when playing <B>Mplayer</B> alone.</LI> + <LI>Feedback to this document is welcome. Please tell us how <B>MPlayer</B> + and your sound card(s) worked together.</LI> </UL> Index: video.html =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/video.html,v retrieving revision 1.84 retrieving revision 1.85 diff -u -r1.84 -r1.85 --- video.html 14 Jul 2002 17:54:05 -0000 1.84 +++ video.html 1 Aug 2002 20:47:46 -0000 1.85 @@ -17,7 +17,7 @@ <P>It is VERY recommended to check if the MTRR registers are set up properly, because they can give a big performance boost.</P> -<P>Do a '<CODE>cat /proc/mtrr</CODE>' :</P> +<P>Do a '<CODE>cat /proc/mtrr</CODE>':</P> <P><CODE> --($:~)-- cat /proc/mtrr<BR> @@ -192,7 +192,7 @@ <A HREF="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/neomagic_drv.o.4.2.0.bz2">Download from here</A>. Driver provided by Stefan Seyfried.</P> -<P>To allow playback of DVD sized content change your XF86Config like this :</P> +<P>To allow playback of DVD sized content change your XF86Config like this:</P> <P> Section "Device"<BR> @@ -471,7 +471,7 @@ </TABLE> <P><B>KNOWN BUGS:</B></P> -<UL><LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa !) +<UL><LI>Keys pressed under sdl:aalib console driver repeat forever. (use -vo aa!) It's bug in SDL, I can't change it (tested with SDL 1.2.1). </UL> @@ -513,10 +513,10 @@ <P>Whether to build the FBdev target is autodetected during ./configure . Read the framebuffer documentation in the kernel sources -(Documentation/fb/*) for info on how to enable it, etc.. !</P> +(Documentation/fb/*) for info on how to enable it, etc..!</P> <P>If your card doesn't support VBE 2.0 standard (older ISA/PCI -cards, such as S3 Trio64), only VBE 1.2 (or older?) : +cards, such as S3 Trio64), only VBE 1.2 (or older?): Well, VESAfb is still available, but you'll have to load SciTech Display Doctor (formerly UniVBE) before booting Linux. Use a DOS boot disk or whatever. And don't forget to register your UniVBE ;))</P> @@ -545,10 +545,10 @@ or if you specify the -bpp option, then that.</LI> <LI><B>-zoom</B> option isn't supported (software scaling is slow). -fs option isn't supported. You can't use 8bpp (or less) modes.</LI> -<LI>you possibly want to turn the cursor off : <CODE>echo -e '\033[?25l'</CODE> +<LI>you possibly want to turn the cursor off: <CODE>echo -e '\033[?25l'</CODE> or <CODE>setterm -cursor off</CODE><BR> and the screen saver: <CODE>setterm -blank 0</CODE><BR> - To turn the cursor back on : <CODE>echo -e '\033[?25h'</CODE> + To turn the cursor back on: <CODE>echo -e '\033[?25h'</CODE> or <CODE>setterm -cursor on</CODE></LI> </UL> @@ -604,7 +604,7 @@ <P>The <CODE>/dev/mga_vid</CODE> device file can be read (for example by <CODE>cat /dev/mga_vid</CODE>) for some info, and written for brightness - change : <CODE>echo "brightness=120" > /dev/mga_vid</CODE></P> + change: <CODE>echo "brightness=120" > /dev/mga_vid</CODE></P> <P><B><A NAME=2.3.1.8>2.3.1.8. SiS 6326 framebuffer (sis_vid)</A></B></P> @@ -736,7 +736,7 @@ - Currently it's available only for <B>Linux</B>.<BR> </P> -<P>Don't use this driver with <B>GCC 2.96</B> ! It won't work !</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> @@ -779,14 +779,14 @@ hardware acceleration on the second head/TV. In those cases, you see green/blue colored window instead of the movie. This is where this driver comes in handy, but you need powerful CPU to use software scaling. Don't use the -SDL driver's software output+scaler, it has worse image quality !</P> +SDL driver's software output+scaler, it has worse image quality!</P> <P>Software scaling is very slow, you better try changing video modes instead. It's very simple. See the <A HREF="#2.3.1.3.A">DGA section's modelines</A>, and insert them into your XF86Config.</P> <UL> <LI>If you have XFree86 4.x.x - use the <CODE>-vm</CODE> option. It will - change to a resolution your movie fits in. If it doesn't :</LI> + change to a resolution your movie fits in. If it doesn't:</LI> <LI>With XFree86 3.x.x - you have to cycle through available resolutions with the <B>CTRL-ALT-plus</B> and <B>minus</B> keys.</LI> </UL> @@ -849,12 +849,12 @@ <B>MPlayer</B> the same keys as for vo_server. In addition it understands <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 + As for <CODE>-vo xvidix</CODE>: currently it recognizes the following options: <CODE>-fs -zoom -x -y -double</CODE>.<BR> </P> <P>Also you can specify VIDIX's driver directly as third subargument in command - line :<BR> + line:<BR> <BR>   <code>mplayer -vo xvidix:mga_vid.so -fs -zoom -double file.avi</code><BR> @@ -888,7 +888,7 @@ 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 : + following options: </P> <TABLE> @@ -1136,7 +1136,7 @@ <P><B><A NAME=2.3.1.A.1>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> +<P>Under Linux you have 2 methods to get G400 TV out working:</P> <P><B>IMPORTANT:</B> Only Matrox G400DH/G400MAX has TV-out support under Linux, others (G450, G550) has <B>NOT!</B></P> @@ -1174,7 +1174,7 @@ to a very simple menu. Press <B>2</B> and <B>ENTER</B>. Now you should have the same picture on your monitor, and TV. The <B>3.</B> option will turn on independent display, but then you <B>can't use X</B>! If - the TV (PAL !) picture has some weird stripes on it, the script wasn't able to + the TV (PAL!) picture has some weird stripes on it, the script wasn't able to set the resolution correctly (to 640x512 by default). Use other menu items randomly and it'll be OK :)</LI> </UL> @@ -1190,15 +1190,15 @@ <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> + the screen.. To turn the cursor back:<BR><CODE>echo -e '\033[?25h'</CODE> 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> + (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> + <B>Enjoy the ultra-fast ultra-featured Matrox TV output (better than Xv)!</B> </P> </LI> </UL>