1wodim(1) wodim(1)
2
6 wodim - write data to optical disk media
7
9 wodim [ general options ] dev=device [ track options ] track1...trackn
10
13 There may be similarities and differences between this program and
14 other disk recording application(s). See the CREDITS and AUTHORS sec‐
15 tions below to learn about the origin of wodim.
16
19 wodim is used to record data or audio Compact Discs on an Orange Book
20 CD-Recorder or to write DVD media on a DVD-Recorder.
21 The device is the device file or label offered by the operating system
23 to access the recorder with SCSI GENERIC (sg) interface. Note that some
24 operating systems may provide separate device nodes for block oriented
25 and sg access. For example, on older Linux systems the sg access was
26 available trough /dev/sg... files while the block oriented access was
27 done through associated (but not identic) /dev/hd... and /dev/sr...
28 (or /dev/scd... ) files.
29 In any case, the user running wodim needs read and write access to the
31 particular device file on a Linux system. It is recommended to be root
32 or install the application as suid-root, because certain versions of
33 Linux (kernel) limit the set of SCSI commands allowed for non-root
34 users. Even if usage without root identity is possible in many cases,
35 some device drivers still may fail, show unexplainable problems and
36 generally the problems become harder to debug. The risk for buffer-
37 underruns is also increased. See the PROCESS SCHEDULING PRIORITY sec‐
38 tion below for more details.
39 There is an alternative way of specifying the device, using the tradi‐
41 tional SCSI descriptions in form of devicetype:bus/target/lun specifi‐
42 cation. However, the success of this method is not guaranteed since it
43 requires an adaptation scheme for your architecture, and the numbers
44 may vary depending on the hardware-internal numbering or on the order
45 of hot-plug device detection. If your operating system does not provide
46 a sufficient framework for keeping this numbers persistent, don't rely
47 on them. See -scanbus and --devices options below for details.
48 There are emulated SCSI compatible device systems, using the SCSI pro‐
50 tocols transported over various hardware/media types. The most known
51 examples is ATAPI ("IDE burners") or USB storage ("external USB case").
52 If the pseudo-SCSI b/t/l device address specification is used instead
53 of the native one, you need to prepend the "devicetype:" description to
54 the emulated "bus/target/lun" device address.
55 If a file /etc/wodim.conf exists, the parameter to the dev= option may
57 also be a drive name label in that file (see FILES section).
58 As a special exception, the device specification can be -1 or just
60 omited, which invokes automatic guessing of an appropriate device for
61 the selected operation. However, this guessing is not available every‐
62 where and is not reliable, it is only available for user's convinience
63 in simple environments.
64 In Track At Once mode, each track corresponds to a single file that
66 contains the prepared data for that track. If the argument is `-',
67 standard input is used for that track. Only one track may be taken
68 from stdin. In the other write modes, the direct file to track rela‐
69 tion may not be implemented. In -clone mode, a single file contains
70 all data for the whole disk. To allow DVD writing on platforms that do
71 not implement large file support, wodim concatenates all file arguments
72 to a single track when writing to DVD media.
73
76 Wodim tries to get higher process priority using different methods.
77 This is important because the burn process is usualy a realtime task,
78 no long delays should occur while transmiting fresh data to the
79 recorder. This is especially important on systems with insufficient RAM
80 where swaping can create delays of many seconds.
81 A possible workaround on underpowered systems is the use of the burn‐
83 free or similar feature, allowing the recorder to resume.
84 Root permissions are usualy required to get higher process scheduling
86 priority.
87 On SVr4 compliant systems, wodim uses the real time class to get the
89 highest scheduling priority that is possible (higher than all kernel
90 processes). On systems with POSIX real time scheduling wodim uses real
91 time scheduling too, but may not be able to gain a priority that is
92 higher than all kernel processes.
93 In order to be able to use the SCSI transport subsystem of the OS, run
95 at highest priority and lock itself into core wodim either needs to be
96 run as root, needs to be installed suid root or must be called via
97 RBACs pfexec mechanism.
98
101 General options must be before any track file name or track option.
102 -version
104 Print version information and exit.
105 -v Increment the level of general verbosity by one. This is used
107 e.g. to display the progress of the writing process.
108 -V Increment the verbose level in respect of SCSI command transport
110 by one. This helps to debug problems during the writing
111 process, that occur in the CD/DVD-Recorder. If you get incom‐
112 prehensible error messages you should use this flag to get more
113 detailed output. -VV will show data buffer content in addition.
114 Using -V or -VV slows down the process and may be the reason for
115 a buffer underrun.
116 debug=#, -d
118 Set the misc debug value to # (with debug=#) or increment the
119 misc debug level by one (with -d). If you specify -dd, this
120 equals to debug=2. This may help to find problems while opening
121 a driver for libusal as well as with sector sizes and sector
122 types. Using -debug slows down the process and may be the rea‐
123 son for a buffer underrun.
124 kdebug=#, kd=#
126 Tell the usal-driver to modify the kernel debug value while SCSI
127 commands are running.
128 -silent, -s
130 Do not print out a status report for failed SCSI commands.
131 -force Force to continue on some errors. Be careful when using this
133 option. wodim implements several checks that prevent you from
134 doing unwanted things like damaging CD-RW media by improper
135 drives. Many of the sanity checks are disabled when the -force
136 option is used.
137 This option also implements some tricks that will allow you to
139 blank bad CD-RW disks.
140 -immed Tell wodim to set the SCSI IMMED flag in certain commands
142 (load/eject/blank/close_track/close_session). This can be use‐
143 ful on broken systems with ATAPI harddisk and CD/DVD writer on
144 the same bus or with SCSI systems that don't use discon‐
145 nect/reconnect. These systems will freeze while blanking or
146 fixating a CD/DVD or while a DVD writer is filling up a session
147 to the minimum amount (approx. 800 MB). Setting the -immed flag
148 will request the command to return immediately while the opera‐
149 tion proceeds in background, making the bus usable for the other
150 devices and avoiding the system freeze. This is an experimental
151 feature which may work or not, depending on the model of the
152 CD/DVD writer. A correct solution would be to set up a correct
153 cabling but there seem to be notebooks around that have been set
154 up the wrong way by the manufacturer. As it is impossible to
155 fix this problem in notebooks, the -immed option has been added.
156 A second experimental feature of the -immed flag is to tell
158 wodim to try to wait short times while writing to the media.
159 This is expected to free the IDE bus if the CD/DVD writer and
160 the data source are connected to the same IDE cable. In this
161 case, the CD/DVD writer would otherwise usually block the IDE
162 bus for nearly all the time making it impossible to fetch data
163 from the source drive. See also minbuf= and -v option.
164 Use both features at your own risk. If it turns out that it
166 would make sense to have a separate option for the wait feature,
167 write to the author and convince him.
168 minbuf=value
170 The # minbuf= option allows to define the minimum drive buffer
171 fill ratio for the experimental ATAPI wait mode that is intended
172 to free the IDE bus to allow hard disk and CD/DVD writer to be
173 on the same IDE cable. As the wait mode currently only works
174 when the verbose option -v has been specified, wodim implies the
175 verbose option in case the -immed or minbuf= option have been
176 specified. Valid values for minbuf= are between 25 and 95 for
177 25%...95% minimum drive buffer fill ratio.
178 -dummy The CD/DVD-Recorder will go through all steps of the recording
180 process, but the laser is turned off during this procedure. It
181 is recommended to run several tests before actually writing to a
182 Compact Disk or Digital Versatile Disk, if the timing and load
183 response of the system is not known.
184 -clone Tells wodim to handle images created by readom -clone. The
186 -clone may only be used in conjunction with with the -raw96r or
187 with the -raw16 option. Using -clone together with -raw96r is
188 preferred as it allows to write all subchannel data. The option
189 -raw16 should only be used with drives that do not support to
190 write in -raw96r mode.
191 -dao
193 -sao Set SAO (Session At Once) mode which is usually called Disk At
195 Once mode. This currently only works with MMC drives that sup‐
196 port Session At Once mode. Note that wodim needs to know the
197 size of each track in advance for this mode (see the genisoimage
198 -print-size option and the EXAMPLES section for more informa‐
199 tion).
200 -tao Set TAO (Track At Once) writing mode. This is the default write
202 mode in previous wodim versions. With most drives, this write
203 mode is required for multi session recording.
204 -raw Set RAW writing mode. Using this option defaults to -raw96r.
206 Note that wodim needs to know the size of each track in advance
207 for this mode (see the genisoimage -print-size option and the
208 EXAMPLES section for more information).
209 -raw96r
211 Select Set RAW writing mode with 2352 byte sectors plus 96 bytes
212 of raw P-W subchannel data resulting in a sector size of 2448
213 bytes. This is the preferred raw writing mode as it gives best
214 control over the CD writing process. If you find any problems
215 with the layout of a disk or with sub channel content (e.g.
216 wrong times on the display when playing the CD) and your drive
217 supports to write in -raw96r or -raw16 mode, you should give it
218 a try. There are several CD writers with bad firmware that
219 result in broken disks when writing in TAO or SAO mode. Writing
220 data disks in raw mode needs significantly more CPU time than
221 other write modes. If your CPU is too slow, this may result in
222 buffer underruns. Note that wodim needs to know the size of
223 each track in advance for this mode (see the genisoimage -print-
224 size option and the EXAMPLES section for more information).
225 -raw96p
227 Select Set RAW writing mode with 2352 byte sectors plus 96 bytes
228 of packed P-W subchannel data resulting in a sector size of 2448
229 bytes. This is the less preferred raw writing mode as only a
230 few recorders support it and some of these recorders have bugs
231 in the firmware implementation. Don't use this mode if your
232 recorder supports -raw96r or -raw16. Writing data disks in raw
233 mode needs significantly more CPU time than other write modes.
234 If your CPU is too slow, this may result in buffer underruns.
235 Note that wodim needs to know the size of each track in advance
236 for this mode (see the genisoimage -print-size option and the
237 EXAMPLES section for more information).
238 -raw16 Select Set RAW writing mode with 2352 byte sectors plus 16 bytes
240 of P-Q subchannel data resulting in a sector size of 2368 bytes.
241 If a recorder does not support -raw96r, this is the preferred
242 raw writing mode. It does not allow to write CD-Text or
243 CD+Graphics but it is the only raw writing mode in cheap CD
244 writers. As these cheap writers in most cases do not support
245 -dao mode. Don't use this mode if your recorder supports
246 -raw96r. Writing data disks in raw mode needs significantly
247 more CPU time than other write modes. If your CPU is too slow,
248 this may result in buffer underruns. Note that wodim needs to
249 know the size of each track in advance for this mode (see the
250 genisoimage -print-size option and the EXAMPLES section for more
251 information).
252 -multi Allow multi session CDs to be made. This flag needs to be
254 present on all sessions of a multi session disk, except you want
255 to create a session that will be the last session on the media.
256 The fixation will be done in a way that allows the CD/DVD-
257 Recorder to append additional sessions later. This is done by
258 generation a TOC with a link to the next program area. The so
259 generated media is not 100% compatible to manufactured CDs
260 (except for CDplus). Use only for recording of multi session
261 CDs. If this option is present, the default track type is CD-
262 ROM XA mode 2 form 1 and the sector size is 2048 bytes. The XA
263 sector subheaders will be created by the drive. The Sony drives
264 have no hardware support for CD-ROM XA mode 2 form 1. You have
265 to specify the -data option in order to create multi session
266 disks on these drives. As long as wodim does not have a coder
267 for converting data sectors to audio sectors, you need to force
268 CD-ROM sectors by including the -data option if you like to
269 record a multisession disk in SAO mode. Not all drives allow
270 multisession CDs in SAO mode.
271 -msinfo
273 Retrieve multi session info in a form suitable for genisoimage
274 and print it to standard output. See msifile= option for another
275 version.
276 This option makes only sense with a CD that contains at least
278 one closed session and is appendable (not finally closed yet).
279 Some drives create error messages if you try to get the multi
280 session info for a disk that is not suitable for this operation.
281 msifile=filename
283 Like -msinfo option but also stores the multi session info in a
284 file.
285 -toc Retrieve and print out the table of content or PMA of a CD.
287 With this option, wodim will work with CD-R drives and with CD-
288 ROM drives.
289 -atip Retrieve and print out the ATIP (absolute Time in Pre-groove)
291 info of a CD/DVD recordable or CD/DVD re-writable media. With
292 this option, wodim will try to retrieve the ATIP info. If the
293 actual drive does not support to read the ATIP info, it may be
294 that only a reduced set of information records or even nothing
295 is displayed. Only a limited number of MMC compliant drives sup‐
296 port to read the ATIP info.
297 If wodim is able to retrieve the lead-in start time for the
299 first session, it will try to decode and print the manufacturer
300 info from the media. DVD media does not have ATIP information
301 but there is equivalent prerecorded information that is read out
302 and printed.
303 -fix The disk will only be fixated (i.e. a TOC for a CD-Reader will
305 be written). This may be used, if for some reason the disk has
306 been written but not fixated. This option currently does not
307 work with old TEAC drives (CD-R50S and CD-R55S).
308 -nofix Do not fixate the disk after writing the tracks. This may be
310 used to create an audio disk in steps. An un-fixated disk can
311 usually not be used on a non CD-writer type drive but there are
312 audio CD players that will be able to play such a disk.
313 -waiti Wait for input to become available on standard input before try‐
315 ing to open the SCSI driver. This allows wodim to read it's
316 input from a pipe even when writing additional sessions to a
317 multi session disk. When writing another session to a multi
318 session disk, genisoimage needs to read the old session from the
319 device before writing output. This cannot be done if wodim
320 opens the SCSI driver at the same time.
321 -load Load the media and exit. This only works with a tray loading
323 mechanism but seems to be useful when using the Kodak disk
324 transporter.
325 -lock Load the media, lock the door and exit. This only works with a
327 tray loading mechanism but seems to be useful when using the
328 Kodak disk transporter.
329 -eject Eject disk after doing the work. Some devices (e.g. Philips)
331 need to eject the medium before creating a new disk. Doing a
332 -dummy test and immediately creating a real disk would not work
333 on these devices.
334 speed=#
336 Set the speed factor of the writing process to #. # is an inte‐
337 ger, representing a multiple of the audio speed. This is about
338 150 KB/s for CD-ROM, about 172 KB/s for CD-Audio and about
339 1385 kB/s for DVD media. If no speed option is present, wodim
340 will try to get a drive specific speed value from the file
341 /etc/wodim.conf and if it cannot find one, it will try to get
342 the speed value from the CDR_SPEED environment and later from
343 the CDR_SPEED= entry in /etc/wodim.conf. If no speed value
344 could be found, wodim uses a drive specific default speed. The
345 default for all new (MMC compliant) drives is to use the maximum
346 supported by the drive. If you use speed=0 with a MMC compliant
347 drive, wodim will switch to the lowest possible speed for drive
348 and medium. If you are using an old (non MMC) drive that has
349 problems with speed=2 or speed=4, you should try speed=0.
350 blank=type
352 Blank a CD-RW and exit or blank a CD-RW before writing. The
353 blanking type may be one of:
354 help Display a list of possible blanking types.
356 all Blank the entire disk. This may take a long time.
358 fast Minimally blank the disk. This results in erasing
360 the PMA, the TOC and the pregap.
361 track Blank a track.
363 unreserve Unreserve a reserved track.
365 trtail Blank the tail of a track.
367 unclose Unclose last session.
369 session Blank the last session.
371 Not all drives support all blanking types. It may be necessary to use
372 blank=all if a drive reports a specified command as being invalid. If
373 used together with the -force flag, this option may be used to blank
374 CD-RW disks that otherwise cannot be blanked. Note that you may need to
375 specify blank=all because some drives will not continue with certain
376 types of bad CD-RW disks. Note also that wodim does it's best if the
377 -force flag is used but it finally depends on the drive's firmware
378 whether the blanking operation will succeed or not.
379 -format
381 Format a CD-RW/DVD-RW/DVD+RW disc. Formatting is currently only
382 implemented for DVD+RW media. A 'maiden' DVD+RW media needs to
383 be formatted before you may write to it. However, as wodim
384 autodetects the need for formatting in this case and auto for‐
385 mats the medium before it starts writing, the -format option is
386 only needed if you like to forcibly reformat a DVD+RW medium.
387 fs=# Set the FIFO (ring buffer) size to #. You may use the same syn‐
389 tax as in dd(1), sdd(1) or star(1). The number representing the
390 size is taken in bytes unless otherwise specified. If a number
391 is followed directly by the letter `b', `k', `m', `s' or `f',
392 the size is multiplied by 512, 1024, 1024*1024, 2048 or 2352.
393 If the size consists of numbers separated by `x' or `*', multi‐
394 plication of the two numbers is performed. Thus fs=10x63k will
395 specify a FIFO size of 630 kBytes.
396 The size specified by the fs= argument includes the shared mem‐
398 ory that is needed for administration. This is at least one page
399 of memory. If no fs= option is present, wodim will try to get
400 the FIFO size value from the CDR_FIFOSIZE environment. The
401 default FIFO size is currently 4 MB.
402 The FIFO is used to increase buffering for the real time writing
404 process. It allows to run a pipe from genisoimage directly into
405 wodim. If the FIFO is active and a pipe from genisoimage into
406 wodim is used to create a CD, wodim will abort prior to do any
407 modifications on the disk if genisoimage dies before it starts
408 writing. The recommended FIFO size is between 4 and 128 MBytes.
409 As a rule of thumb, the FIFO size should be at least equal to
410 the size of the internal buffer of the CD/DVD-Recorder and no
411 more than half of the physical amount of RAM available in the
412 machine. If the FIFO size is big enough, the FIFO statistics
413 will print a FIFO empty count of zero and the FIFO min fill is
414 not below 20%. It is not wise to use too much space for the
415 FIFO. If you need more than 8 MB to write a CD at a speed less
416 than 20x from an image on a local file system on an idle
417 machine, your machine is either underpowered, has hardware prob‐
418 lems or is mis-configured. If you like to write DVDs or CDs at
419 higher speed, it makes sense to use at least 16 MB for the FIFO.
420 On old and small machines, you need to be more careful with the
422 FIFO size. If your machine has less than 256 MB of physical
423 RAM, you should not set up a FIFO size that is more than 32 MB.
424 The sun4c architecture (e.g. a Sparcstation-2) has only MMU page
425 table entries for 16 MBytes per process. Using more than
426 14 MBytes for the FIFO may cause the operating system in this
427 case to spend much time to constantly reload the MMU tables.
428 Newer machines from Sun do not have this MMU hardware problem. I
429 have no information on PC-hardware reflecting this problem.
430 Old Linux systems for non x86 platforms have broken definitions
432 for the shared memory size. You need to fix them and rebuild the
433 kernel or manually tell wodim to use a smaller FIFO.
434 If you have buffer underruns or similar problems (like a con‐
436 stantly empty drive buffer) and observe a zero fifo empty count,
437 you have hardware problems that prevents the data from flowing
438 fast enough from the kernel memory to the drive. The FIFO size
439 in this case is sufficient, but you should check for a working
440 DMA setup.
441 ts=# Set the maximum transfer size for a single SCSI command to #.
443 The syntax for the ts= option is the same as for wodim fs=# or
444 sdd bs=#.
445 If no ts= option has been specified, wodim defaults to a trans‐
447 fer size of 63 kB. If libusal gets lower values from the operat‐
448 ing system, the value is reduced to the maximum value that is
449 possible with the current operating system. Sometimes, it may
450 help to further reduce the transfer size or to enhance it, but
451 note that it may take a long time to find a better value by
452 experimenting with the ts= option.
453 dev=target
455 Sets the SCSI target for the CD/DVD-Recorder, see notes above.
456 A typical device specification is dev=6,0 . A filename or vir‐
457 tual device name can be passed instead of the symbolic SCSI num‐
458 bers. The correct device/filename in this case can be found in
459 the system specific manuals of the target operating system. On
460 a FreeBSD system without CAM support, you need to use the con‐
461 trol device (e.g. /dev/rcd0.ctl). A correct device specifica‐
462 tion in this case may be dev=/dev/rcd0.ctl:@ .
463 On Linux and Windows 2000/XP, drives are accessible with their
465 device (or drive) names or with the symbolic SCSI numbers (not
466 recommended, mapping is not stable and could be completely
467 removed in the future).
468 If no dev option is present, wodim will try to get the device
470 from the CDR_DEVICE environment.
471 If the argument to the dev= option does not contain the charac‐
473 ters ',', '/', '@' or ':', it is interpreted as an label name
474 that may be found in the file /etc/wodim.conf (see FILES sec‐
475 tion).
476 gracetime=#
478 Set the grace time before starting to write to # seconds. Val‐
479 ues below 2 seconds are not recommended to give the kernel or
480 volume management a chance to learn the new state.
481 timeout=#
483 Set the default SCSI command timeout value to # seconds. The
484 default SCSI command timeout is the minimum timeout used for
485 sending SCSI commands. If a SCSI command fails due to a time‐
486 out, you may try to raise the default SCSI command timeout above
487 the timeout value of the failed command. If the command runs
488 correctly with a raised command timeout, please report the bet‐
489 ter timeout value and the corresponding command to the author of
490 the program. If no timeout option is present, a default timeout
491 of 40 seconds is used.
492 driver=name
494 Allows the user to manually select a driver for the device. The
495 reason for the existence of the driver=name option is to allow
496 users to use wodim with drives that are similar to supported
497 drives but not known directly by wodim. All drives made after
498 1997 should be MMC standard compliant and thus supported by one
499 of the MMC drivers. It is most unlikely that wodim is unable to
500 find the right driver automatically. Use this option with
501 extreme care. If a wrong driver is used for a device, the possi‐
502 bility of creating corrupted disks is high. The minimum problem
503 related to a wrong driver is that the speed= or -dummy will not
504 work.
505 The following driver names are supported:
507 help To get a list of possible drivers together with a short
509 description.
510 mmc_cd The generic SCSI-3/mmc CD-ROM driver is auto-selected
512 whenever wodim finds a MMC compliant drive that does not
513 identify itself to support writing at all, or that only
514 identifies to support media or write modes not imple‐
515 mented in wodim.
516 mmc_cd_dvd
518 The generic SCSI-3/mmc CD/DVD driver is auto-selected
519 whenever wodim finds a MMC-2 or MMC-3 compliant drive
520 that seems to support more than one medium type and the
521 tray is open or no medium could be found to select the
522 right driver. This driver tries to close the tray,
523 checks the medium found in the tray and then branches to
524 the driver that matches the current medium.
525 mmc_cdr
527 The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected
528 whenever wodim find a MMC compliant drive that only sup‐
529 ports to write CDs or a multi system drive that contains
530 a CD as the current medium.
531 mmc_cdr_sony
533 The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected
534 whenever wodim would otherwise select the mmc_cdr driver
535 but the device seems to be made by Sony. The
536 mmc_cdr_sony is definitely needed for the Sony CDU 928 as
537 this drive does not completely implement the MMC standard
538 and some of the MMC SCSI commands have to be replaced by
539 Sony proprietary commands. It seems that all Sony drives
540 (even newer ones) still implement the Sony proprietary
541 SCSI commands so it has not yet become a problem to use
542 this driver for all Sony drives. If you find a newer Sony
543 drive that does not work with this driver, please report.
544 mmc_dvd
546 The generic SCSI-3/mmc-2 DVD-R/DVD-RW driver is auto-
547 selected whenever wodim finds a MMC-2 or MMC-3 compliant
548 drive that supports to write DVDs and an appropriate
549 medium is loaded. There is no Track At Once mode for DVD
550 writers.
551 mmc_dvdplus
553 The generic SCSI-3/mmc-3 DVD+R/DVD+RW driver is auto-
554 selected whenever one of the DVD+ media types that are
555 incompatible to each other is found. It checks media and
556 then branches to the driver that matches the current
557 medium.
558 mmc_dvdplusr
560 The generic SCSI-3/mmc-3 DVD+R driver is auto-selected
561 whenever a DVD+R medium is found in an appropriate
562 writer. Note that for unknown reason, the DVD-Plus
563 alliance does not like that there is a simulation mode
564 for DVD+R media. The author of wodim tries to convince
565 manufacturers to implement a simulation mode for DVD+R
566 and implement support. DVD+R only supports one write
567 mode that is somewhere between Track At Once and Packet
568 writing; this mode is selected in wodim via a the
569 -dao/-sao option.
570 mmc_dvdplusrw
572 The generic SCSI-3/mmc-3 DVD+RW driver is auto-selected
573 whenever a DVD+RW medium is found in an appropriate
574 writer. As DVD+RW media needs to be formatted before
575 it's first use, wodim auto-detects this media state and
576 performs a format before it starts to write. Note that
577 for unknown reason, the DVD-Plus alliance does not like
578 that there is a simulation mode nor a way to erase DVD+RW
579 media. DVD+RW only supports one write mode that is close
580 to Packet writing; this mode is selected in wodim via a
581 the -dao/-sao option.
582 cw_7501
584 The driver for Matsushita/Panasonic CW-7501 is auto-
585 selected when wodim finds this old pre MMC drive. wodim
586 supports all write modes for this drive type.
587 kodak_pcd_600
589 The driver for Kodak PCD-600 is auto-selected when wodim
590 finds this old pre MMC drive which has been the first
591 high speed (6x) CD writer for a long time. This drive
592 behaves similar to the Philips CDD-521 drive.
593 philips_cdd521
595 The driver for Philips CDD-521 is auto-selected when
596 wodim finds a Philips CDD-521 drive (which is the first
597 CD writer ever made) or one of the other drives that are
598 known to behave similar to this drive. All Philips
599 CDD-521 or similar drives (see other drivers in this
600 list) do not support Session At Once recording.
601 philips_cdd521_old
603 The driver for Philips old CDD-521 is auto-selected when
604 wodim finds a Philips CDD-521 with very old firmware
605 which has some known limitations.
606 philips_cdd522
608 The driver for Philips CDD-522 is auto-selected when
609 wodim finds a Philips CDD-522 which is the successor of
610 the 521 or one of it's variants with Kodak label. wodim
611 does not support Session At Once recording with these
612 drives.
613 philips_dumb
615 The driver for Philips CDD-521 with pessimistic assump‐
616 tions is never auto-selected. It may be used by hand
617 with drives that behave similar to the Philips CDD-521.
618 pioneer_dws114x
620 The driver for Pioneer DW-S114X is auto-selected when
621 wodim finds one of the old non MMC CD writers from Pio‐
622 neer.
623 plasmon_rf4100
625 The driver for Plasmon RF 4100 is auto-selected when
626 wodim finds this specific variant of the Philips CDD-521.
627 ricoh_ro1060c
629 The driver for Ricoh RO-1060C is auto-selected when wodim
630 finds this drive. There is no real support for this drive
631 yet.
632 ricoh_ro1420c
634 The driver for Ricoh RO-1420C is auto-selected when wodim
635 finds a drive with this specific variant of the Philips
636 CDD-521 command set.
637 scsi2_cd
639 The generic SCSI-2 CD-ROM driver is auto-selected when‐
640 ever wodim finds a pre MMC drive that does not support
641 writing or a pre MMC writer that is not supported by
642 wodim.
643 sony_cdu924
645 The driver for Sony CDU-924 / CDU-948 is auto-selected
646 whenever wodim finds one of the old pre MMC CD writers
647 from Sony.
648 teac_cdr50
650 The driver for Teac CD-R50S, Teac CD-R55S, JVC XR-W2010,
651 Pinnacle RCD-5020 is auto-selected whenever one of the
652 drives is found that is known to the non MMC command set
653 used by TEAC and JVC. Note that many drives from JVC
654 will not work because they do not correctly implement the
655 documented command set and JVC has been unwilling to fix
656 or document the bugs. There is no support for the Ses‐
657 sion At Once write mode yet.
658 tyuden_ew50
660 The driver for Taiyo Yuden EW-50 is auto-selected when
661 wodim finds a drive with this specific variant of the
662 Philips CDD-521 command set.
663 yamaha_cdr100
665 The driver for Yamaha CDR-100 / CDR-102 is auto-selected
666 when wodim finds one of the old pre MMC CD writers from
667 Yamaha. There is no support for the Session At Once
668 write mode yet.
669 cdr_simul
671 The simulation CD-R driver allows to run timing and speed
672 tests with parameters that match the behavior of CD writ‐
673 ers.
674 dvd_simul
676 The simulation DVD-R driver allows to run timing and
677 speed tests with parameters that match the behavior of
678 DVD writers.
679 There are two special driver entries in the list: cdr_simul and
681 dvd_simul. These driver entries are designed to make timing
682 tests at any speed or timing tests for drives that do not sup‐
683 port the -dummy option. The simulation drivers implement a
684 drive with a buffer size of 1 MB that can be changed via the
685 CDR_SIMUL_BUFSIZE environment variable. The simulation driver
686 correctly simulates even a buffer underrun condition. If the
687 -dummy option is present, the simulation is not aborted in case
688 of a buffer underrun.
689 driveropts=option list
691 Set driver specific options. The options are specified a comma
692 separated list. To get a list of valid options use
693 driveropts=help together with the -checkdrive option. If you
694 like to set driver options without running a typical wodim task,
695 you need to use the -setdropts option in addition, otherwise the
696 command line parser in wodim will complain. Currently imple‐
697 mented driver options are:
698 burnfree
700 Turn the support for Buffer Underrun Free writing on.
701 This only works for drives that support Buffer Underrun
702 Free technology, which is available on most drives manu‐
703 factured in this millenium. This may be called: Sanyo
704 BURN-Proof, Ricoh Just-Link, Yamaha Lossless-Link or sim‐
705 ilar.
706 This option is deprecated and is mentioned here for docu‐
708 mentation purposes only. The BURN-Free feature is enabled
709 by default if the drive supports it. However, use of
710 BURN-Free may cause decreased burning quality. Therefore
711 it can be useful to disable it for certain purposes, eg.
712 when creating a master copy for mass CD production.
713 noburnfree
715 Turn the support for Buffer Underrun Free writing off.
716 varirec=value
718 Turn on the Plextor VariRec writing mode. The mandatory
719 parameter value is the laser power offset and currently
720 may be selected from -2, -1, 0, 1, 2. In addition, you
721 need to set the write speed to 4 in order to allow
722 VariRec to work.
723 gigarec=value
725 Manage the Plextor GigaRec writing mode. The mandatory
726 parameter value is the disk capacity ratio compared to
727 normal recording and currently may be selected from 0.6,
728 0.7, 0.8, 1.0, 1.2, 1.3, 1.4. If values < 1.0 are used,
729 then the effect is similar to the Yamaha Audio Master Q.
730 R. feature. If values > 1.0 are used, then the disk
731 capacity is increased.
732 Not all drives support all GigaRec values. When a drive
734 uses the GigaRec feature, the write speed is limited to
735 8x.
736 audiomaster
738 Turn on the Yamaha Audio Master Q. R. feature which usu‐
739 ally should result in high quality CDs that have less
740 reading problems in Hi-Fi players. As this is imple‐
741 mented as a variant of the Session at Once write mode, it
742 will only work if you select SAO write mode and there is
743 no need to turn it off. The Audio Master mode will work
744 with a limited speed but may also be used with data CDs.
745 In Audio Master mode, the pits on the CD will be written
746 larger then usual so the capacity of the medium is
747 reduced when turning this feature on. A 74 minute CD
748 will only have a capacity of 63 minutes if Audio Master
749 is active and the capacity of a 80 minute CD will be
750 reduced to 68 minutes.
751 forcespeed
753 Normally, modern drives know the highest possible speed
754 for different media and may reduce the speed in order to
755 grant best write quality. This technology may be called:
756 Plextor PowerRec, Ricoh Just-Speed, Yamaha Optimum Write
757 Speed Control or similar. Some drives (e.g. Plextor,
758 Ricoh and Yamaha) allow to force the drive to use the
759 selected speed even if the medium is so bad that the
760 write quality would be poor. This option tells such a
761 drive to force to use the selected speed regardless of
762 the medium quality.
763 Use this option with extreme care and note that the drive
765 should know better which medium will work at full speed.
766 The default is to turn forcespeed off, regardless of the
767 defaults of the drive.
768 noforcespeed
770 Turn off the force speed feature.
771 speedread
773 Some ultra high speed drives such as 48x and faster
774 drives from Plextor limit the read speed for unknown
775 media to e.g. 40x in order to avoid damaged disks and
776 drives. Using this option tells the drive to read any
777 media as fast as possible. Be very careful as this may
778 cause the media to break in the drive while reading,
779 resulting in a damaged media and drive!
780 nospeedread
782 Turn off unlimited read speed.
783 singlesession
785 Turn the drive into a single session only drive. This
786 allows to read defective or non-compliant (illegal) media
787 with extremely non-standard additional (broken/illegal)
788 TOC entries in the TOC from the second or higher session.
789 Some of these disks become usable if only the information
790 from the first session is used. You need to enable Sin‐
791 gle Session mode before you insert the defective disk!
792 nosinglesession
794 Turn off single session mode. The drive will again behave
795 as usual.
796 hidecdr
798 Hide the fact that a medium might be a recordable medium.
799 This allows to make CD-Rs look like CD-ROMs and applica‐
800 tions believe that the media in the drive is not a CD-R.
801 nohidecdr
803 Turn off hiding CD-R media.
804 tattooinfo
806 Use this option together with -checkdrive to retrieve the
807 image size information for the Yamaha DiskT@2 feature.
808 The images always have a line length of 3744 pixel. Line
809 number 0 (radius 0) is mapped to the center of the disk.
810 If you know the inner and outer radius you will be able
811 to create a pre distorted image that later may appear
812 undistorted on the disk.
813 tattoofile=name
815 Use this option together with -checkdrive to write an
816 image prepared for the Yamaha DiskT@2 feature to the
817 medium. The file must be a file with raw image B&W data
818 (one byte per pixel) in a size as retrieved by a previous
819 call to tattoofile=name . If the size of the image
820 equals the maximum possible size (3744 x 320 pixel),
821 wodim will use the first part of the file. This first
822 part then will be written to the leftover space on the
823 CD.
824 Note that the image must be mirrored to be readable from
826 the pick up side of the CD.
827 -setdropts
829 Set the driveropts specified by driveropts=option list, the
830 speed of the drive and the dummy flag and exit. This allows
831 wodim to set drive specific parameters that are not directly
832 used by wodim like e.g. single session mode, hide cdr and simi‐
833 lar. It is needed in case that driveropts=option list should be
834 called without planning to run a typical wodim task.
835 -checkdrive
837 Checks if a driver for the current drive is present and exit.
838 If the drive is a known drive, wodim uses exit code 0.
839 -prcap Print the drive capabilities for SCSI-3/mmc compliant drives as
841 obtained from mode page 0x2A. Values marked with kB use 1000
842 bytes as kilo-byte, values marked with KB use 1024 bytes as
843 Kilo-byte.
844 -inq Do an inquiry for the drive, print the inquiry info and exit.
846 -scanbus
848 Scan all SCSI devices on all SCSI busses and print the inquiry
849 strings. This option may be used to find SCSI address of the
850 CD/DVD-Recorder on a system. If some device types are invisible,
851 try using dev=ATA: or similar option to give a hint about the
852 device typ you are looking for. The numbers printed out as
853 labels are computed by: bus * 100 + target. On plattforms and
854 device systems without persistent SCSI number management the
855 results are not reliable. Use the .B --devices option instead.
856 --devices
858 Look for useable devices using the system specific functions,
859 eg. probing with usual device nodes in /dev/*, and display the
860 detections using symbolic device names in OS specific syntax.
861 -reset Try to reset the SCSI bus where the CD recorder is located. This
863 works not on all operating systems.
864 -abort Try to send an abort sequence to the drive. If you use wodim
866 only, this should never be needed; but other software may leave
867 a drive in an unusable condition. Calling wodim -reset may be
868 needed if a previous write has been interrupted and the software
869 did not tell the drive that it will not continue to write.
870 -overburn
872 Allow wodim to write more than the official size of a medium.
873 This feature is usually called overburning and depends on the
874 fact that most blank media may hold more space than the official
875 size. As the official size of the lead-out area on the disk is
876 90 seconds (6750 sectors) and a disk usually works if there are
877 at least 150 sectors of lead out, all media may be overburned by
878 at least 88 seconds (6600 sectors). Most CD recorders only do
879 overburning in SAO or RAW mode. Known exceptions are TEAC CD-
880 R50S, TEAC CD-R55S and the Panasonic CW-7502. Some drives do
881 not allow to overburn as much as you might like and limit the
882 size of a CD to e.g. 76 minutes. This problem may be circum‐
883 vented by writing the CD in RAW mode because this way the drive
884 has no chance to find the size before starting to burn. There
885 is no guarantee that your drive supports overburning at all.
886 Make a test to check if your drive implements the feature.
887 -ignsize
889 Ignore the known size of the medium. This option should be used
890 with extreme care, it exists only for debugging purposes don't
891 use it for other reasons. It is not needed to write disks with
892 more than the nominal capacity. This option implies -overburn.
893 -useinfo
895 Use *.inf files to overwrite audio options. If this option is
896 used, the pregap size information is read from the *.inf file
897 that is associated with the file that contains the audio data
898 for a track.
899 If used together with the -audio option, wodim may be used to
901 write audio CDs from a pipe from icedax if you call wodim with
902 the *.inf files as track parameter list instead of using audio
903 files. The audio data is read from stdin in this case. See
904 EXAMPLES section below. wodim first verifies that stdin is not
905 connected to a terminal and runs some heuristic consistency
906 checks on the *.inf files and then sets the track lengths from
907 the information in the *.inf files.
908 If you like to write from stdin, make sure that wodim is called
910 with a large enough FIFO size, reduce the write speed to a value
911 below the read speed of the source drive and switch the burn-
912 free option for the recording drive on.
913 defpregap=#
915 Set the default pre-gap size for all tracks except track number
916 1. This option currently only makes sense with the TEAC drive
917 when creating track-at-once disks without the 2 second silence
918 before each track.
919 This option may go away in future.
920 -packet
922 Set Packet writing mode. This is an experimental interface.
923 pktsize=#
925 Set the packet size to #, forces fixed packet mode. This is an
926 experimental interface.
927 -noclose
929 Do not close the current track, useful only when in packet writ‐
930 ing mode. This is an experimental interface.
931 mcn=med_cat_nr
933 Set the Media Catalog Number of the CD to med_cat_nr.
934 -text Write CD-Text information based on information taken from a file
936 that contains ascii information for the text strings. wodim
937 supports CD-Text information based on the content of the *.inf
938 files created by icedax and CD-Text information based on the
939 content from a CUE sheet file. If a CUE sheet file contains
940 both (binary CDTEXTFILE and text based SONGWRITER) entries, then
941 the information based on the CDTEXTFILE entry will win.
942 You need to use the -useinfo option in addition in order to tell
944 wodim to read the *.inf files or cuefile=filename in order to
945 tell wodim to read a CUE sheet file in addition. If you like to
946 write your own CD-Text information, edit the *.inf files or the
947 CUE sheet file with a text editor and change the fields that are
948 relevant for CD-Text.
949 textfile=filename
951 Write CD-Text based on information found in the binary file
952 filename. This file must contain information in a data format
953 defined in the SCSI-3 MMC-2 standard and in the Red Book. The
954 four byte size header that is defined in the SCSI standard is
955 optional and allows to make the recognition of correct data less
956 ambiguous. This is the best option to be used to copy CD-Text
957 data from existing CDs that already carry CD-Text information.
958 To get data in a format suitable for this option use wodim -vv
959 -toc to extract the information from disk. If both,
960 textfile=filename and CD-Text information from *.inf or *.cue
961 files are present, textfile=filename will overwrite the other
962 information.
963 cuefile=filename
965 Take all recording related information from a CDRWIN compliant
966 CUE sheet file. No track files are allowed when this option is
967 present and the option -dao is currently needed in addition.
968
971 Track options may be mixed with track file names.
972 isrc=ISRC_number
974 Set the International Standard Recording Number for the next
975 track to ISRC_number.
976 index=list
978 Sets an index list for the next track. In index list is a comma
979 separated list of numbers that are counting from index 1. The
980 first entry in this list must contain a 0, the following numbers
981 must be an ascending list of numbers (counting in 1/75 seconds)
982 that represent the start of the indices. An index list in the
983 form: 0,7500,15000 sets index 1 to the start of the track, index
984 2 100 seconds from the start of the track and index 3 200 sec‐
985 onds from the start of the track.
986 -audio If this flag is present, all subsequent tracks are written in
988 CD-DA (similar to Red Book) audio format. The file with data
989 for this tracks should contain stereo, 16-bit digital audio with
990 44100 samples/s. The byte order should be the following: MSB
991 left, LSB left, MSB right, LSB right, MSB left and so on. The
992 track should be a multiple of 2352 bytes. It is not possible to
993 put the master image of an audio track on a raw disk because
994 data will be read in multiple of 2352 bytes during the recording
995 process.
996 If a filename ends in .au or .wav the file is considered to be a
998 structured audio data file. wodim assumes that the file in this
999 case is a Sun audio file or a Microsoft .WAV file and extracts
1000 the audio data from the files by skipping over the non-audio
1001 header information. In all other cases, wodim will only work
1002 correctly if the audio data stream does not have any header.
1003 Because many structured audio files do not have an integral num‐
1004 ber of blocks (1/75th second) in length, it is often necessary
1005 to specify the -pad option as well. wodim recognizes that audio
1006 data in a .WAV file is stored in Intel (little-endian) byte
1007 order, and will automatically byte-swap the data if the CD
1008 recorder requires big-endian data. wodim will reject any audio
1009 file that does not match the Red Book requirements of 16-bit
1010 stereo samples in PCM coding at 44100 samples/second.
1011 Using other structured audio data formats as input to wodim will
1013 usually work if the structure of the data is the structure
1014 described above (raw pcm data in big-endian byte order). How‐
1015 ever, if the data format includes a header, you will hear a
1016 click at the start of a track.
1017 If neither -data nor -audio have been specified, wodim defaults
1019 to -audio for all filenames that end in .au or .wav and to -data
1020 for all other files.
1021 -swab If this flag is present, audio data is assumed to be in byte-
1023 swapped (little-endian) order. Some types of CD-Writers e.g.
1024 Yamaha, Sony and the new SCSI-3/mmc drives require audio data to
1025 be presented in little-endian order, while other writers require
1026 audio data to be presented in the big-endian (network) byte
1027 order normally used by the SCSI protocol. wodim knows if a CD-
1028 Recorder needs audio data in big- or little-endian order, and
1029 corrects the byte order of the data stream to match the needs of
1030 the recorder. You only need the -swab flag if your data stream
1031 is in Intel (little-endian) byte order.
1032 Note that the verbose output of wodim will show you if swapping
1034 is necessary to make the byte order of the input data fit the
1035 required byte order of the recorder. wodim will not show you if
1036 the -swab flag was actually present for a track.
1037 -data If this flag is present, all subsequent tracks are written in
1039 CD-ROM mode 1 (Yellow Book) format. The data size is a multiple
1040 of 2048 bytes. The file with track data should contain an
1041 ISO-9660 or Rock Ridge filesystem image (see genisoimage for
1042 more details). If the track data is an ufs filesystem image,
1043 fragment size should be set to 2 KB or more to allow CD-drives
1044 with 2 KB sector size to be used for reading.
1045 -data is the default, if no other flag is present and the file
1047 does not appear to be of one of the well known audio file types.
1048 If neither -data nor -audio have been specified, wodim defaults
1050 to -audio for all filenames that end in .au or .wav and to -data
1051 for all other files.
1052 -mode2 If this flag is present, all subsequent tracks are written in
1054 CD-ROM mode 2 format. The data size is a multiple of 2336 bytes.
1055 -xa If this flag is present, all subsequent tracks are written in
1057 CD-ROM XA mode 2 form 1 format. The data size is a multiple of
1058 2048 bytes. The XA sector sub headers will be created by the
1059 drive. With this option, the write mode is the same as with the
1060 -multi option.
1061 -xa1 If this flag is present, all subsequent tracks are written in
1063 CD-ROM XA mode 2 form 1 format. The data size is a multiple of
1064 2056 bytes. The XA sector sub headers are part of the user data
1065 and have to be supplied by the application that prepares the
1066 data to be written.
1067 -xa2 If this flag is present, all subsequent tracks are written in
1069 CD-ROM XA mode 2 form 2 format. The data is a multiple of 2324
1070 bytes. The XA sector sub headers will be created by the drive.
1071 -xamix If this flag is present, all subsequent tracks are written in a
1073 way that allows a mix of CD-ROM XA mode 2 form 1/2 format. The
1074 data size is a multiple of 2332 bytes. The XA sector sub head‐
1075 ers are part of the user data and have to be supplied by the
1076 application that prepares the data to be written. The CRC and
1077 the P/Q parity ECC/EDC information (depending on the sector
1078 type) have to be supplied by the application that prepares the
1079 data to be written.
1080 -cdi If this flag is present, the TOC type for the disk is set to
1082 CDI. This only makes sense with XA disks.
1083 -isosize
1085 Use the ISO-9660 file system size as the size of the next track.
1086 This option is needed if you want wodim to directly read the
1087 image of a track from a raw disk partition or from a TAO master
1088 CD. In the first case the option -isosize is needed to limit the
1089 size of the CD to the size of the ISO filesystem. In the second
1090 case the option -isosize is needed to prevent wodim from reading
1091 the two run out blocks that are appended by each CD-recorder in
1092 track at once mode. These two run out blocks cannot be read and
1093 would cause a buffer underrun that would cause a defective copy.
1094 Do not use this option on files created by genisoimage and in
1095 case wodim reads the track data from stdin. In the first case,
1096 you would prevent wodim from writing the amount of padding that
1097 has been appended by genisoimage and in the latter case, it will
1098 not work because stdin is not seekable.
1099 If -isosize is used for a track, wodim will automatically add
1101 padding for this track as if the -pad option has been used but
1102 the amount of padding may be less than the padding written by
1103 genisoimage. Note that if you use -isosize on a track that con‐
1104 tains Sparc boot information, the boot information will be lost.
1105 Note also that this option cannot be used to determine the size
1107 of a file system if the multi session option is present.
1108 -pad If the track is a data track, 15 sectors of zeroed data will be
1110 added to the end of this and each subsequent data track. In
1111 this case, the -pad option is superseded by the padsize= option.
1112 It will remain however as a shorthand for padsize=15s. If the
1113 -pad option refers to an audio track, wodim will pad the audio
1114 data to be a multiple of 2352 bytes. The audio data padding is
1115 done with binary zeroes which is equal to absolute silence.
1116 -pad remains valid until disabled by -nopad.
1118 padsize=#
1120 Set the amount of data to be appended as padding to the next
1121 track to #. Opposed to the behavior of the -pad option, the
1122 value for padsize= is reset to zero for each new track. wodim
1123 assumes a sector size of 2048 bytes for the padsize= option,
1124 independent from the real sector size and independent from the
1125 write mode. The megabytes mentioned in the verbose mode output
1126 however are counting the output sector size which is e.g. 2448
1127 bytes when writing in RAW/RAW96 mode. See fs= option for possi‐
1128 ble arguments. To pad the equivalent of 20 minutes on a CD, you
1129 may write padsize=20x60x75s. Use this option if your CD-drive
1130 is not able to read the last sectors of a track or if you want
1131 to be able to read the CD on a Linux system with the ISO-9660
1132 filesystem read ahead bug. If an empty file is used for track
1133 data, this option may be used to create a disk that is entirely
1134 made of padding. This may e.g. be used to find out how much
1135 overburning is possible with a specific media.
1136 -nopad Do not pad the following tracks - the default.
1138 -shorttrack
1140 Allow all subsequent tracks to violate the Red Book track length
1141 standard which requires a minimum track length of 4 seconds.
1142 This option is only useful when used in SAO or RAW mode. Not
1143 all drives support this feature. The drive must accept the
1144 resulting CUE sheet or support RAW writing.
1145 -noshorttrack
1147 Re-enforce the Red Book track length standard. Tracks must be at
1148 least 4 seconds.
1149 pregap=#
1151 Set the pre-gap size for the next track. This option currently
1152 only makes sense with the TEAC drive when creating track-at-once
1153 disks without the 2 second silence before each track.
1154 This option may go away in future.
1155 -preemp
1157 If this flag is present, all TOC entries for subsequent audio
1158 tracks will indicate that the audio data has been sampled with
1159 50/15 microsec pre-emphasis. The data, however is not modified
1160 during the process of transferring from file to disk. This
1161 option has no effect on data tracks.
1162 -nopreemp
1164 If this flag is present, all TOC entries for subsequent audio
1165 tracks will indicate that the audio data has been mastered with
1166 linear data - this is the default.
1167 -copy If this flag is present, all TOC entries for subsequent audio
1169 tracks of the resulting CD will indicate that the audio data has
1170 permission to be copied without limit. This option has no
1171 effect on data tracks.
1172 -nocopy
1174 If this flag is present, all TOC entries for subsequent audio
1175 tracks of the resulting CD will indicate that the audio data has
1176 permission to be copied only once for personal use - this is the
1177 default.
1178 -scms If this flag is present, all TOC entries for subsequent audio
1180 tracks of the resulting CD will indicate that the audio data has
1181 no permission to be copied anymore.
1182 tsize=#
1184 If the master image for the next track has been stored on a raw
1185 disk, use this option to specify the valid amount of data on
1186 this disk. If the image of the next track is stored in a regular
1187 file, the size of that file is taken to determine the length of
1188 this track. If the track contains an ISO 9660 filesystem image
1189 use the -isosize option to determine the length of that filesys‐
1190 tem image.
1191 In Disk at Once mode and with some drives that use the TEAC pro‐
1192 gramming interface, even in Track at Once mode, wodim needs to
1193 know the size of each track before starting to write the disk.
1194 wodim now checks this and aborts before starting to write. If
1195 this happens you will need to run genisoimage -print-size before
1196 and use the output (with `s' appended) as an argument to the
1197 tsize= option of wodim (e.g. tsize=250000s).
1198 See fs= option for possible arguments.
1199
1202 For all examples below, it will be assumed that the CD/DVD-Recorder is
1203 connected to the primary SCSI bus of the machine. The SCSI target id is
1204 set to 2.
1205 To record a pure CD-ROM at double speed, using data from the file cdim‐
1207 age.raw:
1208 wodim -v speed=2 dev=2,0 cdimage.raw
1210 To create an image for a ISO 9660 filesystem with Rock Ridge exten‐
1212 sions:
1213 genisoimage -R -o cdimage.raw /home/joerg/master/tree
1215 To check the resulting file before writing to CD on Solaris:
1217 mount -r -F fbk -o type=hsfs /dev/fbk0:cdimage.raw /mnt
1219 On Linux:
1221 mount cdimage.raw -r -t iso9660 -o loop /mnt
1223 Go on with:
1225 ls -lR /mnt
1226 umount /mnt
1227 If the overall speed of the system is sufficient and the structure of
1229 the filesystem is not too complex, wodim will run without creating an
1230 image of the ISO 9660 filesystem. Simply run the pipeline:
1231 genisoimage -R /master/tree | wodim -v fs=6m speed=2 dev=2,0 -
1233 The recommended minimum FIFO size for running this pipeline is 4
1235 MBytes. As the default FIFO size is 4 MB, the fs= option needs only be
1236 present if you want to use a different FIFO size. If your system is
1237 loaded, you should run genisoimage in the real time class too. To
1238 raise the priority of genisoimage replace the command
1239 genisoimage -R /master/tree
1241 by
1242 priocntl -e -c RT -p 59 genisoimage -R /master/tree
1243 on Solaris and by
1245 nice --18 genisoimage -R /master/tree
1247 on systems that don't have UNIX International compliant real-time
1249 scheduling.
1250 wodim runs at priority 59 on Solaris, you should run genisoimage at no
1252 more than priority 58. On other systems, you should run genisoimage at
1253 no less than nice --18.
1254 Creating a CD-ROM without file system image on disk has been tested on
1256 a Sparcstation-2 with a Yamaha CDR-400. It did work up to quad speed
1257 when the machine was not loaded. A faster machine may be able to han‐
1258 dle quad speed also in the loaded case.
1259 To record a pure CD-DA (audio) at single speed, with each track con‐
1261 tained in a file named track01.cdaudio, track02.cdaudio, etc:
1262 wodim -v speed=1 dev=/dev/cdrw -audio track*.cdaudio
1264 To check if it will be ok to use double speed for the example above.
1266 Use the dummy write option:
1267 wodim -v -dummy speed=2 dev=/dev/cdrw -audio track*.cdaudio
1269 To record a mixed-mode CD with an ISO 9660 filesystem from cdimage.raw
1271 on the first track, the other tracks being audio tracks from the files
1272 track01.cdaudio, track02.cdaudio, etc:
1273 wodim -v dev=2,0 cdimage.raw -audio track*.cdaudio
1275 To handle drives that need to know the size of a track before starting
1277 to write, first run
1278 genisoimage -R -q -print-size /master/tree
1280 and then run
1282 genisoimage -R /master/tree | wodim speed=2 dev=2,0 tsize=XXXs -
1284 where XXX is replaced by the output of the previous run of genisoimage.
1286 To copy an audio CD in the most accurate way, first run
1288 icedax dev=/dev/cdrom -vall cddb=0 -B -Owav
1290 and then run
1292 wodim dev=/dev/cdrw -v -dao -useinfo -text *.wav
1294 This will try to copy track indices and to read CD-Text information
1296 from disk. If there is no CD-Text information, icedax will try to get
1297 the information from freedb.org instead.
1298 To copy an audio CD from a pipe (without intermediate files), first run
1300 icedax dev=1,0 -vall cddb=0 -info-only
1302 and then run
1304 icedax dev=1,0 -no-infofile -B -Oraw - | \
1306 wodim dev=2,0 -v -dao -audio -useinfo -text *.inf
1307 This will get all information (including track size info) from the
1309 *.inf files and then read the audio data from stdin.
1310 If you like to write from stdin, make sure that wodim is called with a
1312 large enough FIFO size (e.g. fs=128m), reduce the write speed to a
1313 value below the read speed of the source drive (e.g. speed=12), and
1314 get a CD/DVD drive with BURN-Free feature if it is not available yet.
1315 To set drive options without writing a CD (e.g. to switch a drive to
1317 single session mode), run
1318 wodim dev=1,0 -setdropts driveropts=singlesession
1320 If you like to do this when no CD is in the drive, call
1322 wodim dev=1,0 -force -setdropts driveropts=singlesession
1324 To copy a CD in clone mode, first read the master CD using:
1326 readom dev=b,t,l -clone f=somefile
1328 or (in case the CD contains many sectors that are unreadable by inten‐
1330 tion) by calling:
1331 readom dev=1,0 -clone -nocorr f=somefile
1333 will create the files somefile and somefile.toc. Then write the CD
1335 using:
1336 wodim dev=1,0 -raw96r -clone -v somefile
1338
1342 CDR_DEVICE
1343 This may either hold a device identifier that is suitable to the
1344 open call of the SCSI transport library or a label in the file
1345 /etc/wodim.conf.
1346 CDR_SPEED
1348 Sets the default speed value for writing (see also speed=
1349 option).
1350 CDR_FIFOSIZE
1352 Sets the default size of the FIFO (see also fs=# option).
1353 CDR_FORCERAWSPEED
1355 If this environment variable is set, wodim will allow you to
1356 write at the full RAW encoding speed a single CPU supports.
1357 This will create high potential of buffer underruns. Use with
1358 care.
1359 CDR_FORCESPEED
1361 If this environment variable is set, wodim will allow you to
1362 write at the full DMA speed the system supports. There is no
1363 DMA reserve for reading the data that is to be written from
1364 disk. This will create high potential of buffer underruns. Use
1365 with care.
1366 RSH If the RSH environment is present, the remote connection will
1368 not be created via rcmd(3) but by calling the program pointed to
1369 by RSH. Use e.g. RSH=/usr/bin/ssh to create a secure shell
1370 connection.
1371 Note that this forces wodim to create a pipe to the rsh(1) pro‐
1373 gram and disallows wodim to directly access the network socket
1374 to the remote server. This makes it impossible to set up per‐
1375 formance parameters and slows down the connection compared to a
1376 root initiated rcmd(3) connection.
1377 RSCSI If the RSCSI environment is present, the remote SCSI server will
1379 not be the program /opt/schily/sbin/rscsi but the program
1380 pointed to by RSCSI. Note that the remote SCSI server program
1381 name will be ignored if you log in using an account that has
1382 been created with a remote SCSI server program as login shell.
1383
1386 /etc/wodim.conf
1387 Default values can be set for the following options in
1388 /etc/wodim.conf. For example: CDR_FIFOSIZE=8m or CDR_SPEED=2
1389 CDR_DEVICE
1391 This may either hold a device identifier that is suitable
1392 to the open call of the SCSI transport library or a label
1393 in the file /etc/wodim.conf that allows to identify a
1394 specific drive on the system.
1395 CDR_SPEED
1397 Sets the default speed value for writing (see also speed=
1398 option).
1399 CDR_FIFOSIZE
1401 Sets the default size of the FIFO (see also fs=# option).
1402 CDR_MAXFIFOSIZE
1404 Sets the maximum size of the FIFO (see also fs=# option).
1405 Any other keyword (label) is an identifier (symbolic name) for a
1407 specific drive
1408 on the system. Such an identifier may not contain the
1409 characters ',', '/', '@' or ':'.
1410 Each line that follows a label contains a whitespace sep‐
1412 arated list of items. Currently, four items are recog‐
1413 nized: the drive's target specification, the default
1414 speed that should be used for this drive, the default
1415 FIFO size that should be used for this drive and drive
1416 specific options. The values for speed and fifosize may
1417 be set to -1 to tell wodim to use the global defaults.
1418 target can be -1 to use the auto-guessing of the drive
1419 (see above).
1420 The value for driveropts may be omited or set to "" if no
1422 driveropts are used. A typical line may look this way:
1423 plex760= 0,5,0 12 50m varirec=1
1425 pioneer= /dev/hdd -1 -1
1427 This tells wodim that a drive named plex760 is at scsibus
1429 0, target 5, lun 0 and should be used with speed 12 and a
1430 FIFO size of 50 MB. It also uses some device specific
1431 parameter. A second drive may is accesible via the
1432 device file /dev/hdd and uses the default speed and the
1433 default FIFO size.
1434
1437 icedax(1), readom(1), genisoimage(1), ssh(1).
1438
1441 On Solaris you need to stop the volume management if you like to use
1442 the USCSI fallback SCSI transport code. Even things like wodim -scanbus
1443 will not work if the volume management is running.
1444 Disks made in Track At Once mode are not suitable as a master for
1446 direct mass production by CD manufacturers. You will need the disk at
1447 once option to record such disks. Nevertheless the disks made in Track
1448 At Once will normally be read in all CD players. Some old audio CD
1449 players however may produce a two second click between two audio
1450 tracks.
1451 The minimal size of a track is 4 seconds or 300 sectors. If you write
1453 smaller tracks, the CD-Recorder will add dummy blocks. This is not an
1454 error, even though the SCSI-error message looks this way.
1455 The Yamaha CDR-400 and all new SCSI-3/mmc conforming drives are sup‐
1457 ported in single and multi-session.
1458 You should run several tests in all supported speeds of your drive with
1460 the -dummy option turned on if you are using wodim on an unknown sys‐
1461 tem. Writing a CD is a real-time process. NFS, CIFS and other network
1462 file systems won't always deliver constantly the needed data rates. If
1463 you want to use wodim with CD-images that are located on a NFS mounted
1464 filesystem, be sure that the FIFO size is big enough. If you want to
1465 make sure that buffer underruns are not caused by your source disk, you
1466 may use the command
1467 wodim -dummy dev=2,0 padsize=600m /dev/null
1469 to create a disk that is entirely made of dummy data.
1471 There are also cases where you either need to be root or install wodim
1473 executable with suid-root permissions. First, if you are using a device
1474 manufactured before 1999 which requires a non-MMC driver, you should
1475 run wodim in dummy mode before writing data. If you find a problem
1476 doing this, please report it to the cdrkit maintainers (see below).
1477 Second, certain functionality may be unusable because of Linux's SCSI
1479 command filtering. When using wodim for anything except of pure data
1480 writing, you should also test the process in dummy mode and report
1481 trouble to the contact address below.
1482 If you still want to run wodim with root permissions, you can set the
1484 permissions of the executable to suid-root. See the additional notes of
1485 your system/program distribution or README.suidroot which is part of
1486 the cdrkit source.
1487 You should not connect old drives that do not support disconnect/recon‐
1489 nect to either the SCSI bus that is connected to the CD-Recorder or the
1490 source disk.
1491 A Compact Disc can have no more than 99 tracks.
1493 When creating a disc with both audio and data tracks, the data should
1495 be on track 1 otherwise you should create a CDplus disk which is a
1496 multi session disk with the first session containing the audio tracks
1497 and the following session containing the data track.
1498 Many operating systems are not able to read more than a single data
1500 track, or need special software to do so.
1501 If you have more information or SCSI command manuals for currently
1503 unsupported CD/DVD/BR/HD-DVD-Recorders, please contact the cdrkit main‐
1504 tainers (see below).
1505 Many CD recorders have bugs and often require a firmware update to work
1507 correctly. If you exprience problems which cannot be solved or
1508 explained by the notes above, please look for instructions on the home‐
1509 page of the particular manufacturer.
1510 Some bugs will force you to power cycle the device or to reboot the
1512 machine.
1513 The FIFO percent output is computed just after a block of data has been
1515 written to the CD/DVD-Recorder. For this reason, there will never be
1516 100% FIFO fill ratio while the FIFO is in streaming mode.
1517
1520 You have 4 seconds to abort wodim start after you see the message:
1521 Starting to write CD at speed %d in %s mode for %s session. In most
1523 shells you can do that by pressing Ctrl-C.
1524 A typical error message for a SCSI command looks like:
1526 wodim: I/O error. test unit ready: scsi sendcmd: no error
1528 CDB: 00 20 00 00 00 00
1529 status: 0x2 (CHECK CONDITION)
1530 Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
1531 Sense Key: 0x5 Illegal Request, Segment 0
1532 Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
1533 Sense flags: Blk 0 (not valid)
1534 cmd finished after 0.002s timeout 40s
1535 The first line gives information about the transport of the command.
1537 The text after the first colon gives the error text for the system call
1538 from the view of the kernel. It usually is: I/O error unless other
1539 problems happen. The next words contain a short description for the
1540 SCSI command that fails. The rest of the line tells you if there were
1541 any problems for the transport of the command over the SCSI bus. fatal
1542 error means that it was not possible to transport the command (i.e. no
1543 device present at the requested SCSI address).
1544 The second line prints the SCSI command descriptor block for the failed
1546 command.
1547 The third line gives information on the SCSI status code returned by
1549 the command, if the transport of the command succeeds. This is error
1550 information from the SCSI device.
1551 The fourth line is a hex dump of the auto request sense information for
1553 the command.
1554 The fifth line is the error text for the sense key if available, fol‐
1556 lowed by the segment number that is only valid if the command was a
1557 copy command. If the error message is not directly related to the cur‐
1558 rent command, the text deferred error is appended.
1559 The sixth line is the error text for the sense code and the sense qual‐
1561 ifier if available. If the type of the device is known, the sense data
1562 is decoded from tables in scsierrs.c . The text is followed by the
1563 error value for a field replaceable unit.
1564 The seventh line prints the block number that is related to the failed
1566 command and text for several error flags. The block number may not be
1567 valid.
1568 The eight line reports the timeout set up for this command and the time
1570 that the command really needed to complete.
1571 The following message is not an error:
1573 Track 01: Total bytes read/written: 2048/2048 (1 sectors).
1575 wodim: I/O error. flush cache: scsi sendcmd: no error
1576 CDB: 35 00 00 00 00 00 00 00 00 00
1577 status: 0x2 (CHECK CONDITION)
1578 Sense Bytes: F0 00 05 80 00 00 27 0A 00 00 00 00 B5 00 00 00 00 00
1579 Sense Key: 0x5 Illegal Request, Segment 0
1580 Sense Code: 0xB5 Qual 0x00 (dummy data blocks added) Fru 0x0
1581 Sense flags: Blk -2147483609 (valid)
1582 cmd finished after 0.002s timeout 40s
1583 It simply notifies, that a track that is smaller than the minimum size
1585 has been expanded to 300 sectors.
1586
1588 netscsid does not work properly and is generaly unmaintained. It is
1589 probably not compatible with rscsi from cdrtools either. Good bugfixes
1590 are welcome, talk to Cdrkit maintainers.
1591 cuefile support is very limited, only one file is allowed. For volun‐
1593 teers, see TODO file in the source.
1594 Specifying an audio file multiple times causes corruption of the second
1596 track (effectively no data plus minimum padding).
1597 Some of the bugs may be fixed in Joerg Schilling's cdrtools. See there
1599 for details, URL attached below.
1600
1603 Joerg Schilling (schilling@fokus.fhg.de)
1604 For writing cdrecord and libscg which represent the most
1605 parts of wodim's code.
1606 Bill Swartz (Bill_Swartz@twolf.com)
1608 For helping me with the TEAC driver support
1609 Aaron Newsome (aaron.d.newsome@wdc.com)
1611 For letting me develop Sony support on his drive
1612 Eric Youngdale (eric@andante.jic.com)
1614 For supplying mkisofs
1615 Gadi Oxman (gadio@netvision.net.il)
1617 For tips on the ATAPI standard
1618 Finn Arne Gangstad (finnag@guardian.no)
1620 For the first FIFO implementation.
1621 Dave Platt (dplatt@feghoot.ml.org)
1623 For creating the experimental packet writing support,
1624 the first implementation of CD-RW blanking support, the
1625 first .wav file decoder and many nice discussions on
1626 cdrecord.
1627 Chris P. Ross (cross@eng.us.uu.net)
1629 For the first implementation of a BSDI SCSI transport.
1630 Grant R. Guenther (grant@torque.net)
1632 For creating the first parallel port transport implemen‐
1633 tation for Linux.
1634 Kenneth D. Merry (ken@kdm.org)
1636 for providing the CAM port for FreeBSD together with
1637 Michael Smith (msmith@freebsd.org)
1638 Heiko Eiszfeldt (heiko@hexco.de)
1640 for making libedc_ecc available (needed to write RAW
1641 data sectors).
1642
1645 If you want to actively take part on the development of wodim, you may
1646 join the developer mailing list via this URL:
1647 https://alioth.debian.org/mail/?group_id=31006
1649 The mail address of the list is: debburn-devel@lists.alioth.debian.org
1651
1654 wodim is currently maintained as part of the cdrkit project by its
1655 developers. Most of the code and this manual page was originally writ‐
1656 ten by:
1657 Joerg Schilling
1659 Seestr. 110
1660 D-13353 Berlin
1661 Germany
1662 This application is a spinoff from the original program "cdrecord"
1664 delivered in the cdrtools package [1] created by Joerg Schilling, who
1665 deserves the most credits for its success. However, he is not involved
1666 into the development of this spinoff and therefore he shall not be made
1667 responsible for any problem caused by it. Do not refer to this applica‐
1668 tion as "cdrecord", do not try to get support for wodim by contacting
1669 the original authors.
1670 Additional information can be found on:
1672 https://alioth.debian.org/projects/debburn/
1673 If you have support questions, send them to
1675 debburn-devel@lists.alioth.debian.org
1677 If you have definitely found a bug, send a mail to this list or to
1679 submit@bugs.debian.org
1681 writing at least a short description into the Subject and "Package:
1683 cdrkit" into the first line of the mail body.
1684
1686 [1] Cdrtools 2.01.01a08 from May 2006, http://cdrecord.berlios.de
1687 Version 2.0 wodim(1)