In the cdrdao documentation the generic-mmc-raw driver
is described as a driver that besides the music data
needs to specify the P-Q subchannel data... But since
the cdrdao changelog(1.1.6) states that only the R-W
subs can be written and read, how can the raw driver
then specify the P-Q subs when burning? Or does the raw
driver just burn the raw 2352 bytes sectors, and lets
the drive itself generate the P-Q subs ? Or can cdrdao
burn the P-Q subs, but only packed and not raw ? and
does the raw driver use raw-dao or raw-sao ? And
finally.. Is the burning quality with the
generic-mmc-raw driver the same as the generic-mmc
driver ? Thanks in advance. -Martin.
Logged In: NO
When one has an image, with raw P-W Subs included, then does
the generic-mmc-raw driver just ignore the P-Q subs from the
image and generates them itself ? When one burns an image
without subs included, with the generic-mmc-raw driver, can
cdrdao then generate the P-Q subs by itself and burn them,
or does the drive generate them ? When you use :
--read-subchan rw_raw, is the raw P-W subs then extracted ?
And if you use : --read-subchan rw, is the packed R-W subs
then extracted? -Thanks in advance. -Martin.
Logged In: NO
Please just tell me if this is right : When you have an
image with raw P-W subs included, and you burn the image
with the generic-mmc-raw driver, does the generic-mmc-raw
driver then ignore the P-Q subs from the image and instead
generates them itself, so only the R-W subs is actually
taken from the image and burnt, but the P-Q subs, arent
taken from the image, but the raw driver generates them
itself, and burns them ? Thanks in advance. -Martin.