New command -modesty_on_drive, new -as cdrecord -immed, minbuf=, modesty_on_drive=
This commit is contained in:
@ -9,7 +9,7 @@
|
||||
.\" First parameter, NAME, should be all caps
|
||||
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
.\" other parameters are allowed: see man(7), man(1)
|
||||
.TH XORRECORD 1 "Version 1.4.1, May 17, 2015"
|
||||
.TH XORRECORD 1 "Version 1.4.1, Jul 30, 2015"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -100,8 +100,8 @@ device file.
|
||||
On Solaris, the user needs r\-permission and privilege "sys_devices",
|
||||
which is usually gained by running \fBxorrecord\fR via command pfexec.
|
||||
.br
|
||||
These permissions resp. privileges are needed already for listing a drive.
|
||||
So it might be necessary to get the overview as superuser resp. via pfexec.
|
||||
These permissions or privileges are needed already for listing a drive.
|
||||
So it might be necessary to get the overview as superuser or via pfexec.
|
||||
.br
|
||||
\fBxorrecord\fR does not perform cdrecord option \-scanbus and does
|
||||
not accept the addresses of form Bus,Target,Lun which are told by \-scanbus.
|
||||
@ -128,7 +128,7 @@ to generic xorriso command mode. See \fBman xorriso\fR for its description.
|
||||
Other than in xorriso command mode, the sequence of the cdrecord emulation
|
||||
options does not matter.
|
||||
All pending actions get performed in a fixed sequence before the program
|
||||
run ends resp. before cdrecord emulation ends.
|
||||
run ends or before cdrecord emulation ends.
|
||||
.SS
|
||||
.br
|
||||
.SH OPTIONS
|
||||
@ -471,6 +471,16 @@ MMC drives usually activate their own idea of speed and take
|
||||
the speed value given by the burn program only as a hint
|
||||
for their own decision.
|
||||
.TP
|
||||
\fBminbuf=percentage\fR
|
||||
Equivalent to:
|
||||
.br
|
||||
modesty_on_drive=<percentage>
|
||||
.TP
|
||||
\fB\-immed\fR
|
||||
Equivalent to:
|
||||
.br
|
||||
modesty_on_drive=75
|
||||
.TP
|
||||
\fB\-eject\fR
|
||||
Eject the drive tray after alll other work is done.
|
||||
.TP
|
||||
@ -490,7 +500,7 @@ Afterwards end emulation without performing any drive operation.
|
||||
\fB\-v\fR
|
||||
Increase program verbosity by one level. There are four verbosity levels
|
||||
from nearly silent to debugging verbosity. The both highest levels can
|
||||
be enabled by repeated \-v or by \-vv resp. \-vvv.
|
||||
be enabled by repeated \-v or by \-vv or by \-vvv.
|
||||
.TP
|
||||
\fB\-V\fR
|
||||
Log SCSI commands and drive replies to standard error.
|
||||
@ -569,6 +579,44 @@ 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.
|
||||
.TP
|
||||
\fBmodesty_on_drive=parameter[:parameters]\fR
|
||||
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.
|
||||
.br
|
||||
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. On the other hand it increases
|
||||
the risk of buffer underflow and thus reduced write speed.
|
||||
.br
|
||||
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.
|
||||
.br
|
||||
Parameters "off" or "0" disable this feature.
|
||||
.br
|
||||
The threshhold for beginning to wait is given by parameter "max_percent=".
|
||||
Parameter "min_percent=" defines the threshhold 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=".
|
||||
.br
|
||||
E.g.: modesty_on_drive=75
|
||||
.br
|
||||
The optimal values depend on the buffer behavior of the drive.
|
||||
.br
|
||||
There are also timing parameters "timeout_sec=", "min_usec=", "max_usec=".
|
||||
Read the description of burn_drive_set_buffer_waiting() in libburn.h,
|
||||
before setting them to non\-default values.
|
||||
.br
|
||||
Parameters, which are not mentioned with a modesty_on_drive= option,
|
||||
stay unchanged.
|
||||
Default is:
|
||||
.br
|
||||
modesty_on_drive=off:min_percent=65:max_percent=95
|
||||
.TP
|
||||
\fBwrite_start_address=value\fR
|
||||
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,
|
||||
@ -759,7 +807,7 @@ please send electronic mail to the public list <bug\-xorriso@gnu.org>.
|
||||
If more privacy is desired, mail to <scdbackup@gmx.net>.
|
||||
.br
|
||||
Please describe what you expect \fBxorriso\fR to do,
|
||||
the program arguments resp. commands by which you tried to achieve it,
|
||||
the program arguments or dialog commands by which you tried to achieve it,
|
||||
the messages of \fBxorriso\fR, and the undesirable outcome of your
|
||||
program run.
|
||||
.br
|
||||
|
Reference in New Issue
Block a user