Re: Burning Audio Cd's.

Re: Burning Audio Cd's.

[Thomas Ward]

Hi. I've tried using the -pad option with the same results.
I also know that my burner burns data cd's just fine. The only problem 
begins when i try burning an audio track.
It is an IDE drive using scsi emulation on /dev/sg0.
I checked with the cdrecord mailing list, and they seam to feel it might 
be a firmware issue, or a problem of my drive accepting track at once, and 
that I should ttry disk at once.
However, I am having a hard time finding out how to do disk at once. I've 
been looking over cdrdao, and coming up with a toc file seams pretty 
dificult. Is anyone on list  versed in writing toc files?
I ran cdrdao scanbus and it shows my cdrw on 0,0,0 /dev/sg0 right where it 
should be. However, I can't figure out how to tell the dumb program where 
to find it because when I try commands such as:
cdrdao --device 0,0,0
it screams that --device is not an option.Yet it looked that way in the 
man pages. Any help with cdrecord or drdao is vary welcome.

 

Re: Burning Audio Cd's.

[Janina Sajka]

Disc at once and audio are, I believe, mutually exclusive. I think you
want -tao for track at once, but I don't recall whether that's actually
a switch, or just part of the -audio command. You are putting a dash in
there, right?

Question: Are you writing to a disk that has data files? If so, you need
to use multi mode, and I don't know much about multi mode other than it
exists for that purpose.

Try a never before used blank.

Try another brand of blank media. cdrecord should recobnize your media
by manufacturer. Yours didn't.

OK, no guarantees. Just some thoughts.

Thomas Ward writes:
> From: Thomas Ward <slingshooter@valkyrie.net>
> 
> 
> Hi. I've tried using the -pad option with the same results.
> I also know that my burner burns data cd's just fine. The only problem 
> begins when i try burning an audio track.
> It is an IDE drive using scsi emulation on /dev/sg0.
> I checked with the cdrecord mailing list, and they seam to feel it might 
> be a firmware issue, or a problem of my drive accepting track at once, and 
> that I should ttry disk at once.
> However, I am having a hard time finding out how to do disk at once. I've 
> been looking over cdrdao, and coming up with a toc file seams pretty 
> dificult. Is anyone on list  versed in writing toc files?
> I ran cdrdao scanbus and it shows my cdrw on 0,0,0 /dev/sg0 right where it 
> should be. However, I can't figure out how to tell the dumb program where 
> to find it because when I try commands such as:
> cdrdao --device 0,0,0
> it screams that --device is not an option.Yet it looked that way in the 
> man pages. Any help with cdrecord or drdao is vary welcome.
> 
>  
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Re: Burning Audio Cd's.

[Igor Gueths]

There is a -tao option and a -dao option.

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.

On Sat, 1 Feb 2003, Janina Sajka wrote:

> Disc at once and audio are, I believe, mutually exclusive. I think you
> want -tao for track at once, but I don't recall whether that's actually
> a switch, or just part of the -audio command. You are putting a dash in
> there, right?
>
> Question: Are you writing to a disk that has data files? If so, you need
> to use multi mode, and I don't know much about multi mode other than it
> exists for that purpose.
>
> Try a never before used blank.
>
> Try another brand of blank media. cdrecord should recobnize your media
> by manufacturer. Yours didn't.
>
> OK, no guarantees. Just some thoughts.
>
> Thomas Ward writes:
> > From: Thomas Ward <slingshooter@valkyrie.net>
> >
> >
> > Hi. I've tried using the -pad option with the same results.
> > I also know that my burner burns data cd's just fine. The only problem
> > begins when i try burning an audio track.
> > It is an IDE drive using scsi emulation on /dev/sg0.
> > I checked with the cdrecord mailing list, and they seam to feel it might
> > be a firmware issue, or a problem of my drive accepting track at once, and
> > that I should ttry disk at once.
> > However, I am having a hard time finding out how to do disk at once. I've
> > been looking over cdrdao, and coming up with a toc file seams pretty
> > dificult. Is anyone on list  versed in writing toc files?
> > I ran cdrdao scanbus and it shows my cdrw on 0,0,0 /dev/sg0 right where it
> > should be. However, I can't figure out how to tell the dumb program where
> > to find it because when I try commands such as:
> > cdrdao --device 0,0,0
> > it screams that --device is not an option.Yet it looked that way in the
> > man pages. Any help with cdrecord or drdao is vary welcome.
> >
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
>
> 				Janina Sajka, Director
> 				Technology Research and Development
> 				Governmental Relations Group
> 				American Foundation for the Blind (AFB)
>
> Email: janina@afb.net		Phone: (202) 408-8175
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: new red hat 8.0 not speaking

[Thomas Ward]

Hi, it has been a while since I have used Lilo, because I use the 
Red Hat recommended boot loader grub now days. However, if memory serves 
me 
correctly you would add it to the append line like this:
Try it with the quotes ffirst, and if doesn't work remove them, because I 
can  not remember if lilo needs them or not.

append="speakup_synth=dectlk"

PS

Please, change your emailer settings to send text only messages. Windows 
email programs such as Outlook adds allot of trash to the messages which 
cause text based emailers for Linux such as pine allot of grief.
To change your settings in Outlook, if you are using it, go to tools, 
options, and the send tab. Set your settings from html to text.

Hth. 

Re: dectalk express recieving errors

[Thomas Ward]

Hi, that's a pretty common problem. Red Hat decided to change some things, 
and it causes speakup to get those errors. However, here is how I cut the 
problem to a minimum.
I open /etc/rc.d/rc.local and add the following lines to it:

echo 100 >/proc/speakup/dec_express/delay_time
echo 15 >/proc/speakup/dec_express/jiffy_delta

That usually clears up the problem. You also can add custum speech rate, 
pitch, punc_level, etc to that file so that you get the same speech 
settings on startup.

Hth.

Re: Burning audio cd's.

[igueths]

Well I believe it said somewhere in that msg that the drive was being Atapi-
emulated. This would be true for cdrw disks, however it seems that based on 
Atip info, it is a cdr. I would try using the -pad option since the -audio 
option was already in use. This may not help at all, but possibly try pre-
pending a '-' to dev. I on't know if there is any difference whether the - is 
there or not, but I would try that anyway. 
> Hi Thomas,
> 
> Two suggestions, neither of which are sure fire. How about adding
> the "-pad" option to the cdrecord command along with "-audio"?
> Does that help?
> 
> The other suggestion is how about blanking the disk before
> writing on it. I have found this to be essential when rewriting
> data to a cd-rw. I have used the "blank=fast" option to permit
> overwriting existing data. Maybe this will help for audio tracks
> as well.
> 
> Chuck
> 
> -- 
> The Moon is Waning Crescent (4% of Full)
> So visit me sometime at http://www.mhonline.net/~chuckh
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Burning audio cd's.

[Thomas Ward]

Hello, everyone. I am having the worst time trying to get cdrecord to burn 
my audio cd's. I've never burned an audio cd under Linux before, but have 
burned data cd's before.
I've been reading from the cd-writing-howto, and I've used cdparanoia to 
extract to tracks from another cd, and was trying to burn them on a new 
disk to get the hangg of it. 
Here is a typescript of my commands and the errors I am getting. Can 
anyone help?

Script started on Thu Jan 30 03:12:43 2003
cdrecord -v speed=2 dev=0,0,0 -audio track1.wav track2.wav
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'HL-DT-ST'
Identifikation : 'CD-RW GCE-8240B '
Revision       : '1.06'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Drive buf size : 6037504 = 5896 KB
FIFO size      : 4194304 = 4096 KB
Track 01: audio  40 MB (04:02.36) no preemp
Track 02: audio  40 MB (04:00.29) no preemp
Total size:      81 MB (08:04.65) = 36349 sectors
Lout start:      81 MB (08:06/49) = 36349 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 4
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, low Beta category (A-) (2)
  ATIP start of lead in:  -12294 (97:18/06)
  ATIP start of lead out: 359849 (79:59/74)
Disk type:    unknown
Manuf. index: -1
Manufacturer: unknown (not in table)
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 323500
Starting to write CD/DVD at speed 8 in write mode for single session.
Last chance to quit, starting real write in 9 seconds.\b\b\b\b\b\b\b\b\b\b8 seconds.\b\b\b\b\b\b\b\b\b\b7 seconds.\b\b\b\b\b\b\b\b\b\b6 seconds.\b\b\b\b\b\b\b\b\b\b5 seconds.\b\b\b\b\b\b\b\b\b\b4 seconds.\b\b\b\b\b\b\b\b\b\b3 seconds.\b\b\b\b\b\b\b\b\b\b2 seconds.\b\b\b\b\b\b\b\b\b\b1 seconds.\b\b\b\b\b\b\b\b\b\b0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0

Track 01:   0 of  40 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 00 00 00 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 64 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.002s timeout 40s

write track data: error after 0 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
Writing  time:    5.027s
Fixating...
cdrecord: Input/output error. close track/session: scsi sendcmd: no error
CDB:  5B 00 02 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 04 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x2C Qual 0x04 (current program area is empty) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.001s timeout 480s
cmd finished after 0.001s timeout 480s
Fixating time:    0.004s
cdrecord: fifo had 64 puts and 1 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.
Script done on Thu Jan 30 03:14:03 2003

Re: Burning audio cd's.

[Chuck Hallenbeck]

Hi Thomas,

Two suggestions, neither of which are sure fire. How about adding
the "-pad" option to the cdrecord command along with "-audio"?
Does that help?

The other suggestion is how about blanking the disk before
writing on it. I have found this to be essential when rewriting
data to a cd-rw. I have used the "blank=fast" option to permit
overwriting existing data. Maybe this will help for audio tracks
as well.

Chuck

-- 
The Moon is Waning Crescent (4% of Full)
So visit me sometime at http://www.mhonline.net/~chuckh

Re: Burning audio cd's.

[Frank Carmickle]

On Thu, 30 Jan 2003, Chuck Hallenbeck wrote:
> Two suggestions, neither of which are sure fire. How about adding
> the "-pad" option to the cdrecord command along with "-audio"?

Yes these are necessary if you want to be able to listen to the disk.  But
I think there are bigger problems here.  Is this an ide or a scsi drive?
If it is a scsi drive what kind of controller is it hanging off of?  If it
is an ide drive what chipset is it and do you have support for that
chipset in your kernel?  I'm hoping that the drive is just bitching about
sector size so do try the -pad option before anything else.

--FC