Hi, it’s allways funny to see Linux users here too :). I have the 7S drive too, and I’m using k3b, cdrdao and xcdroast (in fact, cdrdao and cdrecord). The question “whitch driver is better?” has no easy answer, so I think the best is to put the information I have about the two drivers and my final conclusion.
This is a driver for SCSI-3/mmc compatible CD-recorders that support
session-at-once (cue sheet based) writing. Most of the recent drives
(ATAPI, SCSI, USB, Parallel Port) should be compatible with this or
with the ‘generic-mmc-raw’ driver described below. Data track writing
support is also available.
‘read-toc’ scans linearly the Q sub-channel of each track to retrieve
the pre-gap length and index marks. This method is very accurate but
takes the same time like digital audio extraction. It should also work
with recent CD-ROM readers.
0x00000001: Read 16 bytes PQ sub-channel instead of 96 byte
raw P-W sub-channel data. If 'read-toc'/'read-cd'
fails on your drive try to select this option.
0x00000002: Only used if option '0x00000001' is selected. If set
the read PQ sub-channel data is expected to contain
BCD instead of HEX values. If the time count that
is displayed while running 'read-toc' jumps you will
have to toggle this option.
0x00000004: Do not take ISRC code from the sub-channel data but use
the appropriate SCSI command for reading the ISRC
code. This option is automatically selected if 16
byte PQ sub-channel data with HEX values is used.
0x00000008: Try to retrieve the media catalog number by scanning
the sub-channels instead of using the appropriate
SCSI command. This might be an option if the CD-R/CD-ROM
drive does not extract the catalog number otherwise.
Note: A media catalog number need not be present on
on a CD.
0x00000020: Use this option if the drive cannot read sub-channel
data along with audio data. A binary search method for
pre-gap and index mark extraction will be selected in
this case which has to play a sector before the
sub-channel data can be retrieved.
If 'read-toc'/'read-cd' works only with this option
you should consider to use '--fast-toc' since the
data retrieved with the binary search method is usually
not very reliable and not worth the additional time.
0x00000100: Force using the raw R-W sub-channel reading mode for audio
and data tracks.
0x00000010: Enable CD-TEXT writing. This must be done explicitly
because there is no way to detect if a recorder supports
CD-TEXT writing. Trying to write CD-TEXT data with
recorders that do not support this feature usually
results in an error message at the beginning of the
recording process and in real write mode the medium
will be unusable.
0x00000040: Suppresses the activation of the BURN Proof feature.
0x00000080: If the drive does not support packed R-W sub-channel writing
(the drive does not support the L-EC data creation and
interleaving for R-W sub-channel data) you will have to
specify this option. Cdrdao will perform all the encoding
and write in raw R-W mode. If the drive does not support the
raw R-W writing mode, too, it is not possible to write
This is an alternate driver for SCSI-3/mmc compatible CD-recorders.
It uses the raw writing interface where the driver has to provide the
PQ sub-channel data in addition to the audio data. This writing mode
allows using part of the lead-out area for audio data since the drive’s
firmware has no chance to prevent this. Of course, you will get some
error message at the end of writing when the CD-R capacity is exhausted.
Multi session recording is currently not supported.
CD structure analysis is done like in the ‘generic-mmc’ driver.
All of 'generic-mmc' except
0x00000010: CD-TEXT writing capability is automatically determined.
0x00000080: R-W sub-channel writing capability is automatically determined.
If you are going to record audio or data to backup something, use the generic-mmc driver, to 1:1 use generic-mmc-raw.