The most important ones above all:
This section contains information about the DivX4 codec of Project Mayo. Their first available alpha version was OpenDivX 4.0 -alpha 47 and 48. Support for this was/is included in MPlayer, and built by -default. Earlier, we used its postprocessing code to optionally enhance visual -quality of MPEG1/2 movies. Now we use our own.
+alpha 47 and 48. Support for this was included in MPlayer 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.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 @@ compile as usual. If it does not detect it, you did not install or configure it correctly.
-DivX4Linux conflicts with the old OpenDivX because their APIs are similar but -incompatible. Therefore you can only have one of them compiled into MPlayer -at a time.
- -DivX4Linux offers an OpenDivX compatibility mode such that you may choose from -the following options when using this codec:
+DivX4Linux works in two modes:
-vc odivx | Uses the codec in OpenDivX fashion. In this case it produces YV12 images in its own buffer, and MPlayer does colorspace -conversion via libvo. (RECOMMENDED!) | ||
-vc divx4 | Uses the colorspace conversion of the codec. -In this mode you can use YUY2/UYVY, too. |
The -vc odivx method is usually faster, due to the fact that it transfers
@@ -89,18 +88,6 @@
NOTE: If your -vo driver supports direct rendering, then -vc divx4 may be
faster, or even the fastest solution.
Note: OLD OpenDivX supports postprocessing via the
- -oldpp option, but the range of values is strange:
| 0 | - | no postprocessing | |
| 10 .. 20 | -normal postprocessing (like level 2 with divxds) | ||
| 30 .. 60 | -hard postprocessing, CPU intensive (like level 4 with divxds) |
2.2.1.2. FFmpeg DivX/libavcodec
@@ -112,8 +99,8 @@ decoding speed than the Win32 codecs or the original DivX4 library! -It also contains a lot of nice codecs, such as RealVideo 1.0, MJPEG, h263, -h263+, etc.
+It also contains a lot of nice codecs, such as RealVideo 1.0, WMV7, + MJPEG, h263, h263+, etc.
If you use an MPlayer release you have libavcodec right in the package, just build as usual. If you use MPlayer from CVS you have to extract @@ -134,8 +121,6 @@ subdirectory, but it does NOT contain the source for libavcodec! You must follow the steps above to obtain the source for this library.
-The codec also supports postprocessing!
-With FFmpeg and my Matrox G400, I can view even the highest resolution DivX movies without dropped frames on my K6/2 500.
@@ -263,6 +248,24 @@ + + +Sorenson is a video codec developed by Apple. We are currently + able to decode the first version of it (SVQ1), with a native decoder.
+ +Advantages:
+Disadvantages:
+Installation: it's compiled and usable per default.
+ +The most important audio codecs above all:
"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 @@
MPlayer is a movie player for LINUX (runs on many other Unices, and non-x86 CPUs, see section 6). 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 VideoCD, SVCD, DVD, -3ivx, and even DivX movies too (and you don't need the avifile +3ivx, RealMedia, and DivX 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. MPlayer supports displaying through some hardware MPEG decoder boards, such as the DVB and MPlayer is under GPL v2 license.
-My player is rock solid playing damaged MPEG files (useful for some VCDs), +
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 -idx option, or
permanently with MEncoder, thus enabling seeking!
As you see, stability and quality are the most important things,
but the speed is also amazing.
MPlayer can read from stdin (NOT named pipes). This can be for example used to play from FTP:
-wget ftp://micorsops.com/something.avi -O - | mplayer -
wget ftp://micorsops.com/something.avi -O - | mplayer -
Note: it's also recommended to enable CACHE when playback from network:
-wget ftp://micorsops.com/something.avi -O - | mplayer -cache 8192 -
wget ftp://micorsops.com/something.avi -O - | mplayer -cache 8192 -
4. FAQ section
@@ -1585,23 +1590,23 @@(... mplayer detects hardware/software, builds itself and.. ) -dpkg-deb: building package `mplayer' in `../mplayer_0.18-1_i386.deb'.
+dpkg-deb: building package `mplayer' in `../mplayer_0.90-1_i386.deb'.And now just become root, and:
- dpkg -i ../mplayer_0.18-1_i386.deb as root. + dpkg -i ../mplayer_0.90-1_i386.deb as root.
Here's how it looks like:
- 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) ...diff -r f98313dcd428 -r 4b7d097a9c69 DOCS/encoding.html --- a/DOCS/encoding.html Thu Jun 27 23:48:53 2002 +0000 +++ b/DOCS/encoding.html Fri Jun 28 06:07:46 2002 +0000 @@ -18,7 +18,7 @@ (AVI/ASF/OGG/DVD/VCD/VOB/MPG/MOV/VIV/FLI/RM/NUV/NET) to other MPlayer-playable formats (see below). It can encode with various codecs, like DivX4 (1 or 2 passes), libavcodec, PCM/MP3/VBRMP3 audio. Also has -stream copying and video resizing abilities. +powerful plugin system for video manipulation. @@ -29,8 +29,8 @@ and have them PROPERLY installed. You need them if you want DivX4 (1/2 pass) encoding.
-vo null and then
-vo ... and check the difference to see the video_out speed.
+/usr/lib/win32/ ...
@@ -334,7 +337,7 @@
and vice versa.
-bps or -nobps option. If it does not improve,
read this and upload the file to FTP.
./configure --enable-runtime-cpudetection). Don't
+use MPlayer on a CPU different from the one it was compiled on,
+without using the feature mentioned just now.
| - - |
- |
-
-
- |
-
-
- |
-
-
- |
-
| Driver's provider | - -OEM and enthusiasts | - -OEM and enthusiasts | - -OEM or enthusiasts | - -enthusiasts | -
| Driver's quality | - -best (X11,kernel) | - -best (X11,GATOS,kernel) | - -buggy/unstable (X11 only) | - -slow (X11 only) | -
| VIDEO OVERLAY | - -- - | - - | - - | - |
| BES and YV2RGB | - -YES | - -YES | - -YES | - -YES | -
| scaling filters | - -N/A | - -YES | - -N/A | - -N/A | -
| adaptive deinterlace | - -N/A | - -YES | - -N/A | - -N/A | -
| Video equalizer (hue, contrast, saturation, color correction) | - -YES | - -YES | - -GeForce only | - -N/A | -
| Alpha blending, color and video keys | - -PARTIAL | - -PARTIAL (under development) | - -N/A | - -N/A | -
| Video capture | - -YES (Marvel) | - -YES (GATOS) | - -N/A | - -N/A | -
| TV-out | - -G400 only | - -YES | - -N/A | - -N/A | -
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.
-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.
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.
- -Q: If a PCI slot is fast enough for most types of movies then why is
-the S3 Virge too slow for them?
-A: Due to its SIMM memory.
-dumpvideo and -dumpaudio options you can even extract them!).
Codecs: Any codec is allowed, both CBR and VBR. Note: most new QuickTime files use -Sorensen 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).
+Sorenson video and QDesign Music audio. See our +Sorenson codec section. QDesign Music +audio currently can't be played. diff -r f98313dcd428 -r 4b7d097a9c69 DOCS/sound.html --- a/DOCS/sound.html Thu Jun 27 23:48:53 2002 +0000 +++ b/DOCS/sound.html Fri Jun 28 06:07:46 2002 +0000 @@ -22,7 +22,7 @@/dev/audio) for BSD and Solaris8 usersDEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer!-ao oss and
-ao sdl. You can also use -ao alsa9. It works, but
-there are problems like lost sync and disappearing audio.On Solaris/FreeBSD systems, use the SUN audio driver with the diff -r f98313dcd428 -r 4b7d097a9c69 DOCS/users_against_developers.html --- a/DOCS/users_against_developers.html Thu Jun 27 23:48:53 2002 +0000 +++ b/DOCS/users_against_developers.html Fri Jun 28 06:07:46 2002 +0000 @@ -63,6 +63,11 @@ bugs. 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.
+gcc 3.0.4-RedHat update: 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.
+If you have problems with GCC 2.96, you can get 2.96-85 packages from the Red Hat ftp server, 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 @@ welcome to create binary packages as you see fit.
Another impediment to binary redistribution was compiletime optimizations
-for CPU architecture. MPlayer 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
-(configure --disable-runtime-cpudetection).
--enable-runtime-cpudetection 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.
diff -r f98313dcd428 -r 4b7d097a9c69 DOCS/video.html
--- a/DOCS/video.html Thu Jun 27 23:48:53 2002 +0000
+++ b/DOCS/video.html Fri Jun 28 06:07:46 2002 +0000
@@ -430,7 +430,7 @@
-SDL (Simple Directmedia Layer) is basically an unified video/audio +
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 @@
2.3.1.12. VESA - output to VESA BIOS
-This driver was designed and introduced as generic driver 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.
+This driver was designed and introduced as a generic driver 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.
VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998 (Page 70)
says:
What are minuses:
- It works only on x86 systems.
- - It's the slowest driver from all the available ones for MPlayer.
- (But only if your card doesn't support DGA mode - otherwise this
- driver is comparable by speed with -vo dga and -vo fbdev ones.
-
- It can be used only by ROOT.
- Currently it's available only for Linux.
- - It doesn't use any hardware accelerations (like YUV overlay or hw scaling).
Don't use this driver with GCC 2.96 ! It won't work !
@@ -799,48 +795,23 @@ video modes. -2.3.1.14. Rage128 (Pro) / Radeon video overlay (radeon_vid)
- -This section is OBSOLETED ! Use Vidix !
- - - +WHAT IS VIDIX?
VIDIX is the abbreviation for VIDeo Interface for
*niX.
VIDIX was designed and introduced as an interface for fast user-space drivers
- providing DGA everywhere where it's possible (unlike X11). I
- hope that these drivers will be as portable as X11 (not only on
- *nix).
- What it is:
I can tell you in bold capital letters :
- VIDIX PROVIDES DIRECT GRAPHICS ACCESS TO BES YUV MEMORY.
-
Well (it's in my todo) - implement DGA to MPEG2 decoder.
+ providing such video performance as mga_vid does for Matrox cards. It's + also very portable.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.
USAGE
@@ -851,7 +822,7 @@ requires XServer and can work only under XServer.-vo vesa:vidix and -vo fbdev:vidix-vo vesa:vidix (LINUX ONLY) and -vo fbdev:vidix
Indeed it doesn't matter which video output driver is used with VIDIX.
@@ -1064,80 +1035,28 @@
-A few word about ATI's TV-out:
-Currently ATI doesn't want to support any of its TV-out chips under Linux.
-Below is official answer from ATI Inc.:
+PREAMBLE
+Currently ATI doesn't want to support any of its TV-out chips under Linux,
+because their licensed Macrovision technology.
ATI CARDS TV-OUT STATUS ON LINUX
-
-
-
-
-
> Hello!
-
>
-
> On your pages you wrote that you support linux developers.
-
> Currently I participate with mplayer project (www.mplayerhq.hu)
-
> I'm interesting with enabling TV-out on Radeon VE chips during
-
> movie playback. I would be glad to add this feature to radeonfb driver
-
> (which can be found in CVS tree of mplayer project at main/drivers/radeon).
-
> Do I have a chance to get any official technical documenation?
-
-
We will not provide TV out related documents due to macrovision concerns.
-
Also mpeg2 decoding is something that we MAY consider in the future but not
-
at this current time. This is again due to proprietary and 3rd party
-
information.
-
Pity isn't?
- -
-
-Q:What is Macrovision?
-
-A:It's copy protection mechanism.
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.
- -What's status of ATI's tv-out chips under Linux:-Fortunately, owners of fast enough CPUs (Duron, Celeron2 and better) can watch -movies on their TV through VESA drivers. -
- -
-I should say good words to ATI Inc. too:
-they produce top quality BIOSes.
+ On other cards, just use the VESA driver, without
+ Vidix. Powerful CPU is needed, though.
-VESA drivers don't use any hardware acceleration but it simulates
-DGA through 64K window, which is configured through 32-bit mode
-functions of BIOS. ATI cards have enough fast video memory (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 any video mode on your TV (from
-320x200 up to 1024x768).
-From other side (it's known at least for Radeons) there is DGA
-mode which is detected automatically and in this case you'll get comparable
-with -vo dga and -vo fbdev drivers speed.
-Only thing you need to do - have TV connector plugged in before booting your
-PC since video BIOS initializes itself only once during POST procedure.
-
-For detail see VESA sections of this -documentation. +
Only thing you need to do - have TV connector plugged in before + booting your PC since video BIOS initializes itself only once during + POST procedure.