See http://www.mplayerhq.hu/DOCS/codecs-status.html for the complete, daily generated list!!!
-The most important ones above all:
+
The most important ones above all:
If you have a Win32 codec not listed here, and not supported yet, just read the codec importing to get info about how to help us adding support +
If you have a Win32 codec not listed here which is not supported yet, please read the +codec importing HOWTO and help us add support for it!
This section contains information about the DivX4 codec of -ProjectMayo. Their first available alpha version was the OpenDivX 4.0 +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. We used to use its postprocessing code to optionally enhance visual +default. Earlier, we used its postprocessing code to optionally enhance visual quality of MPEG1/2 movies. Now we use our own.
-The new generation of this codec can even decode movies made with the -infamous DivX codec! And it's not everything, it's MUCH faster than the -traditional Win32 DivX DLL's (note that libavcodec's decoder is EVEN FASTER, -so the usage of this codec is DISCOURAGED - you need it only for -encoding). See below for configuration. The only disadvantage of this codec is -that it's currently closed-source. :(
- -The codec can be downloaded from the following URL:
- -http://avifile.sourceforge.net
+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 DISCOURAGED. However, it is useful for +encoding. One disadvantage of this codec is that it is currently closed source.
-If it doesn't work, try :
+The codec can be downloaded from one of the following URLs:
- + http://avifile.sourceforge.net
+ http://divx.com
Unpack it, and run ./install.sh as root.
Note: do NOT forget to add /usr/local/lib to your
-/etc/ld.so.conf and running ldconfig !
Note: Do NOT forget adding /usr/local/lib to your
+/etc/ld.so.conf and running ldconfig!
MPlayer autodetects if DivX4/DivX5 is (properly) installed, just -compile as usual. If it doesn't detect it, you didn't install it exactly as -above, and/or has messed up config (see last question of 5.1 section).
- -Using it is a bit tricky. As it conflicts with the old OpenDivX (its API is -very similar to OpenDivX's), OpenDivX code is disabled, and this (DivX4) -codec will be used to decode old OpenDivX movies.
- -Generally we can pinpoint this issue to that you have two options to use -this codec:
- -| -vc odivx | - | using the codec as a new version of OpenDivX. -in this case it produces YV12 image in its own buffer, -and MPlayer (libvo) does colorspace conversion. (RECOMMENDED!) | |
| -vc divx4 | - | using the codec's colorspace conversion. -in this mode, you can use YUY2/UYVY too. |
MPlayer 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.
+ +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:
+ +-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 'odivx' method is usually faster, due to the fact that it transfers +
The -vc odivx 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 'divx4'
-method. For RGB modes you can choose freely, their speed is same, maybe
-differ according to the current bpp.
-vc divx4
+method. For RGB modes the speed is the same, differing at best
+according to your current color depth.
-NOTE: If your -vo driver supports direct rendering, then -vc divx4 may be +
NOTE: If your -vo driver supports direct rendering, then -vc divx4 may be
faster, or even the fastest solution.
Note: OLD OpenDivX supports postprocessing too (use option
- -oldpp to enable using it), but range of values is strange:
Note: OLD OpenDivX supports postprocessing via the
+ -oldpp option, but the range of values is strange:
| 0 | - | no postproc | |
| 10 .. 20 | -postprocessing, normal (like level 2 with divxds) | ||
| 30 .. 60 | -hard prostprocessing, eats many CPU (like level 4 with divxds | ||
2.2.1.2. ffmpeg's DivX/libavcodec
- -Beginning with version 0.4.2 , -ffmpeg contains an -opensource DivX codec, which is compatible with the traditional DivX. -MPlayer supports this codec, and this makes it possible to watch -DivX/DivX4/DivX5 movies on non-x86 platforms, and gain much faster -DivX/DivX4/DivX5 decoding speed than the Win32 codecs and the original -DivX4 library has!
+| 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
+ +Beginning with version 0.4.2, +FFmpeg contains an +open source DivX codec, which is compatible with the traditional DivX. +MPlayer supports this codec, making it possible to watch +DivX/DivX4/DivX5 movies on non-x86 platforms. Furthermore it offers higher +DivX/DivX4/DivX5 decoding speed than the Win32 codecs or the original +DivX4 library!
-It also contains lots of nice codecs, such as RealVideo 1.0, MJPEG, h263, +
It also contains a lot of nice codecs, such as RealVideo 1.0, MJPEG, h263, h263+, etc.
-If you use MPlayer +
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 +libavcodec from the FFmpeg CVS tree as FFmpeg 0.4.5 does not work with +MPlayer. In order to achieve this do:
+ +cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg logincvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg co ffmpeglibavcodec directory from the FFmpeg sources to the
+ root of the MPlayer CVS tree. It should look like this:
+ main/libavcodec
- cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg login
- cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg co ffmpeg
-
Note: if you copy with CVS subdirs, next time it's enough to do -'cvs update'.
-Now, move the newly downloaded ffmpeg source's libavcodec directory, -(with all it's subdirectories) to MPlayer's tree, so it will look -like this:
- main/libavcodec
The codec also supports postprocessing!
-Symlinking is NOT enough, you have to copy/move it!!!
- -Then compile. configure detects if it's alright, and can be compiled. The -codec also supports postprocessing!
- -With ffmpeg and my Matrox G400, I can view even the highest resolution DivX - movies on my K6/2 500, without dropped frames.
+With FFmpeg and my Matrox G400, I can view even the highest resolution DivX + movies without dropped frames on my K6/2 500.
-Foreword: +
Foreword:
Be advised that the XAnim binary codecs are packaged with a piece of text
-claiming to be a legally binding software license which, among other
-absurdities, forbids the user to use the codecs in conjunction with any
-program other than XAnim. As the XAnim author has yet to bring legal
-action against anyone for codec-related issues, the MPlayer developers
-don't lose too much sleep over this and you probably shouldn't, either.
+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.
So yes, MPlayer can use XAnim's codecs for decoding. It's very -easy to enable them:
+MPlayer is capable of employing the XAnim codecs for decoding. Follow +the instructions to enable them:
-
--with-xanimlibdir option to tell configure where
- it can find the xanim codecs. By default, it checks them at
+ --with-xanimlibdir option to tell configure where
+ to find the XAnim codecs. By default, it looks for them at
/usr/local/lib/xanim/mods, /usr/lib/xanim/mods and /usr/lib/xanim.
Alternatively you can set the environment variable XANIM_MOD_DIR to
- the dir of the XAnim codecs.vid_cvid.xa, vid_h263.xa, vid_iv50.xa
+ vid_cvid.xa, vid_h263.xa, vid_iv50.xa
They are video codec family number 10, so you may want to use -vfm 10
+
XAnim is video codec family number 10, so you may want to use the -vfm 10
option to tell MPlayer to use them if possible.
Tested codecs are: Indeo 3.2, 4.1, 5.0, CVID, 3ivX, h263.
+Tested codecs include: Indeo 3.2, 4.1, 5.0, CVID, 3ivX, h263.
MPlayer 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 -vc
-ffh263 option (default) (you'll need the newest libavcodec !). For 2.0 files, use
+ffh263 option (default) (requires up-to-date libavcodec). For 2.0 files, use
the ivvideo.dll Win32 DLL file (from here),
and install it under /usr/lib/win32 or wherever you store the
-Win32 codecs. This latter codec doesn't support YV12 nor YUY2 only BGR modes,
-thus usable only with the X11 and OpenGL outputs. Hopefully ffh263 will support
+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.
MPEG1 and MPEG2 are decoded with the native library libmpeg2. -Its source code is included in MPlayer, and of course it is multiplatform. +
MPEG1 and MPEG2 are decoded by the multiplatform native libmpeg2 library, +whose source code is included in MPlayer. We handle buggy MPEG 1/2 video files by catching sig11 (segmentation fault), -and quickly reinitializing the codec, and continue exactly from where the failure -did occur. -No speed decrease is measurable.
+and quickly reinitializing the codec, continuing exactly from where the failure +occurred. +This recovery technique has no measurable speed penalty. -This is a very old and very bad codec of Microsoft. In the past it was +
This is a very old and very bad codec from Microsoft. In the past it was
decoded with the msvidc32.dll Win32 codec, now we have our own
-open-source implementation (by Mike
+open source implementation (by Mike
Melanson).
MPlayer now has its own opensource, multiplatform Cinepak decoder. -Supports YUV outputs, thus hardware scaling if video output driver allows. -Used by default.
+MPlayer 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.
-Currently ONLY the RealVideo 1.0 (fourcc RV10) codec is supported, through -ffmpeg. Sadly, no new RealMedia files come with this one, only with the newer -RV20 and RV30 codecs which are closed-source. Their future support is -unlikely :(
+Currently only the RealVideo 1.0 (fourcc RV10) codec is supported through +FFmpeg. Sadly, new RealMedia files come with the newer and closed source RV20 and +RV30 codecs instead. Their future support is unlikely :(
-XViD is another development from good old OpenDivX (first +
XViD is another development from the OpenDivX group (their first development was DivX4).
-Advantages : +
Advantages:
Disadvantages : +
Disadvantages:
Installation : it's currently available only in CVS. Here are the
- downloading and installation instructions :
- cvs -z3 -d:pserver:anonymous@cvs.xvid.org:/xvid
- login
- cvs -z3 -d:pserver:anonymous@cvs.xvid.org:/xvid co
- xvidcore
- cd xvidcore/build/generic
- Edit Makefile.linux to fit your needs
- make -f Makefile.linux
- Get encore2.h and decore.h from Divx4linux package, and copy them to /usr/local/include/
- recompile MPlayer with
- --with-xvidcore=/path/to/libcore.a
-
Installation: It is currently available only from CVS. Here are the + download and installation instructions:
+cvs -z3 -d:pserver:anonymous@cvs.xvid.org:/xvid logincvs -z3 -d:pserver:anonymous@cvs.xvid.org:/xvid co xvidcorecd xvidcore/build/genericMakefile.linux to fit your needs.make -f Makefile.linuxencore2.h and decore.h from the DivX4Linux
+ package, and copy them to /usr/local/include/.--with-xvidcore=/path/to/libcore.a.The most important audio codecs above all :
+
The most important audio codecs above all:
2.2.2.1. Software AC3 decoding
This is the default decoder used for files with AC3 audio.
-The AC3 decoder can create output audio mixes for 2, 4, or 6 +
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 soundcard driver, -allowing the full "surround sound" experience without the external AC3 +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.
Use the -channels option to select the number of output channels.
Use -channels 2 for a stereo downmix. For a 4 channel downmix (Left
Front, Right Front, Left Surround and Right Surround outputs), use
--channels 4. In this case, any Centre channel will be mixed
-equally to the front channels. Lastly, "-channels 6" will output all the AC3
+-channels 4. In this case, any center channel will be mixed
+equally to the front channels. -channels 6 will output all the AC3
channels as they are encoded - in the order Left, Right, Left Surround, Right
-Surround, Centre and LFE.
The default number of output channels is 2.
-To use more than 2 output channels, you'll need to be using OSS, -and to have a soundcard driver that supports the appropriate number of -output channels via the SNDCTL_DSP_CHANNELS ioctl. For example, a -version of the emu10k1 driver (used with the SB Live cards) newer than -August 2001 should be suitable (I heard newest ALSA CVS supports this too).
+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).
2.2.2.2. Hardware AC3 decoding
-You'll need an AC3 capable soundcard, with digital out (SP/DIF). The -card's driver must properly support the AFMT_AC3 format (like C-Media does). -Connect your AC3 decoder to the SP/DIF output, and use the '-ac hwac3' -option. It may or may not work (experimental). It will work with C-Media -cards, and with SB Live! + ALSA driver. It won't work with Live!'s OSS -driver!
+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 -ac hwac3
+option. It is experimental but known to work with C-Media cards and Soundblaster
+Live! + ALSA (but not OSS) drivers.
libmad is a multiplatform MPEG audio -decoding library. If you don't know why is it good, you probably don't need it.
- -It doesn't handle broken files well, and sometimes has problems with seeking.
+decoding library. It does not handle broken files well, and it sometimes has +problems with seeking.To enable support, compile with the --enable-mad configure
option.
The audio codec used in VIVO files depends on whether it's a VIVO/1.0 or +
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 g.723 audio, and VIVO/2.0 files
-have Vivo Siren. Both is supported. You can grab the g.723/Siren
+have Vivo Siren audio. Both are supported. You can grab the g.723/Siren
Win32 DLL from
here,
-then copy it into the /usr/lib/win32 directory, or respectively.
/usr/lib/win32 directory.
-Currently the only supported one is the DNET codec. Actually it's a -low-bitrate version of the well-known AC3 codec. It can be found either in +
Currently the only supported one is the DNET codec. Actually it is a +low-bitrate version of the well known AC3 codec. It can be found in both old and new RealMedia movies.
-2.2.3. Win32 codec importing howto
+2.2.3. Win32 codec importing HOWTO
-VfW (Video for Windows) is the old Video API for Windows. Its codecs have +
VFW (Video for Windows) is the old Video API for Windows. Its codecs have the .DLL or (rarely) .DRV extension. -If MPlayer fails with your AVI:
+If MPlayer fails at playing your AVI with this kind of message: UNKNOWN video codec: HFYU (0x55594648)
It means your AVI is encoded with a codec which has the HFYU fourcc (HFYU = -HuffYUV codec, DIV3 = DivX Low Motion, etc...). Now that we know this, we'll +HuffYUV codec, DIV3 = DivX Low Motion, etc...). Now that you know this, you have to find out which DLL Windows loads in order to play this file. In our -case, the system.ini contains this (with many others):
+case, thesystem.ini contains this information in a line that reads:
VIDC.HFYU=huffyuv.dll
So we'll need the huffyuv.dll file. Note that the audio codecs are specified -with the MSACM prefix:
+So you need the huffyuv.dll file. Note that the audio codecs are
+specified by the MSACM prefix:
msacm.l3acm=L3codeca.acm
This is the MP3 codec. -So, now we have all the info needed (fourcc, codec file, sample AVI), submit -your codec support request in mail, and upload these files to the FTP:
+Now that you have all the necessary information (fourcc, codec file, sample AVI), +submit your codec support request by mail, and upload these files to the FTP site: ftp://ftp.mplayerhq.hu/MPlayer/incoming/[codecname]/
DirectShow is the newer Video API, which is even worse than its predecessor. -Things are harder with DirectShow, since +Things are harder with DirectShow, since
system.ini does not contain the needed information, instead it
+is stored in the registry and
+So let's search that goddamn registry.. +
Take a deep breath and start searching the registry...
NOTE: if searching fails, try to enable all the checkboxes.. you may have -false hits, but maybe you'll have the right, too...
-NOTE: dump that M$ shit.
- - -So, now we have all the info needed (fourcc, GUID, codec file, sample AVI),
-submit your codec support request in mail, and upload these files to the FTP:
-ftp://ftp.mplayerhq.hu/MPlayer/incoming/[codecname]/
regedit.
+Ctrl-f, disable the first two checkboxes, and enable the
+third. Type in the fourcc of the codec (e.g. TM20).
+C:\WINDOWS\SYSTEM\TM20DEC.AX).
+NOTE: If searching fails, try enabling all the checkboxes. You may have +false hits, but you may get lucky...
+ +Now that you have all the necessary information (fourcc, GUID, codec file, +sample AVI), submit your codec support request by mail, and upload these files +to the FTP site:
+ + ftp://ftp.mplayerhq.hu/MPlayer/incoming/[codecname]/