It learns to record cd's from the line of commandos

This document does not try to be an alternative to howto of recorders, but a complement for which they do not have left very clear. Despite I recommend to you that first you read howto official that you can find puncturing here . In howto it is described like forming linux so that the engraver recognizes, as well as the use of the recording programs. In spite of it, there is interesting similarity to me to put here some examples that illustrate better the use of those programs. Of course everything what I comment here you can confirm it with the pages man of the respective programs. I recommend to you that you read them to know exactly that means each parameter of which they will be used here.

Audio CD's

First that there is to do it is to extract the tracks of audio of the CD that you want to copy to archives with format wav. In order to do this you can use two different programs: cdparanoia or cdda2wav. You can use one or another one indifferently, although I show preference for second thanks to the speed.

cdparanoia

If you want to extract the whole disc in separated archives wav you must use:

cdparanoia - B - d { reading device }
Example: cdparanoia - B - d/dev/scd0

If you want to extract single track:

cdparanoia - d { reading device } { number of track }
Example: cdparanoia - d/dev/scd0 5

If you want to extract several tracks in separated archives:

cdparanoia - B - d { reading device } { inicio}-{número number track track aim }
Example: cdparanoia - B - d/dev/scd0 3-5

Also the case that can occur you want to extract several tracks in a single file wav:

cdparanoia - d { reading device } { inicio}-{número number track track aim }
Example: cdparanoia - d/dev/scd0 3-5

If you want to extract the whole disc in separated archives wav you must use:

cdda2wav - B - D { reading device } - s - x
Example: cdda2wav - B - D/dev/scd0 - s - x

If you want to extract single track:

cdda2wav - D { reading device } - s - x - t { number of track }
Example: cdda2wav - D/dev/scd0 - s - x - t 5

If you want to extract several tracks in separated archives:

cdda2wav - D { reading device } - s - x - B - t { inicio}+{número number track track aim }
Example: cdda2wav - D/dev/scd0 - s - x - B - t 3+5

Also the case that can occur you want to extract several tracks in a single file wav:

cdda2wav - D { reading device } - s - x - t { inicio}+{número number track track aim }
Example: cdda2wav - D/dev/scd0 - s - x - t 3+5

The way to indicate to cdrecord as is the recording device becomes of a way different from the used one until now. When we pass the parameter to him dev is necessary to do using it the Channel, You go, typical Lun of devices SCSI. If you read howto you will include/understand why that is thus. The typical question is... and how I that. Then, there are two ways:

First method:


From the line of commandos of the console it keys in:

cat/proc/scsi/scsi

You must obtain something asi ':

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: PIONEER Model: Dvd-ROM Dvd-104 Rev: 1.23
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: PLEXTOR Model: Cd-r Px-w1210a Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02

In my case the recorder is of the Plextor mark, soon the parameter that I will pass despues in cdrecord is 0,1,0. It is clear? I suppose yes that.


Second method:


Using same cdrecord we can know how that parameters to put. The sera opportune commando ':

cdrecord - scanbus

You must obtain something asi ':

Linux sg to driver version: 3.1.20
Using libscg version ' schily-0.5 '
scsibus0:
0,0,0 0) ' PIONEER ' ' Dvd-ROM Dvd-104 ' ' 1,23 ' Removable CD-ROM
0,1,0 1) ' PLEXTOR ' ' Cd-r Px-w1210á ' 1,07 ' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *

As you can observe here also you obtain the same short list like parameters: 0,1,0


Then now single it is to toast the CD. The sera correct order ':

cdrecord - v speed={velocidad of recording } dev={terna of the device } driveropts={opciones several } fs={tamaño of the buffer } - audio * wav

Example: cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m - audio * wav

The option burnproof is only valid if your recorder is of this type. In opposite case quítalo. The size of the buffer does not have to be smaller to the buffer of your recorder. Mb usually is current the use of 8.

Finally to emphasize that as Linux is a multiuser operating system and multitask somebody could spoil the recording of your CD. In order to avoid that you must assign a high priority to your process. This is done putting in front the commando to execute nice -- {prioridad } . Therefore our previous example would be:

nice --20 cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m - audio * wav

The single priority can be modified by the admnistrador of the system, so that you can make two things. Either you happen to be the superuser root (if really you are it) and execute the previous option, or, as usuary normal and current you always forget nice but from the console, nothing of windows in X-Windows. Now already you know all the necessary one to record an CD-audio one with your linux.

Beginning

CD's of data

Creation of the image

Data in the hard disk

The normal thing is to be accumulating the data in a directory who is the future CD. For example, in the directory /home/pepito/futurocd . When we thought that already he is advisable to record what contains that directory in a then CD we created the image with the program mkisofs . It is necessary to stand out that what contains that directory (/home/pepito/futurocd ), it will be what contains the CD in its raiz directory. In order to create the image, from the console we will key in:

mkisofs - R - J - T - or { file image } { directoriós origin of the image }

It is important that in they man of mkisofs you see that means each parameter, despite I leave an aid removed from howto here:

-:Genera R a system of files with extensions Ridge Rock. This is the main option to generate it, maintaining the permissions so and as they are.

- T:Con this option we generated the transcription archives, calls TRANS.TBL in each directory of the CD-ROM, that will contain all the transcriptions of the file names so that they are possible to be seen for example in a system TWO (of type of names of file 8+3) and with its corresponding length in the system Ridge Rock. When we used option - l the archives will have names of 32 characters and not of 8+3.

- J:Gracias to this option we will be able to create CDs with system of Joliet files (Used in Windows 9x).

Therefore, a possible example would be the following one:

mkisofs - R - J - T - or imagen.iso/home/pepito/futurocd

Data in a CD

If the data are in a CD we can make the image of two forms:

cat { device origin } > { file image }
For example: cat/dev/scd0 > imagen.iso

or of this other way:

dd if={dispositivo origin } of={archivo image }
For example: dd if=/dev/scd0 of=imagen.iso

Verification of the image

We can verify the image created with anyone of the previous methods mounting it in a directory. The correct order would be:

mount - or loop { file image } { assembly point }
For example: mount - or loop imagen.iso/home/pepito/prueba

Recording of the CD

In order to record the CD we will use cdrecord. We distinguished if the image were created from archives of the hard disk or from the CD.

Image created from the hard disk

The syntax is the one of always:

cdrecord - v speed={velocidad of recording } dev={terna of the device } driveropts={opciones several } fs={tamaño of the buffer } { file image }

Example: cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m imagen.iso

The values of the parameters speed, dev, driveropts and fs are exactly just as in the section of recording of cd's of audio.

Image created from the CD

He is exactly equal, single that we added to the parameter - isosize .

cdrecord - v speed={velocidad of recording } dev={terna of the device } driveropts={opciones several } fs={tamaño of the buffer } - isosize { file image }

Example: cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m - isosize imagen.iso

Recording in cd's regrabables

It does not change absolutely anything of the saying previously. Single I have left to add that we can erase discs with cdrecord. The sera correct order ':

cdrecord - v speed={velocidad of recording } dev={terna of the device } driveropts={opciones several } fs={tamaño of the buffer } blank={tipo of erasure }

The type of erasure can be total (all), express (fast) and some more than you can see in man corresponding.

Example: cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m blank=fast

Recording of cd's multisession

Probably this is the option more using at the time of recording in cd's regrabables. The method is simple.

First session

The image is created as it is described in the previous sections, without no variation. The CD is recorded exactly equal, single that now we passed an extra parameter to him to cdrecord. The sera syntax ': cdrecord - v speed={velocidad of recording } dev={terna of the device } driveropts={opciones several } fs={tamaño of the buffer } - multi { file image }

Example: cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m - multi imagen1.iso

Rest of sessions

It is necessary to know where the previous session at the time of making the image finishes of the new session with mkisofs. The data we obtain them with cdrecord:

cdrecord - msinfo dev={terna of the device }

Example: cdrecord - msinfo dev=0,1,0

Cdrecord will give back something to us similar to this (beginning, aim):

0,11702

This information we must include it at the time of making the image with mkisofs. In addition we must indicate that year to him this session to the previous one, so that we pruned to see both when finalizing the recording. In order to do this it is necessary to indicate to him that it reads the content of the previous session from the disc:

mkisofs - R - J - T - C { inicio}, {fin } - M { device with the CD } - or { file image } { directoriós origin of the image }

Example: mkisofs - R - J - T - C 0.11702 - Ms/dev/scd1 - or imagen2.iso/home/pepito/otrasesion

Once created the image of the session, the recording becomes just as in the first session:

cdrecord - v speed={velocidad of recording } dev={terna of the device } driveropts={opciones several } fs={tamaño of the buffer } - multi { file image }

Example: cdrecord - v speed=12 dev=0,1,0 driveropts=burnproof fs=8m - multi imagen2.iso

Inicio

CD's mixtos

Pues siento decepcionarte, pero ya sabes grabar cd's mixtos porque no cambia casi nada. La única decisión que debes tomar es el orden de las pistas. Nornmalmente se pone primero la pista de datos y después las de audio. Es decir, que a cdrecord le pasarías algo así:

cdrecord -v speed=12 dev=0,1,0 driveropts=burnproof fs=8m -data datos.iso -audio *.wav

De todos modos últimamente se está poniendo de moda el Cd-Plus, que no es mas que la situación inversa, es decir, primero audio y después datos. Se hace así porque los lectores de audio pueden leer los tracks al estar antes que los datos. Al cdrecord le pasarías algo así:

cdrecord -v speed=12 dev=0,1,0 driveropts=burnproof fs=8m -audio *.wav -data datos.iso

Inicio