cdrecord padsize. Bug or feature ?

[scdbackup@gmx.net]

Hi,

this about a discrepancy between the man page and the behavior of cdrecord
when writing multiple data tracks.

After a track is done the padsize= value does not get reset to zero but
obviously to 30k. At least the messages of cdrecord say so.
I have no problem with that behavior and given the fact that it is probably
quite traditional i propose to change the man page rather than the program.

(If you ask me why i write two data tracks: it's for pure curiosity.)

Freshly tested:

  $ cdrecord -version
  Cdrecord-Clone 2.01.01a04 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling

  $ cdrecord -v -sao dev=0,0,0 padsize=300k fs=8m -eject driveropts=burnfree \
             -data speed=8 /dvdbuffer/fertig.iso /dvdbuffer/fertig.afio 
  ...
  Starting new track at sector: 0
  Track 01:  125 of  125 MB written (fifo 100%) [buf  99%]   8.0x.
  WARNING: padding up to secsize.
  Track 01: writing 300 KB of pad data.
  Track 01: Total bytes read/written: 131198521/131506176 (64212 sectors).
  Writing pregap for track 2 at 64212
  Starting new track at sector: 64362
  Track 02:   38 of   38 MB written (fifo 100%) [buf  99%]   8.5x.
  WARNING: padding up to secsize.
  Track 02: writing  30 KB of pad data.
  Track 02: Total bytes read/written: 40104790/40136704 (19598 sectors).
  ...

  $ man .../cdrtools-2.01.01/cdrecord/cdrecord.1
  ...
       padsize=#
              Set the amount of data to be appended as padding to
              the  next  track  to #.  Opposed to the behavior of
              the -pad option, the value for padsize= is reset to
              zero for each new track.
  ...


Have a nice day :)

Thomas