.\" @(#)wodim.1	 06/12/18 Copyright 2006 Cdrkit maintainers

.\" derived from:

.\" @(#)cdrecord.1	1.106 06/02/09 Copyright 1996 J. Schilling

.\" 

.\" This program is free software; you can redistribute it and/or modify

.\" it under the terms of the GNU General Public License version 2

.\" as published by the Free Software Foundation.

.\"

.\" The GNU General Public License's references to "object code"

.\" and "executables" are to be interpreted as the output of any

.\" document formatting or typesetting system, including

.\" intermediate and printed output.

.\"

.\" This manual is distributed in the hope that it will be useful,

.\" but WITHOUT ANY WARRANTY; without even the implied warranty of

.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

.\" GNU General Public License for more details.

.\"

.\" You should have received a copy of the GNU General Public License along with

.\" this program; see the file COPYING.  If not, write to the Free Software

.\" Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

.\"

.if t .ds a \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'a

.if t .ds o \v'-0.55m'\h'0.00n'\z.\h'0.45n'\z.\v'0.55m'\h'-0.45n'o

.if t .ds u \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'u

.if t .ds A \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'A

.if t .ds O \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'O

.if t .ds U \v'-0.77m'\h'0.30n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.75n'U

.if t .ds s \\(*b

.if t .ds S SS

.if n .ds a ae

.if n .ds o oe

.if n .ds u ue

.if n .ds s sz

.if t .ds m \\(*m

.if n .ds m micro

.TH wodim 1 "Version 2.0" "" ""

.SH NAME

wodim \- write data to optical disk media

.SH SYNOPSIS

.B wodim

.RI [ options "] " track1 .\|.\|. trackn

.SH NOTE

There may be similarities and differences between this program and other disk recording application(s). See the

.B CREDITS

and

.B AUTHORS

sections below to learn about the origin of

.B wodim.

.SH DESCRIPTION

.B wodim

is used to record data or audio Compact Discs on an Orange Book

CD-Recorder or to write DVD media on a DVD-Recorder.

.PP

The

.I device

is the device file or label offered by the operating system to access the

recorder with SCSI GENERIC (sg) interface. Note that some operating systems may

provide separate device nodes for block\-oriented and sg access. For example, on

older

.I Linux

systems, the sg access was available through

.IR /dev/sg...

files while the block oriented access was done through associated (but not identical)

.IR /dev/hd...

and 

.IR /dev/sr...

(or 

.IR /dev/scd...

) files.

.PP

In any case, the user running 

.B wodim

needs read and write access to the particular device file on a Linux system. It

is recommended to be root or install the application as suid-root, because

certain versions of Linux (kernel) limit the set of SCSI commands allowed for

non-root users. Even if usage without root identity is possible in many cases,

some device drivers still may fail, show unexplainable problems and generally

the problems become harder to debug. The risk for buffer-underruns is also

increased. See the

.IR "PROCESS SCHEDULING PRIORITY"

section below for more details.

.PP

There is an alternative way of specifying the device, using the traditional SCSI descriptions in form of

.IR devicetype:bus/target/lun

specification. However, the success of this method is not guaranteed since it

requires an adaptation scheme for your architecture, and the numbers may vary

depending on the hardware-internal numbering or on the order of hot-plug device

detection. If your operating system does not provide a sufficient framework for

keeping this numbers persistent, don't rely on them. See 

.B \-scanbus

and

.B \-\-devices

options below for details.

.PP

There are emulated SCSI compatible device systems, using the SCSI protocols

transported over various hardware/media types. The most known examples is ATAPI

("IDE burners") or USB storage ("external USB case"). If the pseudo-SCSI b/t/l

device address specification is used instead of the native one, you need to

prepend the "devicetype:" description to the emulated "bus/target/lun" device

address.

.PP

If a file /etc/wodim.conf exists, the parameter to the

.B dev=

option may also be a drive name label in that file (see FILES section).

.PP

As a special exception, the device specification can be

.IR -1

or just omitted, which invokes automatic guessing of an appropriate device for

the selected operation. However, this guessing is not available everywhere and

is not reliable; it is only available for the user's convenience in simple

environments.

.PP

In 

.I Track At Once 

mode, each

.I track

corresponds to a single file that contains the prepared data for that track.

If the argument is 

.RB ` \- ',

standard input is used for that track. 

Only one track may be taken from 

.IR stdin .

In the other write modes, the direct file to track relation may not be implemented.

In 

.B \-clone

mode, a single file contains all data for the whole disk.

To allow DVD writing on platforms that do not implement large file support,

.B wodim

concatenates all file arguments to a single track when writing to DVD media.

.SH "PROCESS SCHEDULING PRIORITY"

.PP

Wodim tries to get higher process priority using different methods. This is

important because the burn process is usually a realtime task, no long delays

should occur while transmitting fresh data to the recorder. This is especially

important on systems with insufficient RAM where swapping can create delays of

many seconds.

.PP

A possible workaround on underpowered systems is the use of the burnfree or

similar feature, allowing the recorder to resume.

.PP

Root permissions are usually required to get higher process scheduling priority.

.PP

On 

.B SVr4 

compliant systems, 

.B wodim 

uses the real time class to get the highest scheduling priority that is

possible (higher than all kernel processes).

On systems with 

.B POSIX real time scheduling

wodim uses real time scheduling too, 

but may not be able to gain a priority that is higher than all kernel processes.

.PP

In order to be able to use the SCSI transport subsystem of the OS, run at highest

priority and lock itself into core

.B

wodim

either needs to be run as root, needs to be installed suid root or

must be called via

.B RBACs

pfexec mechanism.

.SH "GENERAL OPTIONS

.PP

General options must be before any track file name or track option.

.TP

.B \-version

Print version information and exit.

.TP

.B \-v

Increment the level of general verbosity by one.

This is used e.g. to display the progress of the writing process.

.TP

.B \-V

Increment the verbose level in respect of SCSI command transport by one.

This helps to debug problems

during the writing process, that occur in the CD/DVD-Recorder. 

If you get incomprehensible error messages you should use this flag

to get more detailed output.

.B \-VV

will show data buffer content in addition.

Using

.B \-V

or

.B \-VV

slows down the process and may be the reason for a buffer underrun.

.TP

.BI debug= "#, " -d

Set the misc debug value to # (with debug=#) or increment

the misc debug level by one (with -d). If you specify

.I -dd,

this equals to 

.BI debug= 2.

This may help to find problems while opening a driver for libusal

as well as with sector sizes and sector types.

Using

.B \-debug

slows down the process and may be the reason for a buffer underrun.

.TP

.BR kdebug= "#, " kd= #

Tell the 

.BR usal -driver

to modify the kernel debug value while SCSI commands are running.

.TP

.BR \-silent ", " \-s

Do not print out a status report for failed SCSI commands.

.TP

.B \-force

Force to continue on some errors. Be careful when using this option.

.B wodim

implements several checks that prevent you from doing unwanted things

like damaging CD-RW media by improper drives. Many of the sanity checks are 

disabled when the 

.B \-force

option is used.

.sp

This option also implements some tricks that will allow 

you to blank bad CD-RW disks.

.TP

.B \-immed

Tell wodim to set the

.B "SCSI IMMED"

flag in certain commands

(load/eject/blank/close_track/close_session).

This can be useful

on broken systems with ATAPI harddisk and CD/DVD writer on the same bus or

with SCSI systems that don't use disconnect/reconnect.

These systems will freeze while blanking or fixating a CD/DVD or while a DVD

writer is filling up a session to the minimum amount (approx. 800 MB).

Setting the

.B \-immed

flag will request the command to return immediately

while the operation proceeds in background, making

the bus usable for the other devices and avoiding the system freeze.

This is an experimental feature which may work or not, depending on the model

of the CD/DVD writer.

A correct solution would be to set up a correct cabling but there seem to be 

notebooks around that have been set up the wrong way by the manufacturer.

As it is impossible to fix this problem in notebooks, the

.B \-immed

option has been added.

.sp

A second experimental feature of the

.B \-immed

flag is to tell wodim to try to wait short times while writing to the

media. This is expected to free the IDE bus if the CD/DVD writer and the

data source are connected to the same IDE cable. In this case, the CD/DVD

writer would otherwise usually block the IDE bus for nearly all the time

making it impossible to fetch data from the source drive. See also

.B minbuf=

and

.B \-v

option.

.sp

Use both features at your own risk.

If it turns out that it would make sense to have a separate option

for the wait feature, write to the author and convince him.

.TP

.BI minbuf= value

The #

.B minbuf=

option allows to define the minimum drive buffer fill ratio for the

experimental ATAPI wait mode that is intended to free the IDE bus

to allow hard disk and CD/DVD writer to be on the same IDE cable.

As the wait mode currently only works when the verbose option

.B \-v

has been specified, 

.B wodim

implies the verbose option in case the 

.B \-immed

or

.B minbuf=

option have been specified.

Valid values for 

.B minbuf= 

are between 25 and 95 for 25%.\|.\|.95% minimum drive buffer fill ratio.

.TP

.B \-dummy

The CD/DVD-Recorder will go through all steps of the recording process,

but the laser is turned off during this procedure.

It is recommended to run several tests before actually writing to a 

Compact Disk or Digital Versatile Disk,

if the timing and load response of the system is not known.

.TP

.B \-clone

Tells 

.B wodim

to handle images created by

.IR "readom \-clone" .

The

.B \-clone

may only be used in conjunction with with the

.B \-raw96r

or with the

.B \-raw16

option.

Using

.B \-clone

together with

.B \-raw96r

is preferred as it allows to write all subchannel data.

The option

.B \-raw16

should only be used with drives that do not support to write in

.B \-raw96r

mode.

.TP

.B \-dao

.TP

.B \-sao

Set 

.B "SAO (Session At Once)

mode which is usually called

.BR "Disk At Once " mode.

This currently only works with MMC drives that support

.B "Session At Once

mode.

Note that wodim needs to know the size of each track in advance for this mode

(see the

.B "genisoimage \-print-size"

option and the 

.I EXAMPLES

section for more information).

.TP

.B \-tao

Set

.B "TAO (Track At Once) writing mode.

This is the default write mode in previous

.B wodim

versions.

With most drives, this write mode is required for multi session recording.

.TP

.B \-raw

Set

.B "RAW writing mode.

Using this option defaults to 

.BR \-raw96r .

Note that wodim needs to know the size of each track in advance for this mode

(see the

.B "genisoimage \-print-size"

option and the 

.I EXAMPLES

section for more information).

.TP

.B \-raw96r

Select

Set

.B "RAW writing mode

with 2352 byte sectors plus 96 bytes of raw P-W subchannel data resulting

in a sector size of 2448 bytes.

This is the preferred raw writing mode as it gives best control over the

CD writing process.

If you find any problems with the layout of a disk or with sub channel 

content (e.g. wrong times on the display when playing the CD) and your drive

supports to write in 

.B \-raw96r

or

.B \-raw16

mode, you should give it a try. There are several CD writers with bad firmware

that result in broken disks when writing in TAO or SAO mode.

Writing data disks in raw mode needs significantly more CPU time than other

write modes. If your CPU is too slow, this may result in buffer underruns.

Note that wodim needs to know the size of each track in advance for this mode

(see the

.B "genisoimage \-print-size"

option and the 

.I EXAMPLES

section for more information).

.TP

.B \-raw96p

Select

Set

.B "RAW writing mode

with 2352 byte sectors plus 96 bytes of packed P-W subchannel data resulting

in a sector size of 2448 bytes.

This is the less preferred raw writing mode as only a few recorders support

it and some of these recorders have bugs in the firmware implementation.

Don't use this mode if your recorder supports

.B \-raw96r

or

.BR \-raw16 .

Writing data disks in raw mode needs significantly more CPU time than other

write modes. If your CPU is too slow, this may result in buffer underruns.

Note that wodim needs to know the size of each track in advance for this mode

(see the

.B "genisoimage \-print-size"

option and the 

.I EXAMPLES

section for more information).

.TP

.B \-raw16

Select

Set

.B "RAW writing mode

with 2352 byte sectors plus 16 bytes of P-Q subchannel data resulting

in a sector size of 2368 bytes.

If a recorder does not support 

.BR \-raw96r ,

this is the preferred raw writing mode.

It does not allow to write

.I CD-Text

or

.I CD+Graphics

but it is the only raw writing mode in cheap CD writers.

As these cheap writers in most cases do not support

.B \-dao

mode.

Don't use this mode if your recorder supports

.BR \-raw96r .

Writing data disks in raw mode needs significantly more CPU time than other

write modes. If your CPU is too slow, this may result in buffer underruns.

Note that wodim needs to know the size of each track in advance for this mode

(see the

.B "genisoimage \-print-size"

option and the 

.I EXAMPLES

section for more information).

.TP

.B \-multi

Allow multi session CDs to be made. This flag needs to be present

on all sessions of a multi session disk,

except you want to create a session that will be 

the last session on the media.

The fixation will be done in a way that allows the CD/DVD-Recorder to

append additional sessions later. This is done by generation a TOC

with a link to the next program area. The so generated media is not

100% compatible to manufactured CDs (except for CDplus). 

Use only for recording of multi session CDs.

If this option is present, the default track type is

.BR "CD-ROM XA mode 2 form 1"

and the sector size is 2048 bytes. 

The XA sector subheaders will be created by the drive. 

The 

.I Sony 

drives have no hardware support for 

.BR "CD-ROM XA mode 2 form 1" .

You have to specify the 

.B \-data 

option in order to create multi session disks on these drives.

As long as wodim does not have a coder for converting data sectors

to audio sectors, you need to force 

.B CD-ROM

sectors by including the

.B \-data

option if you like to record a multisession disk in SAO mode.

Not all drives allow multisession CDs in SAO mode.

.TP

.B \-msinfo

Retrieve multi session info in a form suitable for 

.B genisoimage

and print it to standard output. See

.B msifile=

option for another version.

.sp

This option makes only sense with a CD that contains at least

one closed session and is appendable (not finally closed yet). 

Some drives create error messages if you try to get the multi 

session info for a disk that is not suitable for this operation.

.TP

.BR msifile= filename

Like 

.B \-msinfo

option but also stores the multi session info in a file.

.TP

.B \-toc

Retrieve and print out the table of content or PMA of a CD.

With this option, 

.B wodim

will work with CD-R drives and with CD-ROM drives.

.TP

.B \-atip

Retrieve and print out the ATIP (absolute Time in Pre-groove) info of a CD/DVD

recordable or CD/DVD re-writable media.

With this option, 

.B wodim

will try to retrieve the ATIP info. If the actual drive does not support

to read the ATIP info, it may be that only a reduced set of information

records or even nothing is displayed. Only a limited number of MMC compliant

drives support to read the ATIP info.

.sp

If 

.B wodim

is able to retrieve the lead-in start time for the first session, it will try to

decode and print the manufacturer info from the media.

DVD media does not have ATIP information but there is equivalent prerecorded

information that is read out and printed.

.TP

.B \-fix

The disk will only be fixated (i.e. a TOC for a CD-Reader will be written). 

This may be used, if for some reason the disk has been written but not

fixated. This option currently does not work with old TEAC drives (CD-R50S and

CD-R55S).

.TP

.B \-nofix

Do not fixate the disk after writing the tracks. This may be used

to create an audio disk in steps. An un-fixated disk can usually not be used

on a non CD-writer type drive but there are audio CD players that will

be able to play such a disk.

.TP

.B \-waiti

Wait for input to become available on standard input before trying to open

the SCSI driver. This allows 

.B wodim

to read its input from a pipe even

when writing additional sessions to a multi session disk.

When writing another session to a multi session disk,

.B genisoimage 

needs to read the old session from the device before writing output.

This cannot be done if

.B wodim 

opens the SCSI driver at the same time.

.TP

.B \-load

Load the media and exit. This only works with a tray loading mechanism

but seems to be useful when using the Kodak disk transporter.

.TP

.B \-lock

Load the media, lock the door and exit. This only works with a tray loading mechanism

but seems to be useful when using the Kodak disk transporter.

.TP

.B \-eject

Eject disk after doing the work.

Some devices (e.g. Philips) need to eject the medium before creating a new

disk. Doing a \-dummy test and immediately creating a real disk would not

work on these devices.

.TP

.BR speed= #

Set the speed factor of the writing process to #.

# is an integer, representing a multiple of the audio speed.

This is about 150\ KB/s for CD-ROM, about 172\ KB/s for CD-Audio and about 1385\ kB/s

for DVD media.

If no 

.I speed

option is present,

.B wodim

will try to get a drive specific speed value from the file

.B /etc/wodim.conf

and if it cannot find one, it will try to get the speed value from the

.B CDR_SPEED

environment and later from the 

.B CDR_SPEED=

entry in

.BR /etc/wodim.conf .

If no speed value could be found, wodim uses a drive specific default speed.

The default for all new (MMC compliant) drives is to use the maximum supported by the drive.

If you use 

.I "speed=0"

with a MMC compliant drive,

.B wodim

will switch to the lowest possible speed for drive and medium.

If you are using an old (non MMC) drive that has problems with

.I "speed=2 

or 

.IR "speed=4" , 

you should try 

.IR "speed=0" .

.TP

.BI blank= type

Blank a CD-RW and exit or blank a CD-RW before writing. The blanking type may be one of:

.RS

.TP 12

help

Display a list of possible blanking types.

.TP

all

Blank the entire disk. This may take a long time.

.TP

fast

Minimally blank the disk. This results in erasing the PMA, the TOC and the pregap.

.TP

track

Blank a track.

.TP

unreserve

Unreserve a reserved track.

.TP

trtail

Blank the tail of a track.

.TP

unclose

Unclose last session.

.TP

session

Blank the last session.

.RE

Not all drives support all blanking types. It may be necessary to use

.B "blank=all

if a drive reports a specified command as being invalid.

If used together with the 

.B \-force

flag, this option may be used to blank CD-RW disks that otherwise cannot be

blanked. Note that you may need to specify

.BI blank= all

because some drives will not continue with certain types of bad CD-RW

disks. Note also that

.B wodim

does its best if the 

.B \-force 

flag is used but it finally depends on the drive's firmware 

whether the blanking operation will succeed or not.

.TP

.B \-format

Format a CD-RW/DVD-RW/DVD+RW disc.

Formatting is currently only implemented for DVD+RW media.

A 'maiden' DVD+RW media needs to

be formatted before you may write to it.

However, as

.B wodim

autodetects the need for formatting in this case and auto formats the medium

before it starts writing, the

.B \-format

option is only needed if you like to forcibly reformat a DVD+RW medium.

.TP

.BR fs= #

Set the FIFO (ring buffer) size to #.

You may use the same syntax as in 

.BR dd (1),

.BR sdd (1)

or

.BR star (1).

The number representing the size is taken in bytes unless otherwise specified.

If a number is followed directly by the letter `b', `k', `m', `s' or `f',

the size is multiplied by 512, 1024, 1024*1024, 2048 or 2352.

If the size consists of numbers separated by `x' or `*', multiplication of the 

two numbers is performed.

Thus 

.I "fs=10x63k

will specify a FIFO size of 630\ kBytes.

.sp

The size specified by the 

.I fs=

argument includes the shared memory that is needed for administration. This

is at least one page of memory.

If no

.IR fs =

option is present, 

.B wodim

will try to get the FIFO size value from the 

.B CDR_FIFOSIZE

environment.

The default FIFO size is currently 4 MB.

.sp

The FIFO is used to increase buffering for the real time writing process.

It allows to run a pipe from 

.B genisoimage

directly into 

.BR wodim .

If the FIFO is active and a pipe from 

.B genisoimage

into 

.B wodim

is used to create a CD, 

.B wodim

will abort prior to do any modifications on the disk if 

.B genisoimage 

dies before it starts writing.

The recommended FIFO size is between 4 and 128\ MBytes.

As a rule of thumb, the FIFO size should be at least equal to the size

of the internal buffer of the CD/DVD-Recorder and no more than half of

the physical amount of RAM available in the machine.

If the FIFO size is big enough, the FIFO statistics will print a FIFO

empty count of zero and the FIFO min fill is not below 20%.

It is not wise to use too much space for the FIFO. If you need more

than 8 MB to write a CD at a speed less than 20x from an image on a

local file system on an idle machine, your machine is either underpowered,

has hardware problems or is mis-configured.

If you like to write DVDs or CDs at higher speed, it makes sense

to use at least 16\ MB for the FIFO.

.sp

On old and small machines, you need to be more careful with the FIFO size.

If your machine has less than 256\ MB of physical RAM, you should not

set up a FIFO size that is more than 32\ MB.

The sun4c architecture (e.g. a Sparcstation-2) has only MMU page table entries

for 16\ MBytes per process. Using more than 14\ MBytes for the FIFO

may cause the operating system in this case to spend much time to constantly

reload the MMU tables. Newer machines from Sun do not have this MMU

hardware problem. I have no information on PC-hardware reflecting

this problem.

.sp

Old Linux systems for non x86 platforms have broken definitions for

the shared memory size. You need to fix them and rebuild the kernel

or manually tell

.B wodim

to use a smaller FIFO.

.sp

If you have buffer underruns or similar problems (like a constantly empty

drive buffer) and observe a zero

.IR "fifo empty count" ,

you have hardware problems that prevents the data from flowing fast enough

from the kernel memory to the drive. The FIFO size in this case is sufficient,

but you should check for a working DMA setup.

.TP

.BR ts= #

Set the maximum transfer size for a single SCSI command to #.

The syntax for the 

.B ts=

option is the same as for wodim fs=# or sdd bs=#.

.sp

If no 

.B ts=

option has been specified,

.B wodim

defaults to a transfer size of 63\ kB. If libusal gets lower values from the

operating system, the value is reduced to the maximum value that is possible

with the current operating system.

Sometimes, it may help to further reduce the transfer size or to enhance it,

but note that it may take a long time to find a better value by experimenting

with the

.B ts=

option.

.TP

.BI dev= target

Sets the SCSI target for the CD/DVD-Recorder, see notes above.

A typical device specification is

.BI dev= 6,0

\&.

A filename or virtual device name can be passed instead of the symbolic SCSI

numbers.  The correct device/filename in this case can be found in the system

specific manuals of the target operating system.

On a 

.I FreeBSD

system without 

.I CAM

support, you need to use the control device (e.g.

.IR /dev/rcd0.ctl ).

A correct device specification in this case may be

.BI dev= /dev/rcd0.ctl:@

\&.

.sp

On Linux and Windows 2000/XP, drives are accessible with their device (or

drive) names or with the symbolic SCSI numbers (not recommended, mapping is not

stable and could be completely removed in the future).

.sp

If no 

.I dev

option is present, 

.B wodim

will try to get the device from the 

.B CDR_DEVICE

environment.

.sp

If the argument to the

.B dev=

option does not contain the characters ',', '/', '@' or ':',

it is interpreted as an label name that may be found in the file

/etc/wodim.conf (see FILES section).

.TP

.BI gracetime= #

Set the grace time before starting to write to

.IR # " seconds.

Values below 2 seconds are not recommended to give the kernel or volume

management a chance to learn the new state.

.TP

.BI timeout= #

Set the default SCSI command timeout value to 

.IR # " seconds.

The default SCSI command timeout is the minimum timeout used for sending

SCSI commands.

If a SCSI command fails due to a timeout, you may try to raise the

default SCSI command timeout above the timeout value of the failed command.

If the command runs correctly with a raised command timeout,

please report the better timeout value and the corresponding command to 

the author of the program.

If no 

.I timeout 

option is present, a default timeout of 40 seconds is used.

.TP

.BI driver= name

Allows the user to manually select a driver for the device.

The reason for the existence of the

.BI driver= name

option is to allow users to use

.B wodim

with drives that are similar to supported drives but not known

directly by

.BR wodim .

All drives made after 1997 should be MMC standard compliant and

thus supported by one of the MMC drivers.

It is most unlikely that

.B wodim

is unable to find the right driver automatically.

Use this option with extreme care. If a wrong driver is used for a

device, the possibility of creating corrupted disks is high.

The minimum problem related to a wrong driver is that the 

.B speed=

or 

.B \-dummy

will not work.

.br

.RS

.ne 8

.PP

The following driver names are supported:

.TP

.B help

To get a list of possible drivers together with a short description.

.TP

.B mmc_cd

The generic SCSI-3/mmc CD-ROM driver is auto-selected whenever

.B wodim

finds a MMC compliant drive that does not identify itself to support writing at

all, or that only identifies to support media or write modes not implemented in

.BR wodim .

.TP

.B mmc_cd_dvd

The generic SCSI-3/mmc CD/DVD driver is auto-selected whenever

.B wodim

finds a MMC-2 or MMC-3 compliant drive that seems to support more than 

one medium type and the tray is open or no medium could be found to select the

right driver.

This driver tries to close the tray, checks the medium found in the tray and then

branches to the driver that matches the current medium.

.TP

.B mmc_cdr

The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected whenever

.B wodim

find a MMC compliant drive that only supports to write CDs or a multi system

drive that contains a CD as the current medium.

.TP

.B mmc_cdr_sony

The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected whenever

.B wodim

would otherwise select the

.B mmc_cdr

driver but the device seems to be made by Sony.

The

.B mmc_cdr_sony

is definitely needed for the Sony CDU 928 as this drive does not completely

implement the MMC standard and some of the MMC SCSI commands have to be

replaced by Sony proprietary commands. It seems that all Sony drives (even

newer ones) still implement the Sony proprietary SCSI commands so it has

not yet become a problem to use this driver for all Sony drives. If you find

a newer Sony drive that does not work with this driver, please report.

.TP

.B mmc_dvd

The generic SCSI-3/mmc-2 DVD-R/DVD-RW driver is auto-selected whenever

.B wodim

finds a MMC-2 or MMC-3 compliant drive that supports to write DVDs and

an appropriate medium is loaded.

There is no Track At Once mode for DVD writers.

.TP

.B mmc_dvdplus

The generic SCSI-3/mmc-3 DVD+R/DVD+RW driver is auto-selected whenever

one of the DVD+ media types that are incompatible to each other is found.

It checks media and then 

branches to the driver that matches the current medium.

.TP

.B mmc_dvdplusr

The generic SCSI-3/mmc-3 DVD+R driver is auto-selected whenever

a DVD+R medium is found in an appropriate writer.

Note that for unknown reason, the DVD-Plus alliance does not

like that there is a simulation mode for DVD+R media.

The author of

.B wodim

tries to convince manufacturers to implement a simulation mode for DVD+R

and implement support.

DVD+R only supports one write mode that is somewhere between Track At Once

and Packet writing; this mode is selected in 

.B wodim

via a the 

.BR \-dao / \-sao

option.

.TP

.B mmc_dvdplusrw

The generic SCSI-3/mmc-3 DVD+RW driver is auto-selected whenever

a DVD+RW medium is found in an appropriate writer.

As DVD+RW media needs to be formatted before its first use, wodim

auto-detects this media state and performs a format before it starts

to write.

Note that for unknown reason, the DVD-Plus alliance does not

like that there is a simulation mode nor a way to erase DVD+RW media.

DVD+RW only supports one write mode that is close to

Packet writing; this mode is selected in 

.B wodim

via a the 

.BR \-dao / \-sao

option.