diff options
| author | gabucino <gabucino@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2003-10-11 07:58:55 +0000 |
|---|---|---|
| committer | gabucino <gabucino@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2003-10-11 07:58:55 +0000 |
| commit | 8e0b9bf8186078fa2704b0fa81958a91f709dec2 (patch) | |
| tree | 624d989db9c92a18645d9e39029e69f6df824dad /DOCS | |
| parent | 9dd5ee3afdd1db370c858a04be1b3b67bbb02755 (diff) | |
| download | mpv-8e0b9bf8186078fa2704b0fa81958a91f709dec2.tar.bz2 mpv-8e0b9bf8186078fa2704b0fa81958a91f709dec2.tar.xz | |
English HTML documentation retired (moved to Attic/)
Published in 2001 October 8 (MPlayer 0.50), it has spent 2 years in this form,
and has served its purpose very well.
- Thanks to LGB for starting the conversion from text
- Thanks to me for finishing it and doing further maintaining
- Thanks to Diego Biurrun for stepping in and giving great help in enhancing
and maintaining the documentation
- Thanks to the countless other people for sending patches and suggestions
Please drink 1 litre of cola in remembrance of the english HTML documentation.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@11076 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/en/bugreports.html | 291 | ||||
| -rw-r--r-- | DOCS/en/cd-dvd.html | 256 | ||||
| -rw-r--r-- | DOCS/en/codecs.html | 555 | ||||
| -rw-r--r-- | DOCS/en/documentation.html | 2130 | ||||
| -rw-r--r-- | DOCS/en/encoding.html | 374 | ||||
| -rw-r--r-- | DOCS/en/faq.html | 802 | ||||
| -rw-r--r-- | DOCS/en/formats.html | 320 | ||||
| -rw-r--r-- | DOCS/en/skin.html | 802 | ||||
| -rw-r--r-- | DOCS/en/sound.html | 854 | ||||
| -rw-r--r-- | DOCS/en/users_against_developers.html | 190 | ||||
| -rw-r--r-- | DOCS/en/video.html | 1595 |
11 files changed, 0 insertions, 8169 deletions
diff --git a/DOCS/en/bugreports.html b/DOCS/en/bugreports.html deleted file mode 100644 index 044e5f7789..0000000000 --- a/DOCS/en/bugreports.html +++ /dev/null @@ -1,291 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML> - -<HEAD> - <TITLE>Bug reporting - MPlayer - The Movie Player for Linux</TITLE> - <LINK REL="stylesheet" TYPE="text/css" HREF="../default.css"> - <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> -</HEAD> - -<BODY> - - -<H1><A NAME="appendix_b">Appendix B - How to report bugs</A></H1> - -<P>Good bug reports are a very valuable contribution to the development of any - software project. But just like writing good software, good problem reports - involve some work. Please realize that most developers are extremely busy and - receive obscene amounts of email. So while your feedback is crucial in - improving MPlayer and very much appreciated, please understand that you - have to provide <B>all</B> of the information we request and follow the - instructions in this document closely.</P> - - -<H2><A NAME="fix">B.1 How to fix bugs</A></H2> - -<P>If you feel have the necessary skills you are invited to have a go at fixing - the bug yourself. Or maybe you already did that? Please read - <A HREF="../tech/patches.txt">this short document</A> to find out how to get - your code included in MPlayer. The people on the - <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng">mplayer-dev-eng</A> - mailing list will assist you if you have questions.</P> - - -<H2><A NAME="report">B.2 How to report bugs</A></H2> - -<P>First of all please try the latest CVS version of MPlayer as your bug - might already be fixed there. Development moves extremely fast, most problems - in official releases are reported within days or even hours, so please use - <B>only CVS</B> to report bugs. This includes binary packages of MPlayer. - Please do not report bugs in one of the various RPM or Debian packages of - MPlayer. CVS instructions can be found at the bottom of - <A HREF="http://www.mplayerhq.hu/homepage/dload.html">this page</A> or in the - README. If this did not help please refer to the - <A HREF="documentation.html#known_bugs">list of known bugs</A> and the - rest of the documentation. If your problem is not known or not solvable by our - instructions, then please report the bug.</P> - -<P>Please do not send bug reports privately to individual developers. This is - community work and thus there might be several people interested in it. - Sometimes other users already experienced your troubles and know how to - circumvent a problem even if it is a bug in MPlayer code.</P> - -<P>Please describe your problem in as much detail as possible. Do a little - detective work to narrow down the circumstances under which the problem - occurs. Does the bug only show up in certain situations? Is it specific to - certain files or file types? Does it occur with only one codec or is it codec - independent? Can you reproduce it with all output drivers? The more - information you provide the better are our chances at fixing your problem. - Please do not forget to also include the valuable information requested below, - we will be unable to properly diagnose your problem otherwise.</P> - -<P>An excellent and well written guide to asking questions in public forums is - <A HREF="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</A> - by <A HREF="http://www.catb.org/~esr/">Eric S. Raymond</A>. There is another - called - <A HREF="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to Report Bugs Effectively</A> - by <A HREF="http://www.chiark.greenend.org.uk/~sgtatham/">Simon Tatham</A>. If - you follow these guidelines you should be able to get help. But please - understand that we all follow the mailing lists voluntarily in our free time. - We are very busy and cannot guarantee that you will get a solution for your - problem or even an answer.</P> - - -<H2><A NAME="where">B.3 Where to report bugs</A></H2> - -<P>Subscribe to the mplayer-users mailing list:<BR> - <A HREF="http://mplayerhq.hu/mailman/listinfo/mplayer-users">http://mplayerhq.hu/mailman/listinfo/mplayer-users</A><BR> - and send your bug report to:<BR> - <A HREF="mailto:mplayer-users@mplayerhq.hu">mplayer-users@mplayerhq.hu</A></P> - -<P>The language of this list is <B>English</B>. Please follow the standard - <A HREF="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</A> and - <B>do not send HTML mail</B> to any of our mailing lists. You will only get - ignored or banned. If you do not know what HTML mail is or why it is evil, - read this <A HREF="http://expita.com/nomime.html">fine document</A>. It - explains all the details and has instructions for turning HTML off. Also note - that we will not individually CC (carbon-copy) people so it is a good idea to - subscribe to actually receive your answer.</P> - - -<H2><A NAME="what">B.4 What to report</A></H2> - -<P>You may need to include log, configuration or sample files in your bug - report. If some of them are quite big then it is better to upload them to our - <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">FTP server</A> in a compressed - format (gzip and bzip2 preferred) and include only the path and file name in - your bug report. Our mailing lists have a message size limit of 80k, if you - have something bigger you have to compress or upload it.</P> - - -<H3><A NAME="system">B.4.1 System Information</A></H3> - -<UL> - <LI>Your Linux distribution or operating system and version e.g.: - <UL> - <LI>Red Hat 7.1</LI> - <LI>Slackware 7.0 + devel packs from 7.1 ...</LI> - </UL> - </LI> - <LI>kernel version:<BR> - <CODE>uname -a</CODE></LI> - <LI>libc version:<BR> - <CODE>ls -l /lib/libc[.-]*</CODE></LI> - <LI>X version:<BR> - <CODE>X -version</CODE></LI> - <LI>gcc and ld versions:<BR> - <CODE>gcc -v<BR> - ld -v</CODE></LI> - <LI>binutils version:<BR> - <CODE>as --version</CODE></LI> - <LI>If you have problems with fullscreen mode: - <UL> - <LI>Window manager type and version</LI> - </UL> - </LI> - <LI>If you have problems with XVIDIX: - <UL> - <LI>X colour depth:<BR> - <CODE>xdpyinfo | grep "depth of root"</CODE></LI> - </UL> - </LI> - <LI>If only the GUI is buggy: - <UL> - <LI>GTK version</LI> - <LI>GLIB version</LI> - <LI>libpng version</LI> - <LI>GUI situation in which the bug occurs</LI> - </UL> - </LI> -</UL> - - -<H3><A NAME="hardware">B.4.2 Hardware and drivers</A></H3> - -<UL> - <LI>CPU info (this works on Linux only):<BR> - <CODE>cat /proc/cpuinfo</CODE></LI> - <LI>Video card manufacturer and model, e.g.: - <UL> - <LI>ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM</LI> - <LI>Matrox G400 DH 32MB SGRAM</LI> - </UL> - </LI> - <LI>Video driver type & version, e.g.: - <UL> - <LI>X built-in driver</LI> - <LI>nVidia 0.9.623</LI> - <LI>Utah-GLX CVS 2001-02-17</LI> - <LI>DRI from X 4.0.3</LI> - </UL> - </LI> - <LI>Sound card type & driver, e.g.: - <UL> - <LI>Creative SBLive! Gold with OSS driver from oss.creative.com</LI> - <LI>Creative SB16 with kernel OSS drivers</LI> - <LI>GUS PnP with ALSA OSS emulation</LI> - </UL> - </LI> - <LI>If in doubt include <CODE>lspci -vv</CODE> output on Linux systems.</LI> -</UL> - - -<H3><A NAME="configure">B.4.3 Configure problems</A></H3> - -<P>If you get errors while running <CODE>./configure</CODE>, or autodetection - of something fails, read <CODE>configure.log</CODE>. You may find the answer - there, for example multiple versions of the same library mixed on your system, - or you forgot to install the development package (those with the -dev suffix). If you think there is a bug, include <CODE>configure.log</CODE> in your bug - report.</P> - - -<H3><A NAME="compilation">B.4.4 Compilation problems</A></H3> - -Please include these files: - -<UL> - <LI><CODE>config.h</CODE></LI> - <LI><CODE>config.mak</CODE></LI> -</UL> - -Only if compilation fails below one of these directories, include these files: - -<UL> - <LI><CODE>Gui/config.mak</CODE></LI> - <LI><CODE>libvo/config.mak</CODE></LI> - <LI><CODE>libao2/config.mak</CODE></LI> -</UL> - - -<H3><A NAME="playback">B.4.5 Playback problems</A></H3> - -<P>Please include the output of MPlayer at verbosity level 1, but - remember to <B>not truncate the output</B> when you paste it into your mail. - The developers need all of the messages to properly diagnose a problem. You - can direct the output into a file like this:</P> - -<P><CODE> mplayer -v [options] [filename] > mplayer.log 2>&1</CODE></P> - -<P>If your problem is specific to one or more files, then please upload the - offender(s) to:</P> - -<P> <A HREF="ftp://mplayerhq.hu/MPlayer/incoming/">ftp://mplayerhq.hu/MPlayer/incoming/</A></P> - -<P>Also upload a small text file having the same base name as your file - with a .txt extension. Describe the problem you are having with the - particular file there and include your email address as well as the output - of MPlayer at verbosity level 1. Usually the first 1-5 MB of a file are - enough to reproduce the problem, but to be sure we ask you to:</P> - -<P><CODE> dd if=yourfile of=smallfile bs=1024k count=5</CODE></P> - -<P>It will take the first five megabytes of <STRONG>'your-file'</STRONG> and - write it to <STRONG>'small-file'</STRONG>. Then try again on this small file - and if the bug still shows up your sample is sufficient for us. Please - <STRONG>do not ever</STRONG> send such files via mail! Upload it, and send - only the path/filename of the file on the FTP-server. If the file is - accessible on the net, then sending the <STRONG>exact</STRONG> URL is - sufficient.</P> - - -<H3><A NAME="crash">B.4.6 Crashes</A></H3> - -<P>You have to run MPlayer inside <CODE>gdb</CODE> and send us the complete - output or if you have a core dump of the crash you can extract useful - information from the <CODE>Core</CODE> file. Here's how:</P> - - -<H4><A NAME="debug">B.4.6.1 How to conserve information about a reproducible crash</A></H4> - -Recompile MPlayer with debugging code enabled: - -<P><CODE> ./configure --enable-debug=3<BR> - make</CODE></P> - -and then run MPlayer within gdb using: - -<P><CODE> gdb ./mplayer</CODE></P> - -You are now within gdb. Type: - -<P><CODE> run -v [options-to-mplayer] filename</code></P> - -and reproduce your crash. As soon as you did it, gdb will -return you to the command line prompt where you have to enter - -<P><CODE> bt<BR> - disass $pc-32 $pc+32<BR> - info all-registers</CODE></P> - - -<H4><A NAME="core">B.4.6.2 How to extract meaningful information from a core dump</A></H4> - -<P>Create the following command file:</P> - -<P><CODE>bt<BR> - disass $pc-32 $pc+32<BR> - info all-registers</CODE></P> - -<P>Then simply execute this command:</P> - -<P> <CODE>gdb mplayer --core=core -batch --command=command_file > mplayer.bug</CODE></P> - - -<H2><A NAME="advusers">B.5 I know what I am doing...</A></H2> - -<P>If you created a proper bug report following the steps above and you are - confident it is a bug in MPlayer, not a compiler problem or broken - file, you have already read the documentation and you could not find a - solution, your sound drivers are OK, then you might want to subscribe to the - mplayer-advusers list and send your bug report there to get a better and - faster answer.<BR><BR> - Please be advised that if you post newbie questions or questions answered - in the manual there, you will be ignored or flamed instead of getting an - appropriate answer.<BR> - So do not flame us and subscribe to -advusers only if you really know - what you are doing and feel like being an advanced MPlayer user or - developer. If you meet these criteria it should not be difficult to find - out how to subscribe...</P> - -</BODY> -</HTML> diff --git a/DOCS/en/cd-dvd.html b/DOCS/en/cd-dvd.html deleted file mode 100644 index b5c50241f6..0000000000 --- a/DOCS/en/cd-dvd.html +++ /dev/null @@ -1,256 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML> - -<HEAD> - <TITLE>CD, DVD, VCD - MPlayer - The Movie Player for Linux</TITLE> - <LINK REL="stylesheet" TYPE="text/css" HREF="../default.css"> - <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> -</HEAD> - -<BODY> - - -<H2><A NAME="drives">4.1 CD/DVD drives</A></H2> - -<P>Linux documentation excerpt:</P> - -<P>Modern CD-ROM drives can attain very high head speeds, yet some CD-ROM drives - are capable of running at reduced speeds. There are several reasons that might - make you consider changing the speed of a CD-ROM drive:</P> - -<UL> - <LI>There have been reports of read errors at 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 - noise.</LI> -</UL> - -<P>You can reduce the speed of IDE CD-ROM drives with <CODE>hdparm</CODE> or a - program called <CODE>setcd</CODE>. It works like this:</P> - -<P> <CODE>hdparm -E [speed] [cdrom device]</CODE></P> - -<P> <CODE>setcd -x [speed] [cdrom device]</CODE></P> - -<P>If you have root privileges the following command may also help:</P> - -<P> <CODE>echo file_readahead:2000000 > /proc/ide/[cdrom device]/settings</CODE></P> - -<P>This sets prefetched file reading to 2MB, which helps with scratched CD-ROMs. - If you set it to too high, the drive will continuously spin up and down, and - will dramatically decrease the performance. - It is recommended that you also tune your CD-ROM drive with - <CODE>hdparm</CODE>:</P> - -<P> <CODE>hdparm -d1 -a8 -u1 (cdrom device)</CODE></P> - -<P>This enables DMA access, read-ahead, and IRQ unmasking (read the - <CODE>hdparm</CODE> man page for a detailed explanation).</P> - -<P>Please refer to "<CODE>/proc/ide/[cdrom device]/settings</CODE>" for - fine-tuning your CD-ROM.</P> - -<P>SCSI drives do not have a uniform way of setting these parameters (Do you - know one? Tell us!) There is a tool that works for - <A HREF="http://das.ist.org/~georg/">Plextor SCSI drives</A>.</P> - -<P>FreeBSD:</P> - -<P> Speed: <CODE>cdcontrol [-f device] speed [speed]</CODE></P> -<P> DMA: <CODE>sysctl hw.ata.atapi_dma=1</CODE></P> - - -<H2><A NAME="dvd">4.2 DVD playback</A></H2> - -<P>For the complete list of available options, please read the man page. - The Syntax for a standard Digital Versatile Disc (DVD) is as follows:</P> - -<P><CODE>mplayer dvd://<track> [-dvd-device <device>]</CODE></P> - -<P>Example: <CODE>mplayer dvd://1 -dvd-device /dev/hdc</CODE></P> - -<P>The default DVD device is <CODE>/dev/dvd</CODE>. If your setup differs, - make a symlink or specify the correct device on the command line with the - <CODE>-dvd-device</CODE> option.</P> - -<H4>New-style DVD support (mpdvdkit2)</H4> - -<P>MPlayer uses <CODE>libdvdread</CODE> and <CODE>libdvdcss</CODE> for - DVD decryption and playback. These two libraries are contained in the - <CODE>libmpdvdkit2/</CODE> subdirectory of the MPlayer source tree, you - do not have to install them separately. We opted for this solution because - we had to fix a <CODE>libdvdread</CODE> bug and apply a patch which adds - <B>cracked CSS keys caching support</B> to <CODE>libdvdcss</CODE>. This results - in a large speed increase because the keys do not have to be cracked every time - before playing.</P> - -<P>MPlayer can also use system-wide <CODE>libdvdread</CODE> and - <CODE>libdvdcss</CODE> libraries, but this solution is <B>not</B> recommended, - as it can result in bugs, library incompatibilities and slower speed.</P> - -<H4>Old-style DVD support - OPTIONAL</H4> - -<P>Useful if you want to play encoded VOBs from <B>hard disk</B>. Compile and - install <B>libcss</B> 0.0.1 (not newer) for this (If MPlayer fails to - detect it, use the <CODE>-csslib /path/to/libcss.so</CODE> option). To use it, - you need to be root, use a suid root MPlayer binary or let MPlayer call the - suid-root fibmap_mplayer wrapper program.</P> - -<H4>DVD structure</H4> - -<P>DVD disks have 2048 bytes per sector with ECC/CRC. They usually have an UDF - filesystem on a single track, containing various files (small .IFO and .BUK - files and big (1GB) .VOB files). They are real files and can be copied/played - from the mounted filesystem of an unencrypted DVD.</P> - -<P>The .IFO files contain the movie navigation information (chapter/title/angle - map, language table, etc) and are needed to read and interpret the .VOB - content (movie). The .BUK files are backups of them. They use <B>sectors</B> - everywhere, so you need to use raw addressing of sectors of the disc to - implement DVD navigation or decrypt the content.</P> - -<P>The whole old-style DVD support with <CODE>libcss</CODE> therefore needs a mounted DVD - filesystem and raw sector-based access to the device. Unfortunately you must - (under Linux) be root to get the sector address of a file. You have the - following choices:</P> - -<UL> - <LI>Be root or use a suid-root mplayer binary.</LI> - <LI>Let MPlayer call the suid-root fibmap_mplayer wrapper program to access - the DVD (used in the old-style DVD playback over <CODE>libcss</CODE>).</LI> - <LI>Don't use the kernel's filesystem driver at all and reimplement it in - userspace. <CODE>libdvdread</CODE> 0.9.x and <CODE>libmpdvdkit</CODE> do this (new-style DVD - support). The kernel UDF filesystem driver is not needed as they already - have their own builtin UDF filesystem driver. Also the DVD does not have to - be mounted as only the raw sector-based access is used.</LI> -</UL> - -<P>Sometimes <CODE>/dev/dvd</CODE> cannot be read by users, so the <CODE>libdvdread</CODE> - authors implemented an emulation layer which transfers sector addresses to - filenames+offsets, to emulate raw access on top of a mounted filesystem - or even on a hard disk.</P> - -<P><CODE>libdvdread</CODE> even accepts the mountpoint instead of the device name for raw - access and checks <CODE>/proc/mounts</CODE> to get the device name. It was - developed for Solaris, where device names are dynamically allocated.</P> - -<P>The default DVD device is <CODE>/dev/dvd</CODE>. If your setup differs, - make a symlink, or specify the correct device on the command line with the - <CODE>-dvd-device</CODE> option.</P> - -<H4>DVD authentication</H4> - -<P>The authentication and decryption method of the new-style DVD support is done - using a patched <CODE>libdvdcss</CODE> (see above). The method can be specified through the - environment variable <CODE>DVDCSS_METHOD</CODE>, which can be set to - <CODE>key</CODE>, <CODE>disk</CODE> or <CODE>title</CODE>.</P> - -<P>If nothing is specified it tries the following methods - (default: key, title request):</P> - -<OL> - <LI><B>bus key:</B> This key is negotiated during authentication (a long mix - of ioctls and various key exchanges, crypto stuff) and is used to encrypt - the title and disk keys before sending them over the unprotected bus - (to prevent eavesdropping). The bus key is needed to get and predecrypt the - crypted disk key.</LI> - <LI><B>cached key:</B> MPlayer looks for already cracked - title keys which are stored in the <CODE>~/.mplayer/DVDKeys</CODE> directory - (fast ;).</LI> - <LI><B>key:</B> If no cached key is available, MPlayer tries to - decrypt the disk key with a set of included player keys.</LI> - <LI><B>disk:</B> If the key method fails (e.g. no included player keys), - MPlayer will crack the disk key using a brute force algorithm. - This process is CPU intensive and requires 64 MB of memory (16M 32Bit - entries hash table) to store temporary data. This method should always - work (slow).</LI> - <LI><B>title request:</B> With the disk key MPlayer requests the crypted title - keys, which are inside <I>hidden sectors</I> using <CODE>ioctl()</CODE>. - The region protection of RPC-2 drives is performed in this step and may - fail on such drives. If it succeeds, the title keys will be decrypted with - the bus and disk key.</LI> - <LI><B>title:</B> This method is used if the title request failed and does - not rely on any key exchange with the DVD drive. It uses a crypto attack to - guess the title key directly (by finding a repeating pattern in the - decrypted VOB content and guessing that the plain text corresponding to the - first encrypted bytes is a continuation of that pattern). - The method is also known as "known plaintext attack" or "DeCSSPlus". - In rare cases this may fail because there is not enough encrypted data on - the disk to perform a statistical attack or because the key changes in the - middle of a title. This method is the only way to decrypt a DVD stored on a - hard disk or a DVD with the wrong region on an RPC2 drive (slow).</LI> -</OL> - -<P>RPC-1 DVD drives only protect region settings through software. - RPC-2 drives have a hardware protection that allows 5 changes only. It might - be needed/recommended to upgrade the firmware to RPC-1 if you have a RPC-2 DVD - drive. Firmware upgrades can be found on this - <A HREF="http://www.firmware-flash.com">firmware page</A>. If there is - no firmware upgrade available for your device, use the - <A HREF="http://www.linuxtv.org/download/dvd/dvd_disc_20000215.tar.gz">regionset - tool</A> to set the region code of your DVD drive (under Linux). - <B>Warning:</B> You can only set the region 5 times.</P> - - -<H2><A NAME="vcd">4.3 VCD playback</A></H2> - -<P>For the complete list of available options, please read the man page. - The Syntax for a standard Video CD (VCD) is as follows:</P> - -<P><CODE>mplayer vcd://<track> [-cdrom-device <device>]</CODE></P> - -<P>Example: <CODE>mplayer vcd://2 -cdrom-device /dev/hdc</CODE></P> - -<P>The default VCD device is <CODE>/dev/cdrom</CODE>. If your setup differs, - make a symlink or specify the correct device on the command line with the - <CODE>-cdrom-device</CODE> option.</P> - -<P><B>Note:</B> At least Plextor and some Toshiba SCSI CD-ROM drives have - horrible performance reading VCDs. This is because the the CDROMREADRAW ioctl - is not fully implemented for these drives. If you have some knowledge of SCSI - programming, please <A HREF="../tech/patches.txt">help us</A> implement generic - SCSI support for VCDs.</P> - -<P>In the meantime you can extract data from VCDs with - <A HREF="http://140.132.1.204/OS/Linux/packages/X/viewers/readvcd/">readvcd</A> - and play the resulting file with MPlayer.</P> - -<H4>VCD structure</H4> - -<P>VCD disks consist of one or more tracks:</P> - -<UL> - <LI>The first track is a small 2048 bytes/sector data track with an iso9660 - filesystem, usually containing Windows VCD player programs and maybe other - information (images, text, etc).</LI> - <LI>The second and other tracks are raw 2324 bytes/sector MPEG (movie) tracks, - containing one MPEG PS data packet per sector instead of a filesystem. - Similar to audio CD tracks, these tracks <B>cannot be mounted</B> (Did you - ever mount an audio CD to play it?). As most movies are inside this track, - you should try <CODE>vcd://2</CODE> first.</LI> - <LI>There exist VCD disks without the first track (single track and no - filesystem at all). They are still playable, but cannot be mounted.</LI> -</UL> - -<H4>About .DAT files:</H4> - -<P>The ~600 MB file visible on the first track of the mounted VCD is not a real - file! It is a so called ISO gateway, created to allow Windows to handle such - tracks (Windows does not allow raw device access to applications at all). - Under Linux you cannot copy or play such files (they contain garbage). Under - Windows it is possible as its iso9660 driver emulates the raw reading of - tracks in this file. To play a .DAT file you need the kernel driver which can - be found in the Linux version of PowerDVD. It has a modified iso9660 - filesystem (<CODE>vcdfs/isofs-2.4.X.o</CODE>) driver, which is able to emulate - the raw tracks through this shadow .DAT file. If you mount the disc using - their driver, you can copy and even play .DAT files with mplayer. But it - <B>will not work</B> with the standard iso9660 driver of the Linux kernel! - Use <CODE>vcd://</CODE> instead. Alternatives for VCD copying are - the new <A HREF="http://www.elis.rug.ac.be/~ronsse/cdfs/">cdfs</A> kernel - driver (not part of the official kernel) that shows CD <I>sessions</I> - as image files and <A HREF="http://cdrdao.sourceforge.net/">cdrdao</A>, a - bit-by-bit CD grabbing/copying application.</P> - -</BODY> -</HTML> diff --git a/DOCS/en/codecs.html b/DOCS/en/codecs.html deleted file mode 100644 index 5c1bf5983b..0000000000 --- a/DOCS/en/codecs.html +++ /dev/null @@ -1,555 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML> - -<HEAD> - <TITLE>Codecs - MPlayer - The Movie Player for Linux</TITLE> - <LINK REL="stylesheet" TYPE="text/css" HREF="../default.css"> - <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> -</HEAD> - -<BODY> - - -<H2><A NAME="codecs">2.2 Supported codecs</A></H2> - - -<H3><A NAME="video_codecs">2.2.1 Video codecs</A></H3> - -<P>See the - <A HREF="http://www.mplayerhq.hu/DOCS/codecs-status.html">codec status table</A> - for the complete, daily generated list. Quite a few codecs are available for - download from our homepage. Grab them from our - <A HREF="http://www.mplayerhq.hu/MPlayer/releases/codecs/">codecs page</A>.</P> - -<P>The most important ones above all:</P> -<UL> - <LI><B>MPEG1</B> (<B>VCD</B>) and <B>MPEG2</B> (<B>DVD</B>) video</LI> - <LI>native decoders for <B>DivX ;-)</B>, <B>OpenDivX</B>, <B>DivX4</B>, <B> - DivX5</B>, <B>M$ MPEG4</B> v1, v2 and other MPEG4 variants</LI> - <LI>native decoder for <B>Windows Media Video 7/8</B> (<B>WMV1/WMV2</B>), and - Win32 DLL decoder for <B>Windows Media Video 9</B> (<B>WMV3</B>), both - used in .wmv files</LI> - <LI>native <B>Sorenson 1 (SVQ1)</B> decoder</LI> - <LI>native <B>Sorenson 3 (SVQ3)</B> decoder</LI> - <LI><B>3ivx</B> v1, v2 decoder</LI> - <LI>Cinepak and <B>Intel Indeo</B> codecs (3.1, 3.2, 4.1, 5.0)</LI> - <LI><B>MJPEG</B>, AVID, VCR2, ASV2 and other hardware formats</LI> - <LI>VIVO 1.0, 2.0, I263 and other <B>h263</B>(+) variants</LI> - <LI>FLI/FLC</LI> - <LI><B>RealVideo 1.0</B> codec from libavcodec, and <B>RealVideo 2.0</B>, - <B>3.0</B> and <B>4.0</B> 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> - - -<H4><A NAME="divx">2.2.1.1 DivX4/DivX5</A></H4> - -<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 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.</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 <B>libavcodec</B>. 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 not available under an Open Source - license.</P> - -<P>DivX4Linux works in two modes:</P> - -<DL> - <DT><CODE>-vc odivx</CODE></DT> - <DD>Uses the codec in OpenDivX fashion. In this case it - produces YV12 images in its own buffer, and MPlayer does colorspace - conversion via libvo. (<B>Fast, recommended!</B>)</DD> - - <DT><CODE>-vc divx4</CODE></DT> - <DD>Uses the colorspace conversion of the codec. - In this mode you can use YUY2/UYVY, too. (<B>SLOW</B>)</DD> -</DL> - -<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> - -<P>The Divx4/5 binary codec library can be downloaded from - <A HREF="http://avifile.sourceforge.net">avifile</A> or - <A HREF="http://www.divx.com">divx.com</A>. - Unpack it, run <CODE>./install.sh</CODE> as root and do not forget adding - <CODE>/usr/local/lib</CODE> to your <CODE>/etc/ld.so.conf</CODE> and running - <CODE>ldconfig</CODE>.</P> - -<P>Get the CVS version of the OLD OpenDivx core library like this:</P> - -<OL> - <LI><CODE>cvs -d:pserver:anonymous@cvs.projectmayo.com:/cvsroot login</CODE></LI> - <LI><CODE>cvs -d:pserver:anonymous@cvs.projectmayo.com:/cvsroot co divxcore</CODE></LI> - <LI>This core library is split into a decore and encore library that have to - be compiled separately. For the decore Library, simply type - <PRE> - cd divxcore/decore/build/linux - make - cp libdivxdecore.so /usr/local/lib - ln -s libdivxdecore.so /usr/local/lib/libdivxdecore.so.0 - cp ../../src/decore.h /usr/local/include - </PRE> - </LI> - <LI>Alas, for the encore library there is no Linux Makefile available, and the - MMX optimized code only works on Windows. You can still compile it, though, - by using this - <A HREF="ftp://ftp.mplayerhq.hu/MPlayer/contrib/divx-mf/Makefile">Makefile</A>. - <PRE> - cd ../../../encore/build - mkdir linux - cd linux - cp path/Makefile . - make - cp libdivxencore.so /usr/local/lib - ln -s libdivxencore.so /usr/local/lib/libdivxencore.so.0 - cp ../../src/encore.h /usr/local/include - </PRE> - </LI> -</OL> - -<P>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.</P> - - -<H4><A NAME="libavcodec">2.2.1.2 FFmpeg/libavcodec</A></H4> - -<P><A HREF="http://ffmpeg.sourceforge.net">FFmpeg</A> contains an - <B>open source</B> codec package, which is capable of decoding streams - encoded with - H263/MJPEG/LJPEG/RV10/DivX3/DivX4/DivX5/MP41/MP42/WMV1/WMV2/HuffYUV/SVQ1/SVQ3/ - MPEG1/MPEG2/VCR1/VCR2/ASV1/ASV2/CLJR - video, or WMA (Windows Media Audio) audio codecs. Not only some of - them can be encoded with, but it also offers higher speed than the Win32 - codecs or the DivX.com DivX4/5 library!</P> - -<P>It contains a lot of nice codecs, especially important are the MPEG4 - variants: - DivX |