[Debburn-changes] r441 - in cdrkit/trunk/doc: . icedax

Eduard Bloch blade at alioth.debian.org
Thu Nov 23 20:57:24 CET 2006


Author: blade
Date: 2006-11-23 20:57:24 +0100 (Thu, 23 Nov 2006)
New Revision: 441

Added:
   cdrkit/trunk/doc/icedax/
Removed:
   cdrkit/trunk/doc/cdda2wav/
Modified:
   cdrkit/trunk/doc/icedax/FAQ
   cdrkit/trunk/doc/icedax/Frontends
   cdrkit/trunk/doc/icedax/HOWTOUSE
   cdrkit/trunk/doc/icedax/NEEDED
   cdrkit/trunk/doc/icedax/README
   cdrkit/trunk/doc/icedax/THANKS
   cdrkit/trunk/doc/icedax/cdda_links
   cdrkit/trunk/doc/icedax/tracknames.pl
   cdrkit/trunk/doc/icedax/tracknames.txt
Log:
cdda2wav docs -> icedax

Copied: cdrkit/trunk/doc/icedax (from rev 435, cdrkit/trunk/doc/cdda2wav)

Modified: cdrkit/trunk/doc/icedax/FAQ
===================================================================
--- cdrkit/trunk/doc/cdda2wav/FAQ	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/FAQ	2006-11-23 19:57:24 UTC (rev 441)
@@ -4,7 +4,7 @@
 ======
 
 
-Q: What is the copyright status of cdda2wav?
+Q: What is the copyright status of icedax?
 
 A: Cdda2wav is software copyrighted by Heiko Eissfeldt and released under the
    General Public License from the Free Software Foundation (see file GPL).
@@ -13,15 +13,15 @@
 ===========
 
 
-Q: What are the requirements to run cdda2wav?
+Q: What are the requirements to run icedax?
 
 A: All operating systems that are supported by cdrecord should also be able to
-   run cdda2wav. Currently DOS and Windows are not covered.
-   Requirements of previous versions of cdda2wav have been cut down for the
+   run icedax. Currently DOS and Windows are not covered.
+   Requirements of previous versions of icedax have been cut down for the
    sake of portability. Features like fork(), realtime scheduling, or shared
    memory are all optional now. You need a shell, which runs autoconf, a c
-   compiler (even a K&R compiler should work) and a c library to build cdda2wav
-   on a supported operating system. To run cdda2wav, a SCSI transport
+   compiler (even a K&R compiler should work) and a c library to build icedax
+   on a supported operating system. To run icedax, a SCSI transport
    implementation for the os, a cdrom or cd burner device to read from, and
    at least say 65K of memory for buffers are needed.
 
@@ -36,7 +36,7 @@
 
 Q: Why does it not compile using standard make?
 
-A: Like cdrecord, cdda2wav needs a sophisticated make program like Joerg
+A: Like cdrecord, icedax needs a sophisticated make program like Joerg
    Schilling's smake or GNU gmake. Pure posix make functionality is not enough.
 
 Setting Up (for now Linux only)
@@ -45,13 +45,13 @@
 
 Q: Should I use scsi emulation or the eide driver for my ATAPI cdrom drive?
 
-A: Scsi emulation is preferred, since it enables cdda2wav to use more commands
+A: Scsi emulation is preferred, since it enables icedax to use more commands
    and is often the only way to get special information like track titles with
    cd-text. The emulation module is called ide-scsi, the eide module is called
    ide-cd.
 
 
-Q: How can I use my parallel-port-connected cdrom with cdda2wav?
+Q: How can I use my parallel-port-connected cdrom with icedax?
 
 A: Under Linux there is a driver, that makes this device under SCSI
    emulation available. For more information see the cdrecord documentation.
@@ -65,7 +65,7 @@
    question, otherwise you need to recompile the kernel and enable generic SCSI.
    You might try to use the 'cooked_ioctl' interface as a last resort, but then
    you need to supply a cdrom device with -D (like -D/dev/cdrom). In this case
-   cdda2wav completely relies on the cdda reading methods from the kernel
+   icedax completely relies on the cdda reading methods from the kernel
    driver, so it might not work (due to unsupported). 
 
 
@@ -113,31 +113,31 @@
    beginning of the script.
 
 
-Q: How can I get the highest speed out of cdda2wav?
+Q: How can I get the highest speed out of icedax?
 
 A: See the file README. There is a section about performance and what is
    influencing it.
 
 
-Q: How can I burn audio cds with cdda2wav and cdrecord on-the-fly?
+Q: How can I burn audio cds with icedax and cdrecord on-the-fly?
 
 A: This has not been tested very well, so caveat emptor. It is possible to
-   use cdda2wav and cdrecord with pipes, _but_ there are several issues.
+   use icedax and cdrecord with pipes, _but_ there are several issues.
    1.: The cd drive may become too slow to keep cdrecords buffer happy, when
        a scratch on the audio cd is encountered, and several retries take place.
    2.: Currently there is no way to carry individual track information from
-       cdda2wav to cdrecord. Several information bits are available very late
+       icedax to cdrecord. Several information bits are available very late
        but are needed in advance from cdrecord.
    3.: Some operating systems have limitations in multiple SCSI accesses and
-       other ressources (shared memory). cdda2wav and cdrecord may block each
+       other ressources (shared memory). icedax and cdrecord may block each
        other, or might fight over limited ressources.
-   For these reasons it is not recommended to burn on-the-fly with cdda2wav.
+   For these reasons it is not recommended to burn on-the-fly with icedax.
 
 Frontends
 =========
 
 
-Q: Which frontends for cdda2wav are available?
+Q: Which frontends for icedax are available?
 
 A: See the file 'Frontends'. There are command line and graphical frontends.
 
@@ -145,27 +145,27 @@
 ======================
 
 
-Q: Does cdda2wav support titles from cd extra (aka cd plus aka enhanced cd)?
+Q: Does icedax support titles from cd extra (aka cd plus aka enhanced cd)?
 
-A: In general, yes. In order to get this information, cdda2wav needs to read
+A: In general, yes. In order to get this information, icedax needs to read
    a data sector from the second session of the cd. This requires multisession
    support and the capability to read XA sectors. The titles are printed on the
    screen and written into the inf files, then.
 
 
-Q: Does cdda2wav support titles from cd-text?
+Q: Does icedax support titles from cd-text?
 
 A: Newer versions support the most important features of cd-text like titles
    and creators. Non-supported are currently 16-bit characters, so asian
    titles etc. are currently not available.
 
 
-Q: Does cdda2wav support CDDB ids?
+Q: Does icedax support CDDB ids?
 
 A: Yes, while it does not make CDDB lookups itself, it supplies an cddb file
    with the table of contents and the cddb id. For cddb lookups see the
    perl script tracknames.pl and tracknames.txt. If the titles are known to
-   cdda2wav, it fills the titles itself in the cddb file.
+   icedax, it fills the titles itself in the cddb file.
 
 
 Q: What is the MCN?
@@ -184,7 +184,7 @@
 ==========
 
 
-Q: Does cdda2wav support on-the-fly mp3-coding?
+Q: Does icedax support on-the-fly mp3-coding?
 
 A: Yes. As of version 1.9alpha I integrated the LAME encoding engine as a new
    output format.
@@ -221,17 +221,17 @@
 ========
 
 
-Q: Does cdda2wav support the pre-emphasis bit?
+Q: Does icedax support the pre-emphasis bit?
 
 A: If the table of contents marks a track as pre-emphasized, the corresponding
    inf file will have this information, too. That enables a cd burning program
    to retain the state of the track.
 
 
-Q: Can cdda2wav undo the pre-emphasis effect in the samples?
+Q: Can icedax undo the pre-emphasis effect in the samples?
 
 A: Yes, if the -T option is given (and cd quality is selected),
-   cdda2wav filters the samples with the reverse emphasis on-the-fly. This has
+   icedax filters the samples with the reverse emphasis on-the-fly. This has
    been checked with a sine sweep from a pre-emphasized test cd.
 
 
@@ -240,14 +240,14 @@
 A: Use the -cs option.
 
 
-Q: Does cdda2wav support indices?
+Q: Does icedax support indices?
 
 A: Yes, but since there are positioning problems with a lot of drives,
    information might be inaccurate. A start index can be specified with the
    -i option. To get all indices, use the -v7 option.
 
 
-Q: Can cdda2wav avoid including the pre-gap region at the end of the track?
+Q: Can icedax avoid including the pre-gap region at the end of the track?
 
 A: Currently not. This might be added later, but is not easily done.
 
@@ -258,13 +258,13 @@
    the report.
 
 
-Q: Can cdda2wav display/save the graphics on my CD+graphics disc?
+Q: Can icedax display/save the graphics on my CD+graphics disc?
 
 A: No, this is not planned. A seperate X11 program could do that probably
    better.
 
 
-Q: Can cdda2wav read the audio portion from my CD-I/Video-CD/DVD mpeg streams?
+Q: Can icedax read the audio portion from my CD-I/Video-CD/DVD mpeg streams?
 
 A: No, these are special formats, which require much more effort.
 
@@ -278,7 +278,7 @@
    appreciated.
 
 
-Q: I want to port cdrtools (cdrecord/mkisofs/cdda2wav) to a new platform (like
+Q: I want to port cdrtools (cdrecord/mkisofs/icedax) to a new platform (like
    DJGPP,cygwin,os/2). How should I proceed?
 
 A: It would be convenient to have a unix like environment (like cygwin provides)   A shell, and a make program would be needed to first create smake (in order

Modified: cdrkit/trunk/doc/icedax/Frontends
===================================================================
--- cdrkit/trunk/doc/cdda2wav/Frontends	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/Frontends	2006-11-23 19:57:24 UTC (rev 441)
@@ -1,11 +1,11 @@
-This file lists additional free frontend software to be combined with cdda2wav:
+This file lists additional free frontend software to be combined with icedax:
 
 graphical frontends
 ===================
 
 BurnIT	(http://sunsite.auc.dk/BurnIT/)
 	by Jesper Petersen
-	a Java based frontend for cdrecord and cdda2wav/cdparanoia
+	a Java based frontend for cdrecord and icedax/cdparanoia
 
 Grip	(http://www.ling.ed.ac.uk/~oliphant/grip)
 	by Mike Oliphant

Modified: cdrkit/trunk/doc/icedax/HOWTOUSE
===================================================================
--- cdrkit/trunk/doc/cdda2wav/HOWTOUSE	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/HOWTOUSE	2006-11-23 19:57:24 UTC (rev 441)
@@ -16,7 +16,7 @@
 
 1. Copy an audio CD into wav files one per track.
 
-	cdda2wav -B
+	icedax -B
 
    will produce the sample wav files (one per track)
 	audio_01.wav
@@ -30,19 +30,19 @@
 
 2. Same as above but include MD-5 type signatures
 
-	cdda2wav -B -M<length>
+	icedax -B -M<length>
 
 
 3. Same as above but use other file name ('party_cd.wav')
 
-	cdda2wav -B -M<length> party_cd.wav
+	icedax -B -M<length> party_cd.wav
 
 
 Copy single tracks
 
 1. Copy one track (eg track 6) into a wav file.
 
-	cdda2wav -t6
+	icedax -t6
 
    will produce a wav file including track 6
 
@@ -57,14 +57,14 @@
 
 1. Copy from given start time to end of track
 
-	cdda2wav -t6 -o<delay in 1/75 seconds>
+	icedax -t6 -o<delay in 1/75 seconds>
 
    will record track 6 starting at track time <delay>/75 seconds
    from track beginning upto the end of track.
 
 2. Copy from given start time and record for a given time
 
-	cdda2wav -t6 -o<delay in 1/75 seconds> -d<time to record in seconds>
+	icedax -t6 -o<delay in 1/75 seconds> -d<time to record in seconds>
 
    will record track 6 starting at track time <delay>/75 seconds
    from track beginning for <time to record in seconds> seconds.
@@ -73,7 +73,7 @@
 
 Copy tracks into a pipe
 
-	cdda2wav -t6 -Oraw - | audio_compressor
+	icedax -t6 -Oraw - | audio_compressor
 
    will feed the audio samples (in big endian format) of track 6
    into a secondary program audio_compressor.
@@ -83,9 +83,9 @@
 
 Miscellaneous
 
-1. Use cdda2wav as a cd player
+1. Use icedax as a cd player
 
-	cdda2wav -eN -t6
+	icedax -eN -t6
 
    will copy the audio samples into a sound card (if sound card support
    is compiled in) and will not write any file.
@@ -94,7 +94,7 @@
 
 2. Get complete information on the cd
 
-	cdda2wav -v63 -Nd0.01
+	icedax -v63 -Nd0.01
 
    will try to find out a media catalog number and track related
    information (ISRCs) in addition to indices. For CD-Extra discs

Modified: cdrkit/trunk/doc/icedax/NEEDED
===================================================================
--- cdrkit/trunk/doc/cdda2wav/NEEDED	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/NEEDED	2006-11-23 19:57:24 UTC (rev 441)
@@ -1,5 +1,5 @@
 Here I list some things, which would be very helpful for the further
-development of cdrtools/cdda2wav, but I currently have no access to.
+development of cdrtools/icedax, but I currently have no access to.
 User support for the acquisition of these items is appreciated :-)
 
 Access to all 'coloured books' from Philips/Sony

Modified: cdrkit/trunk/doc/icedax/README
===================================================================
--- cdrkit/trunk/doc/cdda2wav/README	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/README	2006-11-23 19:57:24 UTC (rev 441)
@@ -1,9 +1,9 @@
 Hi dear cdrom drive users,
 
 This README describes hardware related matters as well as the installation of 
-cdda2wav, the sampling utility. 
+icedax, the sampling utility. 
 
-This cdda2wav utility comes with the Cdrkit project. Cdrkit is a spinoff from 
+This icedax utility comes with the Cdrkit project. Cdrkit is a spinoff from 
 cdrtools. However, the cdrtools developers are not involved in the 
 development of this spinoff and therefore shall not be made responsible for 
 any problem caused by it. Please do not try to get support for this program by 
@@ -24,7 +24,7 @@
     with the MAKEDEV script from /dev).
 
 For parallel port cdroms under Linux
-    With newer kernels cdda2wav uses the same parallel port access
+    With newer kernels icedax uses the same parallel port access
     as does cdrecord. Please refer additionally to the cdrecord documentation.
     There are generally two drivers to access the cdrom through the parallel
     port: the ATAPI cd emulation (called pcd), and the SCSI device emulation
@@ -63,7 +63,7 @@
    switched it on with the scsiinfo program from tsx-11.mit.edu), but
    enable this only if it is correctly working ;-)
 
-This has boosted the throughput of cdda2wav considerably.
+This has boosted the throughput of icedax considerably.
 
 
 Supported interfaces
@@ -72,7 +72,7 @@
 Non SCSI drives (Linux only):
 	ATAPI:
 	The greatest group nowadays are ATAPI (EIDE) cdrom drives.
-	Support is only limited by the drive. Kernel and cdda2wav
+	Support is only limited by the drive. Kernel and icedax
 	are ready for them (unless the drive uses a very uncommon method).
 
         Newer kernels can do an scsi emulation for ATAPI devices.
@@ -104,7 +104,7 @@
 =============
 
 There are some adjustable parameters in the beginning of the Makefile
-(which is called local.cnf.in) . They describe default settings of cdda2wav:
+(which is called local.cnf.in) . They describe default settings of icedax:
 
 INTERFACE: 	How the cdrom is accessed. Choose one method for INTERFACE.
 DEVICE:		The default cdrom device is set in DEF_DEVICE.
@@ -141,7 +141,7 @@
 All of those values can be overridden by command line parameters.
 
 
-Compiling cdda2wav
+Compiling icedax
 ==================
 
 Adjust the Makefile (named local.cnf.in) for your cdrom interface and
@@ -152,7 +152,7 @@
 and as root
 	make install
 
-This will compile cdda2wav and copy the binary to /usr/local/bin and the
+This will compile icedax and copy the binary to /usr/local/bin and the
 man page to /usr/local/man/man1 (defaults).
 
 
@@ -160,26 +160,26 @@
 ==========
 
 You can setgid the binary, if you want to allow access to a CDROM's
-scsi_generic interface for cdda2wav but not for arbitrary programs.
+scsi_generic interface for icedax but not for arbitrary programs.
 Giving away permissions to send SCSI commands directly to a device is
 not something you want to do lightly on a multi-user server system.
 The setgid privileges will only be used to access the scsi generic
 interface; for cooked_ioctl, the setgid privileges are not necessary
 and they are simply dropped.
 
-Previous versions of cdda2wav had to be setuid to root.  Such privileges
+Previous versions of icedax had to be setuid to root.  Such privileges
 are no longer necessary and will be dropped if present.
 
 Select device
 =============
 
-By default cdda2wav uses the generic SCSI interface and a device tripel for
+By default icedax uses the generic SCSI interface and a device tripel for
 SCSI bus, id, and lun.
 This setting can be overridden by specifying '-Iinterface' and
 '-D cdromdevice'.
 The following command line example uses the generic_scsi interface and the 
 SCSI device with bus 1, id 2 and lun 3:
-cdda2wav -Igeneric_scsi -D1,2,3
+icedax -Igeneric_scsi -D1,2,3
 
 The shell script 'scan_scsi.linux' will report the generic devices for
 all SCSI cdrom drives.
@@ -188,7 +188,7 @@
 need to fit together.
 Here is an example for an ATAPI cdrom using the cooked_ioctl interface and
 the cdrom device /dev/hdb:
-cdda2wav -Icooked_ioctl -D/dev/hdb
+icedax -Icooked_ioctl -D/dev/hdb
 
 
 Features
@@ -203,7 +203,7 @@
 
 Undersampling is done by summing several samples with reduced amplitude to
 prevent overflows. This damps higher freqencies as well. Compared to
-exact resampling cdda2wav does not use a very sophisticated (expensive)
+exact resampling icedax does not use a very sophisticated (expensive)
 filter algorithm. It currently uses quadratic interpolation for
 noninteger subsampling factors.
 
@@ -221,9 +221,9 @@
 parameters as the drive: 16-bit samples, stereo at 44100 Hz sample rate
 AND with the same endianess (-Cbig and -Ebig, or -Clittle and -Elittle).
 To be sure all parameters can be given explicitly on the command line.
-This avoids an analysis of cdda2wav.
+This avoids an analysis of icedax.
 
-cdda2wav -P0 -q -S<maximum speed> 
+icedax -P0 -q -S<maximum speed> 
 run as root will read with maximum speed and copy its output into the
 wav file, taking advantage of realtime scheduling as well.
 
@@ -261,7 +261,7 @@
 ================================================================
 There are three stages where the endianess matters:
 1.) on the input side the cd drive can deliver in two flavors (called F1).
-    When the flavor is unknown, cdda2wav needs to find out the endianess.
+    When the flavor is unknown, icedax needs to find out the endianess.
     A simple voting method is used. Successive samples are compared in both
     flavors and the flavor with the statistically smaller changes is taken. 
     The flavor can be defined with the -C option, avoiding the analysis. 
@@ -304,7 +304,7 @@
 
 When recording the same audio track twice, recordings can slightly differ.
 Furthermore depending on the firmware in the cdrom drive, positioning
-errors can be so severe that they cannot be easily corrected by cdda2wav.
+errors can be so severe that they cannot be easily corrected by icedax.
 This will unfortunately lead to audible errors.
 
 In this case some overlap or even underlap between successive portions
@@ -546,4 +546,4 @@
 
 and now catch your sounds,
 Heiko 		heiko at colossus.escape.de (Original author)
-Changes for the Cdrkit project by Christian Fromme <kaner at strace.org>
+Changes for the Cdrkit project by Christian Fromme <kaner at strace.org>, Eduard Bloch

Modified: cdrkit/trunk/doc/icedax/THANKS
===================================================================
--- cdrkit/trunk/doc/cdda2wav/THANKS	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/THANKS	2006-11-23 19:57:24 UTC (rev 441)
@@ -25,9 +25,9 @@
 Christopher Montgomery (aka Monty, for his work on jitter correction)
 Zygo Blaxell (a lot of code improvements)
 Thomas Niederreiter (extensions for cd-writers)
-Piercarlo Grandi (rewrote of cdda2wav's man page)
+Piercarlo Grandi (rewrote of icedax's man page)
 Stewart Addison (suggestions and a fine web page on cdda)
-Leland Olds (the cdda2wav debian maintainer)
+Leland Olds (the icedax debian maintainer)
 Francesco Chemolli (getopt_long patches)
 
 Thanks to all testers and finally Jim McLaughlin for supplying

Modified: cdrkit/trunk/doc/icedax/cdda_links
===================================================================
--- cdrkit/trunk/doc/cdda2wav/cdda_links	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/cdda_links	2006-11-23 19:57:24 UTC (rev 441)
@@ -1,4 +1,4 @@
-http://www.escape.de/cdda2wav/cdda2wav.html
+http://www.escape.de/icedax/icedax.html
 http://www.geocities.com/SiliconValley/Bay/6893/multi.htm
 http://www.mp3.com/cdrom.html
 http://www.emi.u-bordeaux.fr/~morel/

Modified: cdrkit/trunk/doc/icedax/tracknames.pl
===================================================================
--- cdrkit/trunk/doc/cdda2wav/tracknames.pl	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/tracknames.pl	2006-11-23 19:57:24 UTC (rev 441)
@@ -1,5 +1,5 @@
 #!/usr/local/bin/perl 
-# A quick perl hack to get rename files pulled in with cdda2wav.
+# A quick perl hack to get rename files pulled in with icedax.
 # by billo at billo.com
 #
 use Socket;

Modified: cdrkit/trunk/doc/icedax/tracknames.txt
===================================================================
--- cdrkit/trunk/doc/cdda2wav/tracknames.txt	2006-11-23 19:19:33 UTC (rev 435)
+++ cdrkit/trunk/doc/icedax/tracknames.txt	2006-11-23 19:57:24 UTC (rev 441)
@@ -1,10 +1,10 @@
 Date: Fri, 2 Oct 1998 16:58:15 -0400
 From: Bill O'Donnell <billo at billo.com>
 To: heiko at colossus.escape.de
-Subject: CDDB/cdda2wav quick lookup utility
+Subject: CDDB/icedax quick lookup utility
 
 
-Hello, I just started using cdda2wav to capture CD audio on Linux.
+Hello, I just started using icedax to capture CD audio on Linux.
 It's working great on my 2.0.22 kernel with NEC CD-ROM DRIVE:273 (ATAPI).
 
 Anyway, I noticed that you're dumping out cddb query info, but not
@@ -12,7 +12,7 @@
 
 If you run with a default extraction like this:
 
-   cdda2wav -B -D /dev/hda
+   icedax -B -D /dev/hda
 
 then run the program included something like this:
 




More information about the Debburn-changes mailing list