Holly Bostick <motub <at> planet.nl> writes:

> > so I tried:
> > cdrecord dev=ATAPI:0,0,0 -eject speed=2 -pad -data -v *.wav

> > cdrecord: Inappropriate audio coding in
> > '18133194218-14129220407-05-18-2005-11-42-.wav'.

> OK, two things occuring to me (though I can't say I know anything about 
> this):
> 
> 1) I was asking originally what the coding of the audio file actually 
> was (meaning check it in mPlayer or some other audio player that will 
> give you the details of the file itself)-- is it stereo, is it 44100 or 
> whatever cdrecord wants, etc? It might also be useful to verify that it 
> is in fact a .wav file and not some other kind of audio encoding that's 
> just *named* with a .wav extension.....

OK, tried these commands on differernt audio files, one of which
is called 'close.wav':
cdrecord dev=ATAPI:0,0,0 -eject speed=2 -pad -data -v close.wav
and
cdrecord dev=ATAPI:0,0,0 -eject speed=2 -pad -data  close.wav

Both give the exact same error messages, as do using these commands
with lots of different files.

also, file close.wav says:
file close.wav
close.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 
16 bit, mono
22050 Hz

So I changed the file to 'close.txt' and ran
cdrecord dev=ATAPI:0,0,0 -eject speed=2 -pad -data  close.txt

Interesting results:
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different
 drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 
1995-2004 Jörg Schilling
on-the-fly encryption (version 1.0-rc1) built-in, (C) 
2004,2005 Maximilian Decker

NOTE: this version of cdrecord is an inofficial (modified) 
release of cdrecord
      and thus may have bugs that are not present in the 
original version.
      Please send bug reports and support requests to 
<burbon04 at gmx.de>.
      For more information please see
http://burbon04.gmxhome.de/linux/CDREncryption.html.
      The original author should not be bothered with 
problems of this version.

cdrecord: Warning: Running on Linux-2.6.12-gentoo-r4
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try 
Linux-2.4 or Solaris.
cdrecord: Cannot allocate memory. WARNING: Cannot do 
mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer 
underruns.
cdrecord: Operation not permitted. WARNING: Cannot set 
RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority 
using setpriority().
cdrecord: WARNING: This causes a high risk for buffer 
underruns.
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems 
to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
Using libscg version 'schily-0.8'.
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'TOSHIBA '
Identifikation : 'DVD-ROM SD-R2412'
Revision       : '1015'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes:
cdrecord: Drive does not support TAO recording.
cdrecord: Illegal write mode for this drive.

<maybe these last 2 lines indicated my trouble?>


> 2) But now that I've seen that filename, I'm wondering, "What happens if 
> you rename that file?" to either a) something shorter (maybe there are 
> too many characters in the filename, if you don't have Joliet and/or 
> other special options allowed that would let you use such a long 
> filename), or b) to a filename that doesn't have a - directly before the 
> .wav (I've seen it happen that applications of various types, K3b among 
> them, choke on filenames with "weird" characters in unusual places, or 
> c) both a) and b) .


Maybe you can tell me to download a specific file that you know
should write to the cd-rw and I'll try a (short) file that should 
write. The exact command line syntax to see of this drive will
work with the linux drivers would be a good idea, as I have not 
found detailed  documentation on cdrecord......

Other ideas???

James

-- 
gentoo-user@gentoo.org mailing list

Reply via email to