1wodim(1) wodim(1)
2
6 wodim - write data to optical disk media
7
9 wodim [options] track1...trackn
10
12 There may be similarities and differences between this program and
13 other disk recording application(s). See the CREDITS and AUTHORS sec‐
14 tions below to learn about the origin of wodim.
15
18 wodim is used to record data or audio Compact Discs on an Orange Book
19 CD-Recorder or to write DVD media on a DVD-Recorder.
20 The device is the device file or label offered by the operating system
22 to access the recorder with SCSI GENERIC (sg) interface. Note that some
23 operating systems may provide separate device nodes for block-oriented
24 and sg access. For example, on older Linux systems, the sg access was
25 available through /dev/sg... files while the block oriented access was
26 done through associated (but not identical) /dev/hd... and /dev/sr...
27 (or /dev/scd... ) files.
28 In any case, the user running wodim needs read and write access to the
30 particular device file on a Linux system. It is recommended to be root
31 or install the application as suid-root, because certain versions of
32 Linux (kernel) limit the set of SCSI commands allowed for non-root
33 users. Even if usage without root identity is possible in many cases,
34 some device drivers still may fail, show unexplainable problems and
35 generally the problems become harder to debug. The risk for buffer-
36 underruns is also increased. See the PROCESS SCHEDULING PRIORITY sec‐
37 tion below for more details.
38 There is an alternative way of specifying the device, using the tradi‐
40 tional SCSI descriptions in form of devicetype:bus/target/lun specifi‐
41 cation. However, the success of this method is not guaranteed since it
42 requires an adaptation scheme for your architecture, and the numbers
43 may vary depending on the hardware-internal numbering or on the order
44 of hot-plug device detection. If your operating system does not provide
45 a sufficient framework for keeping this numbers persistent, don't rely
46 on them. See -scanbus and --devices options below for details.
47 There are emulated SCSI compatible device systems, using the SCSI pro‐
49 tocols transported over various hardware/media types. The most known
50 examples is ATAPI ("IDE burners") or USB storage ("external USB case").
51 If the pseudo-SCSI b/t/l device address specification is used instead
52 of the native one, you need to prepend the "devicetype:" description to
53 the emulated "bus/target/lun" device address.
54 If a file /etc/wodim.conf exists, the parameter to the dev= option may
56 also be a drive name label in that file (see FILES section).
57 As a special exception, the device specification can be -1 or just
59 omitted, which invokes automatic guessing of an appropriate device for
60 the selected operation. However, this guessing is not available every‐
61 where and is not reliable; it is only available for the user's conve‐
62 nience in simple environments.
63 In Track At Once mode, each track corresponds to a single file that
65 contains the prepared data for that track. If the argument is `-',
66 standard input is used for that track. Only one track may be taken
67 from stdin. In the other write modes, the direct file to track rela‐
68 tion may not be implemented. In -clone mode, a single file contains
69 all data for the whole disk. To allow DVD writing on platforms that do
70 not implement large file support, wodim concatenates all file arguments
71 to a single track when writing to DVD media.
72
75 Wodim tries to get higher process priority using different methods.
76 This is important because the burn process is usually a realtime task,
77 no long delays should occur while transmitting fresh data to the
78 recorder. This is especially important on systems with insufficient RAM
79 where swapping can create delays of many seconds.
80 A possible workaround on underpowered systems is the use of the burn‐
82 free or similar feature, allowing the recorder to resume.
83 Root permissions are usually required to get higher process scheduling
85 priority.
86 On SVr4 compliant systems, wodim uses the real time class to get the
88 highest scheduling priority that is possible (higher than all kernel
89 processes). On systems with POSIX real time scheduling wodim uses real
90 time scheduling too, but may not be able to gain a priority that is
91 higher than all kernel processes.
92 In order to be able to use the SCSI transport subsystem of the OS, run
94 at highest priority and lock itself into core wodim either needs to be
95 run as root, needs to be installed suid root or must be called via
96 RBACs pfexec mechanism.
97
100 General options must be before any track file name or track option.
101 -version
103 Print version information and exit.
104 -v Increment the level of general verbosity by one. This is used
106 e.g. to display the progress of the writing process.
107 -V Increment the verbose level in respect of SCSI command transport
109 by one. This helps to debug problems during the writing
110 process, that occur in the CD/DVD-Recorder. If you get incom‐
111 prehensible error messages you should use this flag to get more
112 detailed output. -VV will show data buffer content in addition.
113 Using -V or -VV slows down the process and may be the reason for
114 a buffer underrun.
115 debug=#, -d
117 Set the misc debug value to # (with debug=#) or increment the
118 misc debug level by one (with -d). If you specify -dd, this
119 equals to debug=2. This may help to find problems while opening
120 a driver for libusal as well as with sector sizes and sector
121 types. Using -debug slows down the process and may be the rea‐
122 son for a buffer underrun.
123 kdebug=#, kd=#
125 Tell the usal-driver to modify the kernel debug value while SCSI
126 commands are running.
127 -silent, -s
129 Do not print out a status report for failed SCSI commands.
130 -force Force to continue on some errors. Be careful when using this
132 option. wodim implements several checks that prevent you from
133 doing unwanted things like damaging CD-RW media by improper
134 drives. Many of the sanity checks are disabled when the -force
135 option is used.
136 This option also implements some tricks that will allow you to
138 blank bad CD-RW disks.
139 -immed Tell wodim to set the SCSI IMMED flag in certain commands
141 (load/eject/blank/close_track/close_session). This can be use‐
142 ful on broken systems with ATAPI harddisk and CD/DVD writer on
143 the same bus or with SCSI systems that don't use discon‐
144 nect/reconnect. These systems will freeze while blanking or
145 fixating a CD/DVD or while a DVD writer is filling up a session
146 to the minimum amount (approx. 800 MB). Setting the -immed flag
147 will request the command to return immediately while the opera‐
148 tion proceeds in background, making the bus usable for the other
149 devices and avoiding the system freeze. This is an experimental
150 feature which may work or not, depending on the model of the
151 CD/DVD writer. A correct solution would be to set up a correct
152 cabling but there seem to be notebooks around that have been set
153 up the wrong way by the manufacturer. As it is impossible to
154 fix this problem in notebooks, the -immed option has been added.
155 A second experimental feature of the -immed flag is to tell
157 wodim to try to wait short times while writing to the media.
158 This is expected to free the IDE bus if the CD/DVD writer and
159 the data source are connected to the same IDE cable. In this
160 case, the CD/DVD writer would otherwise usually block the IDE
161 bus for nearly all the time making it impossible to fetch data
162 from the source drive. See also minbuf= and -v option.
163 Use both features at your own risk. If it turns out that it
165 would make sense to have a separate option for the wait feature,
166 write to the author and convince him.
167 minbuf=value
169 The # minbuf= option allows to define the minimum drive buffer
170 fill ratio for the experimental ATAPI wait mode that is intended
171 to free the IDE bus to allow hard disk and CD/DVD writer to be
172 on the same IDE cable. As the wait mode currently only works
173 when the verbose option -v has been specified, wodim implies the
174 verbose option in case the -immed or minbuf= option have been
175 specified. Valid values for minbuf= are between 25 and 95 for
176 25%...95% minimum drive buffer fill ratio.
177 -dummy The CD/DVD-Recorder will go through all steps of the recording
179 process, but the laser is turned off during this procedure. It
180 is recommended to run several tests before actually writing to a
181 Compact Disk or Digital Versatile Disk, if the timing and load
182 response of the system is not known.
183 -clone Tells wodim to handle images created by readom -clone. The
185 -clone may only be used in conjunction with with the -raw96r or
186 with the -raw16 option. Using -clone together with -raw96r is
187 preferred as it allows to write all subchannel data. The option
188 -raw16 should only be used with drives that do not support to
189 write in -raw96r mode.
190 -dao
192 -sao Set SAO (Session At Once) mode which is usually called Disk At
194 Once mode. This currently only works with MMC drives that sup‐
195 port Session At Once mode. Note that wodim needs to know the
196 size of each track in advance for this mode (see the genisoimage
197 -print-size option and the EXAMPLES section for more informa‐
198 tion).
199 -tao Set TAO (Track At Once) writing mode. This is the default write
201 mode in previous wodim versions. With most drives, this write
202 mode is required for multi session recording.
203 -raw Set RAW writing mode. Using this option defaults to -raw96r.
205 Note that wodim needs to know the size of each track in advance
206 for this mode (see the genisoimage -print-size option and the
207 EXAMPLES section for more information).
208 -raw96r
210 Select Set RAW writing mode with 2352 byte sectors plus 96 bytes
211 of raw P-W subchannel data resulting in a sector size of 2448
212 bytes. This is the preferred raw writing mode as it gives best
213 control over the CD writing process. If you find any problems
214 with the layout of a disk or with sub channel content (e.g.
215 wrong times on the display when playing the CD) and your drive
216 supports to write in -raw96r or -raw16 mode, you should give it
217 a try. There are several CD writers with bad firmware that
218 result in broken disks when writing in TAO or SAO mode. Writing
219 data disks in raw mode needs significantly more CPU time than
220 other write modes. If your CPU is too slow, this may result in
221 buffer underruns. Note that wodim needs to know the size of
222 each track in advance for this mode (see the genisoimage -print-
223 size option and the EXAMPLES section for more information).
224 -raw96p
226 Select Set RAW writing mode with 2352 byte sectors plus 96 bytes
227 of packed P-W subchannel data resulting in a sector size of 2448
228 bytes. This is the less preferred raw writing mode as only a
229 few recorders support it and some of these recorders have bugs
230 in the firmware implementation. Don't use this mode if your
231 recorder supports -raw96r or -raw16. Writing data disks in raw
232 mode needs significantly more CPU time than other write modes.
233 If your CPU is too slow, this may result in buffer underruns.
234 Note that wodim needs to know the size of each track in advance
235 for this mode (see the genisoimage -print-size option and the
236 EXAMPLES section for more information).
237 -raw16 Select Set RAW writing mode with 2352 byte sectors plus 16 bytes
239 of P-Q subchannel data resulting in a sector size of 2368 bytes.
240 If a recorder does not support -raw96r, this is the preferred
241 raw writing mode. It does not allow to write CD-Text or
242 CD+Graphics but it is the only raw writing mode in cheap CD
243 writers. As these cheap writers in most cases do not support
244 -dao mode. Don't use this mode if your recorder supports
245 -raw96r. Writing data disks in raw mode needs significantly
246 more CPU time than other write modes. If your CPU is too slow,
247 this may result in buffer underruns. Note that wodim needs to
248 know the size of each track in advance for this mode (see the
249 genisoimage -print-size option and the EXAMPLES section for more
250 information).
251 -multi Allow multi session CDs to be made. This flag needs to be
253 present on all sessions of a multi session disk, except you want
254 to create a session that will be the last session on the media.
255 The fixation will be done in a way that allows the CD/DVD-
256 Recorder to append additional sessions later. This is done by
257 generation a TOC with a link to the next program area. The so
258 generated media is not 100% compatible to manufactured CDs
259 (except for CDplus). Use only for recording of multi session
260 CDs. If this option is present, the default track type is CD-
261 ROM XA mode 2 form 1 and the sector size is 2048 bytes. The XA
262 sector subheaders will be created by the drive. The Sony drives
263 have no hardware support for CD-ROM XA mode 2 form 1. You have
264 to specify the -data option in order to create multi session
265 disks on these drives. As long as wodim does not have a coder
266 for converting data sectors to audio sectors, you need to force
267 CD-ROM sectors by including the -data option if you like to
268 record a multisession disk in SAO mode. Not all drives allow
269 multisession CDs in SAO mode.
270 -msinfo
272 Retrieve multi session info in a form suitable for genisoimage
273 and print it to standard output. See msifile= option for another
274 version.
275 This option makes only sense with a CD that contains at least
277 one closed session and is appendable (not finally closed yet).
278 Some drives create error messages if you try to get the multi
279 session info for a disk that is not suitable for this operation.
280 msifile=filename
282 Like -msinfo option but also stores the multi session info in a
283 file.
284 -toc Retrieve and print out the table of content or PMA of a CD.
286 With this option, wodim will work with CD-R drives and with CD-
287 ROM drives.
288 -atip Retrieve and print out the ATIP (absolute Time in Pre-groove)
290 info of a CD/DVD recordable or CD/DVD re-writable media. With
291 this option, wodim will try to retrieve the ATIP info. If the
292 actual drive does not support to read the ATIP info, it may be
293 that only a reduced set of information records or even nothing
294 is displayed. Only a limited number of MMC compliant drives sup‐
295 port to read the ATIP info.
296 If wodim is able to retrieve the lead-in start time for the
298 first session, it will try to decode and print the manufacturer
299 info from the media. DVD media does not have ATIP information
300 but there is equivalent prerecorded information that is read out
301 and printed.
302 -fix The disk will only be fixated (i.e. a TOC for a CD-Reader will
304 be written). This may be used, if for some reason the disk has
305 been written but not fixated. This option currently does not
306 work with old TEAC drives (CD-R50S and CD-R55S).
307 -nofix Do not fixate the disk after writing the tracks. This may be
309 used to create an audio disk in steps. An un-fixated disk can
310 usually not be used on a non CD-writer type drive but there are
311 audio CD players that will be able to play such a disk.
312 -waiti Wait for input to become available on standard input before try‐
314 ing to open the SCSI driver. This allows wodim to read its input
315 from a pipe even when writing additional sessions to a multi
316 session disk. When writing another session to a multi session
317 disk, genisoimage needs to read the old session from the device
318 before writing output. This cannot be done if wodim opens the
319 SCSI driver at the same time.
320 -load Load the media and exit. This only works with a tray loading
322 mechanism but seems to be useful when using the Kodak disk
323 transporter.
324 -lock Load the media, lock the door and exit. This only works with a
326 tray loading mechanism but seems to be useful when using the
327 Kodak disk transporter.
328 -eject Eject disk after doing the work. Some devices (e.g. Philips)
330 need to eject the medium before creating a new disk. Doing a
331 -dummy test and immediately creating a real disk would not work
332 on these devices.
333 speed=#
335 Set the speed factor of the writing process to #. # is an inte‐
336 ger, representing a multiple of the audio speed. This is about
337 150 KB/s for CD-ROM, about 172 KB/s for CD-Audio and about
338 1385 kB/s for DVD media. If no speed option is present, wodim
339 will try to get a drive specific speed value from the file
340 /etc/wodim.conf and if it cannot find one, it will try to get
341 the speed value from the CDR_SPEED environment and later from
342 the CDR_SPEED= entry in /etc/wodim.conf. If no speed value
343 could be found, wodim uses a drive specific default speed. The
344 default for all new (MMC compliant) drives is to use the maximum
345 supported by the drive. If you use speed=0 with a MMC compliant
346 drive, wodim will switch to the lowest possible speed for drive
347 and medium. If you are using an old (non MMC) drive that has
348 problems with speed=2 or speed=4, you should try speed=0.
349 blank=type
351 Blank a CD-RW and exit or blank a CD-RW before writing. The
352 blanking type may be one of:
353 help Display a list of possible blanking types.
355 all Blank the entire disk. This may take a long time.
357 fast Minimally blank the disk. This results in erasing
359 the PMA, the TOC and the pregap.
360 track Blank a track.
362 unreserve Unreserve a reserved track.
364 trtail Blank the tail of a track.
366 unclose Unclose last session.
368 session Blank the last session.
370 Not all drives support all blanking types. It may be necessary to use
371 blank=all if a drive reports a specified command as being invalid. If
372 used together with the -force flag, this option may be used to blank
373 CD-RW disks that otherwise cannot be blanked. Note that you may need to
374 specify blank=all because some drives will not continue with certain
375 types of bad CD-RW disks. Note also that wodim does its best if the
376 -force flag is used but it finally depends on the drive's firmware
377 whether the blanking operation will succeed or not.
378 -format
380 Format a CD-RW/DVD-RW/DVD+RW disc. Formatting is currently only
381 implemented for DVD+RW media. A 'maiden' DVD+RW media needs to
382 be formatted before you may write to it. However, as wodim
383 autodetects the need for formatting in this case and auto for‐
384 mats the medium before it starts writing, the -format option is
385 only needed if you like to forcibly reformat a DVD+RW medium.
386 fs=# Set the FIFO (ring buffer) size to #. You may use the same syn‐
388 tax as in dd(1), sdd(1) or star(1). The number representing the
389 size is taken in bytes unless otherwise specified. If a number
390 is followed directly by the letter `b', `k', `m', `s' or `f',
391 the size is multiplied by 512, 1024, 1024*1024, 2048 or 2352.
392 If the size consists of numbers separated by `x' or `*', multi‐
393 plication of the two numbers is performed. Thus fs=10x63k will
394 specify a FIFO size of 630 kBytes.
395 The size specified by the fs= argument includes the shared mem‐
397 ory that is needed for administration. This is at least one page
398 of memory. If no fs= option is present, wodim will try to get
399 the FIFO size value from the CDR_FIFOSIZE environment. The
400 default FIFO size is currently 4 MB.
401 The FIFO is used to increase buffering for the real time writing
403 process. It allows to run a pipe from genisoimage directly into
404 wodim. If the FIFO is active and a pipe from genisoimage into
405 wodim is used to create a CD, wodim will abort prior to do any
406 modifications on the disk if genisoimage dies before it starts
407 writing. The recommended FIFO size is between 4 and 128 MBytes.
408 As a rule of thumb, the FIFO size should be at least equal to
409 the size of the internal buffer of the CD/DVD-Recorder and no
410 more than half of the physical amount of RAM available in the
411 machine. If the FIFO size is big enough, the FIFO statistics
412 will print a FIFO empty count of zero and the FIFO min fill is
413 not below 20%. It is not wise to use too much space for the
414 FIFO. If you need more than 8 MB to write a CD at a speed less
415 than 20x from an image on a local file system on an idle
416 machine, your machine is either underpowered, has hardware prob‐
417 lems or is mis-configured. If you like to write DVDs or CDs at
418 higher speed, it makes sense to use at least 16 MB for the FIFO.
419 On old and small machines, you need to be more careful with the
421 FIFO size. If your machine has less than 256 MB of physical
422 RAM, you should not set up a FIFO size that is more than 32 MB.
423 The sun4c architecture (e.g. a Sparcstation-2) has only MMU page
424 table entries for 16 MBytes per process. Using more than
425 14 MBytes for the FIFO may cause the operating system in this
426 case to spend much time to constantly reload the MMU tables.
427 Newer machines from Sun do not have this MMU hardware problem. I
428 have no information on PC-hardware reflecting this problem.
429 Old Linux systems for non x86 platforms have broken definitions
431 for the shared memory size. You need to fix them and rebuild the
432 kernel or manually tell wodim to use a smaller FIFO.
433 If you have buffer underruns or similar problems (like a con‐
435 stantly empty drive buffer) and observe a zero fifo empty count,
436 you have hardware problems that prevents the data from flowing
437 fast enough from the kernel memory to the drive. The FIFO size
438 in this case is sufficient, but you should check for a working
439 DMA setup.
440 ts=# Set the maximum transfer size for a single SCSI command to #.
442 The syntax for the ts= option is the same as for wodim fs=# or
443 sdd bs=#.
444 If no ts= option has been specified, wodim defaults to a trans‐
446 fer size of 63 kB. If libusal gets lower values from the operat‐
447 ing system, the value is reduced to the maximum value that is
448 possible with the current operating system. Sometimes, it may
449 help to further reduce the transfer size or to enhance it, but
450 note that it may take a long time to find a better value by
451 experimenting with the ts= option.
452 dev=target
454 Sets the SCSI target for the CD/DVD-Recorder, see notes above.
455 A typical device specification is dev=6,0 . A filename or vir‐
456 tual device name can be passed instead of the symbolic SCSI num‐
457 bers. The correct device/filename in this case can be found in
458 the system specific manuals of the target operating system. On
459 a FreeBSD system without CAM support, you need to use the con‐
460 trol device (e.g. /dev/rcd0.ctl). A correct device specifica‐
461 tion in this case may be dev=/dev/rcd0.ctl:@ .
462 On Linux and Windows 2000/XP, drives are accessible with their
464 device (or drive) names or with the symbolic SCSI numbers (not
465 recommended, mapping is not stable and could be completely
466 removed in the future).
467 If no dev option is present, wodim will try to get the device
469 from the CDR_DEVICE environment.
470 If the argument to the dev= option does not contain the charac‐
472 ters ',', '/', '@' or ':', it is interpreted as an label name
473 that may be found in the file /etc/wodim.conf (see FILES sec‐
474 tion).
475 gracetime=#
477 Set the grace time before starting to write to # seconds. Val‐
478 ues below 2 seconds are not recommended to give the kernel or
479 volume management a chance to learn the new state.
480 timeout=#
482 Set the default SCSI command timeout value to # seconds. The
483 default SCSI command timeout is the minimum timeout used for
484 sending SCSI commands. If a SCSI command fails due to a time‐
485 out, you may try to raise the default SCSI command timeout above
486 the timeout value of the failed command. If the command runs
487 correctly with a raised command timeout, please report the bet‐
488 ter timeout value and the corresponding command to the author of
489 the program. If no timeout option is present, a default timeout
490 of 40 seconds is used.
491 driver=name
493 Allows the user to manually select a driver for the device. The
494 reason for the existence of the driver=name option is to allow
495 users to use wodim with drives that are similar to supported
496 drives but not known directly by wodim. All drives made after
497 1997 should be MMC standard compliant and thus supported by one
498 of the MMC drivers. It is most unlikely that wodim is unable to
499 find the right driver automatically. Use this option with
500 extreme care. If a wrong driver is used for a device, the possi‐
501 bility of creating corrupted disks is high. The minimum problem
502 related to a wrong driver is that the speed= or -dummy will not
503 work.
504 The following driver names are supported:
506 help To get a list of possible drivers together with a short
508 description.
509 mmc_cd The generic SCSI-3/mmc CD-ROM driver is auto-selected
511 whenever wodim finds a MMC compliant drive that does not
512 identify itself to support writing at all, or that only
513 identifies to support media or write modes not imple‐
514 mented in wodim.
515 mmc_cd_dvd
517 The generic SCSI-3/mmc CD/DVD driver is auto-selected
518 whenever wodim finds a MMC-2 or MMC-3 compliant drive
519 that seems to support more than one medium type and the
520 tray is open or no medium could be found to select the
521 right driver. This driver tries to close the tray,
522 checks the medium found in the tray and then branches to
523 the driver that matches the current medium.
524 mmc_cdr
526 The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected
527 whenever wodim find a MMC compliant drive that only sup‐
528 ports to write CDs or a multi system drive that contains
529 a CD as the current medium.
530 mmc_cdr_sony
532 The generic SCSI-3/mmc CD-R/CD-RW driver is auto-selected
533 whenever wodim would otherwise select the mmc_cdr driver
534 but the device seems to be made by Sony. The
535 mmc_cdr_sony is definitely needed for the Sony CDU 928 as
536 this drive does not completely implement the MMC standard
537 and some of the MMC SCSI commands have to be replaced by
538 Sony proprietary commands. It seems that all Sony drives
539 (even newer ones) still implement the Sony proprietary
540 SCSI commands so it has not yet become a problem to use
541 this driver for all Sony drives. If you find a newer Sony
542 drive that does not work with this driver, please report.
543 mmc_dvd
545 The generic SCSI-3/mmc-2 DVD-R/DVD-RW driver is auto-
546 selected whenever wodim finds a MMC-2 or MMC-3 compliant
547 drive that supports to write DVDs and an appropriate
548 medium is loaded. There is no Track At Once mode for DVD
549 writers.
550 mmc_dvdplus
552 The generic SCSI-3/mmc-3 DVD+R/DVD+RW driver is auto-
553 selected whenever one of the DVD+ media types that are
554 incompatible to each other is found. It checks media and
555 then branches to the driver that matches the current
556 medium.
557 mmc_dvdplusr
559 The generic SCSI-3/mmc-3 DVD+R driver is auto-selected
560 whenever a DVD+R medium is found in an appropriate
561 writer. Note that for unknown reason, the DVD-Plus
562 alliance does not like that there is a simulation mode
563 for DVD+R media. The author of wodim tries to convince
564 manufacturers to implement a simulation mode for DVD+R
565 and implement support. DVD+R only supports one write
566 mode that is somewhere between Track At Once and Packet
567 writing; this mode is selected in wodim via a the
568 -dao/-sao option.
569 mmc_dvdplusrw
571 The generic SCSI-3/mmc-3 DVD+RW driver is auto-selected
572 whenever a DVD+RW medium is found in an appropriate
573 writer. As DVD+RW media needs to be formatted before its
574 first use, wodim auto-detects this media state and per‐
575 forms a format before it starts to write. Note that for
576 unknown reason, the DVD-Plus alliance does not like that
577 there is a simulation mode nor a way to erase DVD+RW
578 media. DVD+RW only supports one write mode that is close
579 to Packet writing; this mode is selected in wodim via a
580 the -dao/-sao option.
581 cw_7501
583 The driver for Matsushita/Panasonic CW-7501 is auto-
584 selected when wodim finds this old pre MMC drive. wodim
585 supports all write modes for this drive type.
586 kodak_pcd_600
588 The driver for Kodak PCD-600 is auto-selected when wodim
589 finds this old pre MMC drive which has been the first
590 high speed (6x) CD writer for a long time. This drive
591 behaves similar to the Philips CDD-521 drive.
592 philips_cdd521
594 The driver for Philips CDD-521 is auto-selected when
595 wodim finds a Philips CDD-521 drive (which is the first
596 CD writer ever made) or one of the other drives that are
597 known to behave similar to this drive. All Philips
598 CDD-521 or similar drives (see other drivers in this
599 list) do not support Session At Once recording.
600 philips_cdd521_old
602 The driver for Philips old CDD-521 is auto-selected when
603 wodim finds a Philips CDD-521 with very old firmware
604 which has some known limitations.
605 philips_cdd522
607 The driver for Philips CDD-522 is auto-selected when
608 wodim finds a Philips CDD-522 which is the successor of
609 the 521 or one of its variants with Kodak label. wodim
610 does not support Session At Once recording with these
611 drives.
612 philips_dumb
614 The driver for Philips CDD-521 with pessimistic assump‐
615 tions is never auto-selected. It may be used by hand
616 with drives that behave similar to the Philips CDD-521.
617 pioneer_dws114x
619 The driver for Pioneer DW-S114X is auto-selected when
620 wodim finds one of the old non MMC CD writers from Pio‐
621 neer.
622 plasmon_rf4100
624 The driver for Plasmon RF 4100 is auto-selected when
625 wodim finds this specific variant of the Philips CDD-521.
626 ricoh_ro1060c
628 The driver for Ricoh RO-1060C is auto-selected when wodim
629 finds this drive. There is no real support for this drive
630 yet.
631 ricoh_ro1420c
633 The driver for Ricoh RO-1420C is auto-selected when wodim
634 finds a drive with this specific variant of the Philips
635 CDD-521 command set.
636 scsi2_cd
638 The generic SCSI-2 CD-ROM driver is auto-selected when‐
639 ever wodim finds a pre MMC drive that does not support
640 writing or a pre MMC writer that is not supported by
641 wodim.
642 sony_cdu924
644 The driver for Sony CDU-924 / CDU-948 is auto-selected
645 whenever wodim finds one of the old pre MMC CD writers
646 from Sony.
647 teac_cdr50
649 The driver for Teac CD-R50S, Teac CD-R55S, JVC XR-W2010,
650 Pinnacle RCD-5020 is auto-selected whenever one of the
651 drives is found that is known to the non MMC command set
652 used by TEAC and JVC. Note that many drives from JVC
653 will not work because they do not correctly implement the
654 documented command set and JVC has been unwilling to fix
655 or document the bugs. There is no support for the Ses‐
656 sion At Once write mode yet.
657 tyuden_ew50
659 The driver for Taiyo Yuden EW-50 is auto-selected when
660 wodim finds a drive with this specific variant of the
661 Philips CDD-521 command set.
662 yamaha_cdr100
664 The driver for Yamaha CDR-100 / CDR-102 is auto-selected
665 when wodim finds one of the old pre MMC CD writers from
666 Yamaha. There is no support for the Session At Once
667 write mode yet.
668 cdr_simul
670 The simulation CD-R driver allows to run timing and speed
671 tests with parameters that match the behavior of CD writ‐
672 ers.
673 dvd_simul
675 The simulation DVD-R driver allows to run timing and
676 speed tests with parameters that match the behavior of
677 DVD writers.
678 There are two special driver entries in the list: cdr_simul and
680 dvd_simul. These driver entries are designed to make timing
681 tests at any speed or timing tests for drives that do not sup‐
682 port the -dummy option. The simulation drivers implement a
683 drive with a buffer size of 1 MB that can be changed via the
684 CDR_SIMUL_BUFSIZE environment variable. The simulation driver
685 correctly simulates even a buffer underrun condition. If the
686 -dummy option is present, the simulation is not aborted in case
687 of a buffer underrun.
688 driveropts=option list
690 Set driver specific options. The options are specified a comma
691 separated list. To get a list of valid options use
692 driveropts=help together with the -checkdrive option. If you
693 like to set driver options without running a typical wodim task,
694 you need to use the -setdropts option in addition, otherwise the
695 command line parser in wodim will complain. Currently imple‐
696 mented driver options are:
697 burnfree
699 Turn the support for Buffer Underrun Free writing on.
700 This only works for drives that support Buffer Underrun
701 Free technology, which is available on most drives manu‐
702 factured in this millennium. This may be called: Sanyo
703 BURN-Proof, Ricoh Just-Link, Yamaha Lossless-Link or sim‐
704 ilar.
705 This option is deprecated and is mentioned here for docu‐
707 mentation purposes only. The BURN-Free feature is enabled
708 by default if the drive supports it. However, use of
709 BURN-Free may cause decreased burning quality. Therefore
710 it can be useful to disable it for certain purposes, eg.
711 when creating a master copy for mass CD production.
712 noburnfree
714 Turn the support for Buffer Underrun Free writing off.
715 varirec=value
717 Turn on the Plextor VariRec writing mode. The mandatory
718 parameter value is the laser power offset and currently
719 may be selected from -2, -1, 0, 1, 2. In addition, you
720 need to set the write speed to 4 in order to allow
721 VariRec to work.
722 gigarec=value
724 Manage the Plextor GigaRec writing mode. The mandatory
725 parameter value is the disk capacity ratio compared to
726 normal recording and currently may be selected from 0.6,
727 0.7, 0.8, 1.0, 1.2, 1.3, 1.4. If values < 1.0 are used,
728 then the effect is similar to the Yamaha Audio Master Q.
729 R. feature. If values > 1.0 are used, then the disk
730 capacity is increased.
731 Not all drives support all GigaRec values. When a drive
733 uses the GigaRec feature, the write speed is limited to
734 8x.
735 audiomaster
737 Turn on the Yamaha Audio Master Q. R. feature which usu‐
738 ally should result in high quality CDs that have less
739 reading problems in Hi-Fi players. As this is imple‐
740 mented as a variant of the Session at Once write mode, it
741 will only work if you select SAO write mode and there is
742 no need to turn it off. The Audio Master mode will work
743 with a limited speed but may also be used with data CDs.
744 In Audio Master mode, the pits on the CD will be written
745 larger then usual so the capacity of the medium is
746 reduced when turning this feature on. A 74 minute CD
747 will only have a capacity of 63 minutes if Audio Master
748 is active and the capacity of a 80 minute CD will be
749 reduced to 68 minutes.
750 forcespeed
752 Normally, modern drives know the highest possible speed
753 for different media and may reduce the speed in order to
754 grant best write quality. This technology may be called:
755 Plextor PowerRec, Ricoh Just-Speed, Yamaha Optimum Write
756 Speed Control or similar. Some drives (e.g. Plextor,
757 Ricoh and Yamaha) allow to force the drive to use the
758 selected speed even if the medium is so bad that the
759 write quality would be poor. This option tells such a
760 drive to force to use the selected speed regardless of
761 the medium quality.
762 Use this option with extreme care and note that the drive
764 should know better which medium will work at full speed.
765 The default is to turn forcespeed off, regardless of the
766 defaults of the drive.
767 noforcespeed
769 Turn off the force speed feature.
770 speedread
772 Some ultra high speed drives such as 48x and faster
773 drives from Plextor limit the read speed for unknown
774 media to e.g. 40x in order to avoid damaged disks and
775 drives. Using this option tells the drive to read any
776 media as fast as possible. Be very careful as this may
777 cause the media to break in the drive while reading,
778 resulting in a damaged media and drive!
779 nospeedread
781 Turn off unlimited read speed.
782 singlesession
784 Turn the drive into a single session only drive. This
785 allows to read defective or non-compliant (illegal) media
786 with extremely non-standard additional (broken/illegal)
787 TOC entries in the TOC from the second or higher session.
788 Some of these disks become usable if only the information
789 from the first session is used. You need to enable Sin‐
790 gle Session mode before you insert the defective disk!
791 nosinglesession
793 Turn off single session mode. The drive will again behave
794 as usual.
795 hidecdr
797 Hide the fact that a medium might be a recordable medium.
798 This allows to make CD-Rs look like CD-ROMs and applica‐
799 tions believe that the media in the drive is not a CD-R.
800 nohidecdr
802 Turn off hiding CD-R media.
803 tattooinfo
805 Use this option together with -checkdrive to retrieve the
806 image size information for the Yamaha DiskT@2 feature.
807 The images always have a line length of 3744 pixel. Line
808 number 0 (radius 0) is mapped to the center of the disk.
809 If you know the inner and outer radius you will be able
810 to create a pre distorted image that later may appear
811 undistorted on the disk.
812 tattoofile=name
814 Use this option together with -checkdrive to write an
815 image prepared for the Yamaha DiskT@2 feature to the
816 medium. The file must be a file with raw image B&W data
817 (one byte per pixel) in a size as retrieved by a previous
818 call to tattoofile=name . If the size of the image
819 equals the maximum possible size (3744 x 320 pixel),
820 wodim will use the first part of the file. This first
821 part then will be written to the leftover space on the
822 CD.
823 Note that the image must be mirrored to be readable from
825 the pick up side of the CD.
826 -setdropts
828 Set the driveropts specified by driveropts=option list, the
829 speed of the drive and the dummy flag and exit. This allows
830 wodim to set drive specific parameters that are not directly
831 used by wodim like e.g. single session mode, hide cdr and simi‐
832 lar. It is needed in case that driveropts=option list should be
833 called without planning to run a typical wodim task.
834 -checkdrive
836 Checks if a driver for the current drive is present and exit.
837 If the drive is a known drive, wodim uses exit code 0.
838 -prcap Print the drive capabilities for SCSI-3/mmc compliant drives as
840 obtained from mode page 0x2A. Values marked with kB use 1000
841 bytes as kilo-byte, values marked with KB use 1024 bytes as
842 Kilo-byte.
843 -inq Do an inquiry for the drive, print the inquiry info and exit.
845 -scanbus
847 Scan all SCSI devices on all SCSI busses and print the inquiry
848 strings. This option may be used to find SCSI address of the
849 CD/DVD-Recorder on a system. If some device types are invisible,
850 try using dev=ATA: or similar option to give a hint about the
851 device type you are looking for. The numbers printed out as
852 labels are computed by: bus * 100 + target. On platforms and
853 device systems without persistent SCSI number management the
854 results are not reliable. Use the .B --devices option instead.
855 --devices
857 Look for useable devices using the system specific functions,
858 eg. probing with usual device nodes in /dev/*, and display the
859 detections using symbolic device names in OS specific syntax.
860 -reset Try to reset the SCSI bus where the CD recorder is located. This
862 works not on all operating systems.
863 -abort Try to send an abort sequence to the drive. If you use wodim
865 only, this should never be needed; but other software may leave
866 a drive in an unusable condition. Calling wodim -reset may be
867 needed if a previous write has been interrupted and the software
868 did not tell the drive that it will not continue to write.
869 -overburn
871 Allow wodim to write more than the official size of a medium.
872 This feature is usually called overburning and depends on the
873 fact that most blank media may hold more space than the official
874 size. As the official size of the lead-out area on the disk is
875 90 seconds (6750 sectors) and a disk usually works if there are
876 at least 150 sectors of lead out, all media may be overburned by
877 at least 88 seconds (6600 sectors). Most CD recorders only do
878 overburning in SAO or RAW mode. Known exceptions are TEAC CD-
879 R50S, TEAC CD-R55S and the Panasonic CW-7502. Some drives do
880 not allow to overburn as much as you might like and limit the
881 size of a CD to e.g. 76 minutes. This problem may be circum‐
882 vented by writing the CD in RAW mode because this way the drive
883 has no chance to find the size before starting to burn. There
884 is no guarantee that your drive supports overburning at all.
885 Make a test to check if your drive implements the feature.
886 -ignsize
888 Ignore the known size of the medium. This option should be used
889 with extreme care, it exists only for debugging purposes don't
890 use it for other reasons. It is not needed to write disks with
891 more than the nominal capacity. This option implies -overburn.
892 -useinfo
894 Use *.inf files to overwrite audio options. If this option is
895 used, the pregap size information is read from the *.inf file
896 that is associated with the file that contains the audio data
897 for a track.
898 If used together with the -audio option, wodim may be used to
900 write audio CDs from a pipe from icedax if you call wodim with
901 the *.inf files as track parameter list instead of using audio
902 files. The audio data is read from stdin in this case. See
903 EXAMPLES section below. wodim first verifies that stdin is not
904 connected to a terminal and runs some heuristic consistency
905 checks on the *.inf files and then sets the track lengths from
906 the information in the *.inf files.
907 If you like to write from stdin, make sure that wodim is called
909 with a large enough FIFO size, reduce the write speed to a value
910 below the read speed of the source drive and switch the burn-
911 free option for the recording drive on.
912 defpregap=#
914 Set the default pre-gap size for all tracks except track number
915 1. This option currently only makes sense with the TEAC drive
916 when creating track-at-once disks without the 2 second silence
917 before each track.
918 This option may go away in future.
919 -packet
921 Set Packet writing mode. This is an experimental interface.
922 pktsize=#
924 Set the packet size to #, forces fixed packet mode. This is an
925 experimental interface.
926 -noclose
928 Do not close the current track, useful only when in packet writ‐
929 ing mode. This is an experimental interface.
930 mcn=med_cat_nr
932 Set the Media Catalog Number of the CD to med_cat_nr.
933 -text Write CD-Text information based on information taken from a file
935 that contains ascii information for the text strings. wodim
936 supports CD-Text information based on the content of the *.inf
937 files created by icedax and CD-Text information based on the
938 content from a CUE sheet file. If a CUE sheet file contains
939 both (binary CDTEXTFILE and text based SONGWRITER) entries, then
940 the information based on the CDTEXTFILE entry will win.
941 You need to use the -useinfo option in addition in order to tell
943 wodim to read the *.inf files or cuefile=filename in order to
944 tell wodim to read a CUE sheet file in addition. If you like to
945 write your own CD-Text information, edit the *.inf files or the
946 CUE sheet file with a text editor and change the fields that are
947 relevant for CD-Text.
948 textfile=filename
950 Write CD-Text based on information found in the binary file
951 filename. This file must contain information in a data format
952 defined in the SCSI-3 MMC-2 standard and in the Red Book. The
953 four byte size header that is defined in the SCSI standard is
954 optional and allows to make the recognition of correct data less
955 ambiguous. This is the best option to be used to copy CD-Text
956 data from existing CDs that already carry CD-Text information.
957 To get data in a format suitable for this option use wodim -vv
958 -toc to extract the information from disk. If both,
959 textfile=filename and CD-Text information from *.inf or *.cue
960 files are present, textfile=filename will overwrite the other
961 information.
962 cuefile=filename
964 Take all recording related information from a CDRWIN compliant
965 CUE sheet file. No track files are allowed when this option is
966 present and the option -dao is currently needed in addition.
967
970 Track options may be mixed with track file names.
971 isrc=ISRC_number
973 Set the International Standard Recording Number for the next
974 track to ISRC_number.
975 index=list
977 Sets an index list for the next track. In index list is a comma
978 separated list of numbers that are counting from index 1. The
979 first entry in this list must contain a 0, the following numbers
980 must be an ascending list of numbers (counting in 1/75 seconds)
981 that represent the start of the indices. An index list in the
982 form: 0,7500,15000 sets index 1 to the start of the track, index
983 2 100 seconds from the start of the track and index 3 200 sec‐
984 onds from the start of the track.
985 -audio If this flag is present, all subsequent tracks are written in
987 CD-DA (similar to Red Book) audio format. The file with data
988 for this tracks should contain stereo, 16-bit digital audio with
989 44100 samples/s. The byte order should be the following: MSB
990 left, LSB left, MSB right, LSB right, MSB left and so on. The
991 track should be a multiple of 2352 bytes. It is not possible to
992 put the master image of an audio track on a raw disk because
993 data will be read in multiple of 2352 bytes during the recording
994 process.
995 If a filename ends in .au or .wav the file is considered to be a
997 structured audio data file. wodim assumes that the file in this
998 case is a Sun audio file or a Microsoft .WAV file and extracts
999 the audio data from the files by skipping over the non-audio
1000 header information. In all other cases, wodim will only work
1001 correctly if the audio data stream does not have any header.
1002 Because many structured audio files do not have an integral num‐
1003 ber of blocks (1/75th second) in length, it is often necessary
1004 to specify the -pad option as well. wodim recognizes that audio
1005 data in a .WAV file is stored in Intel (little-endian) byte
1006 order, and will automatically byte-swap the data if the CD
1007 recorder requires big-endian data. wodim will reject any audio
1008 file that does not match the Red Book requirements of 16-bit
1009 stereo samples in PCM coding at 44100 samples/second.
1010 Using other structured audio data formats as input to wodim will
1012 usually work if the structure of the data is the structure
1013 described above (raw pcm data in big-endian byte order). How‐
1014 ever, if the data format includes a header, you will hear a
1015 click at the start of a track.
1016 If neither -data nor -audio have been specified, wodim defaults
1018 to -audio for all filenames that end in .au or .wav and to -data
1019 for all other files.
1020 -swab If this flag is present, audio data is assumed to be in byte-
1022 swapped (little-endian) order. Some types of CD-Writers e.g.
1023 Yamaha, Sony and the new SCSI-3/mmc drives require audio data to
1024 be presented in little-endian order, while other writers require
1025 audio data to be presented in the big-endian (network) byte
1026 order normally used by the SCSI protocol. wodim knows if a CD-
1027 Recorder needs audio data in big- or little-endian order, and
1028 corrects the byte order of the data stream to match the needs of
1029 the recorder. You only need the -swab flag if your data stream
1030 is in Intel (little-endian) byte order.
1031 Note that the verbose output of wodim will show you if swapping
1033 is necessary to make the byte order of the input data fit the
1034 required byte order of the recorder. wodim will not show you if
1035 the -swab flag was actually present for a track.
1036 -data If this flag is present, all subsequent tracks are written in
1038 CD-ROM mode 1 (Yellow Book) format. The data size is a multiple
1039 of 2048 bytes. The file with track data should contain an
1040 ISO-9660 or Rock Ridge filesystem image (see genisoimage for
1041 more details). If the track data is an ufs filesystem image,
1042 fragment size should be set to 2 KB or more to allow CD-drives
1043 with 2 KB sector size to be used for reading.
1044 -data is the default, if no other flag is present and the file
1046 does not appear to be of one of the well known audio file types.
1047 If neither -data nor -audio have been specified, wodim defaults
1049 to -audio for all filenames that end in .au or .wav and to -data
1050 for all other files.
1051 -mode2 If this flag is present, all subsequent tracks are written in
1053 CD-ROM mode 2 format. The data size is a multiple of 2336 bytes.
1054 -xa If this flag is present, all subsequent tracks are written in
1056 CD-ROM XA mode 2 form 1 format. The data size is a multiple of
1057 2048 bytes. The XA sector sub headers will be created by the
1058 drive. With this option, the write mode is the same as with the
1059 -multi option.
1060 -xa1 If this flag is present, all subsequent tracks are written in
1062 CD-ROM XA mode 2 form 1 format. The data size is a multiple of
1063 2056 bytes. The XA sector sub headers are part of the user data
1064 and have to be supplied by the application that prepares the
1065 data to be written.
1066 -xa2 If this flag is present, all subsequent tracks are written in
1068 CD-ROM XA mode 2 form 2 format. The data is a multiple of 2324
1069 bytes. The XA sector sub headers will be created by the drive.
1070 -xamix If this flag is present, all subsequent tracks are written in a
1072 way that allows a mix of CD-ROM XA mode 2 form 1/2 format. The
1073 data size is a multiple of 2332 bytes. The XA sector sub head‐
1074 ers are part of the user data and have to be supplied by the
1075 application that prepares the data to be written. The CRC and
1076 the P/Q parity ECC/EDC information (depending on the sector
1077 type) have to be supplied by the application that prepares the
1078 data to be written.
1079 -cdi If this flag is present, the TOC type for the disk is set to
1081 CDI. This only makes sense with XA disks.
1082 -isosize
1084 Use the ISO-9660 file system size as the size of the next track.
1085 This option is needed if you want wodim to directly read the
1086 image of a track from a raw disk partition or from a TAO master
1087 CD. In the first case the option -isosize is needed to limit the
1088 size of the CD to the size of the ISO filesystem. In the second
1089 case the option -isosize is needed to prevent wodim from reading
1090 the two run out blocks that are appended by each CD-recorder in
1091 track at once mode. These two run out blocks cannot be read and
1092 would cause a buffer underrun that would cause a defective copy.
1093 Do not use this option on files created by genisoimage and in
1094 case wodim reads the track data from stdin. In the first case,
1095 you would prevent wodim from writing the amount of padding that
1096 has been appended by genisoimage and in the latter case, it will
1097 not work because stdin is not seekable.
1098 If -isosize is used for a track, wodim will automatically add
1100 padding for this track as if the -pad option has been used but
1101 the amount of padding may be less than the padding written by
1102 genisoimage. Note that if you use -isosize on a track that con‐
1103 tains Sparc boot information, the boot information will be lost.
1104 Note also that this option cannot be used to determine the size
1106 of a file system if the multi session option is present.
1107 -pad If the track is a data track, 15 sectors of zeroed data will be
1109 added to the end of this and each subsequent data track. In
1110 this case, the -pad option is superseded by the padsize= option.
1111 It will remain however as a shorthand for padsize=15s. If the
1112 -pad option refers to an audio track, wodim will pad the audio
1113 data to be a multiple of 2352 bytes. The audio data padding is
1114 done with binary zeroes which is equal to absolute silence.
1115 -pad remains valid until disabled by -nopad.
1117 padsize=#
1119 Set the amount of data to be appended as padding to the next
1120 track to #. Opposed to the behavior of the -pad option, the
1121 value for padsize= is reset to zero for each new track. wodim
1122 assumes a sector size of 2048 bytes for the padsize= option,
1123 independent from the real sector size and independent from the
1124 write mode. The megabytes mentioned in the verbose mode output
1125 however are counting the output sector size which is e.g. 2448
1126 bytes when writing in RAW/RAW96 mode. See fs= option for possi‐
1127 ble arguments. To pad the equivalent of 20 minutes on a CD, you
1128 may write padsize=20x60x75s. Use this option if your CD-drive
1129 is not able to read the last sectors of a track or if you want
1130 to be able to read the CD on a Linux system with the ISO-9660
1131 filesystem read ahead bug. If an empty file is used for track
1132 data, this option may be used to create a disk that is entirely
1133 made of padding. This may e.g. be used to find out how much
1134 overburning is possible with a specific media.
1135 -nopad Do not pad the following tracks - the default.
1137 -shorttrack
1139 Allow all subsequent tracks to violate the Red Book track length
1140 standard which requires a minimum track length of 4 seconds.
1141 This option is only useful when used in SAO or RAW mode. Not
1142 all drives support this feature. The drive must accept the
1143 resulting CUE sheet or support RAW writing.
1144 -noshorttrack
1146 Re-enforce the Red Book track length standard. Tracks must be at
1147 least 4 seconds.
1148 pregap=#
1150 Set the pre-gap size for the next track. This option currently
1151 only makes sense with the TEAC drive when creating track-at-once
1152 disks without the 2 second silence before each track.
1153 This option may go away in future.
1154 -preemp
1156 If this flag is present, all TOC entries for subsequent audio
1157 tracks will indicate that the audio data has been sampled with
1158 50/15 microsec pre-emphasis. The data, however is not modified
1159 during the process of transferring from file to disk. This
1160 option has no effect on data tracks.
1161 -nopreemp
1163 If this flag is present, all TOC entries for subsequent audio
1164 tracks will indicate that the audio data has been mastered with
1165 linear data - this is the default.
1166 -copy If this flag is present, all TOC entries for subsequent audio
1168 tracks of the resulting CD will indicate that the audio data has
1169 permission to be copied without limit. This option has no
1170 effect on data tracks.
1171 -nocopy
1173 If this flag is present, all TOC entries for subsequent audio
1174 tracks of the resulting CD will indicate that the audio data has
1175 permission to be copied only once for personal use - this is the
1176 default.
1177 -scms If this flag is present, all TOC entries for subsequent audio
1179 tracks of the resulting CD will indicate that the audio data has
1180 no permission to be copied anymore.
1181 tsize=#
1183 If the master image for the next track has been stored on a raw
1184 disk, use this option to specify the valid amount of data on
1185 this disk. If the image of the next track is stored in a regular
1186 file, the size of that file is taken to determine the length of
1187 this track. If the track contains an ISO 9660 filesystem image
1188 use the -isosize option to determine the length of that filesys‐
1189 tem image.
1190 In Disk at Once mode and with some drives that use the TEAC pro‐
1191 gramming interface, even in Track at Once mode, wodim needs to
1192 know the size of each track before starting to write the disk.
1193 wodim now checks this and aborts before starting to write. If
1194 this happens you will need to run genisoimage -print-size before
1195 and use the output (with `s' appended) as an argument to the
1196 tsize= option of wodim (e.g. tsize=250000s).
1197 See fs= option for possible arguments.
1198
1201 For all examples below, it will be assumed that the CD/DVD-Recorder is
1202 connected to the primary SCSI bus of the machine. The SCSI target id is
1203 set to 2.
1204 To record a pure CD-ROM at double speed, using data from the file cdim‐
1206 age.raw:
1207 wodim -v speed=2 dev=2,0 cdimage.raw
1209 To create an image for a ISO 9660 filesystem with Rock Ridge exten‐
1211 sions:
1212 genisoimage -R -o cdimage.raw /home/joerg/master/tree
1214 To check the resulting file before writing to CD on Solaris:
1216 mount -r -F fbk -o type=hsfs /dev/fbk0:cdimage.raw /mnt
1218 On Linux:
1220 mount cdimage.raw -r -t iso9660 -o loop /mnt
1222 Go on with:
1224 ls -lR /mnt
1225 umount /mnt
1226 If the overall speed of the system is sufficient and the structure of
1228 the filesystem is not too complex, wodim will run without creating an
1229 image of the ISO 9660 filesystem. Simply run the pipeline:
1230 genisoimage -R /master/tree | wodim -v fs=6m speed=2 dev=2,0 -
1232 The recommended minimum FIFO size for running this pipeline is 4
1234 MBytes. As the default FIFO size is 4 MB, the fs= option needs only be
1235 present if you want to use a different FIFO size. If your system is
1236 loaded, you should run genisoimage in the real time class too. To
1237 raise the priority of genisoimage replace the command
1238 genisoimage -R /master/tree
1240 by
1241 priocntl -e -c RT -p 59 genisoimage -R /master/tree
1242 on Solaris and by
1244 nice --18 genisoimage -R /master/tree
1246 on systems that don't have UNIX International compliant real-time
1248 scheduling.
1249 wodim runs at priority 59 on Solaris, you should run genisoimage at no
1251 more than priority 58. On other systems, you should run genisoimage at
1252 no less than nice --18.
1253 Creating a CD-ROM without file system image on disk has been tested on
1255 a Sparcstation-2 with a Yamaha CDR-400. It did work up to quad speed
1256 when the machine was not loaded. A faster machine may be able to han‐
1257 dle quad speed also in the loaded case.
1258 To record a pure CD-DA (audio) at single speed, with each track con‐
1260 tained in a file named track01.cdaudio, track02.cdaudio, etc:
1261 wodim -v speed=1 dev=/dev/cdrw -audio track*.cdaudio
1263 To check if it will be ok to use double speed for the example above.
1265 Use the dummy write option:
1266 wodim -v -dummy speed=2 dev=/dev/cdrw -audio track*.cdaudio
1268 To record a mixed-mode CD with an ISO 9660 filesystem from cdimage.raw
1270 on the first track, the other tracks being audio tracks from the files
1271 track01.cdaudio, track02.cdaudio, etc:
1272 wodim -v dev=2,0 cdimage.raw -audio track*.cdaudio
1274 To handle drives that need to know the size of a track before starting
1276 to write, first run
1277 genisoimage -R -q -print-size /master/tree
1279 and then run
1281 genisoimage -R /master/tree | wodim speed=2 dev=2,0 tsize=XXXs -
1283 where XXX is replaced by the output of the previous run of genisoimage.
1285 To copy an audio CD in the most accurate way, first run
1287 icedax dev=/dev/cdrom -vall cddb=0 -B -Owav
1289 and then run
1291 wodim dev=/dev/cdrw -v -dao -useinfo -text *.wav
1293 This will try to copy track indices and to read CD-Text information
1295 from disk. If there is no CD-Text information, icedax will try to get
1296 the information from freedb.org instead.
1297 To copy an audio CD from a pipe (without intermediate files), first run
1299 icedax dev=1,0 -vall cddb=0 -info-only
1301 and then run
1303 icedax dev=1,0 -no-infofile -B -Oraw - | \
1305 wodim dev=2,0 -v -dao -audio -useinfo -text *.inf
1306 This will get all information (including track size info) from the
1308 *.inf files and then read the audio data from stdin.
1309 If you like to write from stdin, make sure that wodim is called with a
1311 large enough FIFO size (e.g. fs=128m), reduce the write speed to a
1312 value below the read speed of the source drive (e.g. speed=12), and
1313 get a CD/DVD drive with BURN-Free feature if it is not available yet.
1314 To set drive options without writing a CD (e.g. to switch a drive to
1316 single session mode), run
1317 wodim dev=1,0 -setdropts driveropts=singlesession
1319 If you like to do this when no CD is in the drive, call
1321 wodim dev=1,0 -force -setdropts driveropts=singlesession
1323 To copy a CD in clone mode, first read the master CD using:
1325 readom dev=b,t,l -clone f=somefile
1327 or (in case the CD contains many sectors that are unreadable by inten‐
1329 tion) by calling:
1330 readom dev=1,0 -clone -nocorr f=somefile
1332 will create the files somefile and somefile.toc. Then write the CD
1334 using:
1335 wodim dev=1,0 -raw96r -clone -v somefile
1337
1341 CDR_DEVICE
1342 This may either hold a device identifier that is suitable to the
1343 open call of the SCSI transport library or a label in the file
1344 /etc/wodim.conf.
1345 CDR_SPEED
1347 Sets the default speed value for writing (see also speed=
1348 option).
1349 CDR_FIFOSIZE
1351 Sets the default size of the FIFO (see also fs=# option).
1352 CDR_FORCERAWSPEED
1354 If this environment variable is set, wodim will allow you to
1355 write at the full RAW encoding speed a single CPU supports.
1356 This will create high potential of buffer underruns. Use with
1357 care.
1358 CDR_FORCESPEED
1360 If this environment variable is set, wodim will allow you to
1361 write at the full DMA speed the system supports. There is no
1362 DMA reserve for reading the data that is to be written from
1363 disk. This will create high potential of buffer underruns. Use
1364 with care.
1365 RSH If the RSH environment is present, the remote connection will
1367 not be created via rcmd(3) but by calling the program pointed to
1368 by RSH. Use e.g. RSH=/usr/bin/ssh to create a secure shell
1369 connection.
1370 Note that this forces wodim to create a pipe to the rsh(1) pro‐
1372 gram and disallows wodim to directly access the network socket
1373 to the remote server. This makes it impossible to set up per‐
1374 formance parameters and slows down the connection compared to a
1375 root initiated rcmd(3) connection.
1376 RSCSI If the RSCSI environment is present, the remote SCSI server will
1378 not be the program /opt/schily/sbin/rscsi but the program
1379 pointed to by RSCSI. Note that the remote SCSI server program
1380 name will be ignored if you log in using an account that has
1381 been created with a remote SCSI server program as login shell.
1382
1385 /etc/wodim.conf
1386 Default values can be set for the following options in
1387 /etc/wodim.conf. For example: CDR_FIFOSIZE=8m or CDR_SPEED=2
1388 CDR_DEVICE
1390 This may either hold a device identifier that is suitable
1391 to the open call of the SCSI transport library or a label
1392 in the file /etc/wodim.conf that allows to identify a
1393 specific drive on the system.
1394 CDR_SPEED
1396 Sets the default speed value for writing (see also speed=
1397 option).
1398 CDR_FIFOSIZE
1400 Sets the default size of the FIFO (see also fs=# option).
1401 CDR_MAXFIFOSIZE
1403 Sets the maximum size of the FIFO (see also fs=# option).
1404 Any other keyword (label) is an identifier (symbolic name) for a
1406 specific drive
1407 on the system. Such an identifier may not contain the
1408 characters ',', '/', '@' or ':'.
1409 Each line that follows a label contains a whitespace sep‐
1411 arated list of items. Currently, four items are recog‐
1412 nized: the drive's target specification, the default
1413 speed that should be used for this drive, the default
1414 FIFO size that should be used for this drive and drive
1415 specific options. The values for speed and fifosize may
1416 be set to -1 to tell wodim to use the global defaults.
1417 target can be -1 to use the auto-guessing of the drive
1418 (see above).
1419 The value for driveropts may be omitted or set to "" if
1421 no driveropts are used. A typical line may look this
1422 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 accessible 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 experience 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 generally 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 derived from "cdrecord" as included in the cdrtools
1664 package [1] created by Joerg Schilling, who deserves most of the credit
1665 for its success. However, he is not involved into the development of
1666 this spinoff and therefore he shall not be held responsible for any
1667 problems caused by it. Do not refer to this application as "cdrecord",
1668 do not try to get support for wodim by contacting the original authors.
1669 Additional information can be found on:
1671 https://alioth.debian.org/projects/debburn/
1672 If you have support questions, send them to
1674 debburn-devel@lists.alioth.debian.org
1676 If you have definitely found a bug, send a mail to this list or to
1678 submit@bugs.debian.org
1680 writing at least a short description into the Subject and "Package:
1682 cdrkit" in the first line of the mail body.
1683
1685 [1] Cdrtools 2.01.01a08 from May 2006, http://cdrecord.berlios.de
1686 Version 2.0 wodim(1)