From dos4gw Sun Jul 23 09:58:08 2000
Return-Path: <colin@morphin.marquardt-home.de>
Received: from stargate.home.net (really [192.168.17.1]) by inn-salzach.de
	via in.smtpd with esmtp (ident dos4gw using rfc1413)
	id <m13FxXi-000IhCC@stargate.home.net> (Debian Smail3.2.0.102)
	for <dos4gw@stargate.home.net>; Sat, 22 Jul 2000 13:34:06 +0200 (CEST) 
X-Flags: 0000
Delivered-To: GMX delivery to a.eckleder@gmx.de
Received: from pop.gmx.de
	by stargate.home.net (fetchmail-4.3.9 POP3)
	for <dos4gw/stargate.home.net> (single-drop); Sat, 22 Jul 2000 13:34:06 CEST
Received: (qmail 5585 invoked by uid 0); 22 Jul 2000 08:26:53 -0000
Received: from bflitemail6.bigfoot.com (HELO bigfoot.com) (208.156.39.208)
  by mx11.rz2.gmx.net with SMTP; 22 Jul 2000 08:26:53 -0000
Received: from post.webmailer.de ([192.67.198.65])
	by BFLITEMAIL3.bigfoot.com (LiteMail v2.43(BFLITEMAIL3)) with SMTP id 22Jul2000_BFLITEMAIL3_43094_274978;
	Sat, 22 Jul 2000 04:29:19 -0400 EST
Received: from morphin.marquardt-home.de (d31.nas21.sonic.net [209.204.136.31])
	by post.webmailer.de (8.9.3/8.8.7) with ESMTP id KAA05660
	for <A.Eckleder@bigfoot.com>; Sat, 22 Jul 2000 10:26:35 +0200 (MET DST)
Received: from colin by morphin.marquardt-home.de with local (Exim 3.12 #1 (Debian))
	id 13FsXf-0003io-00
	for <A.Eckleder@bigfoot.com>; Fri, 21 Jul 2000 23:13:43 -0700
To: Andreas Eckleder <A.Eckleder@bigfoot.com>
Subject: Re: Gnometoaster User's guide
References: <20000721192839.A3609@hex.home.net>
X-Now-Playing: Benediction's The Grand Leveller - Senile Dementia
In-Reply-To: Andreas Eckleder's message of "Fri, 21 Jul 2000 19:28:39 +0200"
Message-ID: <clemency.87snt2k80y.fsf@morphin.marquardt-home.de>
From: Colin Marquardt <colin@marquardt-home.de>
X-Home-Page: http://www.marquardt-home.de
X-GnuPG-Key: gpg --keyserver pgp.ai.mit.edu --recv-keys F53AF5C4
X-Fingerprint: F374 9BE1 87BE 8166 6D31  08BE 04CB CC2A F53A F5C4
Organization: I'd rather call it chaos.
Date: 21 Jul 2000 23:13:43 -0700
User-Agent: Gnus/5.0806 (Gnus v5.8.6) XEmacs/21.1 (Capitol Reef)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: Colin Marquardt <colin@morphin.marquardt-home.de>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by post.webmailer.de id KAA05660
X-UIDL: abaf96e48aeaf05c75df06282c9baecf
Status: RO
Content-Length: 87702
Lines: 1579

* Andreas Eckleder <A.Eckleder@bigfoot.com> writes:

> Anbei also ein ascii export des vorl=E4ufigen Gnometoaster User's Guide=
 auf
> Englisch.

Mist, wieder attachment nicht geklappt.

Hier halt direkt im Text.

------------------------------------------------------------------------

--- gnometoaster users guide.txt	Fri Jul 21 23:09:04 2000
+++ gnometoaster users guide.txt_corrected	Fri Jul 21 23:08:24 2000
@@ -13,49 +13,49 @@
 1.1 Software Requirements
=20
 Following the Unix concept, Gnometoaster heavily relies on already
-available solutions to fulfill it's task rather than reimplementing
-all the various functions required for cd recording. As a result of
+available solutions to fulfill its task rather than re-implementing
+all the various functions required for CD recording. As a result of
 that, however, you'll need to have a few additional programs and package=
s
-installed on your system in order to successfully record a CDR with
-Gnometoaster.
+installed on your system in order to successfully record a CD-R with
+Gnometoaster:
=20
-* cdrecord,cdrdao or both of them to access your cd writer. gnometoaster
-  is using cdrecord for track at once([footnote] cdrecord is being
+* cdrecord, cdrdao or both of them to access your CD writer. Gnometoaste=
r
+  is using cdrecord for track-at-once (TAO) ([footnote] cdrecord is bein=
g
 called for every track that should be written on your disc. Between
-two tracks,most cd writers insert a pregap of 2 seconds automatically
-in this mode which makes cddb lookups fail for 1:1 copies and doesn't
-sound good for live recordings.)  while it is using cdrdao in disc at
-once mode([footnote] the whole cd is written in a single step. Many
-parameters of the future cd can be controllled manually,so indices
-can be set in the middle of tracks,pregaps of any length can be inserted
-etc. Most importantly,however, Gnometoaster can produce an exact copy
-of a cd in dao mode.) .
-
-* the mpg123 software MPEG1-LayerIII([footnote] a highly efficient
-audio compression scheme that allows for near-cd quality sound streams
-at only 128kbit/sec. It was developed by the Fraunhofer institute
-which is also holding a patent for the alghorithm used to encode/decode
-mp3 files.)  decoder is being used to allow recording of mp3 files on
-cd as regular audiotracks without having to use any buffer space on
+two tracks, most CD writers insert a pregap of 2 seconds automatically
+in this mode which makes CDDB lookups fail for 1:1 copies and doesn't
+sound good for live recordings.)  while it is using cdrdao in disc-at-on=
ce=20
+mode (DAO)([footnote] The whole CD is written in a single step. Many
+parameters of the future CD can be controlled manually, so indices
+can be set in the middle of tracks, pregaps of any length can be inserte=
d
+etc. Most importantly, however, is that Gnometoaster can produce an exac=
t copy
+of a CD in DAO mode.).
+
+* The mpg123 software MPEG 1 Layer III([footnote] a highly efficient
+audio compression scheme that allows for near-CD quality sound streams
+at only 128 kbit/sec. It was developed by the Fraunhofer institute
+which is also holding a patent for the algorithm used to encode/decode
+these mp3 files.)  decoder is being used to allow recording of mp3 files=
 on
+CD as regular audio tracks without having to use any buffer space on
 your harddrive.
=20
-* the famous sound processing utility sox is used to convert wav files
-  into the raw audio data stream required by gnometoaster.
+* The famous sound processing utility sox is used to convert wav files
+  into the raw audio data stream required by Gnometoaster.
=20
 * To read out audio cds you need cdda2wav
=20
-* a utility called mkisofs is used to create ISO9660 Filesystems
+* A utility called mkisofs is used to create ISO9660 file systems.
=20
-You can get all those packages by following the links on the Gnometoaste=
r Homepage \protect\url{http://gnometoaster.rulez.org}.
+You can get all those packages by following the links on the Gnometoaste=
r Homepage \protect\url{http://Gnometoaster.rulez.org}.
 If you have installed Gnometoaster as a distribution package, your
 system should already meet the software requirements mentioned above.
-Nevertheless I suggest to test the availability of the Software componen=
ts
+Nevertheless I suggest to test the availability of the software componen=
ts
 used by Gnometoaster as your package might not have the dependencies
 ([footnote] Most
 program packages coming with a Linux Distribution are heavily relying
 on other packages. For example, The Gimp, the well-known UNIX image
 editing program, requires a library called Gtk which contains code
-to visualize dialogs, buttons etc. In a Micosoft Windows(tm) environment
+to visualize dialogs, buttons etc. In a Microsoft Windows(tm) environmen=
t
 most software packages are providing all the libraries they need themsel=
ves.
 Those libraries are usually copied into the windows system directory
 by the installation routine,a process which not only requires the
@@ -76,13 +76,13 @@
 run and can either refuse to install the program or try to install
 the missing library as well. )  set correctly.
=20
-1.2 Kerneldrivers and other problems
+1.2 Kernel drivers and other problems
=20
 Because of the history of CD Writers, all recorders on the market today
 are using a SCSI command set to communicate with the operating system
 and the recording software. This is how it came: CD Writers, because
 of their nature as write-once devices, need a continuous data stream
-when burning a CDR medium. If the transfer rate drops below a certain
+when burning a CD-R medium. If the transfer rate drops below a certain
 level only once in a recoding session, the blank you've been recording
 is usually lost. With initial medium prices at about $30, it made
 no sense to even risk this to happen. The SCSI transport standard,
@@ -90,68 +90,68 @@
 rates at low CPU time consumption and high reliability because SCSI
 devices are independent to other SCSI devices on their bus. So SCSI
 was chosen to be the bus system for the first CD Writers on the market.
-However, when the first ATAPI cd recorders hit the low-cost market,
+However, when the first ATAPI CD recorders hit the low-cost market,
 nobody wanted to change the way the drives were being accessed at
 software level because this would have required manufacturers to design
-a new drive chipset from scratch, let alone the effort to reimplement
+a new drive chip set from scratch, let alone the effort to re-implement
 all the driver infrastructure present already at the software side.
-So they just designed an additional protocol layer wrapping the scsi
+So they just designed an additional protocol layer wrapping the SCSI
 commands into ATAPI commands for the transfer over the IDE bus. So
 all a recording software wanting to support ATAPI writers has to do
-is wrapping the inital SCSI commands into the ATAPI protocol and sending
-them to the cd writer over the IDE bus. This process is usually performe=
d
-by a special DLL coming the the recording Software in Windows(tm)
+is wrapping the initial SCSI commands into the ATAPI protocol and sendin=
g
+them to the CD writer over the IDE bus. This process is usually performe=
d
+by a special DLL coming with the recording software in Windows(tm)
 environments because there's no support by the operating system. Linux,
-however, comes with a complete SCSI over ATAP emulator kernel driver.
-All you have to do to make your IDE recorder work with any linux cd
-recording software out there is to configure your linux kernel to
+however, comes with a complete SCSI over ATAPI emulator kernel driver.
+All you have to do to make your IDE recorder work with any Linux CD
+recording software out there is to configure your Linux kernel to
 make use of the idescsi device driver. How to do this is highly dependin=
g
 on your system configuration and esp. the distribution you're using.
 Linux Mandrake for example is configuring the idescsi driver automatical=
ly
-if it detects a cd writer during installation. If you're using a self-co=
mpiled
-kernel,however,you'll have to either compile idescsi support directly
-into the kernel, in which case all your ATAPI cdrom drives will appear
-to be SCSI drives from now on or compile idescsi as a module in which
-case you'll have to tell the linux kernel with a parameter handed
+if it detects a CD writer during installation. If you're using a self-co=
mpiled
+kernel however, you'll have to either compile idescsi support directly
+into the kernel, in which case all your ATAPI CD-ROM drives will appear
+to be SCSI drives from now on, or compile idescsi as a module in which
+case you'll have to tell the Linux kernel with a parameter handed
 down to the kernel by LILO at startup which drives you want to use
-idescsi with.=20
+idescsi with.
=20
-If you have a plain SCSI writer all you have to do is to load the hardwa=
re
+If you have a plain SCSI writer, all you have to do is to load the hardw=
are
 driver necessary to access your scsi card. In either case you'll also
 need the SCSI generic kernel module which makes it possible to send
 SCSI commands to individual SCSI drives on the bus directly.
=20
 1.3 Hardware requirements
=20
-Recording CDRs puts a rather high load on your system's components.
-Although most state of the art systems should easily be capable of
-recording CDR media perfectly well the hardware requirements for cd
-recording should not be underestimated as your cd recorder needs a
+Recording CD-Rs puts a rather high load on your system's components.
+Although most state-of-the-art systems should easily be capable of
+recording CD-R media perfectly well, the hardware requirements for CD
+recording should not be underestimated, as your CD recorder needs a
 continuous stream of data with interruptions only as small as can
-easily be handled by the onboard buffer provided by your recorder
-which is usually about 512kb to 2048kb which, depending on the recording
+easily be handled by the on-board buffer provided by your CD writer.
+This buffer is usually about 512kb to 2048kb in size which, depending on=
 the recording
 speed, takes less than a second to exceed.
=20
 For the graphical user interface of Gnometoaster and cdrecord's internal
-data buffer you'll need about 16MB of system RAM to record a CDR.
+data buffer you'll need about 16MB of system RAM to record a CD-R.
 In fact, this amount of memory is not too generous as your X server
 loves eating RAM as well.
=20
-Your CPU should at least be a Pentium class 90Mhz CPU, 200Mhz and more
+Your CPU should be a Pentium class 90Mhz CPU at least, 200Mhz and more
 are required to safely record .mp3 files on the fly([footnote] we
 speak of on the fly recording if we don't store any temporary data
-on your harddrive during the whole recording process. The data are
-taken as and from wherever they come and written to cd directly after
-having been converted into the needed format in realtime by a filter.) .=
=20
+on your harddrive during the whole recording process. The data is
+taken as and from wherever they come and written to CD directly after
+having been converted into the needed format in real-time by a filter.) =
.=20
=20
 If your CPU or the medium your data are coming from is not fast enough
-to provide the content you want to store on a cd in realtime, Gnometoast=
er
+to provide the content you want to store on a CD in real-time, Gnometoas=
ter
 can cache data on your harddrive. To make this possible, you need
 at least 700MB of free harddrive space.
=20
 1.4 Obtaining and installing Gnometoaster
=20
-Gnometoaster is available in a number of different offerings from The Gn=
ometoaster Homepage \protect\url{http://gnometoaster.rulez.org}:
+Gnometoaster is available in a number of different formats from The Gnom=
etoaster Homepage \protect\url{http://Gnometoaster.rulez.org}:
=20
 * the sourcecode in a .tgz archive
=20
@@ -161,29 +161,29 @@
=20
 * binary packages for quite a few distributions including Debian Linux,
   Linux Mandrake, RedHat Linux and several system architectures includin=
g
-  mk68000,intel x86,sparc,alpha. Debian Linux is probably the distributi=
on
-  with the most supported CPUs out there.
+  mk68000, intel x86, sparc, alpha. Debian Linux is probably the distrib=
ution
+  with the most supported architectures out there.
=20
 * CVS. This is for people who like to experiment. The CVS tree of Gnomet=
oaster
-  is being updated whenever there've been changes to the program code.
+  is being updated whenever there have been changes to the program code.
   Thus, it will probably contain untested or incomplete code 90% of
   the time. On the other hand, if you want to be the first to try
   out this cool new feature coming up in the next release...
=20
 1.4.1 Installing Gnometoaster from a source tgz archive
=20
-To install Gnometoaster from sourcecode,your computer needs to have
-all the development tools necessary to create Gtk+/Gnome Applications
-installed. Most importantly, this is the GNU C Compiler of a compatible
+To install Gnometoaster from source code, your computer needs to have
+all the development tools necessary to create Gtk+/Gnome Applications.
+Most importantly, this is the GNU C Compiler or a compatible
 compiler capable of producing ELF executables. You need the kernel
-header files as well as all header files of X,Gtk+ and glib. If your
+header files as well as all header files of X, Gtk+ and glib. If your
 system fulfills those requirements, you can now start the installation
 procedure as follows:
=20
 * unpack the Gnometoaster archive with tar -xzf gtoaster.tgz
=20
 * change into the directory ``gtoaster`` created by this command and
-  type ./configure. A special pre-compilation skript is now examining
+  type ./configure. A special pre-compilation script is now examining
   your system and adjusting the compilation procedure to your system's
   configuration. Especially the presence of GNOME([footnote] GNU Network
 Object model environment, an effort to create both a uniform graphical
@@ -195,7 +195,7 @@
 using it.
=20
 * once the configuration procedure is done, type make to translate
-  the sourcecode into an executable
+  the source code into an executable
=20
 * once all those steps are taken we're ready to actually install Gnometo=
aster
   on your system. To do so, simply type make install. This is the
@@ -204,19 +204,19 @@
=20
 In case you should get fed up by Gnometoaster one day, the program
 can easily be uninstalled by typing make uninstall in Gnometoaster's
-sourcecode directory.
+source code directory.
=20
-1.4.2 Installing a sourcecode distribution package
+1.4.2 Installing a source code distribution package
=20
 This depends on the distribution you're using. The easiest way to find
-out how to build a gnometoaster source package on your system is to
+out how to build a Gnometoaster source package on your system is to
 look it up in your distribution's documentation.
=20
 1.4.3 Installing Gnometoaster as a binary package
=20
-This is the most simple way of installing Gnometoaster. You just have
+This is the simplest way of installing Gnometoaster. You just have
 to use your distribution's package manager to install the Gnometoaster
-package. On a Debian box,you'd type dpkg -i gtoaster-xxxx.deb or apt-get
+package. On a Debian box, you'd type dpkg -i gtoaster-xxxx.deb or apt-ge=
t
 install gtoaster on a Debian potato system to install the most current
 version of Gnometoaster directly over the internet. RedHat, Mandrake
 and SuSE Users should type rpm -i gtoaster-xxxx.xxx.rpm. If Gnometoaster
@@ -227,7 +227,7 @@
 1.5 Configuring Gnometoaster
=20
 You should read the following instructions carefully to make sure that
-the first cd you're recording doesn't become a coaster. Besides, you're
+the first CD you're recording doesn't become a coaster. Besides, you're
 going to learn quite a few important things about the way Gnometoaster
 works.
=20
@@ -236,7 +236,7 @@
 be the root account unless you set the cdrecord executable +suid root
 (please be aware that this is opening a giant security hole on your
 system as everyone can use cdrecord to create cds from any files on
-your system).Now enter Gnometoaster's Preferences window by choosing
+your system). Now enter Gnometoaster's Preferences window by choosing
 Edit/Preferences or clicking the toolbar icon. We'll now step through
 all the panes of the preferences notebook and change the things that
 need to be changed.
@@ -245,50 +245,50 @@
=20
 The first thing we need to have a look at here is the ``Temporary Files'=
'
 entry. Please let this entry point to a directory with enough space
-available to eventually hold about 700MB of data. Gnometoaster will
-create it's temporary files there, especially any track images of
-tracks that have been precached. Please make sure the directory is
+available to hold about 700MB of data. Gnometoaster will
+create its temporary files there, especially any track images of
+tracks that have been pre-cached. Please make sure the directory is
 writable.
=20
-The ``Precache datatracks'' option determines wether Gnometoaster should
+The ``Precache datatracks'' option determines whether Gnometoaster shoul=
d
 create an image on your harddrive when copying a datatrack from one
-cd to another. You should select this option if the CDROM you want
+CD to another. You should select this option if the CD-ROM you want
 to copy contains scratches or your drive isn't fast enough to deliver
-a continuous stream of data at your cd writer's recording speed. As
-a rule of thumb the source your data is coming from should be at least
+a continuous stream of data at your CD writer's recording speed. As
+a rule of thumb, the source your data is coming from should be at least
 twice as fast as your recorder to make sure on-the-fly copying doesn't
 produce coasters.
=20
-The fillstate display options finally are somthing for you to play
+The fillstate display options finally are something for you to play
 around with. They don't have any effect on Gnometoaster's functionality
 whatsoever.
=20
 1.5.2 ISO9660 options
=20
-One important thing to change here is the ``CDfs Area'' entry,which
-should point to an empty,writable directory that is used exclusively
-by Gnometoaster. Do not make this the same directory you're using
+One important thing to change here is the ``CDfs Area'' entry, which
+should point to an empty, writable directory that is used exclusively
+by Gnometoaster (!!! how big should it be? !!!). Do not make this the sa=
me directory you're using
 in the ``Temporary Files'' entry!
=20
 You usually shouldn't need to configure any of the other options, with
 the exception of the ``Mount ISO image with'' and ``Unmount ISO image
 with'' entries. They should contain valid commands for mounting/unmounti=
ng
-the datatrack of a CDROM in you cd writer. ``recorder'' in those lines
-is a variable containing the device special file managing your cd
+the datatrack of a CD-ROM in you CD writer. ``recorder'' in those lines
+is a variable containing the device special file managing your CD
 writer (e.g. /dev/scd0).
=20
 The ``Precache on harddrive'' option is pretty much resembling the
-corresponding field in ``Common Option''. It determines wether an
+corresponding field in ``Common Option''. It determines whether an
 image file of the datatrack you're mastering should be created on
-your harddrive before writing the track to a CDR. You should only
+your harddrive before writing the track to a CD-R. You should only
 select this if you're using a really slow system that can't create
 an ISO track out of the files you decided to go into it as fast as
 your recorder can write it.
=20
 If selected, the last option makes Gnometoaster delete any contents
 of the directory pointed at by the ``CDfs Area'' entry. As Gnometoaster
-is building up the filesystem of the CDR you're creating there, this
-option presents you with a blank Filesystem editor the next time you're
+is building up the file system of the CD-R you're creating there, this
+option presents you with a blank file system editor the next time you're
 running Gnometoaster. The only reason this Option is off by default
 is that it might unintentedly delete any directory mistakenly entered
 as ``CDfs Area''.
@@ -296,33 +296,33 @@
 1.5.3 Audio Functions
=20
 For most users, the only option of interest in this section should
-be wether or not to precache audio tracks. A great majority of all
-CDROM drives are generally slower reading out audio cds than they
-are reading data cds. So please make sure your drive can deliver audio
-data fast enough to make on-the-fly writing possible. Also, audiotrack
+be whether or not to precache audio tracks. A great majority of all
+CD-ROM drives are generally slower reading out audio CDs than they
+are reading data CDs. So please make sure your drive can deliver audio
+data fast enough to make on-the-fly writing possible. Also, audio track
 error correction is generally more difficult so your throughput might
-go down considerably for older/scratched cds.
+go down considerably for older/scratched CDs.
=20
 1.5.4 File Types
=20
-This section is responsible for all file to track conversions done
-by gnometoaster. If you want to record an mp3 or wav file to an audio
-cd, this is where the necessary plugins are configured. Gnometoaster
-is currently preconfigured for 3 different audio file types:
+This section is responsible for all file-to-track conversions done
+by Gnometoaster. If you want to record an mp3 or wav file to an audio
+CD, this is where the necessary plug-ins are configured. Gnometoaster
+is currently pre-configured for 3 different audio file types:
=20
 * mp3 MPEG1-Layer3 audio files
=20
-* wav files supported by sox, the linux audiofile conversion program
+* wav files supported by sox, the Linux audiofile conversion program
=20
-* raw files resembling a plain sound stream in 44kHz,16 Bit,Stereo,littl=
e
-  Endian
+* raw files resembling a plain sound stream in 44kHz, 16 Bit, Stereo, li=
ttle
+  endian
=20
-All other files are generally treated as data tracks (MODE1,2048 Bytes
+All other files are generally treated as data tracks (MODE1, 2048 Bytes
 per sector).
=20
 1.5.5 Drive setup
=20
-This is where you configure the CDROM drives and CD recorders installed
+This is where you configure the CD-ROM drives and CD recorders installed
 on your system. Generally, you should try clicking ``Scan Bus'' which
 invokes some autodetect functionality built into Gnometoaster. In
 about 90% of all cases you won't need to do anything else. Please
@@ -331,9 +331,9 @@
 flag set, which is indicated by a small symbol in the leftmost row
 of the drive list. To keep Gnometoaster up to date about your system
 configuration, you should perform the autodetect function whenever
-you change your drive configuration (e.g. you move a cdrom drive from
+you change your drive configuration (e.g. you move a CD-ROM drive from
 one IDE channel to the other or change it from master to slave or
-you change the LUN(s) of one or more of your scsi drives). You can
+you change the LUN(s) of one or more of your SCSI drives). You can
 edit any entry of Gnometoaster's drive list by selecting it and clicking
 ``Edit''. You can manually add drives by clicking the ``Add'' button
 as well as remove drives clicking ``Remove''. Note that all changes
@@ -344,25 +344,25 @@
=20
 You can select from a list of available audio device drivers here.
 The content of this list depends on what options were available at
-compile-time. Currently, support for the Open Sound system as well
-as the Enlightenment sound daemon is available. If you're using Gnome
+compile-time. Currently, support for the Open Sound System (OSS) as well
+as the Enlightenment sound daemon (ESD) is available. If you're using Gn=
ome
 as your desktop environment of choice, you should make sure to select
-ESD support here as this will allow gnometoaster to share your soundcard
+ESD support here as this will allow Gnometoaster to share your sound car=
d
 with other applications.=20
=20
 1.5.7 Recorder Options
=20
 In most cases, you won't have to change anything here except the paths
-to cdrecord and cdrdao. As both programs should be avaible in your
+to cdrecord and cdrdao. As both programs should be available in your
 exec path anyway there's usually no need to do any changes to those
-entries either. Just leave everything at it's default to be on the
+entries either. Just leave everything at its default to be on the
 safe side. For more informations about configuring the recorder options
 see the chapter about advanced configuration in this manual.=20
=20
 And that's already it! Now your Gnometoaster installation should be
 prepared for a first recording test. Please proceed to reading the
 user documentation now on how to test your Gnometoaster setup as well
-as to learn how to use Gnometoaster to create CDRs.
+as to learn how to use Gnometoaster to create CD-Rs.
=20
 2 Gnometoaster user documentation
=20
@@ -370,28 +370,28 @@
=20
 Now that you have setup Gnometoaster and the system it is running on,
 you'll probably quite eagerly await the moment when you can record
-your first CDR with Gnometoaster. But first we should do a first test
-if everything is working. If you are using Gnometoaster with a CD/RW
-recorder,insert a CD/RW blank and click the ``Clear Disc'' button
-in the toolbar. If you don't have a toolbar (GNOME support disabled),pre=
ss
+your first CD-R with Gnometoaster. But first we should do a first test
+if everything is working. If you are using Gnometoaster with a CD-RW
+recorder,insert a CD-RW blank and click the ``Clear Disc'' button
+in the toolbar. If you don't have a toolbar (GNOME support disabled), pr=
ess
 the recorder icon in the lower left edge of the Gnometoaster window
 and press the ``Clear Disc'' button in the ``notebook page'' showing
 up. Gnometoaster should now show a dialog keeping you up-to-date about
 the cleaning process which should disappear after a few minutes. Notice
 the terminal labelled ``Client output'' to the right of the recorder
-page. It shows the output of cdrecord while blanking your CD/RW. In
+page. It shows the output of cdrecord while blanking your CD-RW. In
 case you should see an error message there please check your configurati=
on
-and consult the troubleshooting section of this Documentation in case
+and consult the troubleshooting section of this documentation in case
 you can't find anything unusual.
=20
 You should now spend a few minutes browsing through the notebook pages
 in the lower section of Gnometoaster's main window.=20
=20
-The first icon leads to a file manager displaying a virtualfilesystem.
+The first icon leads to a file manager displaying a virtual filesystem.
 Editing this filesystem (e.g. adding files, deleting files, creating
 directories) will not affect any filesystem or directory of your compute=
r
 directly. What you're editing in Gnometoaster's Filesystem editor
-is merely a prototype of hypothetical data track on the CDR you want
+is merely a prototype of hypothetical data track on the CD-R you want
 to create.=20
=20
 The second icon is bringing up Gnometoaster's track editor. As with
@@ -401,15 +401,15 @@
 With the last icon you can reach a page with various recorder settings.
 You can use this page to adjust your recording settings to your needs,
 e.g. you can set the recorder speed, the type of lead-out you want
-to write, wether or not your cd should be bootable.
+to write, whether or not your CD should be bootable.
=20
 The upper half of the Gnometoaster window is showing a list of data
-sources, notably an item called ``Unix tree'', one called ``CDROM
+sources, notably an item called ``Unix tree'', one called ``CD-ROM
 drives'' and one called ``Internal structures''. Clicking the ``Unix
 tree'' item will make it expand into your directory structure starting
 at your system's root directory. Simply click a directory to make
-it's contents appear to the right of the tree. Expanding ``CDROM drives'=
'
-will show a list resembling the CDROM units installed on your system.
+it's contents appear to the right of the tree. Expanding ``CD-ROM drives=
''
+will show a list resembling the CD-ROM units installed on your system.
 Clicking one of the drives will show a list of tracks of the medium
 in that particular drive.Finally, ``Internal structures'' will show
 just one item, the ``Gnometoaster filesystem''.=20
@@ -417,35 +417,35 @@
 Generally, you can drag any item showing up in the upper half of the
 Gnometoaster window down into both the track editor and the filesystem
 editor of the lower half. In fact that's how you will create your
-CDRs. If you press your right mouse button instead of the left one
+CD-Rs. If you press your right mouse button instead of the left one
 Gnometoaster will automatically create a copy of the data you added
-on your harddrive. This can be usefuly when working with multiple
-removable media. Additionally to the source section, files may also
+on your harddrive. This can be useful when working with multiple
+removable media. In addition to the source section, files may also
 be dragged into Gnometoaster from external sources like your favourite
-filemanager.
+GNOME file manager.
=20
 Now finally notice Gnometoaster's fillstate display at the bottom of
 the main window. It should display a percentage of space used up by
-your tracks on the CDR you're about to create as well as the space
+your tracks on the CD-R you're about to create as well as the space
 used in MB and audio playing time. MB sizes are displayed for the
 audio track representation of all tracks([footnote] While audio tracks
 have a sector size of 2354 bytes, data tracks have a lower 2048 bytes
 per sector as data tracks are using a few bytes to store some extra
 checksum improving error correction. So you can actually store less
-data to a cd in data track format than you can in audio track format.
-Gnometoaster generally displays tracksizes in audiotrack format. Due
+data to a CD in data track format than you can in audio track format.
+Gnometoaster generally displays track sizes in audio track format. Due
 to that, data track images will always result in tracks bigger than
 their respective file sizes.) .
=20
-2.1.1 Making a CDR out of files stored on your computer's harddrive
+2.1.1 Making a CD-R out of files stored on your computer's harddrive
=20
 This section describes how to record files (e.g. graphics files or
-other documents) on a CDR. To write files to a CDR simply drag them
+other documents) on a CD-R. To write files to a CD-R simply drag them
 from the ``Unix tree'' section in the upper half of the Gnometoaster
 window or from your favourite file manager into the filesystem editor
 (use the first in the list of icons to the lower left of your Gnometoast=
er
 window)([footnote] Please note that in Gnometoaster's current state
-of development, it is impossible to record symbolic links to a cdr.
+of development, it is impossible to record symbolic links to a CD-R.
 Gnometoaster dereferences all symbolic links to the files they are
 pointing at. This can imply some problems if you're adding large and
 complicated directory trees with references within sub directories
@@ -453,12 +453,12 @@
 a way that should prevent endless recursions. However, adding large
 directory structures can still take a very long time. I'm working
 hard on this problem and hope to be able to come up with a Gnometoaster
-version that can handle symbolic links in a more sane way very soon.) .Y=
ou
+version that can handle symbolic links in a more sane way very soon.) . =
You
 can delete files, create directories and rename files or directories
 by selecting the affected files and clicking the right mouse button
 to make a menu containing several options pop up. If you select the
 root item of the filesystem editor's file tree and select rename,
-you can set you data track's Volume ID.=20
+you can set your data track's Volume ID.=20
=20
 Finally, make sure your filesystem is part of Gnometoaster's destination
 tracklist. The ``Gnometoaster Filesystem'' located in the ``Internal
@@ -469,23 +469,23 @@
 toolbar or, if you're using the plain Gtk version, change to the recordi=
ng
 options panel and press record there. Notice that the recording options
 panel is also giving you some control about the recording process.
-You can specify not to fixate a cd or to write a multisession TOC
-([footnote] please
-read this documentation's section about multisession CD recording
-before you attempt to create a multisession CD.)  as well as you can
-select the writing speed and wether or not to eject the CDR after
+You can specify not to fixate a CD or to write a multisession TOC
+([footnote] Please
+read this documentation's section about multi-session CD recording
+before you attempt to create a multi-session CD.), and you can
+select the writing speed and whether or not to eject the CD-R after
 writing.=20
=20
 2.1.2 Audio CD recording
=20
-If you're planning to record an audio cd, the first thing you'll be
+If you're planning to record an audio CD, the first thing you'll be
 bound to care about is where your audio data is going to come from.
 Gnometoaster is providing two general methods to create an audio track:
 building it from a file or taking and existent audio track from another
-cd.=20
+CD.=20
=20
 In the first case, all you need to do is to select the audio file you
-want to record from Gnometoaster's filesysten tree and drag it down
+want to record from Gnometoaster's filesystem tree and drag it down
 to the Track Editor (the pane connected to the second Icon in the
 destination area). You'll see an entry being added to the tracklist
 reading the filename of the audio file it was built from and the audio
@@ -499,24 +499,24 @@
 and there's no way Gnometoaster can get the information that a stream
 is either mono or stereo from mpg123. The filetype registry will support
 one more field for determining the track format in future versions,
-though. I apologize for this inconvience but I have to remind you
+though. I apologize for this inconvenience but I have to remind you
 that Gnometoaster is work in progress and that those little problems
 make about 80% of the work necessary to develop a program like Gnometoas=
ter.) .
=20
 The second case is not really much different. Instead of selecting
 a file from the filesystem tree you select a track from one of the
-cdrom drives listed in the ``cdrom drives'' tree in gnometoaster's
+CD-ROM drives listed in the ``cdrom drives'' tree in Gnometoaster's
 source area.=20
=20
 Finally, you can rearrange the tracks in Gnometoaster's tracklist to
-make the playing order more interesting. To do so,just drag the tracks
-around in the listl. Did you notice that tracks are always inserted
+make the playing order more interesting. To do so, just drag the tracks
+around in the list. Did you notice that tracks are always inserted
 into the tracklist at where you released your mouse button ? All you
 need to do now is adjusting your recorder settings the way you want
 them and hit ``record''.
=20
 Audio CDs created with Gnometoaster are generally playable with any
-audio cd player unless they are multisession discs (might work with
+audio CD player unless they are multisession discs (might work with
 some players) or not ``fixated'' (the leadout hasn't been written).
=20
 Hint: In rare cases it could happen that Gnometoaster will not be able
@@ -529,9 +529,9 @@
 mp3 file which will make Gnometoaster know the real size of the raw
 audio stream as decoded by e.g. mpg123.
=20
-2.1.3 Creating a mixed mode CDR
+2.1.3 Creating a mixed mode CD-R
=20
-The process of creating a mixed mode CDR with gnometoaster is a mere
+The process of creating a mixed mode CD-R with Gnometoaster is a mere
 combination of the steps described in 2.1.2 and 2.1.3. Remember, the
 data track edited in Gnometoaster's filesystem editor can be found
 in the ``internal structures'' section of the source area. Make sure
@@ -541,74 +541,74 @@
=20
 2.2 Advanced functions
=20
-2.2.1 Creating a CDR with multiple data tracks
+2.2.1 Creating a CD-R with multiple data tracks
=20
-Gnometoaster supports creating more than one data tracks on a CDR.
+Gnometoaster supports creating more than one data tracks on a CD-R.
 This is as simple as just dragging the desired tracks to the tracklist
 in the order you want them,the only restriction is that two instances
 of the ``Gnometoaster filesystem'' will always contain the same filesyst=
em
 structure. This might change in future releases. Also note that tracks
 other than the first one can't be read by most operating systems.
-The only OS fully supporting more than one data tracks on a single
-cd I know of is BeOS(tm).
+The only OS fully supporting more than one data track on a single
+CD I know of is BeOS(tm).
=20
-2.2.2 Making a copy of an existing CDROM
+2.2.2 Making a copy of an existing CD-ROM
=20
-In some situations it can be important to make a backup copy of a cdrom.
+In some situations it can be important to make a backup copy of a CD-ROM.
 This can be easily accomplished with Gnometoaster by selecting the
-cdrom drive the cd you want to copy resides in. Select all the tracks
+CD-ROM drive the CD you want to copy resides in. Select all the tracks
 and drag them to Gnometoaster's track editor. Check your recorder
 options and hit record.
=20
-2.2.3 Managing multisession discs
+2.2.3 Managing multi-session discs
=20
-If configured properly, Gnometoaster lets you create Multisession discs
+If configured properly, Gnometoaster lets you create multi-session discs
 just the way your favourite Windows(tm) application does. This is
 how it works:
=20
-When the first CDROMs hit the market, there were no cd recorders and
+When the first CD-ROMs hit the market, there were no CD recorders and
 there was no way to alter the contents of a written CD in any way.
 When the first recorders came out soon voices could be heard asking
 why they couldn't just append files to their backups done with the
-cd recorder, after all the free space on a CDR is visible even with
+CD recorder, after all the free space on a CD-R is visible even with
 your bare eyes if there simply wasn't enough data to fill a whole
 CD. With CDs traditionally being a write-once medium, there was no
 easy way to just append data to it. The result was that a slightly
 modified type of TOC([footnote] Table of Contents: That's what your
-common audio cd player/CDROM drive is reading when you insert a CD.
+common audio CD player/CD-ROM drive is reading when you insert a CD.
 The TOC of a disc is storing informations about the tracks on it.)=20
 was created, containing an additional field with a pointer beyond
-the currently written area of the CD so's CD recorders would know
+the currently written area of the CD so CD recorders would know
 where to continue writing.=20
=20
 So what does all this have to do with Gnometoaster ? Well, to create
-a multisession disc, that is a disc you can append data to later on,
+a multi-session disc, that is a disc you can append data to later on,
 you have to select the ``Multisession'' Option in Gnometoaster's recordi=
ng
 panel. This will make Gnometoaster write the special kind of TOC necessa=
ry
 to make the disc appendable.=20
=20
-To append tracks to your multisession disc, simply drag them to trackedi=
t
+To append tracks to your multi-session disc, simply drag them to the tra=
ck editor
 and hit record. If you're sure you don't want to add any more tracks
 to a particular disc you can unselect the ``Multisession'' option
-when writing the last session([footnote] every write cycle of a multises=
sion
+when writing the last session([footnote] every write cycle of a multi-se=
ssion
 disc is called a session. With special programs, sessions can be ``mount=
ed''
 independently from each other.) .=20
=20
-Now how do you append files to an existing ISO track stored on a multise=
ssion
-disc ? To accomplish this, a concept called session-linking was introduc=
ed.
-With it, you can tell any multisession capable cdrom drive to link
+Now how do you append files to an existing ISO track stored on a multi-s=
ession
+disc? To accomplish this, a concept called session-linking was introduce=
d.
+With it, you can tell any multi-session capable CD-ROM drive to link
 two tracks of different sessions together. However, doing so requires
 some informations about the last session when creating the track contain=
ing
 the files you want to append to the disc. So before you can start
-adding files using Gnometoaster's filesystem editor you have to click
+adding files using Gnometoaster's filesystem editor, you have to click
 the ``Import'' icon or select ``Import session'' in Gnometoaster's
 Edit menu while making sure that the disc you want to append your
-session to is residing in your cd writer. Your writer will now show
+session to is residing in your CD writer. Your writer will now show
 some reading activities over a few seconds and once it's done you'll
 notice that all files already stored on your multisession disc will
 appear in Gnometoaster's Filesystem Editor in blue color to make clear
 that they belong to the last session. You can now edit your Filesystem
-as usual (e.g. add files,create directories etc.) with the only exceptio=
n
+as usual (e.g. add files, create directories etc.) with the only excepti=
on
 that you can't delete any files or directories of the last session
 yet. This functionality will, however, be added in a later version
 of Gnometoaster. Once you're done, hit record and enjoy. If you plan
@@ -618,21 +618,21 @@
 2.2.4 Creating bootable CDs
=20
 Gnometoaster currently supports the most common type of a bootable
-CDROM: floppy disk emulation. In this mode, your PCs BIOS is providing
-some basic CROM access functions that can read out an image file of
-a bootable floppy disc stored on your CDROM. Using this image, your
+CD-ROM: floppy disk emulation. In this mode, your PCs BIOS is providing
+some basic CD-ROM access functions that can read out an image file of
+a bootable floppy disc stored on your CD-ROM. Using this image, your
 BIOS will transparently emulate a normal floppy disc in this mode
-of operation, e.g. when making your CDR bootable using an image of
+of operation, e.g. when making your CD-R bootable using an image of
 a DOS boot disk, you'll have this image visible to your system as
 drive A: once booting is done. Note that floppy emulation as well
 as any other emulations do only work as long as the BIOS is being
-used to access your disk drive. This deserves specific notion as Linux
+used to access your disk drive. This deserves specific mentioning as Lin=
ux
 is using it's own floppy drivers as soon as the kernel has been loaded.
=20
 With this concept in mind it should be pretty easy to create a bootable
-CDR with Gnometoaster. Just drag the bootable floppy image you want
+CD-R with Gnometoaster. Just drag the bootable floppy image you want
 to use into Gnometoaster's Filesystem Editor. Now select it and press
-the right mouse button. Choos ``Make Bootimage'' in the popup menu
+the right mouse button. Choose ``Make Bootimage'' in the pop-up menu
 and you're done. Now add whatever you want to your CD and hit record.
=20
 If you take a look at the recording panel you'll find a section called
@@ -640,68 +640,68 @@
 bootable CDs. So consequently you'll find configuration options regardin=
g
 bootable CDs there. There's not much you'll ever need to do in this
 section of the recording panel. It's there merely to show the current
-state of your CDR regarding booting capabilities. In case you should
+state of your CD-R regarding booting capabilities. In case you should
 suddenly decide not to make your CD bootable after all you can unselect
 the ``Make bootable'' option there. The other way would be to just
 delete the boot image from Gnometoaster's Filesystem Editor. If the
-selected bootimage doesn't point to an existing file, the ``Make bootabl=
e''
+selected boot image doesn't point to an existing file, the ``Make bootab=
le''
 option will be grayed out.
=20
-2.2.5 Working with CD/RW media
+2.2.5 Working with CD-RW media
=20
-CD/RW media are a fine thing for backups and to share your files and
-music with friends. You can work with CD/RW media just the way you
-do with normal CDRs within Gnometoaster. There's really just one thing
-you'll need additionally to the normal functions if you're using CD/RWs:
+CD-RW media are a fine thing for backups and to share your files and
+music with friends. You can work with CD-RW media just the way you
+do with normal CD-Rs within Gnometoaster. There's really just one thing
+you'll need additionally to the normal functions if you're using CD-RWs:
 disc blanking.=20
=20
-To blank a CD/RW disc with Gnometoaster you just have to click the
+To blank (erase) a CD-RW disc with Gnometoaster you just have to click t=
he
 ``Blank Disc'' icon in your toolbar or press the ``Blank Disc'' button
 of Gnometoaster's recording panel. Note that Gnometoaster supports
 two ways of blanking discs: a full blank and TOC only.
=20
-Performing a full blank your cd recorder is burning it's way through
-the whole CD/RW medium and erasing any data on it. Depending on your
-cd writer's speed this can take as long as your disc's maximum playing
+Performing a full blank your CD recorder is burning it's way through
+the whole CD-RW medium and erasing any data on it. Depending on your
+CD writer's speed this can take as long as your disc's maximum playing
 time so you will usually want to clear the TOC only, which will fool
-the cd record into seeing a blank medium while really just the first
+the CD record into seeing a blank medium while really just the first
 few sectors are blank. Clearing a disc this way is taking less than
 two minutes at double-speed([footnote] 300kb/sec. The minimum throughput
-you can currently buy cd writers with.) .
+you can currently buy CD writers with.) .
=20
 2.2.6 Disc at once recording and what it is good for
=20
 Disc-at-once recording has been a buzz-word among audiophiles for quite
-some time now. One of the major problems early cd recorders had was
+some time now. One of the major problems of early CD recorders was
 the fact that they could only write one track at once. Between tracks,
 those devices had to reposition and recalibrate their lasers, leaving
 2 seconds between tracks unusable for recording. Indeed, those 2 seconds
-are filled with rubbish and explicitly silenced by your audio cd player.
+are filled with rubbish and explicitly silenced by your audio CD player.
 If your audio player is somewhat old, you might actually end up hearing
-that rubbish. Anyways, a 2 seconds gap between tracks is a live cd
-killer and that's why there's been an enormous interest in getting
-rid of this gap. Most modern cd writers hence support a mode of operatio=
n
-where the whole cd is being written at once. Of course, this also
+that rubbish. Anyways, a 2 seconds gap between tracks is a=20
+killer for CDs with live music and that's why there's been an enormous i=
nterest in getting
+rid of this gap. Most modern CD writers hence support a mode of operatio=
n
+where the whole CD is being written at once. Of course, this also
 sets certain requirements on the recording software used.=20
=20
 There are a few things you should know about Gnometoaster's disc-at-once
-capabilities: While Joerg Schilling's cdrecord is perfectly capable
-of writing cds in dao mode, it can't do the trick ``on-the-fly'',
+capabilities: while Joerg Schilling's cdrecord is perfectly capable
+of writing cds in DAO mode, it can't do the trick ``on-the-fly'',
 essentially requiring the user to store all audio data to be written
-on cd to his harddrive in either .wav or .raw format. As this doesn't
+on CD to his harddrive in either .wav or .raw format. As this doesn't
 fit Gnometoaster's conception very well, I chose to use cdrdao, yet
-another cd recording backend, for dao recording. So in order to record
-cds in dao mode, you'll have to have cdrdao installed on your system
+another CD recording back-end, for DAO recording. So in order to record
+CDs in DAO mode, you'll have to have cdrdao installed on your system
 ([footnote] Note
 that cdrdao only supports a subset of the drives supported by cdrecord.
 It is thus not guaranteed that your drive will be supported by Gnometoas=
ter
 in disc-at-once mode. The first thing you should make sure is that
-your cd writer is actually capable of writing in disc-at-once mode.
-If your cd writer is (scsi/atapi)-mmc3 compatible it should generally
+your CD writer is actually capable of writing in disc-at-once mode.
+If your CD writer is (SCSI/ATAPI)-MMC3 compatible it should generally
 work with cdrdao. For all other writers, please consult the list of
 drives supported by cdrdao (follow the link to the cdrdao homepage).) .
 You don't have to perform any special configuration steps within Gnometo=
aster
-to make dao recording work.=20
+to make DAO recording work.=20
=20
-To record a CDR in dao mode, simply check the ``Disc-at-once'' option
+To record a CD-R in DAO mode, simply check the ``Disc-at-once'' option
 in the recording panel and hit record.

------------------------------------------------------------------------

Gnometoaster User's Guide

Andreas Eckleder

May 14th 2000

\tableofcontents{}

1 Preparing the use of Gnometoaster

1.1 Software Requirements

Following the Unix concept, Gnometoaster heavily relies on already
available solutions to fulfill its task rather than re-implementing
all the various functions required for CD recording. As a result of
that, however, you'll need to have a few additional programs and packages
installed on your system in order to successfully record a CD-R with
Gnometoaster:

* cdrecord, cdrdao or both of them to access your CD writer. Gnometoaster
  is using cdrecord for track-at-once (TAO) ([footnote] cdrecord is being
called for every track that should be written on your disc. Between
two tracks, most CD writers insert a pregap of 2 seconds automatically
in this mode which makes CDDB lookups fail for 1:1 copies and doesn't
sound good for live recordings.)  while it is using cdrdao in disc-at-onc=
e=20
mode (DAO)([footnote] The whole CD is written in a single step. Many
parameters of the future CD can be controlled manually, so indices
can be set in the middle of tracks, pregaps of any length can be inserted
etc. Most importantly, however, is that Gnometoaster can produce an exact=
 copy
of a CD in DAO mode.).

* The mpg123 software MPEG 1 Layer III([footnote] a highly efficient
audio compression scheme that allows for near-CD quality sound streams
at only 128 kbit/sec. It was developed by the Fraunhofer institute
which is also holding a patent for the algorithm used to encode/decode
these mp3 files.)  decoder is being used to allow recording of mp3 files =
on
CD as regular audio tracks without having to use any buffer space on
your harddrive.

* The famous sound processing utility sox is used to convert wav files
  into the raw audio data stream required by Gnometoaster.

* To read out audio cds you need cdda2wav

* A utility called mkisofs is used to create ISO9660 file systems.

You can get all those packages by following the links on the Gnometoaster=
 Homepage \protect\url{http://Gnometoaster.rulez.org}.
If you have installed Gnometoaster as a distribution package, your
system should already meet the software requirements mentioned above.
Nevertheless I suggest to test the availability of the software component=
s
used by Gnometoaster as your package might not have the dependencies
([footnote] Most
program packages coming with a Linux Distribution are heavily relying
on other packages. For example, The Gimp, the well-known UNIX image
editing program, requires a library called Gtk which contains code
to visualize dialogs, buttons etc. In a Microsoft Windows(tm) environment
most software packages are providing all the libraries they need themselv=
es.
Those libraries are usually copied into the windows system directory
by the installation routine,a process which not only requires the
user to reboot his machine once the installation procedure has finished
in most cases but also increases both the lack of stability of your
system and the size of the software package you want to install. Just
imagine two different programs using the same library in different
versions. as windows can't handle different versions of the same DLL
files effectively one program ends up overwriting the library of the
other with the consequence that one of the two will usually become
very unstable or will refuse to start at all. To overcome this problem
in a Linux(tm) environment, shared libraries are usually separated
>from the programs using them and put into a different library. To
avoid a situation where a program is installed that needs a certain
library which isn't, the program's package will have a dependency
set to the library it needs somewhere in the package header. Thus,
the package manager program knows what it takes to make the program
run and can either refuse to install the program or try to install
the missing library as well. )  set correctly.

1.2 Kernel drivers and other problems

Because of the history of CD Writers, all recorders on the market today
are using a SCSI command set to communicate with the operating system
and the recording software. This is how it came: CD Writers, because
of their nature as write-once devices, need a continuous data stream
when burning a CD-R medium. If the transfer rate drops below a certain
level only once in a recoding session, the blank you've been recording
is usually lost. With initial medium prices at about $30, it made
no sense to even risk this to happen. The SCSI transport standard,
in contrast to IDE/ATAPI, has long been known to yield both high transfer
rates at low CPU time consumption and high reliability because SCSI
devices are independent to other SCSI devices on their bus. So SCSI
was chosen to be the bus system for the first CD Writers on the market.
However, when the first ATAPI CD recorders hit the low-cost market,
nobody wanted to change the way the drives were being accessed at
software level because this would have required manufacturers to design
a new drive chip set from scratch, let alone the effort to re-implement
all the driver infrastructure present already at the software side.
So they just designed an additional protocol layer wrapping the SCSI
commands into ATAPI commands for the transfer over the IDE bus. So
all a recording software wanting to support ATAPI writers has to do
is wrapping the initial SCSI commands into the ATAPI protocol and sending
them to the CD writer over the IDE bus. This process is usually performed
by a special DLL coming with the recording software in Windows(tm)
environments because there's no support by the operating system. Linux,
however, comes with a complete SCSI over ATAPI emulator kernel driver.
All you have to do to make your IDE recorder work with any Linux CD
recording software out there is to configure your Linux kernel to
make use of the idescsi device driver. How to do this is highly depending
on your system configuration and esp. the distribution you're using.
Linux Mandrake for example is configuring the idescsi driver automaticall=
y
if it detects a CD writer during installation. If you're using a self-com=
piled
kernel however, you'll have to either compile idescsi support directly
into the kernel, in which case all your ATAPI CD-ROM drives will appear
to be SCSI drives from now on, or compile idescsi as a module in which
case you'll have to tell the Linux kernel with a parameter handed
down to the kernel by LILO at startup which drives you want to use
idescsi with.

If you have a plain SCSI writer, all you have to do is to load the hardwa=
re
driver necessary to access your scsi card. In either case you'll also
need the SCSI generic kernel module which makes it possible to send
SCSI commands to individual SCSI drives on the bus directly.

1.3 Hardware requirements

Recording CD-Rs puts a rather high load on your system's components.
Although most state-of-the-art systems should easily be capable of
recording CD-R media perfectly well, the hardware requirements for CD
recording should not be underestimated, as your CD recorder needs a
continuous stream of data with interruptions only as small as can
easily be handled by the on-board buffer provided by your CD writer.
This buffer is usually about 512kb to 2048kb in size which, depending on =
the recording
speed, takes less than a second to exceed.

For the graphical user interface of Gnometoaster and cdrecord's internal
data buffer you'll need about 16MB of system RAM to record a CD-R.
In fact, this amount of memory is not too generous as your X server
loves eating RAM as well.

Your CPU should be a Pentium class 90Mhz CPU at least, 200Mhz and more
are required to safely record .mp3 files on the fly([footnote] we
speak of on the fly recording if we don't store any temporary data
on your harddrive during the whole recording process. The data is
taken as and from wherever they come and written to CD directly after
having been converted into the needed format in real-time by a filter.) .=
=20

If your CPU or the medium your data are coming from is not fast enough
to provide the content you want to store on a CD in real-time, Gnometoast=
er
can cache data on your harddrive. To make this possible, you need
at least 700MB of free harddrive space.

1.4 Obtaining and installing Gnometoaster

Gnometoaster is available in a number of different formats from The Gnome=
toaster Homepage \protect\url{http://Gnometoaster.rulez.org}:

* the sourcecode in a .tgz archive

* sourcecode packages for various distributions featuring the advantages
  of ``both worlds'', that is they're both highly configurable and
  easy to install/uninstall.

* binary packages for quite a few distributions including Debian Linux,
  Linux Mandrake, RedHat Linux and several system architectures including
  mk68000, intel x86, sparc, alpha. Debian Linux is probably the distribu=
tion
  with the most supported architectures out there.

* CVS. This is for people who like to experiment. The CVS tree of Gnometo=
aster
  is being updated whenever there have been changes to the program code.
  Thus, it will probably contain untested or incomplete code 90% of
  the time. On the other hand, if you want to be the first to try
  out this cool new feature coming up in the next release...

1.4.1 Installing Gnometoaster from a source tgz archive

To install Gnometoaster from source code, your computer needs to have
all the development tools necessary to create Gtk+/Gnome Applications.
Most importantly, this is the GNU C Compiler or a compatible
compiler capable of producing ELF executables. You need the kernel
header files as well as all header files of X, Gtk+ and glib. If your
system fulfills those requirements, you can now start the installation
procedure as follows:

* unpack the Gnometoaster archive with tar -xzf gtoaster.tgz

* change into the directory ``gtoaster`` created by this command and
  type ./configure. A special pre-compilation script is now examining
  your system and adjusting the compilation procedure to your system's
  configuration. Especially the presence of GNOME([footnote] GNU Network
Object model environment, an effort to create both a uniform graphical
user interface similar to KDE and to provide a powerful application
framework including advanced IPC functions including OLE.)  is being
detected as well as the presence of the Enlightenment Sound Daemon
and other goodies. Please note that Gnometoaster will work perfectly
well without all those things, they are merely adding some spice to
using it.

* once the configuration procedure is done, type make to translate
  the source code into an executable

* once all those steps are taken we're ready to actually install Gnometoa=
ster
  on your system. To do so, simply type make install. This is the
  only step to be performed as root. The rest of the installation
  process can be performed as a normal user.

In case you should get fed up by Gnometoaster one day, the program
can easily be uninstalled by typing make uninstall in Gnometoaster's
source code directory.

1.4.2 Installing a source code distribution package

This depends on the distribution you're using. The easiest way to find
out how to build a Gnometoaster source package on your system is to
look it up in your distribution's documentation.

1.4.3 Installing Gnometoaster as a binary package

This is the simplest way of installing Gnometoaster. You just have
to use your distribution's package manager to install the Gnometoaster
package. On a Debian box, you'd type dpkg -i gtoaster-xxxx.deb or apt-get
install gtoaster on a Debian potato system to install the most current
version of Gnometoaster directly over the internet. RedHat, Mandrake
and SuSE Users should type rpm -i gtoaster-xxxx.xxx.rpm. If Gnometoaster
came with your distribution as is the case with Linux Mandrake and
Debian, you can also use your distribution's package selection tool
to install Gnometoaster.

1.5 Configuring Gnometoaster

You should read the following instructions carefully to make sure that
the first CD you're recording doesn't become a coaster. Besides, you're
going to learn quite a few important things about the way Gnometoaster
works.

Start Gnometoaster from the account you're planning to run it in the
future by typing gtoaster on an X Terminal. In most cases this will
be the root account unless you set the cdrecord executable +suid root
(please be aware that this is opening a giant security hole on your
system as everyone can use cdrecord to create cds from any files on
your system). Now enter Gnometoaster's Preferences window by choosing
Edit/Preferences or clicking the toolbar icon. We'll now step through
all the panes of the preferences notebook and change the things that
need to be changed.

1.5.1 Common Options

The first thing we need to have a look at here is the ``Temporary Files''
entry. Please let this entry point to a directory with enough space
available to hold about 700MB of data. Gnometoaster will
create its temporary files there, especially any track images of
tracks that have been pre-cached. Please make sure the directory is
writable.

The ``Precache datatracks'' option determines whether Gnometoaster should
create an image on your harddrive when copying a datatrack from one
CD to another. You should select this option if the CD-ROM you want
to copy contains scratches or your drive isn't fast enough to deliver
a continuous stream of data at your CD writer's recording speed. As
a rule of thumb, the source your data is coming from should be at least
twice as fast as your recorder to make sure on-the-fly copying doesn't
produce coasters.

The fillstate display options finally are something for you to play
around with. They don't have any effect on Gnometoaster's functionality
whatsoever.

1.5.2 ISO9660 options

One important thing to change here is the ``CDfs Area'' entry, which
should point to an empty, writable directory that is used exclusively
by Gnometoaster (!!! how big should it be? !!!). Do not make this the sam=
e directory you're using
in the ``Temporary Files'' entry!

You usually shouldn't need to configure any of the other options, with
the exception of the ``Mount ISO image with'' and ``Unmount ISO image
with'' entries. They should contain valid commands for mounting/unmountin=
g
the datatrack of a CD-ROM in you CD writer. ``recorder'' in those lines
is a variable containing the device special file managing your CD
writer (e.g. /dev/scd0).

The ``Precache on harddrive'' option is pretty much resembling the
corresponding field in ``Common Option''. It determines whether an
image file of the datatrack you're mastering should be created on
your harddrive before writing the track to a CD-R. You should only
select this if you're using a really slow system that can't create
an ISO track out of the files you decided to go into it as fast as
your recorder can write it.

If selected, the last option makes Gnometoaster delete any contents
of the directory pointed at by the ``CDfs Area'' entry. As Gnometoaster
is building up the file system of the CD-R you're creating there, this
option presents you with a blank file system editor the next time you're
running Gnometoaster. The only reason this Option is off by default
is that it might unintentedly delete any directory mistakenly entered
as ``CDfs Area''.

1.5.3 Audio Functions

For most users, the only option of interest in this section should
be whether or not to precache audio tracks. A great majority of all
CD-ROM drives are generally slower reading out audio CDs than they
are reading data CDs. So please make sure your drive can deliver audio
data fast enough to make on-the-fly writing possible. Also, audio track
error correction is generally more difficult so your throughput might
go down considerably for older/scratched CDs.

1.5.4 File Types

This section is responsible for all file-to-track conversions done
by Gnometoaster. If you want to record an mp3 or wav file to an audio
CD, this is where the necessary plug-ins are configured. Gnometoaster
is currently pre-configured for 3 different audio file types:

* mp3 MPEG1-Layer3 audio files

* wav files supported by sox, the Linux audiofile conversion program

* raw files resembling a plain sound stream in 44kHz, 16 Bit, Stereo, lit=
tle
  endian

All other files are generally treated as data tracks (MODE1, 2048 Bytes
per sector).

1.5.5 Drive setup

This is where you configure the CD-ROM drives and CD recorders installed
on your system. Generally, you should try clicking ``Scan Bus'' which
invokes some autodetect functionality built into Gnometoaster. In
about 90% of all cases you won't need to do anything else. Please
make sure, though, that Gnometoaster really did detect all your drives
correctly. At least one drive (the recorder), should have the recorder
flag set, which is indicated by a small symbol in the leftmost row
of the drive list. To keep Gnometoaster up to date about your system
configuration, you should perform the autodetect function whenever
you change your drive configuration (e.g. you move a CD-ROM drive from
one IDE channel to the other or change it from master to slave or
you change the LUN(s) of one or more of your SCSI drives). You can
edit any entry of Gnometoaster's drive list by selecting it and clicking
``Edit''. You can manually add drives by clicking the ``Add'' button
as well as remove drives clicking ``Remove''. Note that all changes
to the drive list apply immediately, the undo function of the preferences
dialog won't work for the drive list.

1.5.6 Audio Properties

You can select from a list of available audio device drivers here.
The content of this list depends on what options were available at
compile-time. Currently, support for the Open Sound System (OSS) as well
as the Enlightenment sound daemon (ESD) is available. If you're using Gno=
me
as your desktop environment of choice, you should make sure to select
ESD support here as this will allow Gnometoaster to share your sound card
with other applications.=20

1.5.7 Recorder Options

In most cases, you won't have to change anything here except the paths
to cdrecord and cdrdao. As both programs should be available in your
exec path anyway there's usually no need to do any changes to those
entries either. Just leave everything at its default to be on the
safe side. For more informations about configuring the recorder options
see the chapter about advanced configuration in this manual.=20

And that's already it! Now your Gnometoaster installation should be
prepared for a first recording test. Please proceed to reading the
user documentation now on how to test your Gnometoaster setup as well
as to learn how to use Gnometoaster to create CD-Rs.

2 Gnometoaster user documentation

2.1 Basic functionality and Interface concept

Now that you have setup Gnometoaster and the system it is running on,
you'll probably quite eagerly await the moment when you can record
your first CD-R with Gnometoaster. But first we should do a first test
if everything is working. If you are using Gnometoaster with a CD-RW
recorder,insert a CD-RW blank and click the ``Clear Disc'' button
in the toolbar. If you don't have a toolbar (GNOME support disabled), pre=
ss
the recorder icon in the lower left edge of the Gnometoaster window
and press the ``Clear Disc'' button in the ``notebook page'' showing
up. Gnometoaster should now show a dialog keeping you up-to-date about
the cleaning process which should disappear after a few minutes. Notice
the terminal labelled ``Client output'' to the right of the recorder
page. It shows the output of cdrecord while blanking your CD-RW. In
case you should see an error message there please check your configuratio=
n
and consult the troubleshooting section of this documentation in case
you can't find anything unusual.

You should now spend a few minutes browsing through the notebook pages
in the lower section of Gnometoaster's main window.=20

The first icon leads to a file manager displaying a virtual filesystem.
Editing this filesystem (e.g. adding files, deleting files, creating
directories) will not affect any filesystem or directory of your computer
directly. What you're editing in Gnometoaster's Filesystem editor
is merely a prototype of hypothetical data track on the CD-R you want
to create.=20

The second icon is bringing up Gnometoaster's track editor. As with
the filesystem editor, this is just a virtual list of tracks. It will
become ``real'' as soon as you press Gnometoaster's record button.

With the last icon you can reach a page with various recorder settings.
You can use this page to adjust your recording settings to your needs,
e.g. you can set the recorder speed, the type of lead-out you want
to write, whether or not your CD should be bootable.

The upper half of the Gnometoaster window is showing a list of data
sources, notably an item called ``Unix tree'', one called ``CD-ROM
drives'' and one called ``Internal structures''. Clicking the ``Unix
tree'' item will make it expand into your directory structure starting
at your system's root directory. Simply click a directory to make
it's contents appear to the right of the tree. Expanding ``CD-ROM drives'=
'
will show a list resembling the CD-ROM units installed on your system.
Clicking one of the drives will show a list of tracks of the medium
in that particular drive.Finally, ``Internal structures'' will show
just one item, the ``Gnometoaster filesystem''.=20

Generally, you can drag any item showing up in the upper half of the
Gnometoaster window down into both the track editor and the filesystem
editor of the lower half. In fact that's how you will create your
CD-Rs. If you press your right mouse button instead of the left one
Gnometoaster will automatically create a copy of the data you added
on your harddrive. This can be useful when working with multiple
removable media. In addition to the source section, files may also
be dragged into Gnometoaster from external sources like your favourite
GNOME file manager.

Now finally notice Gnometoaster's fillstate display at the bottom of
the main window. It should display a percentage of space used up by
your tracks on the CD-R you're about to create as well as the space
used in MB and audio playing time. MB sizes are displayed for the
audio track representation of all tracks([footnote] While audio tracks
have a sector size of 2354 bytes, data tracks have a lower 2048 bytes
per sector as data tracks are using a few bytes to store some extra
checksum improving error correction. So you can actually store less
data to a CD in data track format than you can in audio track format.
Gnometoaster generally displays track sizes in audio track format. Due
to that, data track images will always result in tracks bigger than
their respective file sizes.) .

2.1.1 Making a CD-R out of files stored on your computer's harddrive

This section describes how to record files (e.g. graphics files or
other documents) on a CD-R. To write files to a CD-R simply drag them
>from the ``Unix tree'' section in the upper half of the Gnometoaster
window or from your favourite file manager into the filesystem editor
(use the first in the list of icons to the lower left of your Gnometoaste=
r
window)([footnote] Please note that in Gnometoaster's current state
of development, it is impossible to record symbolic links to a CD-R.
Gnometoaster dereferences all symbolic links to the files they are
pointing at. This can imply some problems if you're adding large and
complicated directory trees with references within sub directories
referencing others. Gnometoaster is dereferencing symbolic links in
a way that should prevent endless recursions. However, adding large
directory structures can still take a very long time. I'm working
hard on this problem and hope to be able to come up with a Gnometoaster
version that can handle symbolic links in a more sane way very soon.) . Y=
ou
can delete files, create directories and rename files or directories
by selecting the affected files and clicking the right mouse button
to make a menu containing several options pop up. If you select the
root item of the filesystem editor's file tree and select rename,
you can set your data track's Volume ID.=20

Finally, make sure your filesystem is part of Gnometoaster's destination
tracklist. The ``Gnometoaster Filesystem'' located in the ``Internal
structures'' folder in Gnometoaster's source area is the track-representa=
tion
of the virtual filesystem you just edited. It's getting added to the
tracklist automatically if it is empty when you start editing the
virtual filesystem. If you're done just hit the record button in Gnometoa=
ster's
toolbar or, if you're using the plain Gtk version, change to the recordin=
g
options panel and press record there. Notice that the recording options
panel is also giving you some control about the recording process.
You can specify not to fixate a CD or to write a multisession TOC
([footnote] Please
read this documentation's section about multi-session CD recording
before you attempt to create a multi-session CD.), and you can
select the writing speed and whether or not to eject the CD-R after
writing.=20

2.1.2 Audio CD recording

If you're planning to record an audio CD, the first thing you'll be
bound to care about is where your audio data is going to come from.
Gnometoaster is providing two general methods to create an audio track:
building it from a file or taking and existent audio track from another
CD.=20

In the first case, all you need to do is to select the audio file you
want to record from Gnometoaster's filesystem tree and drag it down
to the Track Editor (the pane connected to the second Icon in the
destination area). You'll see an entry being added to the tracklist
reading the filename of the audio file it was built from and the audio
track size in bytes to the right. Notice, that you can only use audio
files of a type Gnometoaster knows about. The default configuration
supports .mp3 and .wav files but it is pretty easy to add others (see
``advanced configuration'')([footnote] Due to some miscommunication
between mpg123 and Gnometoaster it is currently not possible to convert
single-channel mp3 files into audio tracks with Gnometoaster. mpg123
doesn't provide an option to force the creation of a raw stereo stream
and there's no way Gnometoaster can get the information that a stream
is either mono or stereo from mpg123. The filetype registry will support
one more field for determining the track format in future versions,
though. I apologize for this inconvenience but I have to remind you
that Gnometoaster is work in progress and that those little problems
make about 80% of the work necessary to develop a program like Gnometoast=
er.) .

The second case is not really much different. Instead of selecting
a file from the filesystem tree you select a track from one of the
CD-ROM drives listed in the ``cdrom drives'' tree in Gnometoaster's
source area.=20

Finally, you can rearrange the tracks in Gnometoaster's tracklist to
make the playing order more interesting. To do so, just drag the tracks
around in the list. Did you notice that tracks are always inserted
into the tracklist at where you released your mouse button ? All you
need to do now is adjusting your recorder settings the way you want
them and hit ``record''.

Audio CDs created with Gnometoaster are generally playable with any
audio CD player unless they are multisession discs (might work with
some players) or not ``fixated'' (the leadout hasn't been written).

Hint: In rare cases it could happen that Gnometoaster will not be able
to calculate the playing time of an mp3 or wav file correctly. This
is especially true for files containing small defects (e.g. an mp3
file transmitted over digital radio etc.). If you realize that the
calculated playing time of your mp3 as display in the tracklist differs
>from it's real playing time, drag it into the tracklist with your
right mouse button pressed. This will make Gnometoaster precache your
mp3 file which will make Gnometoaster know the real size of the raw
audio stream as decoded by e.g. mpg123.

2.1.3 Creating a mixed mode CD-R

The process of creating a mixed mode CD-R with Gnometoaster is a mere
combination of the steps described in 2.1.2 and 2.1.3. Remember, the
data track edited in Gnometoaster's filesystem editor can be found
in the ``internal structures'' section of the source area. Make sure
it always is the first track in your tracklist and you should be perfectl=
y
fine. Just add whatever audio tracks you need behind the ``Gnometoaster
filesystem'' track in the tracklist.

2.2 Advanced functions

2.2.1 Creating a CD-R with multiple data tracks

Gnometoaster supports creating more than one data tracks on a CD-R.
This is as simple as just dragging the desired tracks to the tracklist
in the order you want them,the only restriction is that two instances
of the ``Gnometoaster filesystem'' will always contain the same filesyste=
m
structure. This might change in future releases. Also note that tracks
other than the first one can't be read by most operating systems.
The only OS fully supporting more than one data track on a single
CD I know of is BeOS(tm).

2.2.2 Making a copy of an existing CD-ROM

In some situations it can be important to make a backup copy of a CD-ROM.
This can be easily accomplished with Gnometoaster by selecting the
CD-ROM drive the CD you want to copy resides in. Select all the tracks
and drag them to Gnometoaster's track editor. Check your recorder
options and hit record.

2.2.3 Managing multi-session discs

If configured properly, Gnometoaster lets you create multi-session discs
just the way your favourite Windows(tm) application does. This is
how it works:

When the first CD-ROMs hit the market, there were no CD recorders and
there was no way to alter the contents of a written CD in any way.
When the first recorders came out soon voices could be heard asking
why they couldn't just append files to their backups done with the
CD recorder, after all the free space on a CD-R is visible even with
your bare eyes if there simply wasn't enough data to fill a whole
CD. With CDs traditionally being a write-once medium, there was no
easy way to just append data to it. The result was that a slightly
modified type of TOC([footnote] Table of Contents: That's what your
common audio CD player/CD-ROM drive is reading when you insert a CD.
The TOC of a disc is storing informations about the tracks on it.)=20
was created, containing an additional field with a pointer beyond
the currently written area of the CD so CD recorders would know
where to continue writing.=20

So what does all this have to do with Gnometoaster ? Well, to create
a multi-session disc, that is a disc you can append data to later on,
you have to select the ``Multisession'' Option in Gnometoaster's recordin=
g
panel. This will make Gnometoaster write the special kind of TOC necessar=
y
to make the disc appendable.=20

To append tracks to your multi-session disc, simply drag them to the trac=
k editor
and hit record. If you're sure you don't want to add any more tracks
to a particular disc you can unselect the ``Multisession'' option
when writing the last session([footnote] every write cycle of a multi-ses=
sion
disc is called a session. With special programs, sessions can be ``mounte=
d''
independently from each other.) .=20

Now how do you append files to an existing ISO track stored on a multi-se=
ssion
disc? To accomplish this, a concept called session-linking was introduced.
With it, you can tell any multi-session capable CD-ROM drive to link
two tracks of different sessions together. However, doing so requires
some informations about the last session when creating the track containi=
ng
the files you want to append to the disc. So before you can start
adding files using Gnometoaster's filesystem editor, you have to click
the ``Import'' icon or select ``Import session'' in Gnometoaster's
Edit menu while making sure that the disc you want to append your
session to is residing in your CD writer. Your writer will now show
some reading activities over a few seconds and once it's done you'll
notice that all files already stored on your multisession disc will
appear in Gnometoaster's Filesystem Editor in blue color to make clear
that they belong to the last session. You can now edit your Filesystem
as usual (e.g. add files, create directories etc.) with the only exceptio=
n
that you can't delete any files or directories of the last session
yet. This functionality will, however, be added in a later version
of Gnometoaster. Once you're done, hit record and enjoy. If you plan
on adding any further sessions, make sure you select the ``Multisession''
option in Gnometoaster's recording panel.

2.2.4 Creating bootable CDs

Gnometoaster currently supports the most common type of a bootable
CD-ROM: floppy disk emulation. In this mode, your PCs BIOS is providing
some basic CD-ROM access functions that can read out an image file of
a bootable floppy disc stored on your CD-ROM. Using this image, your
BIOS will transparently emulate a normal floppy disc in this mode
of operation, e.g. when making your CD-R bootable using an image of
a DOS boot disk, you'll have this image visible to your system as
drive A: once booting is done. Note that floppy emulation as well
as any other emulations do only work as long as the BIOS is being
used to access your disk drive. This deserves specific mentioning as Linu=
x
is using it's own floppy drivers as soon as the kernel has been loaded.

With this concept in mind it should be pretty easy to create a bootable
CD-R with Gnometoaster. Just drag the bootable floppy image you want
to use into Gnometoaster's Filesystem Editor. Now select it and press
the right mouse button. Choose ``Make Bootimage'' in the pop-up menu
and you're done. Now add whatever you want to your CD and hit record.

If you take a look at the recording panel you'll find a section called
``El Torito'' there. El Torito is the name of the standard defining
bootable CDs. So consequently you'll find configuration options regarding
bootable CDs there. There's not much you'll ever need to do in this
section of the recording panel. It's there merely to show the current
state of your CD-R regarding booting capabilities. In case you should
suddenly decide not to make your CD bootable after all you can unselect
the ``Make bootable'' option there. The other way would be to just
delete the boot image from Gnometoaster's Filesystem Editor. If the
selected boot image doesn't point to an existing file, the ``Make bootabl=
e''
option will be grayed out.

2.2.5 Working with CD-RW media

CD-RW media are a fine thing for backups and to share your files and
music with friends. You can work with CD-RW media just the way you
do with normal CD-Rs within Gnometoaster. There's really just one thing
you'll need additionally to the normal functions if you're using CD-RWs:
disc blanking.=20

To blank (erase) a CD-RW disc with Gnometoaster you just have to click th=
e
``Blank Disc'' icon in your toolbar or press the ``Blank Disc'' button
of Gnometoaster's recording panel. Note that Gnometoaster supports
two ways of blanking discs: a full blank and TOC only.

Performing a full blank your CD recorder is burning it's way through
the whole CD-RW medium and erasing any data on it. Depending on your
CD writer's speed this can take as long as your disc's maximum playing
time so you will usually want to clear the TOC only, which will fool
the CD record into seeing a blank medium while really just the first
few sectors are blank. Clearing a disc this way is taking less than
two minutes at double-speed([footnote] 300kb/sec. The minimum throughput
you can currently buy CD writers with.) .

2.2.6 Disc at once recording and what it is good for

Disc-at-once recording has been a buzz-word among audiophiles for quite
some time now. One of the major problems of early CD recorders was
the fact that they could only write one track at once. Between tracks,
those devices had to reposition and recalibrate their lasers, leaving
2 seconds between tracks unusable for recording. Indeed, those 2 seconds
are filled with rubbish and explicitly silenced by your audio CD player.
If your audio player is somewhat old, you might actually end up hearing
that rubbish. Anyways, a 2 seconds gap between tracks is a=20
killer for CDs with live music and that's why there's been an enormous in=
terest in getting
rid of this gap. Most modern CD writers hence support a mode of operation
where the whole CD is being written at once. Of course, this also
sets certain requirements on the recording software used.=20

There are a few things you should know about Gnometoaster's disc-at-once
capabilities: while Joerg Schilling's cdrecord is perfectly capable
of writing cds in DAO mode, it can't do the trick ``on-the-fly'',
essentially requiring the user to store all audio data to be written
on CD to his harddrive in either .wav or .raw format. As this doesn't
fit Gnometoaster's conception very well, I chose to use cdrdao, yet
another CD recording back-end, for DAO recording. So in order to record
CDs in DAO mode, you'll have to have cdrdao installed on your system
([footnote] Note
that cdrdao only supports a subset of the drives supported by cdrecord.
It is thus not guaranteed that your drive will be supported by Gnometoast=
er
in disc-at-once mode. The first thing you should make sure is that
your CD writer is actually capable of writing in disc-at-once mode.
If your CD writer is (SCSI/ATAPI)-MMC3 compatible it should generally
work with cdrdao. For all other writers, please consult the list of
drives supported by cdrdao (follow the link to the cdrdao homepage).) .
You don't have to perform any special configuration steps within Gnometoa=
ster
to make DAO recording work.=20

To record a CD-R in DAO mode, simply check the ``Disc-at-once'' option
in the recording panel and hit record.

------------------------------------------------------------------------


