xorrecord: NonCdrecord
5.5 Options not compatible to cdrecord
======================================
--no_rc
Only if used as first command line argument this option prevents
reading and interpretation of startup files. See section FILES
below.
drive_scsi_dev_family=sr|sdc|sg|default
GNU/Linux specific:
By default, cdrskin tries to map Linux drive addresses to /dev/sr*
before they get opened for operating the drive. This coordinates
well with other use cases of optical drives, like mount(8). But
since year 2010 all /dev/sr* share a global lock which allows only
one drive to process an SCSI command while all others have to wait
for its completion. This yields awful throughput if more than one
drive is writing or reading simultaneously.
The global lock is not applied to device files /dev/sg* and also
not with the system calls read(2), write(2). But ioctl(SG_IO) is
affected, which is needed to perform the SCSI commands for optical
burning.
So for simultaneous burn runs on modern GNU/Linux it is advisable
to use drive_scsi_dev_family="sg". The drive addresses may then
well be given as /dev/sr* but will nevertheless get used as
/dev/sg*.
--grow_overwriteable_iso
Enable emulation of multi-session writing on overwriteable media
which contain an ISO 9660 filesystem. This emulation is learned
from growisofs -M but adapted to the usage model of
xorrecord -msinfo
xorrisofs -C -M | xorrecord -waiti -multi -
for sequential media.
-grow_overwriteable_iso does not hamper the use of true
multi-session media. I.e. it is possible to use the same
'xorrecord' options with both kinds of media and to achieve similar
results if ISO 9660 filesystem images are to be written. This
option implies option -isosize and therefore demands that the track
source is a ISO 9660 filesystem image.
With overwriteable media and no option blank=fast|all present it
expands an eventual ISO 9660 filesystem on media. It is assumed
that this image's inner size description points to the end of the
valuable data. Overwriteable media with a recognizable ISO 9660
size will be regarded as appendable rather than as blank. I.e.
options -msinfo and -toc will work. -toc will always show a single
session with its size increasing with every added ISO 9660 image.
--multi_if_possible
Apply option -multi if the medium is suitable. Not suitable are
DVD-R DL and DVD-RW, which were blanked with mode
"deformat_quickest".
Not all drives correctly recognize such fast-blanked DVD-RW which
need "on". If there is well founded suspicion that a burn run
failed due to -multi, then this causes a re-try without -multi.
stream_recording="on"|"off"|number
Mode "on" requests that compliance to the desired speed setting is
preferred over management of write errors. With DVD-RAM and BD
this can bring effective write speed near to the nominal write
speed of the media. But it will also disable the automatic use of
replacement blocks if write errors occur. It might as well be
disliked or ignored by the drive.
If a number is given, then error management stays enabled for all
byte addresses below that number. Any number below 16s is the same
as "off".
dvd_obs="default"|"32k"|"64k"
Linux specific: Set the number of bytes to be transmitted with each
write operation to DVD or BD media. Tracks get padded up to the
next multiple of this write size. A number of 64 KB may improve
throughput with bus systems which show latency problems. The
default depends on media type, option stream_recording=, and on
compile time options.
modesty_on_drive=parameter[:parameters]
Control whether the drive buffer shall be kept from getting
completely filled. Parameter "on" (or "1") keeps the program from
trying to write to the burner drive while its buffer is in danger
to be filled over a given limit. If this filling is exceeded then
the program will wait until the filling reaches a given low
percentage value.
This can ease the load on operating system and drive controller and
thus help with achieving better input bandwidth if disk and burner
are not on independent controllers (like hda and hdb). It may also
help with simultaneous burns on different burners with Linux
kernels like 3.16, if one has reason not to fix the problem by
drive_scsi_dev_family="sg". On the other hand it increases the
risk of buffer underflow and thus reduced write speed.
Some burners are not suitable because they report buffer fill with
granularity too coarse in size or time, or expect their buffer to
be filled to the top before they go to full speed.
Parameters "off" or "0" disable this feature.
The threshold for beginning to wait is given by parameter
"max_percent=". Parameter "min_percent=" defines the threshold for
resuming transmission. Percentages are permissible in the range of
25 to 100. Numbers in this range without a prepended name are
interpreted as "on:min_percent=".
E.g.: modesty_on_drive=75
The optimal values depend on the buffer behavior of the drive.
Parameter "timeout_sec=" defines after which time of unsuccessful
waiting the modesty shall be disabled because it does not work.
Parameter "min_usec=" defines the initial sleeping period in
microseconds. If the drive buffer appears to be too full for
sending more data, the program will wait the given time and inquire
the buffer fill state again. If repeated inquiry shows not enough
free space, the sleep time will slowly be increased to what
parameter "max_usec=" defines.
Parameters, which are not mentioned with a modesty_on_drive=
option, stay unchanged. Default is:
modesty_on_drive=off:min_percent=90:max_percent=95:
timeout_sec=120:min_usec=5000:max_usec=25000
use_immed_bit="on"|"off"|"default"
Control whether several long lasting SCSI commands shall be
executed with the Immed bit, which makes the commands end early
while the drive operation is still going on. xorriso then inquires
progress indication until the drive reports to be ready again. If
this feature is turned off, then blanking and formatting will show
no progress indication.
It may depend on the operating system whether -use_immed_bit is set
to "off" by default.
write_start_address=value
Set the block address on overwritable media where to start writing
the track. With DVD+RW, DVD-RAM or BD-RE, byte_offset must be
aligned to 2 kiB blocks, but better is 32 kiB on DVD and 64 kiB on
BD. With formatted DVD-RW 32 kiB alignment is mandatory.
Other media are not suitable for this option.
stdio_sync="on"|"off"|number
Set the number of bytes after which to force output to emulated
stdio: drives. This forcing keeps the memory from being clogged
with lots of pending data for slow devices. Default "on" is the
same as "16m". Forced output can be disabled by "off".
Info Catalog
xorrecord: Verbous
xorrecord: Options
xorrecord: ExDevices