Clarified behavior of burn_source with pipes
This commit is contained in:
parent
de274ddaff
commit
6053f3a6e3
@ -1 +1 @@
|
|||||||
#define Cdrskin_timestamP "2008.11.01.121240"
|
#define Cdrskin_timestamP "2008.11.08.134828"
|
||||||
|
@ -384,6 +384,13 @@ struct burn_source {
|
|||||||
The size of a sector depends on BURN_MODE_*. The known range is
|
The size of a sector depends on BURN_MODE_*. The known range is
|
||||||
2048 to 2352.
|
2048 to 2352.
|
||||||
|
|
||||||
|
If this call is reading from a pipe then it will learn
|
||||||
|
about the end of data only when that pipe gets closed on the
|
||||||
|
feeder side. So if the track size is not fixed or if the pipe
|
||||||
|
delivers less than the predicted amount or if the size is not
|
||||||
|
block aligned, then burning will halt until the input process
|
||||||
|
closes the pipe.
|
||||||
|
|
||||||
IMPORTANT:
|
IMPORTANT:
|
||||||
If this function pointer is NULL, then the struct burn_source is of
|
If this function pointer is NULL, then the struct burn_source is of
|
||||||
version >= 1 and the job of .(*read)() is done by .(*read_xt)().
|
version >= 1 and the job of .(*read)() is done by .(*read_xt)().
|
||||||
|
Loading…
Reference in New Issue
Block a user