From dc86f6ed17b8e7a702856baefc1d8c3dbd8e229a Mon Sep 17 00:00:00 2001 From: torinthiel Date: Fri, 8 Dec 2006 11:38:06 +0000 Subject: General reformatting round: - fix some " -> " - reindent with more consistency - visual markup of tags - break overly long lines - add missing tags in examples - cola truck standing by git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@21537 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/audio.xml | 23 +- DOCS/xml/en/bugreports.xml | 264 ++- DOCS/xml/en/bugs.xml | 163 +- DOCS/xml/en/cd-dvd.xml | 109 +- DOCS/xml/en/codecs.xml | 406 ++-- DOCS/xml/en/containers.xml | 152 +- DOCS/xml/en/documentation.xml | 48 +- DOCS/xml/en/encoding-guide.xml | 4292 +++++++++++++++++++++------------------- DOCS/xml/en/faq.xml | 321 +-- DOCS/xml/en/history.xml | 261 ++- DOCS/xml/en/install.xml | 145 +- DOCS/xml/en/mencoder.xml | 293 +-- DOCS/xml/en/ports.xml | 654 +++--- DOCS/xml/en/radio.xml | 101 +- DOCS/xml/en/skin.xml | 922 +++++---- DOCS/xml/en/tvinput.xml | 268 ++- DOCS/xml/en/usage.xml | 507 ++--- DOCS/xml/en/video.xml | 645 +++--- 18 files changed, 5111 insertions(+), 4463 deletions(-) diff --git a/DOCS/xml/en/audio.xml b/DOCS/xml/en/audio.xml index 385f02044c..77a815012e 100644 --- a/DOCS/xml/en/audio.xml +++ b/DOCS/xml/en/audio.xml @@ -35,23 +35,28 @@ information. + + + + Troubleshooting Some notes: - If you have ALSA version 0.5, then you almost always have to use - , since ALSA 0.5 has buggy OSS emulation code, - and will crash MPlayer - with a message like this: - -DEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer! +If you have ALSA version 0.5, then you almost always have to use +, since ALSA 0.5 has buggy OSS emulation code, +and will crash MPlayer +with a message like this: + +DEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer! + + - If the sound clicks when playing from CD-ROM, turn on IRQ unmasking as - described in the CD-ROM section. +If the sound clicks when playing from CD-ROM, turn on IRQ unmasking as +described in the CD-ROM section. diff --git a/DOCS/xml/en/bugreports.xml b/DOCS/xml/en/bugreports.xml index d40a16723b..3122c3bca4 100644 --- a/DOCS/xml/en/bugreports.xml +++ b/DOCS/xml/en/bugreports.xml @@ -2,6 +2,7 @@ How to report bugs + Good bug reports are a very valuable contribution to the development of any software project. But just like writing good software, good problem reports @@ -11,8 +12,14 @@ receive obscene amounts of email. So while your feedback is crucial in improving that you have to provide all of the information we request and follow the instructions in this document closely. + + + + + Report security releated bugs + In case you have found an exploitable bug and you would like to do the right thing and let us fix it before you disclose it, we would be happy @@ -25,33 +32,48 @@ Please don't delay your report to write proof-of-concept exploit, you can send that one with another mail. + + + + + How to fix bugs + 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 -this short document to find out how to -get your code included in MPlayer. The people on the +this short document to find out how +to get your code included in MPlayer. The people on +the MPlayer-dev-eng mailing list will assist you if you have questions. + + + + + How to do regression testing using Subversion + A problem that can happen sometimes is 'it used to work before, now it doesn't anymore...'. Here is a step by step procedure to try to pinpoint when the problem occurred. This is not for casual users. + First, you'd need to fetch MPlayer's source tree from Subversion. Instructions can be found at the bottom of this page. + -You will have now in the mplayer/ directory an image of the Subversion tree, on the -client side. +You will have now in the mplayer/ directory an image of the Subversion tree, on +the client side. Now update this image to the date you want: cd mplayer/ @@ -62,6 +84,7 @@ Using this date format ensure that you will be able to extract patches according to the date at which they were committed, as in the MPlayer-cvslog archive. + Now proceed as for a normal update: @@ -69,6 +92,7 @@ Now proceed as for a normal update: make + If any non-programmer reads this, the fastest method to get at the point where the problem occurred is to use a binary search — that is, @@ -79,6 +103,7 @@ For example, if the problem occurred in 2003, start at mid-year, then ask If yes, go back to the first of April; if not, go to the first of October, and so on. + If you have lot of free hard disk space (a full compile currently takes 100 MB, and around 300-350 MB if debugging symbols are enabled), copy the @@ -89,6 +114,7 @@ earlier version, so if you do not make a backup copy of your original source tree, you will have to recompile everything in it when you come back to the present.) + When you have found the day where the problem happened, continue the search using the mplayer-cvslog archive (sorted by date) and a more precise svn @@ -98,6 +124,7 @@ svn update -r {"2004-08-23 15:17:25"} This will allow you to easily find the exact patch that did it. + If you find the patch that is the cause of the problem, you have almost won; report about it to the @@ -110,80 +137,102 @@ You may also look hard at the patch until it is coerced to reveal where the bug is :-). + + + + + How to report bugs + -First of all please try the latest Subversion version of MPlayer +First of all please try the latest Subversion 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 only Subversion to report bugs. This -includes binary packages of MPlayer. Subversion -instructions can be found at the bottom of +most problems in official releases are reported within days or even hours, +so please use only Subversion to report bugs. +This includes binary packages of MPlayer. +Subversion instructions can be found at the bottom of this page or in the README. If this did not help please refer to the list of -known bugs and the rest of the documentation. If your -problem is not known or not solvable by our instructions, then please report the bug. +known bugs and the rest of the documentation. +If your problem is not known or not solvable by our instructions, +then please report the bug. 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. +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. -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. +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. An excellent and well written guide to asking questions in public forums is -How To Ask -Questions The Smart Way by Eric S. Raymond. +How To Ask Questions The Smart Way +by Eric S. Raymond. There is another called -How to Report -Bugs Effectively by Simon Tatham. +How to Report Bugs Effectively +by Simon Tatham. 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. - + + + + Where to report bugs + Subscribe to the MPlayer-users mailing list: and send your bug report to where you can discuss it. + If you prefer, you can use our brand-new Bugzilla instead. + -The language of this list is English. Please follow the standard -Netiquette Guidelines and -do not send HTML mail to any of our mailing lists. You will only get ignored or +The language of this list is English. +Please follow the standard +Netiquette Guidelines +and do not send HTML mail 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 -fine document. 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. +fine document. +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. + + + + What to report + 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 @@ -193,54 +242,56 @@ 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. + + System Information + -Your Linux distribution or operating system and version e.g.: + Your Linux distribution or operating system and version e.g.: Red Hat 7.1 Slackware 7.0 + devel packs from 7.1 ... -kernel version: -uname -a + kernel version: + uname -a -libc version: -ls -l /lib/libc[.-]* + libc version: + ls -l /lib/libc[.-]* -gcc and ld versions: - + gcc and ld versions: + gcc -v -ld -v - +ld -v -binutils version: - -as --version - + binutils version: + as --version -If you have problems with fullscreen mode: + If you have problems with fullscreen mode: Window manager type and version -If you have problems with XVIDIX: + If you have problems with XVIDIX: - X colour depth: -xdpyinfo | grep "depth of root" - + + X colour depth: + xdpyinfo | grep "depth of root" + -If only the GUI is buggy: + If only the GUI is buggy: GTK version GLIB version @@ -252,23 +303,26 @@ If only the GUI is buggy: + + Hardware and drivers + -CPU info (this works on Linux only): -cat /proc/cpuinfo + CPU info (this works on Linux only): + cat /proc/cpuinfo -Video card manufacturer and model, e.g.: + Video card manufacturer and model, e.g.: ASUS V3800U chip: nVidia TNT2 Ultra pro 32MB SDRAM Matrox G400 DH 32MB SGRAM -Video driver type & version, e.g.: + Video driver type & version, e.g.: X built-in driver nVidia 0.9.623 @@ -277,7 +331,7 @@ Video driver type & version, e.g.: -Sound card type & driver, e.g.: + Sound card type & driver, e.g.: Creative SBLive! Gold with OSS driver from oss.creative.com Creative SB16 with kernel OSS drivers @@ -285,14 +339,17 @@ Sound card type & driver, e.g.: -If in doubt include lspci -vv output on Linux systems. + If in doubt include lspci -vv output on Linux systems. + + Configure problems + If you get errors while running ./configure, or autodetection of something fails, read configure.log. You may find the @@ -305,57 +362,74 @@ in your bug report. Compilation problems + Please include these files: -config.h -config.mak + config.h + config.mak + + Playback problems + -Please include the output of MPlayer at verbosity level -1, but remember to not truncate the output when +Please include the output of MPlayer at verbosity +level 1, but remember to +not truncate the output 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: -mplayer -v options filename > mplayer.log 2>&1 + +mplayer -v options filename > mplayer.log 2>&1 + -If your problem is specific to one or more files, then please upload the offender(s) to: +If your problem is specific to one or more files, +then please upload the offender(s) to: 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 +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: -dd if=yourfile of=smallfile bs=1024k count=5 -It will take the first five megabytes of 'your-file' -and write it to 'small-file'. Then try again on + +dd if=yourfile of=smallfile bs=1024k count=5 + +It will take the first five megabytes of +'your-file' and write it to +'small-file'. Then try again on this small file and if the bug still shows up your sample is sufficient for us. Please do not ever 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 exact -URL is sufficient. +file is accessible on the net, then sending the +exact URL is sufficient. + + Crashes + You have to run MPlayer inside gdb -and send us the complete output or if you have a core dump of -the crash you can extract useful information from the Core file. Here's how: +and send us the complete output or if you have a core dump +of the crash you can extract useful information from the Core file. Here's how: + How to conserve information about a reproducible crash + Recompile MPlayer with debugging code enabled: @@ -365,9 +439,11 @@ make and then run MPlayer within gdb using: gdb ./mplayer You are now within gdb. Type: -run -v options-to-mplayer filename -and reproduce your crash. As soon as you did it, gdb will return you to the command -line prompt where you have to enter + +run -v options-to-mplayer filename + +and reproduce your crash. As soon as you did it, gdb will return you to the +command line prompt where you have to enter bt disass $pc-32 $pc+32 @@ -376,8 +452,10 @@ info all-registers + How to extract meaningful information from a core dump + Create the following command file: @@ -386,30 +464,38 @@ disass $pc-32 $pc+32 info all-registers Then simply execute this command: -gdb mplayer --core=core -batch --command=command_file > mplayer.bug + +gdb mplayer --core=core -batch --command=command_file > mplayer.bug + + + + + I know what I am doing... + -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. +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. 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. -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... +manual there, you will be ignored or flamed instead of getting an appropriate +answer. 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... - diff --git a/DOCS/xml/en/bugs.xml b/DOCS/xml/en/bugs.xml index 79cbc43223..d5996c0ee6 100644 --- a/DOCS/xml/en/bugs.xml +++ b/DOCS/xml/en/bugs.xml @@ -3,147 +3,184 @@ Known bugs - Special system/CPU-specific bugs/problems + -SIGILL (signal 4) on P3 using 2.2.x kernels: -Problem: kernel 2.2.x doesn't have proper (working) SSE support -Solution: upgrade kernel to 2.4.x -Workaround: ./configure --disable-sse + SIGILL (signal 4) on P3 using 2.2.x kernels: + Problem: kernel 2.2.x doesn't have proper (working) SSE support + Solution: upgrade kernel to 2.4.x + Workaround: ./configure --disable-sse -General SIGILL (signal 4): -Problem: you compiled and run MPlayer on -different machines (for example compiled on P3 and running on Celeron) -Solution: compile MPlayer on the same machine -where you will use it! -Workaround: You can forget all this by configuring with the - option or you can -disable particular CPU instruction sets with more specific options (like -, , etc). - + General SIGILL (signal 4): + + Problem: you compiled and run MPlayer on + different machines (for example compiled on P3 and running on Celeron) + + + Solution: compile MPlayer on the same machine + where you will use it! + + + Workaround: You can forget all this by configuring with the + option or you can + disable particular CPU instruction sets with more specific options (like + , , etc). + -Crashes when dumping streams: -Problem: core dump -Solution: Don't panic. Make sure you know where your towel is. + Crashes when dumping streams: + Problem: core dump + Solution: Don't panic. Make sure you know where your towel is. + + + Various A-V sync and other audio problems -General audio delay or jerky sound (exists with all or many files) +General audio delay or jerky sound + (exists with all or many files) + -most common: buggy audio driver! - try to use different drivers, try ALSA OSS -emulation with , also try , -sometimes it helps. If your file plays fine with , then you can be sure -it's sound card (driver) problem. + most common: buggy audio driver! - try to use different drivers, try ALSA OSS + emulation with , also try , + sometimes it helps. If your file plays fine with , + then you can be sure it's sound card (driver) problem. -audio buffer problems (buffer size badly detected) -Workaround: MPlayer's option + audio buffer problems (buffer size badly detected) + + Workaround: MPlayer's option + -samplerate problems - maybe your card doesn't support the samplerate used in your -files - try the resampling filter () + samplerate problems - maybe your card doesn't support the samplerate used in + your files - try the resampling filter () -slow machine (CPU or VGA) -try with , if it plays well, then you have slow -VGA card/driver -Workaround: buy a faster card or read this documentation about how to -speed up -Also try + slow machine (CPU or VGA) + + try with , if it plays well, then you have slow + VGA card/driver + + + Workaround: buy a faster card or read this documentation about how to speed up + + Also try + Audio delay/de-sync specific to one or a few files + -bad file - -Workaround: + bad file + + Workaround: - or option (for - non-interleaved or bad files) + + or option + (for non-interleaved or bad files) + and/or - (required for files with badly - interleaved VBR audio) + + + (required for files with badly interleaved VBR audio) + and/or - or +/- - keys at runtime to adjust delay + + or +/- + keys at runtime to adjust delay + -If none of these help, please upload the file, we'll check (and fix). + If none of these help, please upload the file, we'll check (and fix). -your sound card doesn't support 48kHz playback -Workaround: buy a better sound card... or try to decrease fps by 10% (use - for a 30fps movie) or use the resample filter + your sound card doesn't support 48kHz playback + + Workaround: buy a better sound card... or try to decrease fps by 10% + (use for a 30fps movie) or use the resample filter + -slow machine (if A-V is not around 0, and the last number in the status -line increasing) -Workaround: + + slow machine (if A-V is not around 0, + and the last number in the status line increasing) + + Workaround: + No sound at all + -your file uses an unsupported audio codec -Solution: read the documentation and help us adding support for it + your file uses an unsupported audio codec + + Solution: read the documentation and help us adding support for it + + No picture at all (just plain grey/green window) + -your file uses an unsupported video codec -Solution: read the documentation and help us adding support for it + your file uses an unsupported video codec + + Solution: read the documentation and help us adding support for it + - -auto-selected codec can't decode the file, try to select another using - or options - + + auto-selected codec can't decode the file, try to select another using + or options + + Video-out problems + First note that the options , and are not supported by all drivers. Plus, not all @@ -154,18 +191,20 @@ drivers support scaling/zooming in hardware. OSD/sub flickering -x11 driver: sorry, it can't be fixed now -xv driver: use option + x11 driver: sorry, it can't be fixed now + xv driver: use option -Green image using mga_vid (<option>-vo mga</option> / <option>-vo xmga</option>) +Green image using mga_vid + (<option>-vo mga</option> / <option>-vo xmga</option>) -mga_vid misdetected your card's RAM amount, reload it using - option + + mga_vid misdetected your card's RAM amount, reload it using + option. diff --git a/DOCS/xml/en/cd-dvd.xml b/DOCS/xml/en/cd-dvd.xml index 6f54c908d4..927d7efbe3 100644 --- a/DOCS/xml/en/cd-dvd.xml +++ b/DOCS/xml/en/cd-dvd.xml @@ -14,16 +14,18 @@ make you consider changing the speed of a CD-ROM drive: -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. + 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. -Many CD-ROM drives are annoyingly loud, a lower speed may reduce the noise. + Many CD-ROM drives are annoyingly loud, a lower speed may reduce the noise. + + Linux @@ -49,28 +51,30 @@ If you have root privileges the following command may also help: 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 hdparm: +It is recommended that you also tune your CD-ROM drive +with hdparm: hdparm -d1 -a8 -u1 [cdrom device] -This enables DMA access, read-ahead, and IRQ unmasking (read the hdparm -man page for a detailed explanation). +This enables DMA access, read-ahead, and IRQ unmasking (read the +hdparm man page for a detailed explanation). -Please refer to "/proc/ide/[cdrom device]/settings" +Please refer to +"/proc/ide/[cdrom device]/settings" for fine-tuning your CD-ROM. -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 +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 Plextor SCSI drives. - + FreeBSD @@ -92,13 +96,18 @@ sysctl hw.ata.atapi_dma=1 + + DVD playback + For the complete list of available options, please read the man page. The syntax to play a standard DVD is as follows: -mplayer dvd://<track> [-dvd-device <device>] + +mplayer dvd://<track> [-dvd-device <device>] + @@ -200,12 +209,15 @@ to set the region code of your DVD drive (under Linux). + + VCD playback + -For the complete list of available options, please read the man page. The Syntax for a -standard Video CD (VCD) is as follows: +For the complete list of available options, please read the man page. The +Syntax for a standard Video CD (VCD) is as follows: mplayer vcd://<track> [-cdrom-device <device>] Example: mplayer vcd://2 -cdrom-device /dev/hdc @@ -230,50 +242,50 @@ and play the resulting file with MPlayer. VCD structure - A Video CD (VCD) is made up of CD-ROM XA sectors, i.e. CD-ROM mode 2 -form 1 and 2 tracks: - - +form 1 and 2 tracks: -The first track is in mode 2 form 2 format which means it uses L2 -error correction. The track contains an ISO-9660 filesystem with 2048 -bytes/sector. This filesystem contains VCD metadata information, as -well as still frames often used in menus. MPEG segments for menus can -also be stored in this first track, but the MPEGs have to be broken up -into a series of 150-sector chunks. The ISO-9660 filesystem may -contain other files or programs that are not essential for VCD -operation. + The first track is in mode 2 form 2 format which means it uses L2 + error correction. The track contains an ISO-9660 filesystem with 2048 + bytes/sector. This filesystem contains VCD metadata information, as + well as still frames often used in menus. MPEG segments for menus can + also be stored in this first track, but the MPEGs have to be broken up + into a series of 150-sector chunks. The ISO-9660 filesystem may + contain other files or programs that are not essential for VCD + operation. -The second and remaining tracks are generally raw 2324 bytes/sector -MPEG (movie) tracks, containing one MPEG PS data packet per -sector. These are in mode 2 form 1 format, so they store more data per -sector at the loss of some error correction. It is also legal to have -CD-DA tracks in a VCD after the first track as well. -On some operating systems there is some trickery that goes on to make -these non-ISO-9660 tracks appear in a filesystem. On other operating -systems like GNU/Linux this is not the case (yet). Here the MPEG data -cannot be mounted. As most movies are -inside this kind of track, you should try -first. + The second and remaining tracks are generally raw 2324 bytes/sector + MPEG (movie) tracks, containing one MPEG PS data packet per + sector. These are in mode 2 form 1 format, so they store more data per + sector at the loss of some error correction. It is also legal to have + CD-DA tracks in a VCD after the first track as well. + On some operating systems there is some trickery that goes on to make + these non-ISO-9660 tracks appear in a filesystem. On other operating + systems like GNU/Linux this is not the case (yet). Here the MPEG data + cannot be mounted. As most movies are + inside this kind of track, you should try + first. + -There exist VCD disks without the first track (single track and no filesystem -at all). They are still playable, but cannot be mounted. + There exist VCD disks without the first track (single track and no filesystem + at all). They are still playable, but cannot be mounted. - The definition of the Video CD standard is called the -Philips "White Book" and it is not generally available online as it -must be purchased from Philips. More detailed information about Video -CDs can be found in the -vcdimager documentation. + + The definition of the Video CD standard is called the + Philips "White Book" and it is not generally available online as it + must be purchased from Philips. More detailed information about Video + CDs can be found in the + vcdimager documentation. - + + About .DAT files @@ -287,12 +299,13 @@ 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 (vcdfs/isofs-2.4.X.o) 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 will not +driver, you can copy and even play .DAT files with +MPlayer. But it will not work with the standard iso9660 driver of the Linux kernel! Use instead. Alternatives for VCD copying are the new cdfs kernel -driver (not part of the official kernel) that shows CD sessions as image files and -cdrdao, a bit-by-bit +driver (not part of the official kernel) that shows CD sessions as image files +and cdrdao, a bit-by-bit CD grabbing/copying application. diff --git a/DOCS/xml/en/codecs.xml b/DOCS/xml/en/codecs.xml index 2a3dcebf6d..ac184f9595 100644 --- a/DOCS/xml/en/codecs.xml +++ b/DOCS/xml/en/codecs.xml @@ -22,52 +22,54 @@ The most important ones above all: MPEG-1 (VCD) and MPEG-2 (DVD) video - + native decoders for all DivX variants, 3ivX, M$ MPEG-4 v1, v2 and other MPEG-4 variants - + native decoder for Windows Media Video 7/8 (WMV1/WMV2), and Win32 DLL decoder for Windows Media Video 9 - (WMV3), both used in .wmv - files - + (WMV3), + both used in .wmv files + native Sorenson 1 (SVQ1) decoder - + native Sorenson 3 (SVQ3) decoder - + 3ivx v1, v2 decoder - + - Cinepak and Intel Indeo codecs (3.1,3.2,4.1,5.0) - + Cinepak and Intel Indeo codecs + (3.1,3.2,4.1,5.0) + MJPEG, AVID, VCR2, ASV2 and other hardware formats - + - VIVO 1.0, 2.0, I263 and other H.263(+) variants - + VIVO 1.0, 2.0, I263 and other H.263(+) + variants + FLI/FLC - + RealVideo 1.0 & 2.0 from libavcodec, and - RealVideo 3.0 & 4.0 codecs using RealPlayer - libraries - + RealVideo 3.0 & 4.0 codecs using + RealPlayer libraries + native decoder for HuffYUV - + Various old simple RLE-like formats - + @@ -76,6 +78,7 @@ please read the codec importing HOWTO and help us add support for it. + FFmpeg/libavcodec @@ -104,9 +107,9 @@ codecs please visit the FFmpeg homepage. libavcodec. Just run ./configure and compile. - + Xvid @@ -118,6 +121,7 @@ support, making it a lot more efficient than the well-known DivX codec. It yields very good video quality and good performance due to CPU optimizations for most modern processors. + It began as a forked development of the OpenDivX codec. This happened when ProjectMayo changed OpenDivX to closed source @@ -146,179 +150,196 @@ default as it offers better speed. 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 - + ./bootstrap.sh - + ./configure You may have to add some options (examine the output of ./configure --help). - + make && make install - + If you specified , copy ../../src/divx4.h to /usr/local/include/. - + Recompile MPlayer with . - + + <systemitem class="library">x264</systemitem> What is <systemitem class="library">x264</systemitem>? + - x264 - is a library for - creating H.264 video streams. - It is not 100% complete, but currently it has at least some kind - of support for most of the H.264 features which impact quality. - There are also many advanced features in the H.264 specification - which have nothing to do with video quality per se; many of these - are not yet implemented in - x264. +x264 +is a library for creating H.264 video streams. +It is not 100% complete, but currently it has at least some kind +of support for most of the H.264 features which impact quality. +There are also many advanced features in the H.264 specification +which have nothing to do with video quality per se; many of these +are not yet implemented in x264. Encoder features CAVLC/CABAC Multi-references - Intra: all macroblock types (16x16, 8x8, and 4x4 with - all predictions) - Inter P: all partitions (from 16x16 down to - 4x4) - Inter B: partitions from 16x16 down to 8x8 - (including SKIP/DIRECT) - Ratecontrol: constant quantizer, constant bitrate, - single or multipass ABR, optional VBV + + Intra: all macroblock types (16x16, 8x8, and 4x4 with all predictions) + + + Inter P: all partitions (from 16x16 down to 4x4) + + + Inter B: partitions from 16x16 down to 8x8 (including SKIP/DIRECT) + + + Ratecontrol: constant quantizer, constant bitrate, single or multipass ABR, + optional VBV + Scene cut detection Adaptive B-frame placement - B-frames as references / arbitrary frame - order + + B-frames as references / arbitrary frame order + 8x8 and 4x4 adaptive spatial transform Lossless mode Custom quantization matrices Parallel encoding of multiple slices Interlacing - + What is H.264? + - H.264 is one name for a new digital video codec jointly developed - by the ITU and MPEG. - It can also be correctly referred to by the cumbersome names of - "ISO/IEC 14496-10" or "MPEG-4 Part 10". - More frequently, it is referred to as "MPEG-4 AVC" or just "AVC". - - - Whatever you call it, H.264 may be worth trying because it can - typically match the quality of MPEG-4 ASP with 5%-30% less - bitrate. - Actual results will depend on both the source material and the - encoder. - The gains from using H.264 do not come for free: Decoding H.264 - streams seems to have steep CPU and memory requirements. - For instance, on a 1733 MHz Athlon, a DVD-resolution 1500kbps H.264 - video requires around 35% CPU to decode. - By comparison, decoding a DVD-resolution 1500kbps MPEG-4 ASP stream - requires around 10% CPU. - This means that decoding high-definition streams is almost out of - the question for most users. - It also means that even a decent DVD rip may sometimes stutter on - processors slower than 2.0 GHz or so. - - - At least with x264, - encoding requirements are not much worse than what you are used to - with MPEG-4 ASP. - For instance, on a 1733 MHz Athlon a typical DVD encode would run - at 5-15fps. - - - This document is not intended to explain the details of H.264, - but if you are interested in a brief overview, you may want to read - The H.264/AVC Advanced Video Coding Standard: Overview and Introduction to the Fidelity Range Extensions. +H.264 is one name for a new digital video codec jointly developed +by the ITU and MPEG. +It can also be correctly referred to by the cumbersome names of +"ISO/IEC 14496-10" or "MPEG-4 Part 10". +More frequently, it is referred to as "MPEG-4 AVC" or just "AVC". + + + +Whatever you call it, H.264 may be worth trying because it can typically match +the quality of MPEG-4 ASP with 5%-30% less bitrate. +Actual results will depend on both the source material and the encoder. +The gains from using H.264 do not come for free: Decoding H.264 +streams seems to have steep CPU and memory requirements. +For instance, on a 1733 MHz Athlon, a DVD-resolution 1500kbps H.264 +video requires around 35% CPU to decode. +By comparison, decoding a DVD-resolution 1500kbps MPEG-4 ASP stream +requires around 10% CPU. +This means that decoding high-definition streams is almost out of +the question for most users. +It also means that even a decent DVD rip may sometimes stutter on +processors slower than 2.0 GHz or so. + + + +At least with x264, +encoding requirements are not much worse than what you are used to +with MPEG-4 ASP. +For instance, on a 1733 MHz Athlon a typical DVD encode would run +at 5-15fps. + + + +This document is not intended to explain the details of H.264, +but if you are interested in a brief overview, you may want to read +The H.264/AVC Advanced Video Coding Standard: Overview and Introduction to the Fidelity Range Extensions. + -How can I play H.264 videos with <application>MPlayer</application>? +How can I play H.264 videos with + <application>MPlayer</application>? + - MPlayer uses - libavcodec's H.264 - decoder. - libavcodec has had at - least minimally usable H.264 decoding since around July 2004, - however major changes and improvements have been implemented since - that time, both in terms of more functionalities supported and in - terms of improved CPU usage. - Just to be certain, it is always a good idea to use a recent Subversion - checkout. +MPlayer uses +libavcodec's H.264 decoder. +libavcodec has had at +least minimally usable H.264 decoding since around July 2004, +however major changes and improvements have been implemented since +that time, both in terms of more functionalities supported and in +terms of improved CPU usage. +Just to be certain, it is always a good idea to use a recent Subversion +checkout. + - If you want a quick and easy way to know whether there have been - recent changes to libavcodec's - H.264 decoding, you might keep an eye on - FFmpeg Subversion repository's web interface. +If you want a quick and easy way to know whether there have been +recent changes to libavcodec's +H.264 decoding, you might keep an eye on +FFmpeg Subversion repository's web interface. + -How can I encode videos using <application>MEncoder</application> and <systemitem class="library">x264</systemitem>? - - If you have the subversion client installed, the latest x264 - sources can be gotten with this command: - svn co svn://svn.videolan.org/x264/trunk x264 - MPlayer sources are updated whenever - an x264 API change - occurs, so it is always suggested to use - MPlayer from Subversion as well. - Perhaps this situation will change when and if an - x264 "release" occurs. - Meanwhile, x264 should - be considered very unstable, in the sense that its programming - interface is subject to change. - - - x264 is built and - installed in the standard way: - ./configure && make && sudo make install - This installs libx264.a in /usr/local/lib and x264.h is placed in - /usr/local/include. - - With the x264 library - and header placed in the standard locations, building - MPlayer with - x264 support is easy. - Just run the standard: - ./configure && make && sudo make install - The ./configure script will autodetect that you have satisfied the - requirements for x264. +How can I encode videos using <application>MEncoder</application> + and <systemitem class="library">x264</systemitem>? + + +If you have the subversion client installed, the latest x264 +sources can be gotten with this command: +svn co svn://svn.videolan.org/x264/trunk x264 +MPlayer sources are updated whenever +an x264 API change +occurs, so it is always suggested to use +MPlayer from Subversion as well. +Perhaps this situation will change when and if an +x264 "release" occurs. +Meanwhile, x264 should +be considered very unstable, in the sense that its programming +interface is subject to change. + + + +x264 is built and +installed in the standard way: +./configure && make && sudo make install +This installs libx264.a in /usr/local/lib and x264.h is placed in +/usr/local/include. + +With the x264 library +and header placed in the standard locations, building +MPlayer with +x264 support is easy. +Just run the standard: +./configure && make && sudo make install +The ./configure script will autodetect that you have +satisfied the requirements for x264. - + + + Audio codecs @@ -328,48 +349,50 @@ default as it offers better speed. MPEG layer 1/2/3 (MP1/2/3) audio (native code, with MMX/SSE/3DNow! optimization) - + - Windows Media Audio 7 and 8 (AKA WMAv1 and WMAv2) (native code, with + Windows Media Audio 7 and 8 (AKA WMAv1 and WMAv2) + (native code, with libavcodec) - + Windows Media Audio 9 (WMAv3) (using DMO DLL) - + AC3 Dolby audio (native code, with MMX/SSE/3DNow! optimization) - + AC3 passing through sound card hardware - + AAC - + Ogg Vorbis audio codec (native library) - + RealAudio: DNET (low bitrate AC3), Cook, Sipro and ATRAC3 - + QuickTime: Qualcomm and QDesign audio codecs - + VIVO audio (g723, Vivo Siren) - + Voxware audio (using DirectShow DLL) - + alaw and ulaw, various gsm, adpcm and pcm formats and other simple old audio codecs - + Adaptive Multi-Rate (AMR) speech codecs - + + Software AC3 decoding @@ -391,9 +414,10 @@ Use the option to select the number of output channels. Use for a stereo downmix. For a 4 channel downmix (Left Front, Right Front, Left Surround and Right Surround outputs), use . In this case, any center -channel will be mixed equally to the front channels. will output all the AC3 channels as they are encoded - in the -order Left, Right, Left Surround, Right Surround, Center and LFE. +channel will be mixed equally to the front channels. + will output all the AC3 channels as they are +encoded - in the order Left, Right, Left Surround, Right Surround, Center and +LFE. @@ -409,9 +433,11 @@ also supposed to work). + Hardware AC3 decoding + You need an AC3 capable sound card, with digital out (S/PDIF). The card's driver must properly support the AFMT_AC3 format (C-Media does). Connect @@ -422,6 +448,7 @@ MPEG decoder cards. + <systemitem class="library">libmad</systemitem> support @@ -431,23 +458,27 @@ MPEG decoder cards. is a multiplatform, integer (internally 24bit PCM) only MPEG audio decoding library. It does not handle broken files well, and it sometimes has problems with seeking, but it may perform better on FPU-less -(such as ARM) platform than mp3lib. +(such as ARM) +platform than mp3lib. -If you have a proper installation of libmad, -./configure -will notice and support for MPEG audio decoding via -libmad will be built automatically. +If you have a proper installation of +libmad, +./configure will notice and support for MPEG audio +decoding via libmad will be built +automatically. + + Hardware MPEG audio codec -This codec (selected by ) passes through MPEG audio packets -to hardware decoders, such as the ones found in full-featured DVB cards +This codec (selected by ) passes through MPEG audio +packets to hardware decoders, such as the ones found in full-featured DVB cards and DXR2 adapters. Don't use it in combination with any other audio output device (such as OSS and ALSA) that isn't able to decode it (you will hear @@ -455,9 +486,11 @@ only white noise). + AAC codec + AAC (Advanced Audio Coding) is an audio codec sometimes found in MOV and MP4 files. An open source decoder called FAAD is available from @@ -470,7 +503,8 @@ beta, so you do not need to get it separately. If you use gcc 3.2 which fails to compile our internal FAAD or want to use the external library for some other reason, download the library from the download page -and pass to ./configure. +and pass +to ./configure