diff options
| author | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2003-02-10 00:00:00 +0000 |
|---|---|---|
| committer | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2003-02-10 00:00:00 +0000 |
| commit | 41198d0c024dc57d005f839ddcde2e323b278b29 (patch) | |
| tree | c2f5ab2ace2fce23bcc095330ac8c16d929677de /DOCS/en | |
| parent | 3e718780f2dd3375f272c6e28becedd5f792f192 (diff) | |
| download | mpv-41198d0c024dc57d005f839ddcde2e323b278b29.tar.bz2 mpv-41198d0c024dc57d005f839ddcde2e323b278b29.tar.xz | |
Move English files to en/ subdirectory.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@9383 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS/en')
| -rw-r--r-- | DOCS/en/bugreports.html | 289 | ||||
| -rw-r--r-- | DOCS/en/cd-dvd.html | 266 | ||||
| -rw-r--r-- | DOCS/en/codecs-in.html | 185 | ||||
| -rw-r--r-- | DOCS/en/codecs.html | 539 | ||||
| -rw-r--r-- | DOCS/en/documentation.html | 2061 | ||||
| -rw-r--r-- | DOCS/en/encoding.html | 320 | ||||
| -rw-r--r-- | DOCS/en/faq.html | 803 | ||||
| -rw-r--r-- | DOCS/en/formats.html | 320 | ||||
| -rw-r--r-- | DOCS/en/mplayer.1 | 3524 | ||||
| -rw-r--r-- | DOCS/en/skin.html | 805 | ||||
| -rw-r--r-- | DOCS/en/sound.html | 848 | ||||
| -rw-r--r-- | DOCS/en/users_against_developers.html | 190 | ||||
| -rw-r--r-- | DOCS/en/video.html | 1469 |
13 files changed, 11619 insertions, 0 deletions
diff --git a/DOCS/en/bugreports.html b/DOCS/en/bugreports.html new file mode 100644 index 0000000000..b75ef9bd50 --- /dev/null +++ b/DOCS/en/bugreports.html @@ -0,0 +1,289 @@ +<!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. 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.tuxedo.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</A> + by <A HREF="http://www.tuxedo.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>Please 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 the following on your command line:</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 new file mode 100644 index 0000000000..dc7e847362 --- /dev/null +++ b/DOCS/en/cd-dvd.html @@ -0,0 +1,266 @@ +<!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>You can also try</P> + +<P> <CODE>echo current_speed:4 > /proc/ide/[cdrom device]/settings</CODE></P> + +<P>but you will need 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>DVD Navigation support (dvdnav)</H4> + +<P>Support for DVD navigation via <CODE>dvdnav</CODE> was being worked on, but + it was never finished properly and it is currently unmaintained. Who knows, it + might even compile.</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 the <CODE>-vcd</CODE> option 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-in.html b/DOCS/en/codecs-in.html new file mode 100644 index 0000000000..941113f591 --- /dev/null +++ b/DOCS/en/codecs-in.html @@ -0,0 +1,185 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + <title>Codec Status Table - 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 text="#000000" link="#666666" vlink="#666666" alink="#666666"> +<table width=750 border="0"> + <tr> + <td align="right"> + <p> </p> + + <p><b>Status of codecs support</b></p> + </td> + </tr> + <tr> + <td> + <p><a href="#vc">Video codecs</a><br><a href="#ac">Audio codecs</a><br></p> + </td> + </tr> + <tr> + <td align="center"> + <b><font face="Verdana, Arial, Helvetica, sans-serif" size="5"><a name="vc">Video codecs:</a></font></b><br><br> + + <table width="100%" border="1" cellspacing="0" cellpadding="5"> + + <tr> + <td colspan=6 bgcolor="#CCCCCC"><b>Working video codecs</b></td> + </tr> + <tr> + <td width=150 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codec name</font></b></td> + <td width=70 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">fourcc</font></b></td> + <td width=120 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codecfile</font></b></td> + <td width=40 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">out</font></b></td> + <td align=center colspan=2><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">comments</font></b></td> + </tr> +<!-- %0 --> + <tr> + <td align=center><b>%i</b></td> + <td align=center><b>%F</b></td> + <td align=center><b>%d</b></td> + <td align=center><b>%Y</b></td> + <td align=center colspan=2><b>%c</b></td> + </tr> +<!-- %. --> + + <tr> + <td colspan=6 bgcolor="#CCCCCC"><b>New / Untested codecs</b></td> + </tr> + <tr> + <td width=150 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codec name</font></b></td> + <td width=70 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">fourcc</font></b></td> + <td width=120 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codecfile</font></b></td> + <td colspan=3 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">problem</font></b></td> + </tr> +<!-- %4 --> + <tr> + <td align=center><b>%i</b></td> + <td align=center><b>%F</b></td> + <td align=center><b>%d</b></td> + <td align=center colspan=3><b>%c</b></td> + </tr> +<!-- %. --> + + <tr> + <td colspan=6 bgcolor="#CCCCCC"><b>Codecs with problems</b></td> + </tr> + <tr> + <td width=150 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codec name</font></b></td> + <td width=70 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">fourcc</font></b></td> + <td width=120 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codecfile</font></b></td> + <td colspan=3 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">problem</font></b></td> + </tr> +<!-- %2 --> + <tr> + <td align=center><b>%i</b></td> + <td align=center><b>%F</b></td> + <td align=center><b>%d</b></td> + <td align=center colspan=3><b>%c</b></td> + </tr> +<!-- %. --> + + <tr> + <td colspan=6 bgcolor="#CCCCCC"><b>Not yet working codecs:</b></td> + </tr> + <tr> + <td width=150 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codec name</font></b></td> + <td width=70 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">fourcc</font></b></td> + <td width=120 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">codecfile</font></b></td> + <td colspan=3 align=center><b><font color="#AAAAAA" face="Verdana, Arial, Helvetica, sans-serif" size="2">problem</font></b></td> + </tr> +<!-- %3 --> + <tr> + <td align=center><b>%i</b></td> + <td align=center><b>%F</b></td> + <td align=center><b>%d</b></td> + <td align=center colspan=3><b>%c</b></td> + </tr> +<!-- %. --> + + </table> + + <br><b><font face="Verdana, Arial, Helvetica, sans-serif" size="5"><a name="ac">Audio codecs:</a></font></b><br><br> + + <table width="100%" border="1" cellspacing="0" cellpadding="5"> + + <tr> + <td colspan=6 bgcolor="#CCCCCC"><b> |