Mercurial > mplayer.hg
changeset 6960:87deea511b1f
continuing paragraph reformatting
| author | gabucino |
|---|---|
| date | Sat, 10 Aug 2002 20:26:43 +0000 |
| parents | f7d8c02536e4 |
| children | 201b25a9b939 |
| files | DOCS/cd-dvd.html DOCS/codecs.html DOCS/documentation.html DOCS/encoding.html DOCS/formats.html DOCS/sound.html DOCS/video.html |
| diffstat | 7 files changed, 1087 insertions(+), 995 deletions(-) [+] |
line wrap: on
line diff
--- a/DOCS/cd-dvd.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/cd-dvd.html Sat Aug 10 20:26:43 2002 +0000 @@ -19,7 +19,7 @@ make you consider changing the speed of a CD-ROM drive:</P> <UL> - <LI>Ther have been reports of read errors at these high speeds, especially + <LI>There have been reports of read errors at these high speeds, especially with badly pressed CD-ROMs. Reducing the speed can prevent data loss under these circumstances.</LI> <LI>Many CD-ROM drives are annoyingly loud, a lower speed may reduce the
--- a/DOCS/codecs.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/codecs.html Sat Aug 10 20:26:43 2002 +0000 @@ -20,53 +20,55 @@ <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="#importing">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="#importing">codec importing HOWTO</A> and help us add support + for it!</P> <P><B><A NAME="divx">2.2.1.1 DivX4/DivX5</A></B></P> -<P>This section contains information about the DivX4 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>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 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>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> @@ -80,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> @@ -92,21 +94,21 @@ <P><B><A NAME="libavcodec">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><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 also contains a lot of nice codecs, such as RealVideo 1.0, WMV7, - MJPEG, h263, h263+, etc.</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> +<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> @@ -119,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> @@ -129,15 +131,15 @@ <P><B><A NAME="xanim">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 @@ -156,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> @@ -164,39 +166,38 @@ <P><B><A NAME="vivo_video">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="mpeg">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="ms_video1">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="cinepak">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="realvideo">2.2.1.8 RealVideo</A></B></P> @@ -210,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> @@ -285,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> @@ -300,68 +301,67 @@ <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>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>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="hardware_ac3">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="libmad">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="vivo_audio">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="realaudio">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#real">RealMedia file format</A> section.</P>
--- a/DOCS/documentation.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/documentation.html Sat Aug 10 20:26:43 2002 +0000 @@ -339,12 +339,11 @@ supported output drivers. It works with X11, Xv, DGA, OpenGL, SVGAlib, fbdev, AAlib, DirectFB, but you can use GGI and SDL (and this way all their drivers) and some lowlevel card-specific drivers (for Matrox, 3Dfx and Radeon, -Mach64, Permedia3), too! Most +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="video.html#dvb">DVB</A></B> and -<B> <A HREF="video.html#dxr3">DXR3/Hollywood+</A></B>! And what about the -nice big antialiased +<B><A HREF="video.html#dxr3">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> @@ -405,7 +404,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> @@ -426,7 +425,7 @@ <LI><B>binutils</B> - suggested version is <B>2.11.x</B> . This program is responsible for generating MMX/3DNow!/etc instructions, thus very important.</LI> <LI><B>gcc</B> - suggested versions are: <B>2.95.3</B>, <B>2.95.4</B> and <B>3.1</B>. - <B>NEVER</B> use 2.96 or 3.0.x!!! They generate faulty code for MPlayer. + <B>NEVER</B> use 2.96 or 3.0.x !!! They generate faulty code for MPlayer. If you decide to change gcc from 2.96, then don't decide in favor of 3.0.x just because it's newer! Early releases of 3.0.x were even more buggy than 2.96. So downgrade to 2.95.x (downgrade libstdc++ too, other programs may @@ -464,59 +463,64 @@ <UL> <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. Details can be found - <A HREF="codecs.html#libavcodec">here</A>. Features: + 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#libavcodec">here</A>. Features:<BR> <UL> - <LI>Decoding of above mentioned codecs on non-x86 machines.</LI> - <LI>Encoding with most of the above mentioned codecs.</LI> - <LI>This is the <B>fastest available</B> codec for DivX/3/4/5 and other - MPEG4 types and therefore highly recommended.</LI> + <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> + <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>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>DivX4/DivX5</B>: information about this codec is available in the + <A HREF="codecs.html#divx">DivX4/DivX5</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>DivX4/DivX5:</B> information about this codec is available in the -<A HREF="codecs.html#divx">DivX4/DivX5</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>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><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> - -<LI>The <A HREF="codecs.html#xanim">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#xanim">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 @@ -528,7 +532,6 @@ files with <B>RealVideo 2.0 and 3.0</B> video, and Sipro/Cook audio. See <A HREF="formats.html#real">RealMedia file format</A> section for installation instructions and more information!</LI> - </UL> <P><B>VIDEO CARDS</B></P> @@ -545,8 +548,8 @@ you get a nice and very fast fullscreen playing.</P> <UL> -<LI><B>Matrox G200/G400/G450/G550 cards:</B> although a - <A HREF="video.html#vidix">VIDIX driver</A> is provided, it is recommended +<LI><B>Matrox G200/G400/G450/G550 cards</B>: although a + <A HREF="video.html#vidix">Vidix driver</A> is provided, it is recommended to use the old mga_vid kernel module instead, for it works much better. Please see the <A HREF="video.html#mga_vid">mga_vid</A> section about its installation and usage. It is important to do these steps <I>before</I> @@ -555,7 +558,7 @@ <U><B>If you are non-Linux user</B></U>, your only possibility is the Vidix driver: read <A HREF="video.html#vidix">VIDIX</A> documentation!</LI> -<LI><B>3Dfx Voodoo3/Banshee cards:</B> please see the +<LI><B>3Dfx Voodoo3/Banshee cards</B>: please see the <A HREF="video.html#tdfxfb">tdfxfb</A> section in order to gain big speedup. It is important to do these steps <I>before</I> compiling <B>MPlayer</B>, otherwise no 3Dfx support will be built. Also see the <A @@ -563,41 +566,42 @@ least 4.2.0, as 3dfx Xv driver was broken in 4.1.0, and earlier releases!</LI> -<LI><B>ATI cards:</B> <A HREF="video.html#vidix">VIDIX driver</A> is +<LI><B>ATI cards</B>: <A HREF="video.html#vidix">Vidix driver</A> is provided for the following cards: <B>Radeon</B>, <B>Rage128</B>, <B>Mach64</B> (Rage XL/Mobility, Xpert98). Also see the <A HREF="video.html#tv-out_ati">ATI cards 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#xv_s3">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#xv_nvidia">nVidia Xv driver</A> section.</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#xv_s3">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#xv_nvidia">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#vidix">VIDIX instructions</A>.</LI> -<LI><B>other cards:</B> none of the above? +<LI><B>other cards</B>: none of the above? <UL> <LI>Try if the XFree86 driver (and your card) supports hardware acceleration. See the <A HREF="video.html#xv">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> @@ -607,14 +611,13 @@ <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> @@ -629,35 +632,64 @@ <A HREF="video.html#aalib">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 buggy in 800x600@16bpp + <B>Recommended: 640x480@16bpp</B></LI> + <LI>XFree86 4: the Xserver freezes soon after start unless + acceleration is disabled, but then the whole thing gets + slower than XFree86 3. No XVideo.</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 but slow with + <CODE>-bpp 8</CODE>.</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#software_ac3">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>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#software_ac3">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 with these cards, see <A HREF="codecs.html#hardware_ac3">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">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="#gui">GUI 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">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="#tv">TV input</A> section.</LI> + see the <A HREF="encoding.html">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="#tv">TV input</A> + section.</LI> <LI>There are three timing methods in <B>MPlayer</B>. <UL> @@ -673,7 +705,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 @@ -703,9 +735,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> @@ -716,29 +747,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#debian">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#debian">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 the -<A HREF="#subtitles_osd">subtitle and OSD section</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="#subtitles_osd">1.5</A> for details.</P> <PRE> mkdir ~/.mplayer/font @@ -751,86 +783,94 @@ <P><B><A NAME="gui">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> - -<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> + 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 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="subtitles_osd">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#dvd">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> @@ -847,64 +887,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> + There are many ways to get it:</P> + <UL> - -<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>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>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 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="features">2. Features</A></B></P> @@ -1053,11 +1097,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> @@ -1279,7 +1323,7 @@ <P><B><U>Description</U></B>:</P> -<P>Draws a rectangle of the requested width and height at the designated +<P>Draws a white rectangle of the requested width and height at the designated coordinates over the image. Useful to get visual feedback for the parameters of <CODE>-vop crop</CODE> before applying them.</P> @@ -1590,7 +1634,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="slave">3.2.4 Slave mode</A></B></P> @@ -1604,17 +1648,18 @@ <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 is recommended to enable the cache when playing from the network:</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> @@ -1631,7 +1676,7 @@ <P><B><A NAME="debian">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 @@ -1639,7 +1684,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> @@ -1662,15 +1707,15 @@ <P><B><A NAME="freebsd">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> @@ -1679,22 +1724,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 Colaris 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 @@ -1702,21 +1747,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> - -<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> + 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 + <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 @@ -1728,7 +1772,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 @@ -1742,22 +1786,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 @@ -1782,7 +1827,7 @@ <P><B><A NAME="sgi">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="qnx">6.6 QNX</A></B></P> @@ -1798,31 +1843,31 @@ <P><B><A NAME="openbsd">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> - -<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> + /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>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> - -<P><A NAME="cygwin"></A><B>6.8 Cygwin</B><BR> -</P> + version (/usr/ports/x11/mplayer).</P> + + +<P><A NAME="cygwin"></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="authors">Appendix A - Authors</A></B></P> @@ -2528,7 +2573,7 @@ </LI> <LI>MPlayer & DVB card users:<BR> <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">http://mplayerhq.hu/mailman/listinfo/mplayer-dvb</A> -<P>Things related to the hardware decoder card called DVB. (NOT DXR3!)</P> +<P>Things related to the hardware decoder card called DVB. (NOT dxr3!)</P> </LI> <LI>MPlayer CVS-log: <BR> <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-cvslog">http://mplayerhq.hu/mailman/listinfo/mplayer-cvslog</A>
--- a/DOCS/encoding.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/encoding.html Sat Aug 10 20:26:43 2002 +0000 @@ -15,11 +15,12 @@ <P><B><A NAME="overview">2.4.1 Overview</A></B></P> <P><B>MEncoder</B> (<B>MPlayer</B>'s Movie Encoder) is a simple movie encoder, -designed to encode MPlayer-playable movies -(<B>AVI/ASF/OGG/DVD/VCD/VOB/MPG/MOV/VIV/FLI/RM/NUV/NET</B>) to other MPlayer-playable -formats (see below). It can encode with various codecs, like <B>DivX4</B> (1 or -2 passes), libavcodec, <B>PCM</B>/<B>MP3</B>/<B>VBRMP3</B> audio. Also has -powerful plugin system for video manipulation.</P> + designed to encode MPlayer-playable movies + (<B>AVI/ASF/OGG/DVD/VCD/VOB/MPG/MOV/VIV/FLI/RM/NUV/NET</B>) to other + MPlayer-playable formats (see below). It can encode with various codecs, like + <B>DivX4</B> (1 or 2 passes), libavcodec, + <B>PCM</B>/<B>MP3</B>/<B>VBR MP3</B> audio. Also has powerful plugin system + for video manipulation.</P> <P><B><A NAME="compilation">2.4.2 Compilation</A></B></P> @@ -52,7 +53,7 @@ </UL> <P>You are ready. As you probably know, other encoding tools need the -<I>avifile</I> library installed. <B>MEncoder</B> doesn't need it at all.</P> + <I>avifile</I> library installed. <B>MEncoder</B> doesn't need it at all.</P> <P><B><A NAME="features">2.4.3 MEncoder features</A></B></P> @@ -71,7 +72,7 @@ <LI>stream copying</LI> <LI>input A/V synchronizing (PTS-based, can be disabled with -mc 0 option)</LI> <LI>FPS correction with <CODE>-ofps</CODE> option (useful when encoding - 29.97fps VOB to 24fps AVI)</LI> + 29.97fps VOB to 24fps AVI)</LI> <LI>using our very powerful plugin system (crop, expand, flip, postprocess, rotate, scale, rgb/yuv conversion)</LI> <LI>can encode DVD/VOBsub <B>AND</B> text subtitles into the output file</LI> @@ -81,26 +82,30 @@ <B>Planned features:</B> <UL> <LI>even wider variety of available en/decoding formats/codecs - (creating VOB files with DivX4/Indeo5/VIVO streams :)</LI> + (creating VOB files with DivX4/Indeo5/VIVO streams :)</LI> <LI>audio encoding from v4l (DONE for FreeBSD ?)</LI> </UL> <P><B><A NAME="2pass">2.4.3.1 Encoding 2 or 3-pass DivX4</A></B></P> -<P><U><B>2-pass encoding:</B></U> the name comes from the fact that this method encodes the file <I>twice</I>. -The first encoding (dubbed <I>pass</I>) creates some temporary files (*.log) with a -size of few megabytes, do not delete them yet (you can delete the AVI). In the second pass, the -2-pass output file is created, using the bitrate data from the temporary files. The resulting -file will have much better image quality. If this is the first time you heard -about this, you should consult some guides available on the Net.</P> +<P><U><B>2-pass encoding:</B></U> the name comes from the fact that this method + encodes the file <I>twice</I>. The first encoding (dubbed <I>pass</I>) + creates some temporary files (*.log) with a size of few megabytes, do not + delete them yet (you can delete the AVI). In the second pass, the 2-pass + output file is created, using the bitrate data from the temporary files. The + resulting file will have much better image quality. If this is the first time + you heard about this, you should consult some guides available on the + Net.</P> <P>This example shows how to encode a DVD to a 2-pass DivX4 AVI. Just two -commands are needed:<BR> -<CODE> rm frameno.avi</CODE> - remove this file, which - can come from a previous 3-pass encoding (it interferes with current one)<BR> -<CODE> mencoder -dvd 2 -lavcopts vcodec=mpeg4:more_options - -o movie.avi -pass 1<BR> - mencoder -dvd 2 -lavcopts vcodec=mpeg4:more_options -o movie.avi -pass 2</CODE></P> + commands are needed:<BR> + <CODE> rm frameno.avi</CODE> - remove this file, which + can come from a previous 3-pass encoding (it interferes with current + one)<BR> + <CODE> mencoder -dvd 2 -lavcopts + -vcodec=mpeg4:more_options -o movie.avi -pass 1<BR> + mencoder -dvd 2 -lavcopts vcodec=mpeg4:more_options + -o movie.avi -pass 2</CODE></P> <P><U><B>3-pass encoding:</B></U> this is an extension of 2-pass encoding, where the audio encoding takes place in a separate pass. This method enables @@ -143,29 +148,33 @@ <P><CODE> rm frameno.avi</CODE> - remove this file, which can come from a previous 3-pass encoding (it interferes with current one)<BR> -<CODE> mencoder -dvd 2 -ovc frameno - -o frameno.avi</CODE><BR> -<CODE> mencoder -dvd 2 - -lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 1<BR> - mencoder -dvd 2 - -lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 2</CODE> + <CODE> mencoder -dvd 2 -ovc frameno + -o frameno.avi<BR> + mencoder -dvd 2 + -lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 1<BR> + mencoder -dvd 2 + -lavcopts vcodec=mpeg4:more_options -oac copy -o movie.avi -pass 2</CODE> </P> <P><U><B>2 or 3-pass encoding using internal libavcodec controller:</B></U> -Optionally you can use libavcodec's internal 2 or 3-pass mode, it may gives you -better final rate accuracy than using the external, DivX4-inspired 2-pass rate -controler with libavcodec.</P> + Optionally you can use libavcodec's internal 2 or 3-pass mode, it may give + you better final rate accuracy than using the external, DivX4-inspired 2-pass + rate controler with libavcodec.</P> <UL> -<LI><B>2-pass encoding:</B><BR> -<CODE>rm -f lavc_stats.txt<BR> -mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=1 (audio-options) -o movie.avi<BR> -mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=2 (audio-options) -o movie.avi</CODE></LI> -<LI><B>3-pass encoding:</B><BR> -<CODE>rm -f frameno.avi lavc_stats.txt<BR> -mencoder -dvd 2 -ovc frameno (audio-options) -o frameno.avi<BR> -mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=1 -oac copy -o movie.avi<BR> -mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=2 -oac copy -o movie.avi</CODE></LI> + <LI><B>2-pass encoding:</B><BR> + <CODE>rm -f lavc_stats.txt<BR> + mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=1 (audio-options) -o + movie.avi<BR> + mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=2 (audio-options) -o + movie.avi</CODE></LI> + <LI><B>3-pass encoding:</B><BR> + <CODE>rm -f frameno.avi lavc_stats.txt<BR> + mencoder -dvd 2 -ovc frameno (audio-options) -o frameno.avi<BR> + mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=1 -oac copy -o + movie.avi<BR> + mencoder -dvd 2 -ovc lavc -lavcopts vcodec=mpeg4:vpass=2 -oac copy -o + movie.avi</CODE></LI> </UL> <P><B><A NAME="rescaling">2.4.3.2 Rescaling movies</A></B></P> @@ -185,7 +194,9 @@ fast bilinear.</P> <P>Usage:<BR> -<CODE> mencoder sample-svcd.mpg -lavcopts vcodec=mpeg4:more_options -vop scale=640:480 -sws 2 -o output.avi</CODE></P> + <CODE> mencoder sample-svcd.mpg -lavcopts + vcodec=mpeg4:more_options -vop scale=640:480 -sws 2 -o + output.avi</CODE></P> <P><B><A NAME="copying">2.4.3.3 Stream copying</A></B></P> @@ -194,26 +205,28 @@ <B>copy</B> them. This section is about <B>copying</B>.</P> <UL> - <LI><B>Video stream</B> (option <CODE>-ovc copy</CODE>): nice stuff can be done :)<BR> - Like, putting (not converting!) FLI or VIVO or MPEG1 video into an AVI file! - Of course only <B>MPlayer</B> can play such files :) And it probably has no - real life value at all. Rationally: video stream copying can be useful for - example when only the audio stream has to be encoded (like, uncompressed PCM - to MP3).</LI> + <LI><B>Video stream</B> (option <CODE>-ovc copy</CODE>): nice stuff can be + done :)<BR> + Like, putting (not converting!) FLI or VIVO or MPEG1 video into + an AVI file! Of course only <B>MPlayer</B> can play such files :) And it + probably has no real life value at all. Rationally: video stream copying + can be useful for example when only the audio stream has to be encoded + (like, uncompressed PCM to MP3).</LI> <LI><B>Audio stream</B> (option <CODE>-oac copy</CODE>): straightforward. - It is possible to take an external audio file (MP3, AC3, Vorbis) and mux it - into the output stream. Use the <CODE>-audiofile <filename></CODE> - option for this.</LI> + It is possible to take an external audio file (MP3, Vorbis) and mux it + into the output stream. Use the <CODE>-audiofile <filename></CODE> + option for this.</LI> </UL> <P><B><A NAME="fixing">2.4.3.4 Fixing AVIs with broken index or interleaving</A></B></P> <P>Easiest thing. We simply copy the video and audio streams, and -<B>MEncoder</B> generates the index. Of course this cannot fix possible bugs in -the video and/or audio streams. It also fixes files with broken interleaving, -thus the <CODE>-ni</CODE> option won't be needed for them anymore.</P> + <B>MEncoder</B> generates the index. Of course this cannot fix possible bugs + in the video and/or audio streams. It also fixes files with broken + interleaving, thus the <CODE>-ni</CODE> option won't be needed for them + anymore.</P> <P>Command: <CODE>mencoder -idx input.avi -ovc copy -oac copy -o output.avi</CODE></P> @@ -221,8 +234,8 @@ <P><B><A NAME="libavcodec">2.4.3.5 Encoding with the libavcodec codec family</A></B></P> <P><A HREF="codecs.html#libavcodec">libavcodec</A> provides simple encoding to a -lot of interesting video and audio formats (currently its audio codecs are -unsupported). You can encode to the following codecs:</P> + lot of interesting video and audio formats (currently its audio codecs are + unsupported). You can encode to the following codecs:</P> <UL> <LI>mjpeg - Motion JPEG</LI> @@ -239,7 +252,8 @@ <CODE>vcodec</CODE> config, like: <CODE>-lavcopts vcodec=msmpeg4</CODE></P> <P>An example, with MJPEG compression:<BR> - <CODE> mencoder -dvd 2 -o title2.avi -ovc lavc -lavcopts vcodec=mjpeg</CODE></P> + <CODE> mencoder -dvd 2 -o title2.avi -ovc lavc + -lavcopts vcodec=mjpeg</CODE></P> <P><B><A NAME="image_files">2.4.3.6 Encoding from multiple input image files (JPEGs or PNGs)</A></B></P> @@ -288,38 +302,42 @@ <P><B><A NAME="vobsub">2.4.3.7 Extracting DVD subtitles to Vobsub file</A></B></P> <P><B>MEncoder</B> is capable of extracting subtitles from a DVD into -Vobsub fomat files. They consist of a pair of files ending in <CODE>.idx</CODE> -and <CODE>.sub</CODE> and are usually packaged in a single <CODE>.rar</CODE> -archive. <B>MPlayer</B> can play these with the <CODE>-vobsub</CODE> and -<CODE>-vobsubid</CODE> options.</P> + Vobsub fomat files. They consist of a pair of files ending in + <CODE>.idx</CODE> and <CODE>.sub</CODE> and are usually packaged in a single + <CODE>.rar</CODE> archive. <B>MPlayer</B> can play these with the + <CODE>-vobsub</CODE> and <CODE>-vobsubid</CODE> options.</P> <P>You specify the basename (i.e without the <CODE>.idx</CODE> or -<CODE>.sub</CODE> extension) of the output files with <CODE>-vobsubout</CODE> -and the index for this subtitle in the resulting files with -<CODE>-vobsuboutindex</CODE>.</P> + <CODE>.sub</CODE> extension) of the output files with <CODE>-vobsubout</CODE> + and the index for this subtitle in the resulting files with + <CODE>-vobsuboutindex</CODE>.</P> <P>If the input is not from a DVD you should use <CODE>-ifo</CODE> to -indicate the <CODE>.ifo</CODE> file needed to construct the resulting -<CODE>.idx</CODE> file.</P> + indicate the <CODE>.ifo</CODE> file needed to construct the resulting + <CODE>.idx</CODE> file.</P> -<P>If the input is not from a DVD and you do not have the <CODE>.ifo</CODE> file -you will need to use the <CODE>-vobsubid</CODE> option to let it know what -language id to put in the <CODE>.idx</CODE> file.</P> +<P>If the input is not from a DVD and you do not have the <CODE>.ifo</CODE> + file you will need to use the <CODE>-vobsubid</CODE> option to let it know + what language id to put in the <CODE>.idx</CODE> file.</P> <P>Each run will append the running subtitle if the <CODE>.idx</CODE> and -<CODE>.sub</CODE> files already exist. So you should remove any before starting.</P> + <CODE>.sub</CODE> files already exist. So you should remove any before + starting.</P> <P><B>Examples</B></P> <P><I>Copying two subtitles from a DVD while doing 3-pass encoding</I><BR> - <CODE>rm subtitles.idx subtitles.sub</CODE><BR> - <CODE>mencoder -dvd 1 -vobsubout subtitles -vobsuboutindex 0 -sid 2 -o frameno.avi -ovc frameno</CODE><BR> - <CODE>mencoder -dvd 1 -oac copy -ovc divx4 -pass 1</CODE><BR> - <CODE>mencoder -dvd 1 -oac copy -ovc divx4 -pass 2 -vobsubout subtitles -vobsuboutindex 1 -sid 5</CODE></P> + <CODE>rm subtitles.idx subtitles.sub</CODE><BR> + <CODE>mencoder -dvd 1 -vobsubout subtitles -vobsuboutindex 0 + -sid 2 -o frameno.avi -ovc frameno</CODE><BR> + <CODE>mencoder -dvd 1 -oac copy -ovc divx4 -pass 1</CODE><BR> + <CODE>mencoder -dvd 1 -oac copy -ovc divx4 -pass 2 -vobsubout + subtitles -vobsuboutindex 1 -sid 5</CODE></P> <P><I>Copying a french subtitle from an MPEG file</I><BR> - <CODE>rm subtitles.idx subtitles.sub</CODE><BR> - <CODE>mencoder movie.mpg -ifo movie.ifo -vobsubout subtitles -vobsuboutindex 0 -vobsuboutid fr -sid 1</CODE></P> + <CODE>rm subtitles.idx subtitles.sub</CODE><BR> + <CODE>mencoder movie.mpg -ifo movie.ifo -vobsubout subtitles + -vobsuboutindex 0 -vobsuboutid fr -sid 1</CODE></P> <P><B><A NAME="syntax">2.4.4 Syntax</A></B></P> @@ -468,8 +486,7 @@ <P>Encoding from tuner (for tuner options <A HREF="documentation.html#tv">see the TV input section!</A>):<BR> <CODE> mencoder -tv on:driver=v4l:width=640:height=480 <options></CODE></P> -<P>For all available options, <B>check the MEncoder man page!</B> -<P> +<P>For all available options, <B>check the MEncoder man page!</B></P> </BODY> </HTML>
--- a/DOCS/formats.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/formats.html Sat Aug 10 20:26:43 2002 +0000 @@ -13,21 +13,22 @@ <P><B><A NAME="formats">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> @@ -39,38 +40,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#dvd">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#dvd">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="avi">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> @@ -80,9 +82,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> @@ -110,32 +112,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="asf">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="mov">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#sorenson">Sorenson</A> codec @@ -144,26 +147,26 @@ <P><B><A NAME="vivo">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#vivo_video">VIVO video codec</A> -and <A HREF="codecs.html#vivo_audio">VIVO audio codec</A> sections for installation -instructions.</P> +<P>See the <A HREF="codecs.html#vivo_video">VIVO video codec</A> and + <A HREF="codecs.html#vivo_audio">VIVO audio codec</A> sections for installation + instructions.</P> <P><B><A NAME="fli">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="real">2.1.1.7 RealMedia (RM) files</A></B></P> @@ -178,19 +181,20 @@ <P><B><A NAME="nuppelvideo">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="yuv4mpeg">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> @@ -224,10 +228,10 @@ <P><B><A NAME="mp3">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="wav">2.1.2.2 WAV files</A></B></P>
--- a/DOCS/sound.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/sound.html Sat Aug 10 20:26:43 2002 +0000 @@ -33,22 +33,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="experiences">2.3.2.1 Sound Card experiences, recommendations</A></B></P> @@ -120,17 +122,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#drives">CD/DVD drives</A> section.</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#drives">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>
--- a/DOCS/video.html Sat Aug 10 18:56:45 2002 +0000 +++ b/DOCS/video.html Sat Aug 10 20:26:43 2002 +0000 @@ -16,38 +16,37 @@ <P><B><A NAME="mtrr">2.3.1.1 Setting up MTRR</A></B></P> <P>It is VERY recommended to check if the MTRR registers are set up properly, -because they can give a big performance boost.</P> + 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> -reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9<BR> -reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<BR> + --($:~)-- cat /proc/mtrr<BR> + reg00: base=0xe4000000 (3648MB), size= 16MB: write-combining, count=9<BR> + reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1<BR> </CODE></P> <P>It's right, shows my Matrox G400 with 16MB memory. I did this from -XFree 4.x.x , which sets up MTRR registers automatically.</P> + XFree 4.x.x , which sets up MTRR registers automatically.</P> -<P>If nothing worked, you have to do it manually. First, you have to find the base -address. -You have 3 ways to find it:</P> +<P>If nothing worked, you have to do it manually. First, you have to find the + base address. You have 3 ways to find it:</P> <UL> -<LI>from X11 startup messages, for example: -<P><CODE>(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000<BR> -(--) SVGA: Linear framebuffer at 0xD8000000</CODE></P></LI> -<LI>from /proc/pci (use lspci -v command): -<P> -<CODE>01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525</CODE> -<CODE>Memory at d8000000 (32-bit, prefetchable)</CODE> -</P></LI> -<LI>from mga_vid kernel driver messages (use dmesg): -<P><CODE>mga_mem_base = d8000000</CODE></P></LI> + <LI>from X11 startup messages, for example: + <P><CODE>(--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000<BR> + (--) SVGA: Linear framebuffer at 0xD8000000</CODE></P></LI> + <LI>from /proc/pci (use lspci -v command): + <P> + <CODE>01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525</CODE> + <CODE>Memory at d8000000 (32-bit, prefetchable)</CODE> + </P></LI> + <LI>from mga_vid kernel driver messages (use dmesg): + <P><CODE>mga_mem_base = d8000000</CODE></P></LI> </UL> <P>Then let's find the memory size. This is very easy, just convert video ram -size to hexadecimal, or use this table:</P> + size to hexadecimal, or use this table:</P> <TABLE BORDER=0> <TR><TD> </TD><TD>1 MB</TD><TD WIDTH="10%"></TD><TD>0x100000</TD></TR> @@ -60,41 +59,47 @@ <P>You know base address and memory size, let's setup MTRR registers! -For example, for the Matrox card above (base=0xd8000000) with 32MB -ram (size=0x2000000) just execute:</P> + For example, for the Matrox card above (base=0xd8000000) with 32MB + ram (size=0x2000000) just execute:</P> <P><CODE> echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr</CODE></P> <P>Not all CPUs support MTRRs. For example older K6-2's [around 266MHz, -stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat /proc/cpuinfo</CODE>' -to check it').</P> + stepping 0] doesn't support MTRR, but stepping 12's do ('<CODE>cat + /proc/cpuinfo</CODE>' to check it').</P> <P><B><A NAME="xv">2.3.1.2 Xv</A></B></P> <P>Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines -using the XVideo extension. This is what the option '-vo xv' uses. Also, -this is driver supports adjusting brightness/contrast/hue/etc (unless you use -the old, slow DirectShow DivX codec, which supports it everywhere), see the -man page.</P> + using the XVideo extension. This is what the option '-vo xv' uses. Also, + this is driver supports adjusting brightness/contrast/hue/etc (unless you use + the old, slow DirectShow DivX codec, which supports it everywhere), see the + man page.</P> <P>In order to make this work, be sure to check the following:</P> + <UL> -<LI>You have to use XFree86 4.0.2 or newer (former versions don't have XVideo)</LI> -<LI>Your card actually supports hardware acceleration (modern cards do)</LI> -<LI>X loads the XVideo extension, it's something like this: + <LI>You have to use XFree86 4.0.2 or newer (former versions don't have + XVideo)</LI> + <LI>Your card actually supports hardware acceleration (modern cards do)</LI> + <LI>X loads the XVideo extension, it's something like this: -<P><CODE> (II) Loading extension XVideo</CODE></P> -<P>in /var/log/XFree86.0.log</P> + <P><CODE> (II) Loading extension XVideo</CODE></P> + + <P>in /var/log/XFree86.0.log</P> -<P>NOTE: this loads only the XFree86's extension. In a good install, this is -always loaded, and doesn't mean that the _card's_ XVideo support is loaded!</P> + <P>NOTE: this loads only the XFree86's extension. In a good install, this + is always loaded, and doesn't mean that the _card's_ XVideo support is + loaded!</P> + </LI> -<LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the -part of the XFree86 distribution. It should display a long text, similar -to this: -<PRE> + <LI>Your card has Xv support under Linux. To check, try 'xvinfo', it is the + part of the XFree86 distribution. It should display a long text, similar + to this: + + <PRE> X-Video Extension version 2.2 screen #0 Adaptor #0: "Savage Streams Engine" @@ -118,71 +123,73 @@ number of planes: 3 type: YUV (planar) (...etc...) -</PRE> + </PRE> -<P>It must support YUY2 packed, and YV12 planar pixel formats to be -usable with <B>MPlayer</B>.</P> -</LI> + <P>It must support YUY2 packed, and YV12 planar pixel formats to be + usable with <B>MPlayer</B>.</P> + </LI> -<LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support. -./configure prints this.</LI> + <LI>And finally, check if <B>MPlayer</B> was compiled with 'xv' support. + ./configure prints this.</LI> </UL> <P><B><A NAME="xv_3dfx">2.3.1.2.1 3dfx cards</A></B></P> -<P>Older 3dfx drivers were known to have problems with XVideo acceleration, -it didn't support either YUY2 or YV12, and so. Verify that you have -XFree86 version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous -versions, including 4.1.0 <B>crashes with YV12</B>! -If you experience strange effects using -vo xv, try SDL (it has XVideo too) -and see if it helps. Check the <A HREF="#sdl">SDL section</A> for details.</P> +<P>Older 3dfx drivers were known to have problems with XVideo acceleration, it + didn't support either YUY2 or YV12, and so. Verify that you have XFree86 + version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous versions, + including 4.1.0 <B>crashes with YV12</B>! If you experience strange effects + using -vo xv, try SDL (it has XVideo too) and see if it helps. Check the + <A HREF="#sdl">SDL section</A> for details.</P> -<P><B>OR</B>, try the NEW -vo tdfxfb driver! See the <A HREF="#tdfxfb">tdfxfb</A> -section!</P> +<P><B>OR</B>, try the NEW -vo tdfxfb driver! See the + <A HREF="#tdfxfb">tdfxfb</A> section!</P> <P><B><A NAME="xv_s3">2.3.1.2.2 S3 cards</A></B></P> <P>S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3 -or greater (in case of image problems, try 16bpp). As for S3 Virge.. there is -xv support, but the card itself is very slow, so you better sell it.</P> + or greater (in case of image problems, try 16bpp). As for S3 Virge.. there is + xv support, but the card itself is very slow, so you better sell it.</P> -<P><B>NOTE</B>: Savage cards have a slow YV12 image displaying capability (it needs -to do YV12->YUY2 conversion, because the Savage hardware can't display YV12). -So when this documentation says at some point "this has YV12 output use this, -it's faster", it's not sure. Try <A HREF="http://www.mplayerhq.hu/MPlayer/contrib/Savage-driver/savage_drv.o.mmx2.bz2">this -driver</A>, it uses MMX2 for this task and is faster than the native X driver.</P> +<P><B>NOTE</B>: Savage cards have a slow YV12 image displaying capability (it + needs to do YV12->YUY2 conversion, because the Savage hardware can't display + YV12). So when this documentation says at some point "this has YV12 output + use this, it's faster", it's not sure. Try + <A HREF="http://www.mplayerhq.hu/MPlayer/contrib/Savage-driver/savage_drv.o.mmx2.bz2">this + driver</A>, it uses MMX2 for this task and is faster than the native X + driver.</P> <P><B><A NAME="xv_nvidia">2.3.1.2.3 nVidia cards</A></B></P> -<P>nVidia isn't a very good choice under Linux (according to nVidia, this -is <A HREF="users_against_developers.html#nvidia">not true</A>).. You'll have to use the -binary closed-source nVidia driver, available at nVidia's web site. The standard XFree86 -driver doesn't support XVideo for these cards, due to nVidia's closed -sources/specifications.</P> +<P>nVidia isn't a very good choice under Linux (according to nVidia, this is + <A HREF="users_against_developers.html#nvidia">not true</A>).. You'll have to + use the binary closed-source nVidia driver, available at nVidia's web site. + The standard XFree86 driver doesn't support XVideo for these cards, due to + nVidia's closed sources/specifications.</P> <P>As far as I know the latest XFree86 driver contains XVideo support for -GeForce 2 and 3.</P> + GeForce 2 and 3.</P> <P>Riva128 cards don't have XVideo support even with the nVidia driver :( -Complain to nVidia.</P> + Complain to nVidia.</P> <P><B><A NAME="xv_ati">2.3.1.2.4 ATI cards</A></B></P> <UL> -<LI>The <A HREF="http://www.linuxvideo.org/gatos">GATOS driver</A> (which you -should use, unless you have Rage128 or Radeon) has VSYNC enabled by default. It -means that decoding speed (!) is synced to the monitor's refresh rate. If -playing seems to be slow, try disabling VSYNC somehow, or set refresh rate to -n*(fps of the movie) Hz.</LI> + <LI>The <A HREF="http://www.linuxvideo.org/gatos">GATOS driver</A> (which you + should use, unless you have Rage128 or Radeon) has VSYNC enabled by + default. It means that decoding speed (!) is synced to the monitor's + refresh rate. If playing seems to be slow, try disabling VSYNC somehow, or + set refresh rate to n*(fps of the movie) Hz.</LI> -<LI>Radeon VE - currently only XFree86 CVS has driver for this card, version -4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can -happily get <B>accelerated</B> display, with or without <B>TV output</B>, and -no libraries or X are needed. Read the <A HREF="#vidix">VIDIX</A> section.</LI> + <LI>Radeon VE - currently only XFree86 CVS has driver for this card, version + 4.1.0 doesn't. And no TV out support. Of course with <B>MPlayer</B> you can + happily get <B>accelerated</B> display, with or without <B>TV output</B>, and + no libraries or X are needed. Read <A HREF="#vidix">Vidix</A> section.</LI> </UL> @@ -193,58 +200,59 @@ <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> - <I>[...]</I><BR> - Driver "neomagic"<BR> - <B>Option "OverlayMem" "829440"</B><BR> - <I>[...]</I><BR> -EndSection + Section "Device"<BR> + <I>[...]</I><BR> + Driver "neomagic"<BR> + <B>Option "OverlayMem" "829440"</B><BR> + <I>[...]</I><BR> + EndSection </P> <P><B><A NAME="xv_trident">2.3.1.2.6 Trident cards</A></B></P> <P>If you want to use xv with a trident card, provided that it doesn't -work with 4.1.0, try the latest CVS of XFree or wait for XFree 4.2.0. -The latest CVS adds support for fullscreen xv support with the -Cyberblade XP card.</P> + work with 4.1.0, try the latest CVS of XFree or wait for XFree 4.2.0. + The latest CVS adds support for fullscreen xv support with the + Cyberblade XP card.</P> <P><B><A NAME="dga">2.3.1.3 DGA</A></B></P> <P><B><A NAME="dga_summary">2.3.1.3.1 Summary</A></B></P> -<P>This document tries to explain in some words what DGA is in general and -what the DGA video output driver for <B>MPlayer</B> can do (and what it can't).</P> +<P>This document tries to explain in some words what DGA is in general and what + the DGA video output driver for <B>MPlayer</B> can do (and what it + can't).</P> <P><B><A NAME="dga_whatis">2.3.1.3.2 What is DGA</A></B></P> <P>DGA is short for Direct Graphics Access and is a means for a program to -bypass the X-Server and directly modifying the framebuffer memory. -Technically spoken this happens by mapping the framebuffer memory into -the memory range of your process. This is allowed by the kernel only -if you have superuser privileges. You can get these either by logging in -as root or by setting the SUID bit on the <B>MPlayer</B> executable (NOT -recommended!).</P> + bypass the X-Server and directly modifying the framebuffer memory. + Technically spoken this happens by mapping the framebuffer memory into + the memory range of your process. This is allowed by the kernel only + if you have superuser privileges. You can get these either by logging in + as root or by setting the SUID bit on the <B>MPlayer</B> executable (NOT + recommended!).</P> <P>There are two versions of DGA: DGA1 is used by XFree 3.x.x and DGA2 was -introduced with XFree 4.0.1.</P> + introduced with XFree 4.0.1.</P> <P>DGA1 provides only direct framebuffer access as described above. For -switching the resolution of the video signal you have to rely on the -XVidMode extension.</P> + switching the resolution of the video signal you have to rely on the + XVidMode extension.</P> <P>DGA2 incorporates the features of XVidMode extension and also allows -switching the depth of the display. So you may, although basically -running a 32 bit depth X server, switch to a depth of 15 bits and vice -versa. </P> + switching the depth of the display. So you may, although basically + running a 32 bit depth X server, switch to a depth of 15 bits and vice + versa. </P> <P>However DGA has some drawbacks. It seems it is somewhat dependent on the -graphics chip you use and on the implementation of the X server's video -driver that controls this chip. So it does not work on every system ...</P> + graphics chip you use and on the implementation of the X server's video + driver that controls this chip. So it does not work on every system ...</P> <P><B><A NAME="dga_installation">2.3.1.3.3 Installing DGA support for MPlayer</A></B></P> @@ -253,146 +261,151 @@ <P> <CODE>(II) Loading extension XFree86-DGA</CODE></P> -<P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! -<B>MPlayer</B>'s DGA driver is autodetected on ./configure, or you can force it -with --enable-dga.</P> +<P>See, XFree86 4.0.x or greater is VERY RECOMMENDED! <B>MPlayer</B>'s DGA + driver is autodetected on ./configure, or you can force it with + --enable-dga.</P> <P>If the driver couldn't switch to a smaller resolution, experiment with -switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that -the movie fits in. There is no converter right now.. :(</P> + switches -vm (only with X 3.3.x), -fs, -bpp, -zoom to find a video mode that + the movie fits in. There is no converter right now.. :(</P> -<P>Become ROOT. DGA needs root access to be able to write directly video memory. -If you want to run it as user, then install <B>MPlayer</B> SUID root:</P> +<P>Become ROOT. DGA needs root access to be able to write directly video + memory. If you want to run it as user, then install <B>MPlayer</B> SUID + root:</P> <P><CODE> - chown root /usr/local/bin/mplayer<BR> - chmod 750 /usr/local/bin/mplayer<BR> - chmod +s /usr/local/bin/mplayer</CODE></P> + chown root /usr/local/bin/mplayer<BR> + chmod 750 /usr/local/bin/mplayer<BR> + chmod +s /usr/local/bin/mplayer</CODE></P> <P>Now it works as a simple user, too.</P> <P><B>!!!! BUT STAY TUNED !!!!</B><BR> -This is a <B>BIG</B> security risk! Never do this on a server or on a computer -can be accessed by more people than only you because they can gain root -privileges through SUID root <B>MPlayer</B>.<BR> -<B>!!!! SO YOU HAVE BEEN WARNED ... !!!!</B></P> + This is a <B>BIG</B> security risk! Never do this on a server or on a + computer can be accessed by more people than only you because they can gain + root privileges through SUID root <B>MPlayer</B>.<BR> + <B>!!!! SO YOU HAVE BEEN WARNED ... !!!!</B></P> <P>Now use '-vo dga' option, and there you go! (hope so:) -You should also try if the '-vo sdl:dga' option works for you! It's much -faster!!!</P> + You should also try if the '-vo sdl:dga' option works for you! It's much + faster!!!</P> <P><B><A NAME="dga_resolution">2.3.1.3.4 Resolution switching</A></B></P> -<P>The DGA driver allows for switching the resolution of the output signal. -This avoids the need for doing (slow) software scaling and at the same -time provides a fullscreen image. Ideally it would switch to the exact -resolution (except for honoring aspect ratio) of the video data, but the -X server only allows switching to resolutions predefined in -<CODE>/etc/X11/XF86Config</CODE> (<CODE>/etc/X11/XF86Config-4</CODE> for XFree 4.0.X respectively). -Those are defined by so-called modelines and depend on the capabilities -of your video hardware. The X server scans this config file on startup and -disables the modelines not suitable for your hardware. You can find -out which modes survive with the X11 log file. It can be found at: -<CODE>/var/log/XFree86.0.log</CODE>.</P> +<P>The DGA driver allows for switching the resolution of the output signal. + This avoids the need for doing (slow) software scaling and at the same time + provides a fullscreen image. Ideally it would switch to the exact resolution + (except for honoring aspect ratio) of the video data, but the X server only + allows switching to resolutions predefined in + <CODE>/etc/X11/XF86Config</CODE> (<CODE>/etc/X11/XF86Config-4</CODE> for + XFree 4.0.X respectively). Those are defined by so-called modelines and + depend on the capabilities of your video hardware. The X server scans this + config file on startup and disables the modelines not suitable for your + hardware. You can find out which modes survive with the X11 log file. It can + be found at: + <CODE>/var/log/XFree86.0.log</CODE>.</P> + <P>See appendix A for some sample modeline definitions.</P> <P><B><A NAME="dga_mplayer">2.3.1.3.5 DGA & MPlayer</A></B></P> -<P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to make -use of it (-vo sdl:dga) and within the DGA driver (-vo dga). -The above said is true for both; in the following sections I'll explain -how the DGA driver for <B>MPlayer</B> works.</P> +<P>DGA is used in two places with <B>MPlayer</B>: The SDL driver can be made to + make use of it (-vo sdl:dga) and within the DGA driver (-vo dga). The above + said is true for both; in the following sections I'll explain how the DGA + driver for <B>MPlayer</B> works.</P> <P><B><A NAME="dga_features">2.3.1.3.6 Features of the DGA driver</A></B></P> <P>The DGA driver is invoked by specifying -vo dga at the command line. -The default behavior is to switch to a resolution matching the original -resolution of the video as close as possible. It deliberately ignores the --vm and -fs switches (enabling of video mode switching and fullscreen) - -it always tries to cover as much area of your screen as possible by switching -the video mode, thus refraining to use a single additional cycle of your CPU -to scale the image. -If you don't like the mode it chooses you may force it to choose the mode -matching closest the resolution you specify by -x and -y. -By providing the -v option, the DGA driver will print, among a lot of other -things, a list of all resolutions supported by your current XF86-Config -file. -Having DGA2 you may also force it to use a certain depth by using the -bpp -option. Valid depths are 15, 16, 24 and 32. It depends on your hardware -whether these depths are natively supported or if a (possibly slow) -conversion has to be done.</P> + The default behavior is to switch to a resolution matching the original + resolution of the video as close as possible. It deliberately ignores the + -vm and -fs switches (enabling of video mode switching and fullscreen) - + it always tries to cover as much area of your screen as possible by switching + the video mode, thus refraining to use a single additional cycle of your CPU + to scale the image. + If you don't like the mode it chooses you may force it to choose the mode + matching closest the resolution you specify by -x and -y. + By providing the -v option, the DGA driver will print, among a lot of other + things, a list of all resolutions supported by your current XF86-Config + file. + Having DGA2 you may also force it to use a certain depth by using the -bpp + option. Valid depths are 15, 16, 24 and 32. It depends on your hardware + whether these depths are natively supported or if a (possibly slow) + conversion has to be done.</P> <P>If you should be lucky enough to have enough offscreen memory left to -put a whole image there, the DGA driver will use doublebuffering, which -results in much smoother movie replaying. It will tell you whether double- -buffering is enabled or not.</P> + put a whole image there, the DGA driver will use doublebuffering, which + results in much smoother movie replaying. It will tell you whether double- + buffering is enabled or not.</P> <P>Doublebuffering means that the next frame of your video is being drawn in -some offscreen memory while the current frame is being displayed. When the -next frame is ready, the graphics chip is just told the location in memory -of the new frame and simply fetches the data to be displayed from there. -In the meantime the other buffer in memory will be filled again with new -video data.</P> + some offscreen memory while the current frame is being displayed. When the + next frame is ready, the graphics chip is just told the location in memory + of the new frame and simply fetches the data to be displayed from there. + In the meantime the other buffer in memory will be filled again with new + video data.</P> <P>Doublebuffering may be switched on by using the option -double and may be -disabled with -nodouble. Current default option is to disable -doublebuffering. When using the DGA driver, onscreen display (OSD) only -works with doublebuffering enabled. However, enabling doublebuffering may -result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of -CPU time!) depending on the implementation of DGA for your hardware.</P> + disabled with -nodouble. Current default option is to disable + doublebuffering. When using the DGA driver, onscreen display (OSD) only + works with doublebuffering enabled. However, enabling doublebuffering may + result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of + CPU time!) depending on the implementation of DGA for your hardware.</P> <P><B><A NAME="dga_speed">2.3.1.3.7 Speed issues</A></B></P> <P>Generally spoken, DGA framebuffer access should be at least as fast as using -the X11 driver with the additional benefit of getting a fullscreen image. -The percentage speed values printed by <B>MPlayer</B> have to be interpreted with -some care, as for example, with the X11 driver they do not include the time -used by the X-Server needed for the actual drawing. Hook a terminal to a -serial line of your box and start top to see what is really going on in your -box ...</P> + the X11 driver with the additional benefit of getting a fullscreen image. + The percentage speed values printed by <B>MPlayer</B> have to be interpreted + with some care, as for example, with the X11 driver they do not include the + time used by the X-Server needed for the actual drawing. Hook a terminal to a + serial line of your box and start top to see what is really going on in your + box...</P> <P>Generally spoken, the speedup done by using DGA against 'normal' use of X11 -highly depends on your graphics card and how well the X-Server module for it -is optimized.</P> + highly depends on your graphics card and how well the X-Server module for it + is optimized.</P> <P>If you have a slow system, better use 15 or 16bit depth since they require -only half the memory bandwidth of a 32 bit display.</P> + only half the memory bandwidth of a 32 bit display.</P> -<P>Using a depth of 24bit is even a good idea if your card natively just supports -32 bit depth since it transfers 25% less data compared to the 32/32 mode.</P> +<P>Using a depth of 24bit is even a good idea if your card natively just + supports 32 bit depth since it transfers 25% less data compared to the 32/32 + mode.</P> <P>I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2 -CPUs might work at 400 MHZ and above.</P> + CPUs might work at 400 MHZ and above.</P> <P><B><A NAME="dga_bugs">2.3.1.3.8 Known bugs</A></B></P> <P>Well, according to some developers of XFree, DGA is quite a beast. They -tell you better not to use it. Its implementation is not always flawless -with every chipset driver for XFree out there.</P> + tell you better not to use it. Its implementation is not always flawless + with every chipset driver for XFree out there.</P> <UL> -<LI>With XFree 4.0.3 and nv.o there is a bug resulting in strange colors.</LI> -<LI>ATI driver requires to switch mode back more than once after finishing -using of DGA.</LI> -<LI>Some drivers simply fail to switch back to normal resolution (use -Ctrl-Alt-Keypad +, - to switch back manually).</LI> -<LI>Some drivers simply display strange colors.</LI> -<LI>Some drivers lie about the amount of memory they map into the process's -address space, thus vo_dga won't use doublebuffering (SIS?).</LI> -<LI>some drivers seem to fail to report even a single valid mode. In this -case the DGA driver will crash telling you about a nonsense mode of -100000x100000 or the like ...</LI> -<LI>OSD only works with doublebuffering enabled.</LI> + <LI>With XFree 4.0.3 and nv.o there is a bug resulting in strange + colors.</LI> + <LI>ATI driver requires to switch mode back more than once after finishing + using of DGA.</LI> + <LI>Some drivers simply fail to switch back to normal resolution (use + Ctrl-Alt-Keypad +, - to switch back manually).</LI> + <LI>Some drivers simply display strange colors.</LI> + <LI>Some drivers lie about the amount of memory they map into the process's + address space, thus vo_dga won't use doublebuffering (SIS?).</LI> + <LI>some drivers seem to fail to report even a single valid mode. In this + case the DGA driver will crash telling you about a nonsense mode of + 100000x100000 or the like ...</LI> + <LI>OSD only works with doublebuffering enabled.</LI> </UL> <P><B><A NAME="dga_future">2.3.1.3.9 Future work</A></B></P> <UL> -<LI>use of the new X11 render interface for OSD</LI> -<LI>where is my TODO list ???? :-(((</LI> + <LI>use of the new X11 render interface for OSD</LI> + <LI>where is my TODO list ???? :-(((</LI> </UL> @@ -412,18 +425,19 @@ </PRE> <P>These entries work fine with my Riva128 chip, using nv.o X server driver -module.</P> + module.</P> <P><B><A NAME="dga_bug_reports">2.3.1.3.B Bug Reports</A></B></P> <P>If you experience troubles with the DGA driver please feel free to file -a bug report to me (e-mail address below). Please start <B>MPlayer</B> with the --v option and include all lines in the bug report that start with vo_dga:</P> + a bug report to me (e-mail address below). Please start <B>MPlayer</B> with + the -v option and include all lines in the bug report that start with + vo_dga:</P> <P>Please do also include the version of X11 you are using, the graphics card -and your CPU type. The X11 driver module (defined in XF86-Config) might -also help. Thanks!</P> + and your CPU type. The X11 driver module (defined in XF86-Config) might + also help. Thanks!</P> <P><I>Acki (acki@acki-netz.de, www.acki-netz.de)</I></P> @@ -472,8 +486,10 @@ </TABLE> <P><B>KNOWN BUGS:</B></P> -<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> + <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).</LI> </UL> <P><B><A NAME="svgalib">2.3.1.5 SVGAlib</A></B></P> @@ -513,14 +529,14 @@ <P><B><A NAME="fbdev">2.3.1.6 Framebuffer output (FBdev)</A></B></P> <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> + Read the framebuffer documentation in the kernel sources + (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?) : -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> + 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> <P>The FBdev output takes some additional parameters above the others:</P> @@ -539,29 +555,29 @@ <P><CODE> mplayer -vm -fbmode (NameOfMode) filename</CODE></P> <UL> -<LI><B>-vm</B> alone will choose the most suitable mode from /etc/fb.modes . Can be -used together with -x and -y options too. The -flip option is supported only -if the movie's pixel format matches the video mode's pixel format. -Pay attention to the bpp value, fbdev driver tries to use the current, -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> - 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> - or <CODE>setterm -cursor on</CODE></LI> + <LI><B>-vm</B> alone will choose the most suitable mode from /etc/fb.modes. + Can be used together with -x and -y options too. The -flip option is + supported only if the movie's pixel format matches the video mode's pixel + format. Pay attention to the bpp value, fbdev driver tries to use the + current, 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> 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> + or <CODE>setterm -cursor on</CODE></LI> </UL> <P>NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer, -and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P> + and don't ask for it, since it's not an <B>MPlayer</B> limitation.</P> <P><B><A NAME="mga_vid">2.3.1.7 Matrox framebuffer (mga_vid)</A></B></P> <P>This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler) -support, the mga_vid kernel driver. It's active developed by me (A'rpi), and -it has hardware VSYNC support with triple buffering. It works on both -framebuffer console and under X.</P> + support, the mga_vid kernel driver. It's active developed by me (A'rpi), and + it has hardware VSYNC support with triple buffering. It works on both + framebuffer console and under X.</P> <P><B>WARNING</B>: on non-Linux systems, use <A HREF="#vidix">VIDIX</A> for mga_vid !!!</P> @@ -569,7 +585,7 @@ <P>To use it, you first have to compile mga_vid.o:</P> <P><CODE> cd drivers<BR> - make</CODE></P> + make</CODE></P> <P>Then create /dev/mga_vid device:</P> @@ -580,13 +596,13 @@ <P><CODE> insmod mga_vid.o</CODE></P> <P>You should verify the memory size detection using the 'dmesg' command. If -it's bad, use the mga_ram_size option (rmmod mga_vid first), specify card's -memory size in MB:</P> + it's bad, use the mga_ram_size option (rmmod mga_vid first), specify card's + memory size in MB:</P> <P><CODE> insmod mga_vid.o mga_ram_size=16</CODE></P> <P>To make it load/unload automatically when needed, first insert the following line -at the end of /etc/modules.conf:</P> + at the end of /etc/modules.conf:</P> <P><CODE> alias char-major-178 mga_vid</CODE></P> @@ -598,14 +614,14 @@ <P><CODE> depmod -a</CODE></P> <P>Now you have to (re)compile <B>MPlayer</B>, ./configure will detect /dev/mga_vid -and build the 'mga' driver. Using it from <B>MPlayer</B> goes by '-vo mga' if -you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.</P> + and build the 'mga' driver. Using it from <B>MPlayer</B> goes by '-vo mga' if + you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.</P> <P>The mga_vid driver cooperates with Xv.</P> <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="sis_vid">2.3.1.8 SiS 6326 framebuffer (sis_vid)</A></B></P> @@ -613,38 +629,39 @@ <P>SiS 6326 YUV Framebuffer driver -> sis_vid kernel driver</P> <P>Its interface should be compatible with the mga_vid, but the driver was not -updated after the mga_vid changes, so it's outdated now. Volunteers -needed to test it and bring the code up-to-date.</P> + updated after the mga_vid changes, so it's outdated now. Volunteers + needed to test it and bring the code up-to-date.</P> <P><B><A NAME="tdfxfb">2.3.1.9 3dfx YUV support (tdfxfb)</A></B></P> <P>This driver uses the kernel's tdfx framebuffer driver to play movies with -YUV acceleration. You'll need a kernel with tdfxfb support, and recompile with -<CODE>./configure --enable-tdfxfb</CODE></P> + YUV acceleration. You'll need a kernel with tdfxfb support, and recompile + with <CODE>./configure --enable-tdfxfb</CODE></P> <P><B><A NAME="opengl">2.3.1.10 OpenGL output</A></B></P> <P><B>MPlayer</B> supports displaying movies using OpenGL, but if your -platform/driver supports xv as should be the case on a PC with Linux, use xv -instead, OpenGL performance is considerably worse. If you have an X11 -implementation without xv support, OpenGL is a viable alternative.</P> + platform/driver supports xv as should be the case on a PC with Linux, use xv + instead, OpenGL performance is considerably worse. If you have an X11 + implementation without xv support, OpenGL is a viable alternative.</P> <P>Unfortunately not all drivers support this feature. The Utah-GLX drivers -(for XFree86 3.3.6) support it for all cards. See -<A HREF="http://utah-glx.sourceforge.net">http://utah-glx.sourceforge.net</A> -for details about how to install it.</P> + (for XFree86 3.3.6) support it for all cards. See + <A HREF="http://utah-glx.sourceforge.net">http://utah-glx.sourceforge.net</A> + for details about how to install it.</P> <P>XFree86(DRI) >= 4.0.3 supports OpenGL with Matrox and Radeon cards, >= 4.2 -supports Rage128. See -<A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> -for download and installation instructions.</P> + supports Rage128. See + <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A> + for download and installation instructions.</P> <P><B><A NAME="aalib">2.3.1.11 AAlib - text mode displaying</A></B></P> <P><B>AAlib</B> is a library for displaying graphics in text mode, using powerful -ASCII renderer. There are LOTS of programs already supporting it, like Doom, -Quake, etc. <B>MPlayer</B> contains a very usable driver for it. -If ./configure detects aalib installed, the aalib libvo driver will be built.</P> + ASCII renderer. There are LOTS of programs already supporting it, like Doom, + Quake, etc. <B>MPlayer</B> contains a very usable driver for it. + If ./configure detects aalib installed, the aalib libvo driver will be + built.</P> <TABLE BORDER=0> <TR><TD COLSPAN=4><P><B>You can use some keys in the AA Window to change rendering options:</B></P></TD></TR> @@ -673,72 +690,71 @@ </TABLE> <P>NOTE: the rendering is very CPU intensive, especially when using AA-on-X -(using aalib on X), and it's least CPU intensive on standard, -non-framebuffer console. Use SVGATextMode to set up a big textmode, -then enjoy! (secondary head Hercules cards rock :)) (anyone can enhance -fbdev to do conversion/dithering to hgafb? Would be neat :)</P> + (using aalib on X), and it's least CPU intensive on standard, + non-framebuffer console. Use SVGATextMode to set up a big textmode, + then enjoy! (secondary head Hercules cards rock :)) (anyone can enhance + fbdev to do conversion/dithering to hgafb? Would be neat :)</P> <P>Use the <CODE>-framedrop</CODE> option if your computer isn't fast enough to -render all frames!</P> + render all frames!</P> -<P>Playing on terminal you'll get better speed and quality using the Linux driver, not -curses (-aadriver linux). But therefore you need write access on /dev/vcsa<terminal>! -That isn't autodetected by aalib, but vo_aa tries to find the best mode. -See <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> for further tuning issues.</P> +<P>Playing on terminal you'll get better speed and quality using the Linux + driver, not curses (-aadriver linux). But therefore you need write access on + /dev/vcsa<terminal>! That isn't autodetected by aalib, but vo_aa tries + to find the best mode. See + <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourceforge.net/tune/</A> + for further tuning issues.</P> -<P><B><A NAME="vesa">2.3.1.12 VESA - output to VESA BIOS</A></B></P> +<P><B><A NAME="vesa">2.3.1.12. VESA - output to VESA BIOS</A></B></P> -<P> -This driver was designed and introduced as a <B>generic driver</B> for any video -card which has VESA VBE 2.0 compatible BIOS. Another advantage of this -driver is that it tries to force TV output on.<BR> -<B>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998</B> (Page 70) -says: -</P> +<P>This driver was designed and introduced as a <B>generic driver</B> for any + video card which has VESA VBE 2.0 compatible BIOS. Another advantage of this + driver is that it tries to force TV output on.<BR> + <B>VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998</B> (Page + 70) says:</P> <BLOCKQUOTE> <B>Dual-Controller Designs</B><BR> -VBE 3.0 supports the dual-controller design by assuming that since both -controllers are typically provided by the same OEM, under control of a -single BIOS ROM on the same graphics card, it is possible to hide the fact -that two controllers are indeed present from the application. This has the -limitation of preventing simultaneous use of the independent controllers, -but allows applications released before VBE 3.0 to operate normally. The -VBE Function 00h (Return Controller Information) returns the combined -information of both controllers, including the combined list of available modes. -When the application selects a mode, the appropriate controller is activated. -Each of the remaining VBE functions then operates on the active controller. + VBE 3.0 supports the dual-controller design by assuming that since both + controllers are typically provided by the same OEM, under control of a + single BIOS ROM on the same graphics card, it is possible to hide the fact + that two controllers are indeed present from the application. This has the + limitation of preventing simultaneous use of the independent controllers, + but allows applications released before VBE 3.0 to operate normally. The + VBE Function 00h (Return Controller Information) returns the combined + information of both controllers, including the combined list of available + modes. When the application selects a mode, the appropriate controller is + activated. Each of the remaining VBE functions then operates on the active + controller. </BLOCKQUOTE> -<P> -So you have chances to get working TV-out by using this driver.<BR> -(I guess that TV-out frequently is standalone head or standalone output -at least.) +<P>So you have chances to get working TV-out by using this driver.<BR> + (I guess that TV-out frequently is standalone head or standalone output + at least.)</P> + +<P><B>What are pluses:</B><BR> + - You have chances to watch movies <B>if Linux even doesn't know</B> your + video hardware.<BR> + - You don't need to have installed any graphics' related things on your Linux + (like X11 (aka XFree86), fbdev and so on). This driver can be run from + <B>text-mode</B>.<BR> + - You have chances to get <B>working TV-out</B>. (It's known at least for + ATI's cards).<BR> + - This driver calls <B>int 10h</B> handler thus it's not an emulator - it + calls <B>real</B> things of <B>real</B> BIOS in <B>real</B>-mode. (Finely - + in vm86 mode).<BR> + - You can use Vidix with it, thus getting accelerated video display + <B>AND</B> TV output at the same time! (recommended for ATI cards) </P> -<P> -<B>What are pluses:</B><BR> - - You have chances to watch movies <B>if Linux even doesn't know</B> your video hardware.<BR> - - You don't need to have installed any graphics' related things on your Linux -(like X11 (aka XFree86), fbdev and so on). This driver can be run from -<B>text-mode</B>.<BR> - - You have chances to get <B>working TV-out</B>. (It's known at least for ATI's cards).<BR> - - This driver calls <B>int 10h</B> handler thus it's not an emulator - it -calls <B>real</B> things of <B>real</B> BIOS in <B>real</B>-mode. (Finely - -in vm86 mode).<BR> - - You can use VIDIX with it, thus getting accelerated video display -<B>AND</B> TV output at the same time! (recommended for ATI cards) +<P><B>What are minuses:</B><BR> + - It works only on <B>x86 systems</B>.<BR> + - It can be used only by <B>ROOT</B>.<BR> + - Currently it's available only for <B>Linux</B>.<BR> </P> -<P> -<B>What are minuses:</B><BR> - - It works only on <B>x86 systems</B>.<BR> - - It can be used only by <B>ROOT</B>.<BR> - - Currently it's available only for <B>Linux</B>.<BR> -</P> - -<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> @@ -751,51 +767,54 @@ <TR><TD></TD><TD VALIGN="top"><CODE>-double</CODE></TD><TD></TD><TD>enables double buffering mode. (Available only in DGA mode). Should be slower of single buffering, but has no flickering effects.</TD></TR> </TABLE> -<P> -<B>Known problems and workaround:</B><BR> - - If you have installed <B>NLS</B> font on your Linux box and run VESA driver -from text-mode then after terminating <B>MPlayer</B> you will have <B>ROM font</B> loaded instead -of national. You can load national font again by using <B><I>setsysfont</I></B> utility -from for example Mandrake distribution.<BR> -(<B>Hint</B>: The same utility is used for localization of fbdev).<BR> - - Some <B>Linux graphics drivers</B> don't update active <B>BIOS mode</B> in DOS memory. So if you have such -problem - always use VESA driver only from <B>text-mode</B>. Otherwise text-mode (#03) will be -activated anyway and you will need restart your computer.<BR> - - Often after terminating VESA driver you get <B>black screen</B>. To return your screen -to original state - simply switch to other console (by pressing <B>Alt-Fx</B>) then switch -to your previous console by the same way.<BR> - - To get <B>working TV-out</B> you need have plugged TV-connector in before booting -your PC since video BIOS initializes itself only once during POST procedure. +<P><B>Known problems and workaround:</B><BR> + - If you have installed <B>NLS</B> font on your Linux box and run VESA driver + from text-mode then after terminating <B>MPlayer</B> you will have <B>ROM + font</B> loaded instead of national. You can load national font again by + using <B><I>setsysfont</I></B> utility from for example Mandrake + distribution.<BR> + (<B>Hint</B>: The same utility is used for localization of fbdev).<BR> + - Some <B>Linux graphics drivers</B> don't update active <B>BIOS mode</B> in + DOS memory. So if you have such problem - always use VESA driver only from + <B>text-mode</B>. Otherwise text-mode (#03) will be activated anyway and + you will need restart your computer.<BR> + - Often after terminating VESA driver you get <B>black screen</B>. To return + your screen to original state - simply switch to other console (by pressing + <B>Alt-Fx</B>) then switch to your previous console by the same way.<BR> + - To get <B>working TV-out</B> you need have plugged TV-connector in before + booting your PC since video BIOS initializes itself only once during POST + procedure. </P> <P><B><A NAME="x11">2.3.1.13 X11</A></B></P> <P>Avoid if possible. Outputs to X11 (uses shared memory extension), with no -hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but still -slow) software scaling, use the options <CODE>-fs -zoom</CODE>. Most cards have -hardware scaling support, use the <CODE>-vo xv</CODE> output for them, or -<CODE>-vo xmga</CODE> for Matroxes.</P> + hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but still + slow) software scaling, use the options <CODE>-fs -zoom</CODE>. Most cards + have hardware scaling support, use the <CODE>-vo xv</CODE> output for them, + or <CODE>-vo xmga</CODE> for Matroxes.</P> -<P>The problem is that most cards' driver doesn't support -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> +<P>The problem is that most cards' driver doesn't support 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> -<P>Software scaling is very slow, you better try changing video modes instead. -It's very simple. See the <A HREF="#dga_modelines">DGA section's modelines</A>, and -insert them into your XF86Config.</P> +<P>Software scaling is very slow, you better try changing video modes instead. + It's very simple. See the <A HREF="#dga_modelines">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> <P>If you can't find the modes you inserted, browse XFree86's output. Some -drivers can't use low pixelclocks that are needed for low resolution -video modes.</P> + drivers can't use low pixelclocks that are needed for low resolution + video modes.</P> <P><B><A NAME="vidix">2.3.1.14 VIDIX</A></B></P> @@ -851,12 +870,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> @@ -890,7 +909,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> @@ -936,15 +955,15 @@ <P><B><A NAME="zr">2.3.1.15 Zr</A></B></P> <P>This is a display-driver (<CODE>-vo zr</CODE>) for a number of MJPEG -capture/playback cards (tested for DC10+ and Buz, and it should work for the -LML33, the DC10). The driver works by encoding the frame to jpeg and then -sending it to the card. For the jpeg encoding <B>libavcodec</B> is -used, and required.</P> + capture/playback cards (tested for DC10+ and Buz, and it should work for the + LML33, the DC10). The driver works by encoding the frame to jpeg and then + sending it to the card. For the jpeg encoding <B>libavcodec</B> is + used, and required.</P> <P>This driver talks to the kernel driver available at -<A HREF="http://mjpeg.sourceforge.net">http://mjpeg.sourceforge.net</A>, so -you must get it working first. Then recompile <B>MPlayer</B> with -<CODE>--enable-zr</CODE>.</P> + <A HREF="http://mjpeg.sourceforge.net">http://mjpeg.sourceforge.net</A>, so + you must get it working first. Then recompile <B>MPlayer</B> with + <CODE>--enable-zr</CODE>.</P> Some remarks: <UL> @@ -969,9 +988,9 @@ <P><B><A NAME="dvb">2.3.1.16 DVB</A></B></P> <P><B>MPlayer</B> supports cards with the Siemens DVB chipset from vendors like -Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB drivers are -available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you -want to do software transcoding you should have at least a 1GHz CPU.</P> + Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB drivers are + available from the <A HREF="http://www.linuxtv.org">Linux TV site</A>. If you + want to do software transcoding you should have at least a 1GHz CPU.</P> <P>Configure should detect your DVB card. If it did not, force detection with @@ -990,14 +1009,14 @@ <P><B>USAGE</B></P> <P>Hardware decoding (playing standard MPEG1/2 files) can be done with this -command:</P> + command:</P> <PRE> mplayer -ao mpegpes -vo mpegpes file.mpg|vob </PRE> <P>Software decoding or transcoding different formats to MPEG1 can be achieved -using a command like this:</P> + using a command like this:</P> <PRE> mplayer -ao mpegpes -vo mpegpes -vop lavc yourfile.ext @@ -1005,19 +1024,20 @@ </PRE> <P>Note that DVB cards only support heights 288 and 576 for PAL or 240 and 480 -for NTSC. You <B>must</B> rescale for other heights by adding -<CODE>scale=width:height</CODE> with the width and height you want to the -<CODE>-vop</CODE> option. DVB cards accept various widths, like 720, 704, 640, -512, 480, 352 etc and do hardware scaling in horizontal direction, so you do not -need to scale horizontally in most cases. For a 512x384 (aspect 4:3) DivX try:</P> + for NTSC. You <B>must</B> rescale for other heights by adding + <CODE>scale=width:height</CODE> with the width and height you want to the + <CODE>-vop</CODE> option. DVB cards accept various widths, like 720, 704, + 640, 512, 480, 352 etc and do hardware scaling in horizontal direction, so + you do not need to scale horizontally in most cases. For a 512x384 (aspect + 4:3) DivX try:</P> <PRE> mplayer -ao mpegpes -vo mpegpes -vop lavc,scale=512:576 </PRE> <P>If you have a widescreen movie and you do not want to scale it to full height, -you can use the <CODE>expand=w:h</CODE> plugin to add black bands. To view a -640x384 DivX, try:</P> + you can use the <CODE>expand=w:h</CODE> plugin to add black bands. To view a + 640x384 DivX, try:</P> <PRE> mplayer -ao mpegpes -vo mpegpes -vop lavc,expand=640:576 file.avi @@ -1036,19 +1056,19 @@ </PRE> <P>For OSD and subtitles use the expand feature of the OSD plugin. So, instead -of <CODE>expand=w:h</CODE> or <CODE>expand=w:h:x:y</CODE>, use -<CODE>expand=w:h:x:y:1</CODE> (the 5th parameter <CODE>:1</CODE> at the end -will enable OSD rendering). You may want to move the image up a bit to get a -bigger black zone for subtitles. You may also want to move subtitles up, if they -are outside your TV screen, use the <CODE>-subpos <0-100></CODE> switch to -adjust this (<CODE>-subpos 80</CODE> is a good choice).</P> + of <CODE>expand=w:h</CODE> or <CODE>expand=w:h:x:y</CODE>, use + <CODE>expand=w:h:x:y:1</CODE> (the 5th parameter <CODE>:1</CODE> at the end + will enable OSD rendering). You may want to move the image up a bit to get a + bigger black zone for subtitles. You may also want to move subtitles up, if + they are outside your TV screen, use the <CODE>-subpos <0-100></CODE> switch + to adjust this (<CODE>-subpos 80</CODE> is a good choice).</P> <P>In order to play non-25fps movies on a PAL TV or with a slow CPU, add the -<CODE>-framedrop</CODE> option.</P> + <CODE>-framedrop</CODE> option.</P> <P>To keep the aspect ratio of DivX files and get the optimal scaling parameters -(hardware horizontal scaling and software vertical scaling while keeping the -right aspect ratio), use the new dvbscale plugin:</P> + (hardware horizontal scaling and software vertical scaling while keeping the + right aspect ratio), use the new dvbscale plugin:</P> <PRE> for 3:4 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale @@ -1058,26 +1078,26 @@ <P><B>FUTURE</B></P> <P>If you have questions or want to hear feature announcements and take part in -discussions on this subject, join our -<A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</A> -mailing list. Please remember that the list language is English.</P> + discussions on this subject, join our + <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dvb">MPlayer-DVB</A> + mailing list. Please remember that the list language is English.</P> <P>In the future you may expect the ability to display OSD and subtitles using -the native OSD feature of DVB cards, as well as more fluent playback of -non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial -decompression).</P> + the native OSD feature of DVB cards, as well as more fluent playback of + non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial + decompression).</P> <P><B><A NAME="dxr3">2.3.1.17 DXR3</A></B></P> <P><B>MPlayer</B> supports hardware accelerated playback with the Creative DXR3 -and Sigma Designs Hollywood Plus cards.</P> + and Sigma Designs Hollywood Plus cards.</P> -<P>First of all you will need properly installed DXR3/H+ drivers, version 0.12.0 -or later. You can find the drivers and installation instructions at the -<A HREF="http://dxr3.sourceforge.net/">DXR3 & Hollywood Plus for Linux</A> -site. Configure should detect your card automatically, compilation should go -without any problems.</P> +<P>First of all you will need properly installed DXR3/H+ drivers, version + 0.12.0 or later. You can find the drivers and installation instructions at + the <A HREF="http://dxr3.sourceforge.net/">DXR3 & Hollywood Plus for + Linux</A> site. Configure should detect your card automatically, compilation + should go without any problems.</P> <P><B>USAGE</B></P> @@ -1117,28 +1137,29 @@ <P><B>Overlay</B><P> <P>To get overlay run dxr3view that comes with the em8300 package before -starting <B>MPlayer</B>. You can set various options in dxr3view by pressing -<CODE>T</CODE> while holding the mouse cursor above the window.</P> + starting <B>MPlayer</B>. You can set various options in dxr3view by pressing + <CODE>T</CODE> while holding the mouse cursor above the window.</P> <P><B>MPEG1, MPEG2, VCD and DVD Notes</B></P> -<P>MPEG1/2 content should now automatically be detected by <B>MPlayer</B> and it -will use the hardware acceleration of the DXR3 to play it. If not, you can force -it to hardware acceleration with <CODE>-vc mpegpes</CODE>. Also, if you plan to -use any postprocessing filters you must use <CODE>-vc mpeg12</CODE>.</P> +<P>MPEG1/2 content should now automatically be detected by <B>MPlayer</B> and + it will use the hardware acceleration of the DXR3 to play it. If not, you can + force it to hardware acceleration with <CODE>-vc mpegpes</CODE>. Also, if you + plan to use any postprocessing filters you must use <CODE>-vc + mpeg12</CODE>.</P> -<P>In some instances, subtitles may not appear properly in sync with the A/V stream -when using hardware decoding (<CODE>-vc mpegpes</CODE>). This is a known bug. The -em8300 will also improperly handle subtitles that are too big, and may hang for -a second or two. At this time, the only workaround is to use -<CODE>-vc mpeg12</CODE> when viewing DVDs with subtitles.<P> +<P>In some instances, subtitles may not appear properly in sync with the A/V + stream when using hardware decoding (<CODE>-vc mpegpes</CODE>). This is a + known bug. The em8300 will also improperly handle subtitles that are too big, + and may hang for a second or two. At this time, the only workaround is to use + <CODE>-vc mpeg12</CODE> when viewing DVDs with subtitles.<P> <P><B><A NAME="tv-out">2.3.1.A TV-out support</A></B></P> <P><B><A NAME="tv-out_matrox">2.3.1.A.1 Matrox G400 cards</A></B></P> -<P>Under Linux you have 2 methods to get G400 TV out working :</P> +<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> @@ -1176,7 +1197,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> @@ -1192,15 +1213,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> @@ -1210,17 +1231,19 @@ <P> <B><U>PREAMBLE</U></B><BR> -Currently ATI doesn't want to support any of its TV-out chips under Linux, -because of their licensed Macrovision technology.</P> + Currently ATI doesn't want to support any of its TV-out chips under Linux, + because of their licensed Macrovision technology.</P> <P><B><U>ATI CARDS TV-OUT STATUS ON LINUX</U></B></P> <UL> -<LI><B>ATI Mach64</B>: supported by <A HREF="http://gatos.sf.net">gatos</A>.</LI> -<LI><B>ASIC Radeon VIVO</B>: supported by <A HREF="http://gatos.sf.net">gatos</A>.</LI> -<LI><B>Radeon</B> and <B>Rage128</B>: supported by <B>MPlayer</B>! -Check <a href="#vesa">VESA driver</a> and <A HREF="#vidix">VIDIX</A> -sections.</LI> + <LI><B>ATI Mach64</B>: supported by + <A HREF="http://gatos.sf.net">gatos</A>.</LI> + <LI><B>ASIC Radeon VIVO</B>: supported by + <A HREF="http://gatos.sf.net">gatos</A>.</LI> + <LI><B>Radeon</B> and <B>Rage128</B>: supported by <B>MPlayer</B>! + Check <a href="#vesa">VESA driver</a> and <A HREF="#2.3.1.15">Vidix</A> + sections.</LI> </UL> <P> @@ -1237,7 +1260,7 @@ <P><B><A NAME="tv-out_voodoo">2.3.1.A.3 Voodoo 3</A></B></P> <P> -Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>. + Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>. </P> </BODY>