From aae530974747ffe340aa58e9785e9c56a2a29986 Mon Sep 17 00:00:00 2001 From: gabucino Date: Thu, 31 Oct 2002 05:07:43 +0000 Subject: fixes git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7993 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/cd-dvd.html | 78 ++++++++++++++++++++++++------------------------- DOCS/documentation.html | 2 +- 2 files changed, 40 insertions(+), 40 deletions(-) diff --git a/DOCS/cd-dvd.html b/DOCS/cd-dvd.html index da12308ee2..2f2a891f87 100644 --- a/DOCS/cd-dvd.html +++ b/DOCS/cd-dvd.html @@ -92,20 +92,20 @@

DVD structure

DVD disks use all 2048 b/s sectors 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 a mounted file system of an unencrypted DVD.

+ 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 a mounted file system of an unencrypted DVD.

The .IFO files contain the movie navigation informations (chapter/title/angle -map, language table, etc) and is needed to read and interpret the .VOB content -(movie). The .BUK files are backups of them. They use sectors everywhere, -so you need to use raw addressing of sectors of the disc to implement DVD -navigation. It's also needed to decrypt the content.

+ map, language table, etc) and is needed to read and interpret the .VOB content + (movie). The .BUK files are backups of them. They use sectors everywhere, + so you need to use raw addressing of sectors of the disc to implement DVD + navigation. It's also needed to decrypt the content.

The whole old-style DVD support with libcss needs therefore a mounted DVD -filesystem and a raw sector-based access to the device. Unfortunately you must -be root (under Linux) to get the sector address of a file. You got the -following choices:

+ filesystem and a raw sector-based access to the device. Unfortunately you must + be root (under Linux) to get the sector address of a file. You got the + following choices:

Sometimes /dev/dvd can't be read by users, so the libdvdread authors -implemented an emulation layer which transfers sector addresses to -filenames+offsets, to emulate raw access on the top of a mounted filesystem -or even on a hard disk.

+ implemented an emulation layer which transfers sector addresses to + filenames+offsets, to emulate raw access on the top of a mounted filesystem + or even on a hard disk.

libdvdread even accepts the mountpoint instead of the device name for raw -access and checks in /proc/mounts to get the device name. It was -developed for Solaris, where device names are dynamically allocated.

+ access and checks in /proc/mounts to get the device name. It was + developed for Solaris, where device names are dynamically allocated.

The default DVD device is /dev/dvd. If your setup differs, -make a symlink, or specify the correct device on the command line with the --dvd-device option.

+ make a symlink, or specify the correct device on the command line with the + -dvd-device option.

DVD authentication

@@ -146,22 +146,22 @@ make a symlink, or specify the correct device on the command line with the 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. + crypted disk key.
  • cached key: MPlayer looks for eventually already cracked title keys which are stored in the ~/.mplayer/DVDKeys directory (fast ;).
  • key: If no cached key is available, MPlayer tries to - decrypt the disk key with a set of included player keys. + decrypt the disk key with a set of included player keys.
  • disk: 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).
    • -
  • title request:With the disk key MPlayer requests the crypted title +
  • title request: With the disk key MPlayer requests the crypted title keys, which are inside hidden sectors using ioctl(). 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. + the bus and disk key.
  • title: 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 @@ -189,9 +189,9 @@ make a symlink, or specify the correct device on the command line with the

    4.3 VCD playback

    For the complete list of available options, please read the man page. -The Syntax for a standard Video CD (VCD) is as followed: -mplayer -vcd <track> [-cdrom-device <device>].
    -Example: mplayer -vcd 2 -cdrom-device /dev/hdc

    + The Syntax for a standard Video CD (VCD) is as followed: + mplayer -vcd <track> [-cdrom-device <device>].
    + Example: mplayer -vcd 2 -cdrom-device /dev/hdc

    VCD structure

    @@ -214,23 +214,23 @@ Example: mplayer -vcd 2 -cdrom-device /dev/hdc

    About .DAT files:

    The ~600 MB file visible on the first track of the mounted vcd isn't a real -file! It's a so called iso gateway, created to allow Windows to handle such -tracks (Windows doesn't 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 a 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 won't -work with the standard iso9660 driver of the kernel! It is recommended to -use the -vcd option instead. Alternate options for VCD copy are -the new cdfs kernel driver (shows CD sessions as image files) and -cdrdao (a bit-to-bit cd grabber/copier application).

    + file! It's a so called iso gateway, created to allow Windows to handle such + tracks (Windows doesn't 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 a 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 won't + work with the standard iso9660 driver of the kernel! It is recommended to + use the -vcd option instead. Alternate options for VCD copy are + the new cdfs kernel driver (shows CD sessions as image files) and + cdrdao (a bit-to-bit cd grabber/copier application).

    The default VCD device is /dev/cdrom. If your setup differs, -make a symlink, or specify the correct device on the command line with the --cdrom-device option.

    + make a symlink, or specify the correct device on the command line with the + -cdrom-device option.

    diff --git a/DOCS/documentation.html b/DOCS/documentation.html index 0b5d4abd26..9b4aa47da4 100644 --- a/DOCS/documentation.html +++ b/DOCS/documentation.html @@ -61,7 +61,7 @@
  • 2.1.1.10 FILM files
  • 2.1.1.11 RoQ files
  • 2.1.1.12 OGG/OGM files
    • -
  • 2.1.1.12 SDP files
    • +
  • 2.1.1.13 SDP files
  • 2.1.2 Audio formats -- cgit v1.2.3