mirror of
https://github.com/mpv-player/mpv
synced 2024-10-26 07:22:17 +02:00
big update
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@6584 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
gabucino
parent
e02775f59a
commit
56b2014b75
@ -20,14 +20,17 @@ daily generated list!!!</P>
|
||||
<P>The most important ones above all:</P>
|
||||
<UL>
|
||||
<LI>MPEG1 (VCD) and MPEG2 (DVD) video</LI>
|
||||
<LI>DivX ;-), OpenDivX (DivX4), DivX 5.01, 3ivX, M$ MPEG4 v2 and other MPEG4 variants</LI>
|
||||
<LI>Windows Media Video 7 (WMV1) and 8 (WMV2) used in .wmv files</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>
|
||||
</UL>
|
||||
|
||||
@ -39,9 +42,10 @@ for it!</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/is included in <B>MPlayer</B>, and built by
|
||||
default. Earlier, we used its postprocessing code to optionally enhance visual
|
||||
quality of MPEG1/2 movies. Now we use our own.</P>
|
||||
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
|
||||
@ -63,21 +67,16 @@ encoding. One disadvantage of this codec is that it is currently closed source.<
|
||||
compile as usual. If it does not detect it, you did not install or configure
|
||||
it correctly.</P>
|
||||
|
||||
<P>DivX4Linux conflicts with the old OpenDivX because their APIs are similar but
|
||||
incompatible. Therefore you can only have one of them compiled into <B>MPlayer</B>
|
||||
at a time.</P>
|
||||
|
||||
<P>DivX4Linux offers an OpenDivX compatibility mode such that you may choose from
|
||||
the following options when using this codec:</P>
|
||||
<P>DivX4Linux works in two modes:</P>
|
||||
|
||||
<TABLE BORDER=0>
|
||||
<TR><TD> </TD><TD VALIGN=top><CODE>-vc odivx</CODE></TD><TD> </TD>
|
||||
<TD>Uses the codec in OpenDivX fashion. In this case it
|
||||
produces YV12 images in its own buffer, and <B>MPlayer</B> does colorspace
|
||||
conversion via libvo. (<B>RECOMMENDED!</B>)</TD></TR>
|
||||
conversion via libvo. (<B>FAST, RECOMMENDED!</B>)</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top><CODE>-vc divx4</CODE></TD><TD></TD>
|
||||
<TD>Uses the colorspace conversion of the codec.
|
||||
In this mode you can use YUY2/UYVY, too.</TD></TR>
|
||||
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
|
||||
@ -89,18 +88,6 @@ according to your current color depth.</P>
|
||||
<P>NOTE: If your -vo driver supports direct rendering, then <CODE>-vc divx4</CODE> may be
|
||||
faster, or even the fastest solution.</P>
|
||||
|
||||
<P>Note: <B>OLD</B> OpenDivX supports postprocessing via the
|
||||
<CODE>-oldpp</CODE> option, but the range of values is strange:</P>
|
||||
|
||||
<TABLE BORDER=0>
|
||||
<TR><TD> </TD><TD>0</TD><TD> </TD>
|
||||
<TD>no postprocessing</TD></TR>
|
||||
<TR><TD></TD><TD>10 .. 20</TD>
|
||||
<TD></TD><TD>normal postprocessing (like level 2 with divxds)</TD></TR>
|
||||
<TR><TD></TD><TD>30 .. 60</TD>
|
||||
<TD></TD><TD>hard postprocessing, CPU intensive (like level 4 with divxds)</TD></TR>
|
||||
</TABLE>
|
||||
|
||||
|
||||
<P><B><A NAME=2.2.1.2>2.2.1.2. FFmpeg DivX/libavcodec</A></B></P>
|
||||
|
||||
@ -112,8 +99,8 @@ DivX/DivX4/DivX5/MP41/MP42 movies on non-x86 platforms</B>. Furthermore it offer
|
||||
decoding speed than the Win32 codecs or the original
|
||||
DivX4 library!</P>
|
||||
|
||||
<P>It also contains a lot of nice codecs, such as RealVideo 1.0, MJPEG, h263,
|
||||
h263+, etc.</P>
|
||||
<P>It also contains a lot of nice codecs, such as RealVideo 1.0, WMV7,
|
||||
MJPEG, h263, h263+, etc.</P>
|
||||
|
||||
<P>If you use an <B>MPlayer</B> release you have libavcodec right in the package,
|
||||
just build as usual. If you use <B>MPlayer</B> from CVS you have to extract
|
||||
@ -134,8 +121,6 @@ libavcodec from the FFmpeg CVS tree as FFmpeg 0.4.5 does <B>not</B> work with
|
||||
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>The codec also <B>supports postprocessing!</B></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>
|
||||
|
||||
@ -263,6 +248,24 @@ development was DivX4).</P>
|
||||
</OL>
|
||||
|
||||
|
||||
<P><B><A NAME=2.2.1.10>2.2.1.10. Sorenson</A></B></P>
|
||||
|
||||
<P><B>Sorenson</B> is a video codec developed by Apple. We are currently
|
||||
able to decode the first version of it (SVQ1), with a native decoder.</P>
|
||||
|
||||
<P><B>Advantages:</B></P>
|
||||
<UL>
|
||||
<LI>old, slow Macintosh machines were able to decode it</LI>
|
||||
</UL>
|
||||
|
||||
<P><B>Disadvantages:</B></P>
|
||||
<UL>
|
||||
<LI>SVQ3 is still not reverse-engineered</LI>
|
||||
</UL>
|
||||
|
||||
<P><B>Installation:</B> it's compiled and usable per default.</P>
|
||||
|
||||
|
||||
<P><B><A NAME=2.2.2>2.2.2. Audio codecs</A></B></P>
|
||||
|
||||
<P>The most important audio codecs above all:<BR></P>
|
||||
@ -274,7 +277,7 @@ development was DivX4).</P>
|
||||
<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)</LI>
|
||||
<LI>RealAudio: DNET (low bitrate AC3), Cook, Sipro</LI>
|
||||
</UL>
|
||||
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
body,table {
|
||||
body {
|
||||
font-family : Arial, Helvetica, sans-serif;
|
||||
font-size : 14px;
|
||||
background : white;
|
||||
|
||||
@ -79,6 +79,7 @@
|
||||
<LI><A HREF="codecs.html#2.2.1.7">2.2.1.7 Cinepak CVID</A></LI>
|
||||
<LI><A HREF="codecs.html#2.2.1.8">2.2.1.8 RealVideo</A></LI>
|
||||
<LI><A HREF="codecs.html#2.2.1.9">2.2.1.9 XViD</A></LI>
|
||||
<LI><A HREF="codecs.html#2.2.1.10">2.2.1.10 Sorenson</A></LI>
|
||||
</UL>
|
||||
</LI>
|
||||
<LI><A HREF="codecs.html#2.2.2">2.2.2 Audio</A>
|
||||
@ -138,7 +139,7 @@
|
||||
<LI><A HREF="video.html#2.3.1.11">2.3.1.11 AAlib - text mode displaying</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.12">2.3.1.12 VESA - output to VESA BIOS</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.13">2.3.1.13 X11</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.15">2.3.1.14 Rage128 / Radeon video overlay (OBSOLETED - link to Vidix!)</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.15">2.3.1.14 (non-existant section)</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.15">2.3.1.15 Vidix</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.16">2.3.1.16 Zr (for some MJPEG capture/playback boards)</A></LI>
|
||||
<LI><A HREF="video.html#2.3.1.A">2.3.1.A TVout</A>
|
||||
@ -308,7 +309,7 @@ Developer Cries
|
||||
Chris Phillips from the <B>mplayer-users</B> mailing list:</P>
|
||||
|
||||
<P><I>"I said a while ago that there is such a difference between a newbie and
|
||||
a dumbass. No matter what you actaully know about a system (linux, cars,
|
||||
a dumbass. No matter what you actually know about a system (linux, cars,
|
||||
girls :D) you should ALWAYS be able to take a step back and be objective,
|
||||
otherwise, you're just dumb IMHO. A girl i live with assumed the vacuum
|
||||
cleaner was broken because it didn't suck things up. never thought to change
|
||||
@ -326,13 +327,15 @@ Developer Cries
|
||||
<P><B>MPlayer</B> is a movie player for LINUX (runs on many other Unices, and
|
||||
<B>non-x86</B> CPUs, see <A HREF="#6">section 6</A>). It plays most MPEG, VOB,
|
||||
AVI, OGG, VIVO, ASF/WMV, QT/MOV, FLI, RM, NuppelVideo, yuv4mpeg, FILM, RoQ
|
||||
files, supported by many native, XAnim, and
|
||||
files, supported by many native, XAnim, RealPlayer, and
|
||||
Win32 DLL codecs. You can watch <B>VideoCD</B>, <B>SVCD</B>, <B>DVD</B>,
|
||||
<B>3ivx</B>, and even <B>DivX</B> movies too (and you don't need the avifile
|
||||
<B>3ivx</B>, <B>RealMedia</B>, and <B>DivX</B> movies too (and you don't need
|
||||
the avifile
|
||||
library at all!). The another big feature of mplayer is the wide range of
|
||||
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) too! Most
|
||||
and some lowlevel card-specific drivers (for Matrox, 3Dfx and Radeon,
|
||||
Mach64, Permedia3) too! Most
|
||||
of them supports software or hardware scaling, so you can enjoy movies in
|
||||
fullscreen. <B>MPlayer</B> supports displaying through some hardware MPEG
|
||||
decoder boards, such as the <B><A HREF="DVB">DVB</A></B> and <B> <A
|
||||
@ -343,10 +346,10 @@ display (OSD)?</P>
|
||||
|
||||
<P><B>MPlayer</B> is under GPL v2 license.</P>
|
||||
|
||||
<P>My player is rock solid playing damaged MPEG files (useful for some VCDs),
|
||||
<P>The player is rock solid playing damaged MPEG files (useful for some VCDs),
|
||||
and it plays bad AVI files which are unplayable with the famous
|
||||
windows media player. Even AVI files without index chunk are playable, and
|
||||
you can temporarily rebuild their indexes with the -idx option, or
|
||||
you can temporarily rebuild their indexes with the <CODE>-idx</CODE> option, or
|
||||
permanently with <B>MEncoder</B>, thus enabling seeking!
|
||||
As you see, stability and quality are the most important things,
|
||||
but the speed is also amazing.</P>
|
||||
@ -397,7 +400,7 @@ too. So I've decided to write/modify one...</P>
|
||||
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> May? ??, 2002<BR>
|
||||
<LI><B>MPlayer 0.90 "?"</B> Jul? ??, 2002<BR>
|
||||
</LI>
|
||||
</UL>
|
||||
|
||||
@ -480,7 +483,9 @@ 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>WMV movies</B> or older (MP41/MP42) ASF's</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>
|
||||
|
||||
@ -519,7 +524,7 @@ movies are best played with <B>MPlayer</B>'s own Cinepak decoder !</LI>
|
||||
(this is a nightly updated tarball of vorbis CVS).</LI>
|
||||
|
||||
<LI><B>MPlayer</B> can use the libraries of RealPlayer 8 or RealONE to play
|
||||
<B>RealVideo 2.0 and 3.0</B> files. See
|
||||
files with <B>RealVideo 2.0 and 3.0</B> video, and Sipro/Cook audio. See
|
||||
<A HREF="formats.html#2.1.1.7">RealMedia file format</A> section for
|
||||
installation instructions and more information!</LI>
|
||||
|
||||
@ -539,7 +544,7 @@ their memory, with <B>small CPU usage</B> (zooming doesn't increase it!), thus
|
||||
you get a nice and very fast fullscreen playing.</P>
|
||||
|
||||
<UL>
|
||||
<LI><B>Matrox G200/G400/G450/G550 cards</B> : although a
|
||||
<LI><B>Matrox G200/G400/G450/G550 cards</B>: although a
|
||||
<A HREF="video.html#2.3.1.9">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#2.3.1.7">mga_vid</A> section about its
|
||||
@ -549,7 +554,7 @@ you get a nice and very fast fullscreen playing.</P>
|
||||
<U><B>If you are non-Linux user</B></U>, your only possibility is the Vidix
|
||||
driver: read <A HREF="video.html#2.3.1.15">Vidix</A> documentation !</LI>
|
||||
|
||||
<LI><B>3Dfx Voodoo3/Banshee cards</B> : please see the
|
||||
<LI><B>3Dfx Voodoo3/Banshee cards</B>: please see the
|
||||
<A HREF="video.html#2.3.1.9">2.3.1.9</A> section in order to gain big
|
||||
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
|
||||
@ -557,20 +562,20 @@ you get a nice and very fast fullscreen playing.</P>
|
||||
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#2.3.1.14">Vidix driver</A> is
|
||||
<LI><B>ATI cards</B>: <A HREF="video.html#2.3.1.14">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#2.3.1.A.2">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
|
||||
<LI><B>S3 cards</B>: the Savage and Virge/DX chips have hardware acceleration. Use as
|
||||
new XFree86 version as possible, older drivers are buggy. Savage chips
|
||||
have problems with YV12 display, see <A HREF="video.html#2.3.1.2.2">S3 Xv
|
||||
section</A> for details. Older, Trio cards have no, or slow hardware
|
||||
support.</LI>
|
||||
|
||||
<LI><B>Nvidia cards</B> : very bad choice for video playing (NVidia has
|
||||
<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
|
||||
@ -578,11 +583,11 @@ contain support for hardware YUV acceleration for all NVidia cards !</U>
|
||||
You have to download Nvidia's closed-source drivers from nvidia.com. See
|
||||
details in <A HREF="video.html#2.3.1.2.3">Nvidia Xv driver</A> section.</LI>
|
||||
|
||||
<LI><B>3DLabs GLINT R3 and Permedia3</B> : a Vidix driver is provided
|
||||
<LI><B>3DLabs GLINT R3 and Permedia3</B>: a Vidix driver is provided
|
||||
(pm3_vid). Please see the <A HREF="video.html#2.3.1.15">Vidix
|
||||
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#2.3.1.2">Xv section</A> for
|
||||
@ -1559,10 +1564,10 @@ Proxy usage can also be forced :</P>
|
||||
|
||||
<P><B>MPlayer</B> can read from stdin (NOT named pipes). This can be for example
|
||||
used to play from FTP:</P>
|
||||
<P><CODE>wget ftp://micorsops.com/something.avi -O - | mplayer -</CODE></P>
|
||||
<P><CODE> wget ftp://micorsops.com/something.avi -O - | mplayer -</CODE></P>
|
||||
|
||||
<P>Note: it's also recommended to enable CACHE when playback from network:</P>
|
||||
<P><CODE>wget ftp://micorsops.com/something.avi -O - | mplayer -cache 8192 -</CODE></P>
|
||||
<P><CODE> wget ftp://micorsops.com/something.avi -O - | mplayer -cache 8192 -</CODE></P>
|
||||
|
||||
|
||||
<P><B><A NAME=4></A>4. <A HREF="faq.html">FAQ section</A></B></P>
|
||||
@ -1585,23 +1590,23 @@ and cd into programs directory:</P>
|
||||
</PRE>
|
||||
|
||||
<P>(... mplayer detects hardware/software, builds itself and.. )
|
||||
dpkg-deb: building package `mplayer' in `../mplayer_0.18-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>
|
||||
|
||||
<PRE>
|
||||
dpkg -i ../mplayer_0.18-1_i386.deb as root.
|
||||
dpkg -i ../mplayer_0.90-1_i386.deb as root.
|
||||
</PRE>
|
||||
|
||||
<P>Here's how it looks like:</P>
|
||||
|
||||
<PRE>
|
||||
eyck@incubus:/src/main$ sudo dpkg -i ../mplayer_0.18-1_i386.deb
|
||||
eyck@incubus:/src/main$ sudo dpkg -i ../mplayer_0.90-1_i386.deb
|
||||
Password:
|
||||
(Reading database ... 26946 files and directories currently installed.)
|
||||
Preparing to replace mplayer 0.17a-1 (using ../mplayer_0.18-1_i386.deb)
|
||||
Preparing to replace mplayer 0.50-1 (using ../mplayer_0.90-1_i386.deb)
|
||||
Unpacking replacement mplayer ...
|
||||
Setting up mplayer (0.18-1) ...
|
||||
Setting up mplayer (0.90-1) ...
|
||||
</PRE>
|
||||
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ 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
|
||||
stream copying and video resizing abilities.</P>
|
||||
powerful plugin system for video manipulation.</P>
|
||||
|
||||
<P><B><A NAME=2.4.2>2.4.2. Compiling</A></B></P>
|
||||
|
||||
@ -29,8 +29,8 @@ stream copying and video resizing abilities.</P>
|
||||
and have them PROPERLY installed. You need them if you want DivX4
|
||||
(1/2 pass) encoding.</LI>
|
||||
<LI><B>OPTIONAL</B> - <A HREF="codecs.html#2.2.1.9">download and install
|
||||
<B>XViD</B></A>. Very useful on non-Linux boxes, and/or when you need
|
||||
faster encoding than DivX4, with approximately the same quality.</LI>
|
||||
<B>XViD</B></A>. Not very useful, libavcodec's <I>mpeg4</I> codec
|
||||
can encode with much better speed AND quality than XViD or DivX4/5.</LI>
|
||||
<LI><B>OPTIONAL</B> - for libavcodec support, install libavcodec as
|
||||
described in the <A HREF="codecs.html#2.2.1.2">libavcodec section</A>.</LI>
|
||||
<LI><B>OPTIONAL</B> - download and compile <B>libmp3lame</B> (from lame 3.89beta or lame CVS).<BR>
|
||||
|
||||
242
DOCS/faq.html
242
DOCS/faq.html
@ -61,8 +61,8 @@ in case you run into problems.
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>Great, I have gcc 3.0.1 from Red Hat/Mandrake, then I'm fine--!
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>No, since there have been/are issues with these compilers as well.<BR>
|
||||
Use the 2.95.x series for reliability (not <A HREF="users_against_developers.html#gcc">2.96</A>).
|
||||
Use the latest gcc 3.x (starting at 3.0.4) if you want to use a 3.x version.
|
||||
To check the status of current compilers' MPlayer support, see the
|
||||
<A HREF="documentation.html#1.3">Installation</A> section.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>I tried to compile MPlayer, but I got this output:
|
||||
@ -236,9 +236,12 @@ Most of them are for debug purposes and will be removed soon.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>Why is video_out cpu usage zero (0%) for some files?
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>It's not zero, but it's called from the codec and thus cannot be measured
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A1:</TD><TD>It's not zero, but it's called from the codec and thus cannot be measured
|
||||
separately. You should try to play the file using <CODE>-vo null</CODE> and then
|
||||
<CODE>-vo ...</CODE> and check the difference to see the video_out speed.
|
||||
</TD><TR><TD></TD><TD VALIGN=top>A2:</TD><TD>You are using Direct Rendering,
|
||||
where the codec renders to the video memory itself. In this case, the
|
||||
decoding percentage contains the display percentage too.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>There are error messages about file not found <CODE>/usr/lib/win32/</CODE> ...
|
||||
@ -334,7 +337,7 @@ If something works with aviplay it doesn't mean that <B>MPlayer</B> will work
|
||||
and vice versa.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>Audio goes out of sync playing a .avi file.
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>Audio goes out of sync playing an AVI file.
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>Try the <CODE>-bps</CODE> or <CODE>-nobps</CODE> option. If it does not improve,
|
||||
read <A HREF="bugreports.html">this</A> and upload the file to FTP.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
@ -359,8 +362,11 @@ performance.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>MPlayer dies with "MPlayer interrupted by signal 4 in module: decode_video".
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>Try running <B>MPlayer</B> on the machine you compiled on. Or recompile. Don't
|
||||
use <B>MPlayer</B> on a CPU different from the one it was compiled on.
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>Try running <B>MPlayer</B> on the machine you compiled on. Or recompile
|
||||
with runtime CPU detection
|
||||
(<CODE>./configure --enable-runtime-cpudetection</CODE>). Don't
|
||||
use <B>MPlayer</B> on a CPU different from the one it was compiled on,
|
||||
without using the feature mentioned just now.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>I have problems with [your window manager] and fullscreen xv/xmga/sdl/x11 modes ...
|
||||
@ -542,7 +548,8 @@ While playing a DVD, I encountered this error:<BR>
|
||||
sizeof(cell_adr_t) >= c_adt->nr_of_vobs' failed.</CODE>
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>
|
||||
This is a known libdvdread 0.9.1/0.9.2 bug.
|
||||
Use libmpdvdkit.
|
||||
Use <B>libmpdvdkit</B>, which is present in MPlayer source, and used by
|
||||
default.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>
|
||||
@ -550,7 +557,8 @@ Can I compile libdvdread and libdvdcss on my sweet SPARC under Solaris?
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>
|
||||
Who knows ... It's said to work, so please test it and send feedback. Refer to
|
||||
the documentation of libdvdread and its homepage as well. We're not the authors
|
||||
of libdvdread.
|
||||
of libdvdread. Use <B>libmpdvdkit</B>, which is present in MPlayer source, and used by
|
||||
default.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>
|
||||
@ -576,7 +584,9 @@ the proper rights on the DVD device entry (in <CODE>/dev/</CODE>).
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>
|
||||
Where can I get libdvdread and libdvdcss packages?
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD>
|
||||
From the
|
||||
You don't need to. Use <B>libmpdvdkit</B>, which is present in MPlayer source, and used by
|
||||
default.
|
||||
Anyway, the packages mentioned can be get from the
|
||||
<A HREF="http://www.dtek.chalmers.se/groups/dvd">Ogle site</A>.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
@ -606,218 +616,8 @@ implement it, and send a patch. Don't ask for it.
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B> Where is the Windows version?
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's not released, and won't be. Look around the Windows scene (open source
|
||||
ASF parsers, open source ASF encoders, etc) and you'll know why. We don't
|
||||
want to go to jail.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
|
||||
<TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH="100%"><B>What card do you suggest me to buy?
|
||||
</B></TD><TR><TD></TD><TD VALIGN=top>A0:</TD><TD>It's for your information only but our criteria are:
|
||||
</TD><TR><TD></TD><TD VALIGN=top>A1:</TD><TD>Speed:<BR>
|
||||
This parameter can be computed easily:
|
||||
<OL>
|
||||
<LI>Which movies do you plan to watch?
|
||||
<UL>
|
||||
<LI><B>MPEG1:</B> 320x200@32=256000<BR>
|
||||
You need only 256*25fps=6.4MB/sec of bandwidth (This format can be played
|
||||
in real-time on any PC since the times of Pentium-100 + S3Virge).</LI>
|
||||
<LI><B>MPEG4:</B> 640x480@32=1228800<BR>
|
||||
You need a video bandwidth of 1.2*25fps=30MB/sec. To watch such a movie
|
||||
in real-time you need a PC equivalent to a Celeron-450 and a DIMM based
|
||||
video card.</LI>
|
||||
<LI><B>MPEG2 (aka DVD or SDTV):</B> 1024x768@32=3145728<BR>
|
||||
You need a video bandwidth of 3*30fps=90MB/sec. In extreme cases (if your
|
||||
video card supports IDCT decoding) the hardware requirements are the same
|
||||
as for MPEG4.</LI>
|
||||
<LI><B>HDTV (High Definition TeleVision):</B> 2000x2000@32=16000000<BR>
|
||||
You need a video bandwidth of 16*30fps=480MB/sec. You also need at least
|
||||
32MB of video memory to watch this stream: 16MB for the RGB area and 16MB
|
||||
for the YUV area.</LI>
|
||||
</UL>
|
||||
</LI>
|
||||
<LI>The bandwidth of PCI slots is: 33MHz*32Bit=133MB/sec. PCI2.1 has
|
||||
66MHz*32Bit=266MB/sec which is more than enough for playing any movie (except
|
||||
HDTV streams which really require an AGP bus).</LI>
|
||||
<LI>What memory type should be installed on the video card:
|
||||
<UL>
|
||||
<LI><B>SIMM</B> - Avoid that.</LI>
|
||||
<LI><B>DIMM</B> - Good if your video card has 128-bit memory access.</LI>
|
||||
<LI><B>DDR</B> - Is fast enough for all types.</LI>
|
||||
</UL>
|
||||
</LI>
|
||||
</OL>
|
||||
Note: DGA comparison shows that there is no visible difference between video
|
||||
cards which have the same type of video memory installed.<BR>
|
||||
<B>Conclusion:</B> If you have enough CPU power (Celeron-450 or K6-2-500) it
|
||||
should be enough to buy any video card which has at least 8MB of DIMM or DDR
|
||||
memory.
|
||||
</TD><TR><TD></TD><TD VALIGN=top>A2:</TD><TD>Quality:<BR>
|
||||
This question was investigated in depth at:
|
||||
<BR><A HREF="http://www.anandtech.com/showdoc.html?i=1332&rndr=04132002115140">
|
||||
AnandTech</a> - Video Card Roundup - DVD Quality, Features & Performance
|
||||
(October 2000)
|
||||
</TD><TR><TD></TD><TD VALIGN=top>A3:</TD><TD><B>Working</B> features under Linux:<BR>
|
||||
If you are a Win32 user then probably you have support (from driver and DirectX8
|
||||
side) for any feature your chip has.<BR>
|
||||
But for <B>Linux</B> users there are currently only a few vendors which have more
|
||||
or less advanced driver support:<BR><BR>
|
||||
|
||||
<TABLE BORDER=1 WIDTH="100%">
|
||||
<TR>
|
||||
<TD> </TD>
|
||||
|
||||
<TD>
|
||||
<CENTER>Matrox Gxxx</CENTER>
|
||||
</TD>
|
||||
|
||||
<TD>
|
||||
<CENTER>ATI m64/r128/radeon</CENTER>
|
||||
</TD>
|
||||
|
||||
<TD>
|
||||
<CENTER>nVidia tnt/geforce</CENTER>
|
||||
</TD>
|
||||
|
||||
<TD>
|
||||
<CENTER>S3 Virge/Savage</CENTER>
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>Driver's provider</TD>
|
||||
|
||||
<TD>OEM and enthusiasts</TD>
|
||||
|
||||
<TD>OEM and enthusiasts</TD>
|
||||
|
||||
<TD>OEM or enthusiasts</TD>
|
||||
|
||||
<TD>enthusiasts</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>Driver's quality</TD>
|
||||
|
||||
<TD>best (X11,kernel)</TD>
|
||||
|
||||
<TD>best (X11,GATOS,kernel)</TD>
|
||||
|
||||
<TD>buggy/unstable (X11 only)</TD>
|
||||
|
||||
<TD>slow (X11 only)</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>VIDEO OVERLAY</TD>
|
||||
|
||||
<TD></TD>
|
||||
|
||||
<TD></TD>
|
||||
|
||||
<TD></TD>
|
||||
|
||||
<TD></TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>BES and YV2RGB</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>scaling filters</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>adaptive deinterlace</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>Video equalizer (hue, contrast, saturation, color correction)</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>GeForce only</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>Alpha blending, color and video keys</TD>
|
||||
|
||||
<TD>PARTIAL</TD>
|
||||
|
||||
<TD>PARTIAL (under development)</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>Video capture</TD>
|
||||
|
||||
<TD>YES (Marvel)</TD>
|
||||
|
||||
<TD>YES (GATOS)</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD>TV-out</TD>
|
||||
|
||||
<TD>G400 only</TD>
|
||||
|
||||
<TD>YES</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
|
||||
<TD>N/A</TD>
|
||||
</TR>
|
||||
</TABLE>
|
||||
|
||||
<P>It's a very rough overview of video cards. We should pay attention to video
|
||||
card models. If for example Matrox G400 drivers support TV-out then G450 and
|
||||
G550 do not necessarily have this feature.<BR>
|
||||
Another example: Adaptive deinterlacing exists only for the Rage128 chip and
|
||||
isn't present on Mach64+ ones. The same goes for 3D features. They are different
|
||||
from Mach64 to the Radeon 8500 with TRUFORM technology.</P>
|
||||
|
||||
<P><B>ANYWAY - THE MPLAYER TEAM DOESN'T ACCEPT ANY CLAIMS IF AFTER READING THIS
|
||||
MATERIAL YOU BUY A CARD WHICH IS UNSATISFACTORY FOR YOU!!! THIS IS ONLY OUR
|
||||
POINT OF VIEW.</B></P>
|
||||
|
||||
<P><B>Q:</B> If a PCI slot is fast enough for most types of movies then why is
|
||||
the S3 Virge too slow for them?<BR>
|
||||
<B>A:</B> Due to its SIMM memory.</P>
|
||||
|
||||
want to go to jail. BTW you can compile it yourself, under
|
||||
<A HREF="documentation.html#6.8">Cygwin</A>.
|
||||
</TD><TR><TD COLSPAN=3> </TD><TR>
|
||||
|
||||
<TD COLSPAN=3>
|
||||
|
||||
@ -136,9 +136,9 @@ the video and audio streams in these files are real MPG and AAC files. With the
|
||||
<CODE>-dumpvideo</CODE> and <CODE>-dumpaudio</CODE> options you can even extract them!).</P>
|
||||
|
||||
<P><B>Codecs</B>: Any codec is allowed, both CBR and VBR. Note: most new QuickTime files use
|
||||
<B>Sorensen</B> video and QDesign Music audio. These formats have not been
|
||||
disclosed and will probably remain so in the future, making Apple's QuickTime
|
||||
player the only player able to play these files (on Windows/Mac OS only).</P>
|
||||
<B>Sorenson</B> video and QDesign Music audio. See our
|
||||
<A HREF="codecs.html#2.2.1.10">Sorenson</A> codec section. QDesign Music
|
||||
audio currently can't be played.</P>
|
||||
|
||||
|
||||
<P><B><A NAME=2.1.1.5>2.1.1.5. VIVO files</A></B></P>
|
||||
|
||||
@ -22,7 +22,7 @@ contains these drivers:</P>
|
||||
<TR><TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD>SDL driver (supports up/downsampling, <B>ESD</B>, <B>ARTS</B> etc)</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top>nas</TD><TD></TD><TD>NAS (Network Audio System) driver</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top>alsa5</TD><TD></TD><TD>native ALSA 0.5 driver</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top>alsa9</TD><TD></TD><TD>native ALSA 0.9 driver (works, but has problems -> use OSS) (supports hardware AC3 passthrough)</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top>alsa9</TD><TD></TD><TD>native ALSA 0.9 driver (supports hardware AC3 passthrough)</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top>sun</TD><TD></TD><TD>SUN audio driver (<CODE>/dev/audio</CODE>) for BSD and Solaris8 users</TD></TR>
|
||||
<TR><TD></TD><TD VALIGN=top>arts</TD><TD></TD><TD>native ARTS driver (mostly for KDE users)</TD></TR>
|
||||
|
||||
@ -43,7 +43,7 @@ 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 are problems like lost sync and disappearing audio.</LI>
|
||||
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
|
||||
|
||||
@ -63,6 +63,11 @@ flag to configure. Remember that you are on your own and <B>do not report any
|
||||
bugs</B>. If you do, you will only get banned from our mailing list because
|
||||
we have had more than enough flame wars over GCC 2.96. Please let the matter rest.</P>
|
||||
|
||||
<P><B>gcc 3.0.4-RedHat update</B>: RedHat managed to break gcc again, this
|
||||
time the victim is 3.0.4 . It may fail with internal compiler error when
|
||||
compiling with GUI support. DO NOT REPORT THIS BUG TO US! Use 2.95.3 or
|
||||
a vanilla 3.0.4 compiled from source.</P>
|
||||
|
||||
<P>If you have problems with GCC 2.96, you can get 2.96-85 packages from the
|
||||
Red Hat <A HREF="ftp://updates.redhat.com">ftp server</A>, or just go for the
|
||||
3.0.4 packages offered for version 7.2 and later. You can also get gcc-3.1
|
||||
@ -102,11 +107,11 @@ which disallows binary redistribution. This code has been removed and you are no
|
||||
welcome to create binary packages as you see fit.</P>
|
||||
|
||||
<P>Another impediment to binary redistribution was compiletime optimizations
|
||||
for CPU architecture. <B>MPlayer</B> now supports runtime CPU detection.
|
||||
Although this implies a small speed sacrifice, it is now possible to create
|
||||
binaries that run on different members of the Intel CPU family. For optimum
|
||||
performance you may wish to disable runtime CPU detection before compilation
|
||||
(<CODE>configure --disable-runtime-cpudetection</CODE>).</P>
|
||||
for CPU architecture. <B>MPlayer</B> now supports runtime CPU detection
|
||||
(specify the <CODE>--enable-runtime-cpudetection</CODE> option when
|
||||
compiling). It is disabled by default because it implies a small speed
|
||||
sacrifice, it is now possible to create binaries that run on different
|
||||
members of the Intel CPU family.</P>
|
||||
|
||||
<P><A NAME=nvidia><B>nVidia</B></A></P>
|
||||
|
||||
|
||||
133
DOCS/video.html
133
DOCS/video.html
@ -430,7 +430,7 @@ also help. Thanks!</P>
|
||||
|
||||
<P><B><A NAME=2.3.1.4>2.3.1.4. SDL</A></B></P>
|
||||
|
||||
<P>SDL (Simple Directmedia Layer) is basically an unified video/audio
|
||||
<P>SDL (Simple Directmedia Layer) is basically a unified video/audio
|
||||
interface. Programs that use it know only about SDL, and not about what video
|
||||
or audio driver does SDL actually use. For example a Doom port using SDL can
|
||||
run on svgalib, aalib, X, fbdev, and others, you only have to specify the
|
||||
@ -687,9 +687,9 @@ See <A HREF="http://aa-project.sourceforge.net/tune/">http://aa-project.sourcefo
|
||||
|
||||
<P><B><A NAME=2.3.1.12>2.3.1.12. VESA - output to VESA BIOS</A></B></P>
|
||||
<P>
|
||||
This driver was designed and introduced as <B>generic driver</B> for any video
|
||||
card which has VESA VBE 2.0 compatible BIOS. But exists still one reason of
|
||||
developing of this driver - it's multiple troubles with displaying movie on TV.<BR>
|
||||
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>
|
||||
@ -724,19 +724,15 @@ at least.)
|
||||
- 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>
|
||||
- Most important :) You can watch <B>DVD at 320x200</B> if you don't have a powerful CPU.<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 minuses:</B><BR>
|
||||
- It works only on <B>x86 systems</B>.<BR>
|
||||
- <B>It's the slowest driver</B> from all the available ones for MPlayer.<BR>
|
||||
(But only if your card doesn't support <B>DGA mode</B> - otherwise this
|
||||
driver is comparable by speed with <B>-vo dga</B> and <B>-vo fbdev</B> ones.<BR>
|
||||
|
||||
- It can be used only by <B>ROOT</B>.<BR>
|
||||
- Currently it's available only for <B>Linux</B>.<BR>
|
||||
- It <B>doesn't use</B> any <B>hardware accelerations</B> (like YUV overlay or hw scaling).<BR>
|
||||
</P>
|
||||
|
||||
<P>Don't use this driver with <B>GCC 2.96</B> ! It won't work !</P>
|
||||
@ -799,48 +795,23 @@ drivers can't use low pixelclocks that are needed for low resolution
|
||||
video modes.</P>
|
||||
|
||||
|
||||
<P><B><A NAME=2.3.1.14>2.3.1.14. Rage128 (Pro) / Radeon video overlay (radeon_vid)</A></B></P>
|
||||
|
||||
<P>This section is OBSOLETED ! Use Vidix !</P>
|
||||
|
||||
|
||||
<P><B><A NAME=2.3.1.15>2.3.1.15. VIDIX</A></B></P>
|
||||
<P><B><A NAME=2.3.1.15>2.3.1.15. Vidix</A></B></P>
|
||||
|
||||
<P><B>WHAT IS VIDIX?</B></P>
|
||||
|
||||
<P>VIDIX is the abbreviation for <B>VID</B>eo <B>I</B>nterface for
|
||||
*ni<B>X</B>.<BR>
|
||||
VIDIX was designed and introduced as an interface for fast user-space drivers
|
||||
providing <B>DGA</B> everywhere where it's possible (<B>unlike X11</B>). I
|
||||
hope that these drivers will be as portable as X11 (<B>not only on
|
||||
*nix</B>).<BR>
|
||||
What it is:</P>
|
||||
|
||||
<UL>
|
||||
<LI>It's a portable successor of mga_vid technology, but it's located in
|
||||
user-space.</LI>
|
||||
<LI>Unlike X11 it provides DGA everywhere it's possible</LI>
|
||||
<LI>Unlike v4l it provides interface for video playback</LI>
|
||||
<LI>Unlike linux's drivers it uses mathematics library</LI>
|
||||
</UL>
|
||||
|
||||
<P>I can tell you in bold capital letters :<BR>
|
||||
<B>VIDIX PROVIDES DIRECT GRAPHICS ACCESS TO BES YUV MEMORY.</B>
|
||||
</P>
|
||||
|
||||
<P><I>Well (it's in my todo) - implement DGA to MPEG2 decoder.</I></P>
|
||||
providing such video performance as mga_vid does for Matrox cards. It's
|
||||
also very portable.</P>
|
||||
|
||||
<P>This interface was designed as an attempt to fit existing video acceleration
|
||||
interfaces (known as mga_vid, mga_yuv, radeon_vid) into a fixed scheme. It
|
||||
interfaces (known as mga_vid, rage128_vid, radeon_vid, pm3_vid) into a fixed scheme. It
|
||||
provides highlevel interface to chips which are known as BES (BackEnd
|
||||
scalers) or OV (Video Overlays). It doesn't provide lowlevel interface to
|
||||
things which are known as graphics servers. (I don't want to compete with X11
|
||||
team in graphics mode switching). I.e. main goal of this interface is to
|
||||
provide maximal speed of video playback but not putting video signal on
|
||||
screen of your TV or on tape of your VCR. Although these things are also very
|
||||
significant - it's perfectly other task. (However I guess that it would be
|
||||
possible to implement something like mini-X (don't mix it with Minix ;) in
|
||||
the future, if some number of volunteers will be found.
|
||||
maximize the speed of video playback.
|
||||
</P>
|
||||
|
||||
<P><B>USAGE</B></P>
|
||||
@ -851,7 +822,7 @@ video modes.</P>
|
||||
requires XServer and can work only under XServer.</LI>
|
||||
<LI>You can use VIDIX subdevice which was applied to several video output
|
||||
drivers, such as:<BR>
|
||||
<CODE>-vo vesa:vidix</CODE> and <CODE>-vo fbdev:vidix</CODE></LI>
|
||||
<CODE>-vo vesa:vidix</CODE> (<B>LINUX ONLY</B>) and <CODE>-vo fbdev:vidix</CODE></LI>
|
||||
</UL>
|
||||
Indeed it doesn't matter which video output driver is used with <B>VIDIX</B>.
|
||||
|
||||
@ -1064,80 +1035,28 @@ Some remarks:
|
||||
<P><B><A NAME=2.3.1.A.2>2.3.1.A.2. ATI cards</A></B></P>
|
||||
|
||||
<P>
|
||||
<B>A few word about ATI's TV-out:</B><BR>
|
||||
Currently ATI doesn't want to support any of its TV-out chips under Linux.
|
||||
Below is official answer from ATI Inc.:
|
||||
<B><U>PREAMBLE</U></B><BR>
|
||||
Currently ATI doesn't want to support any of its TV-out chips under Linux,
|
||||
because their licensed Macrovision technology.</P>
|
||||
|
||||
<P>
|
||||
<code>
|
||||
<I>
|
||||
<BR>> Hello!
|
||||
<BR>>
|
||||
<BR>> On your pages you wrote that you support linux developers.
|
||||
<BR>> Currently I participate with mplayer project (www.mplayerhq.hu)
|
||||
<BR>> I'm interesting with enabling TV-out on Radeon VE chips during
|
||||
<BR>> movie playback. I would be glad to add this feature to radeonfb driver
|
||||
<BR>> (which can be found in CVS tree of mplayer project at main/drivers/radeon).
|
||||
<BR>> Do I have a chance to get any official technical documenation?
|
||||
</I>
|
||||
<BR>We will not provide TV out related documents due to macrovision concerns.
|
||||
<BR>Also mpeg2 decoding is something that we MAY consider in the future but not
|
||||
<BR>at this current time. This is again due to proprietary and 3rd party
|
||||
<BR>information.
|
||||
</code>
|
||||
</P>
|
||||
<P><B><U>ATI CARDS TV-OUT STATUS ON LINUX</U></B></P>
|
||||
|
||||
<P>Pity isn't?</P>
|
||||
|
||||
<P>
|
||||
<code>
|
||||
<B>Q:What is Macrovision?</B><BR>
|
||||
A:It's copy protection mechanism.</code>
|
||||
</P>
|
||||
|
||||
<P>It means that if they open any TV-out related information then
|
||||
hackers will be able to disable copy protection on their chips. Therefore
|
||||
we have no chance to get working TV-out on ATI.</P>
|
||||
|
||||
What's status of ATI's tv-out chips under Linux:
|
||||
<UL>
|
||||
<LI><B>ATI Mach64</B> has <I>ImpacTV</I> which is supported by <A HREF="http://gatos.sf.net">gatos</A>.</LI>
|
||||
<LI><B>ASIC Radeon VIVO</B> has <I>Rage Theatre</I> which is supported by <A HREF="http://gatos.sf.net">gatos</A>.</LI>
|
||||
<LI><B>Radeon VE</B> and <B>Rage PRO LT</B> have <I>ImpacTV2+</I> which is not supported under Linux.
|
||||
But with <B>MPlayer</B> you get <B>full hardware acceleration</B> and <B>TV out</B>
|
||||
for Radeons !
|
||||
Check <a href="#2.3.1.12">VESA driver</a> and <A HREF="#2.3.1.14">Radeon
|
||||
acceleration</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="#2.3.1.12">VESA driver</a> and <A HREF="#2.3.1.15">Vidix</A>
|
||||
sections.</LI>
|
||||
</UL>
|
||||
|
||||
<P>
|
||||
Fortunately, owners of fast enough CPUs (Duron, Celeron2 and better) <B>can watch
|
||||
movies on their TV</B> through <a href="#2.3.1.12">VESA drivers</a>.
|
||||
On other cards, just use the <a href="#2.3.1.12">VESA driver</a>, without
|
||||
Vidix. Powerful CPU is needed, though.
|
||||
</P>
|
||||
|
||||
<P>
|
||||
I should say good words to ATI Inc. too:<BR>
|
||||
<B>they produce top quality BIOSes.</B>
|
||||
</P>
|
||||
|
||||
<P>
|
||||
<B>VESA drivers</B> don't use any hardware acceleration but it simulates
|
||||
<B>DGA</B> through 64K window, which is configured through 32-bit mode
|
||||
functions of BIOS. ATI cards have enough <B>fast video memory</B> (DIMM or DDR
|
||||
chips with 64 - 128-bit access) so it's not bottleneck for them. There are no
|
||||
limitations on which video mode can be displayed on your TV (like on other
|
||||
cards) so you can use <B>any video mode</B> on your <B>TV</B> (from
|
||||
<B>320x200</B> up to <B>1024x768</B>).<BR>
|
||||
From other side (it's known at least for <B>Radeons</B>) there is <B>DGA</B>
|
||||
mode which is detected automatically and in this case you'll get comparable
|
||||
with <B>-vo dga</B> and <B>-vo fbdev</B> drivers speed.<BR>
|
||||
Only thing you need to do - <B>have TV connector plugged in before booting your
|
||||
PC</B> since video BIOS initializes itself only once during POST procedure.
|
||||
</P>
|
||||
|
||||
<P>
|
||||
For detail see <a href="video.html#2.3.1.12">VESA</a> sections of this
|
||||
documentation.
|
||||
<P>Only thing you need to do - <B>have TV connector plugged in before
|
||||
booting your PC</B> since video BIOS initializes itself only once during
|
||||
POST procedure.
|
||||
</P>
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user