GNU/Linux |
RedHat 6.2(Zoot) |
|
![]() |
cdparanoia(1) |
![]() |
cdparanoia (Paranoia release III) − an audio CD reading utility which includes extra data verification features
version III release alpha 9.6 (17 Aug 1999)
cdparanoia [options] span [outfile]
cdparanoia retrieves audio tracks from CDDA capable CDROM drives. The data can be saved to a file or directed to standard output in WAV, AIFF, AIFF-C or raw format. Most ATAPI, SCSI and several proprietary CDROM drive makes are supported; cdparanoia can determine if the target drive is CDDA capable.
In addition to simple reading, cdparanoia adds extra-robust data verification, synchronization, error handling and scratch reconstruction capability.
−v --verbose
Be absurdly verbose about the autosensing and reading process. Good for setup and debugging.
−q --quiet
Do not print any progress or error information during the reading process.
−e --stderr-progress
Force output of progress information to stderr (for wrapper scripts).
−V --version
Print the program version and quit.
−Q --query
Perform CDROM drive autosense, query and print the CDROM table of contents, then quit.
−s --search-for-drive
Forces a complete search for a cdrom drive, even if the /dev/cdrom link exists.
−h --help
Print a brief synopsis of cdparanoia usage and options.
−p --output-raw
Output headerless data as raw 16 bit PCM data with interleaved samples in host byte order. To force little or big endian byte order, use −r or −R as described below.
−r --output-raw-little-endian
Output headerless data as raw 16 bit PCM data with interleaved samples in LSB first byte order.
−R --output-raw-big-endian
Output headerless data as raw 16 bit PCM data with interleaved samples in MSB first byte order.
−w --output-wav
Output data in Micro$oft RIFF WAV format (note that WAV data is always LSB first byte order).
−f --output-aiff
Output data in Apple AIFF format (note that AIFC data is always in MSB first byte order).
−a --output-aifc
Output data in uncompressed Apple AIFF-C format (note that AIFF-C data is always in MSB first byte order).
−B --batch
Cdda2wav-style batch output flag; cdparanoia will split the output into multiple files at track boundaries. Output file names are prepended with ’track#.’
−c --force-cdrom-little-endian
Some CDROM drives misreport their endianness (or do not report it at all); it’s possible that cdparanoia will guess wrong. Use −c to force cdparanoia to treat the drive as a little endian device.
−C --force-cdrom-big-endian
As above but force cdparanoia to treat the drive as a big endian device.
−n --force-default-sectors n
Force the interface backend to do atomic reads of n sectors per read. This number can be misleading; the kernel will often split read requests into multiple atomic reads (the automated Paranoia code is aware of this) or allow reads only wihin a restricted size range. This option should generally not be used.
−d --force-cdrom-device device
Force the interface backend to read from device rather than the first readable CDROM drive it finds. This can be used to specify devices of any valid interface type (ATAPI, SCSI or proprietary).
−g --force-generic-device device
This option is used along with −d when one wants explicit control in setting both the SCSI cdrom and generic devices seperately. This option is only useful on non-standard SCSI setups.
−S --force-read-speed number
Use this option explicitly to set the read rate of the CD drive (where supported). This can reduce underruns on machines with slow disks, or which are low on memory.
−Z --disable-paranoia
Disable data verification and correction features. When using -Z, cdparanoia reads data exactly as would cdda2wav with an overlap setting of zero. This option implies that and −Y are active, but is not equivalent to −Z −W −X −Y as the −W through −Z options specify layered levels of verification. The last specified option takes precedence.
−Y --disable-extra-paranoia
Disables intra-read data verification; only overlap checking at read boundaries is performed.
−X --disable-scratch-detection
Neither look for scratches nor perform scratch-tolerant synchronization during verification. With −X specified, a scratched disc will cause cdparanoia to abort its read.
−W --disable-scratch-repair
Detect and hold sync across scratches, but do not attempt any repair of damaged data. If an info file is in use (−i) log the frame positions of all scratches.
:-) |
Normal operation, low/no jitter | ||
:-| |
Normal operation, considerable jitter | ||
:-/ |
Read drift | ||
:-P |
Unreported loss of streaming in atomic read operation | ||
8-| |
Finding read problems at same point during reread; hard to correct | ||
:-0 |
SCSI/ATAPI transport error | ||
:-( |
Scratch detected | ||
;-( |
Gave up trying to perform a correction | ||
:^D |
Finished extracting |
<space>
No corrections needed
- |
Jitter correction required | ||
+ |
Unreported loss of streaming/other error in read | ||
! |
Errors found after stage 1 correction; the drive is making the same error through multiple re-reads, and cdparanoia is having trouble detecting them. | ||
e |
SCSI/ATAPI transport error (corrected) | ||
V |
Uncorrected error/skip |
The span argument specifies which track, tracks or subsections of tracks to read. This argument is required. NOTE: Unless the span is a simple number, it’s generally a good idea to quote the span argument to protect it from the shell.
The span argument may be a simple track number or an offset/span specification. The syntax of an offset/span takes the rough form:
1[ww:xx:yy.zz]-2[aa:bb:cc.dd]
Here, 1 and 2 are track numbers; the numbers in brackets provide a finer grained offset within a particular track. [aa:bb:cc.dd] is in hours/minutes/seconds/sectors format. Zero fields need not be specified: [::20], [:20], [20], [20.], etc, would be interpreted as twenty seconds, [10:] would be ten minutes, [.30] would be thirty sectors (75 sectors per second).
When only a
single offset is supplied, it is interpreted as a starting
offset and ripping will continue to the end of he track. If
a single offset is preceeded or followed by a hyphen, the
implicit missing offset is taken to be the start or end of
the disc, respectively. Thus:
1:[20.35]
Specifies ripping from track 1, second 20, sector 35 to the end of track 1.
1:[20.35]-
Specifies ripping from 1[20.35] to the end of the disc
−2 |
Specifies ripping from the beginning of the disc up to (and including) track 2 |
−2:[30.35]
Specifies ripping from the beginning of the disc up to 2:[30.35]
2-4 |
Specifies ripping from the beginning of track two to the end of track 4. |
Again, don’t forget to protect square brackets and preceeding hyphens from the shell.
A few examples,
protected from the shell:
Query only with exhaustive search for a drive and full
reporting of
autosense:
cdparanoia -vsQ
Extract an entire disc, putting each track in a seperate
file:
cdparanoia -B
"1-"
Extract from track 1, time 0:30.12 to 1:10.00:
cdparanoia
"1[:30.12]-1[1:10]"
Extract one minute from track 1, starting at time
0:30.12:
cdparanoia "1[:30.12]-[1:00]"
The output file argument is optional; if it is not specified, cdparanoia will output samples to one of cdda.wav, cdda.aifc, or cdda.raw depending on whether −w, −a, −r or −R is used (−w is the implicit default). The output file argument of − specifies standard output; all data formats may be piped.
Cdparanoia sprang from and once drew heavily from the interface of Heiko Eissfeldt’s (heiko@colossus.escape.de) ’cdda2wav’ package. Cdparanoia would not have happened without it.
Joerg Schilling has also contributed SCSI expertise through his generic SCSI transport library.
Monty <monty@xiph.org>
Cdparanoia’s homepage may be found at:
http://www.xiph.org/paranoia/
![]() |
cdparanoia(1) | ![]() |