From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DvJc2-0004P4-4K for garchives@archives.gentoo.org; Wed, 20 Jul 2005 18:48:10 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6KIlADV020822; Wed, 20 Jul 2005 18:47:10 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6KIfhGo025228 for ; Wed, 20 Jul 2005 18:41:43 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.43) id 1DvJVv-0006mx-GQ for gentoo-user@lists.gentoo.org; Wed, 20 Jul 2005 18:41:51 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DvJVe-0008To-U5 for gentoo-user@gentoo.org; Wed, 20 Jul 2005 20:41:35 +0200 Received: from buffer.net ([24.73.161.102]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Jul 2005 20:41:34 +0200 Received: from wireless by buffer.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Jul 2005 20:41:34 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: James Subject: [gentoo-user] Re: DVD-cd usage Date: Wed, 20 Jul 2005 18:40:45 +0000 (UTC) Message-ID: References: <20050719113053.7AAC.NICK@rout.co.nz> <20050719120033.7AB5.NICK@rout.co.nz> <42DC5680.3000302@planet.nl> <42DD664B.40505@planet.nl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 24.73.161.102 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517) Sender: news Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id j6KIlADm020822 X-Archives-Salt: 11632489-3c13-4140-9618-96a3a58499ae X-Archives-Hash: 4e4d24ebf1ef846c6ba67fa1a178bedb Holly Bostick planet.nl> writes: > > so I tried: > > cdrecord dev=3DATAPI:0,0,0 -eject speed=3D2 -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= =20 > this): >=20 > 1) I was asking originally what the coding of the audio file actually=20 > was (meaning check it in mPlayer or some other audio player that will=20 > give you the details of the file itself)-- is it stereo, is it 44100 or= =20 > whatever cdrecord wants, etc? It might also be useful to verify that it= =20 > is in fact a .wav file and not some other kind of audio encoding that's= =20 > just *named* with a .wav extension..... OK, tried these commands on differernt audio files, one of which is called 'close.wav': cdrecord dev=3DATAPI:0,0,0 -eject speed=3D2 -pad -data -v close.wav and cdrecord dev=3DATAPI:0,0,0 -eject speed=3D2 -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,=20 16 bit, mono 22050 Hz So I changed the file to 'close.txt' and ran cdrecord dev=3DATAPI:0,0,0 -eject speed=3D2 -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)=20 1995-2004 J=C3=B6rg Schilling on-the-fly encryption (version 1.0-rc1) built-in, (C)=20 2004,2005 Maximilian Decker NOTE: this version of cdrecord is an inofficial (modified)=20 release of cdrecord and thus may have bugs that are not present in the=20 original version. Please send bug reports and support requests to=20 . For more information please see http://burbon04.gmxhome.de/linux/CDREncryption.html. The original author should not be bothered with=20 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=20 Linux-2.4 or Solaris. cdrecord: Cannot allocate memory. WARNING: Cannot do=20 mlockall(2). cdrecord: WARNING: This causes a high risk for buffer=20 underruns. cdrecord: Operation not permitted. WARNING: Cannot set=20 RR-scheduler cdrecord: Permission denied. WARNING: Cannot set priority=20 using setpriority(). cdrecord: WARNING: This causes a high risk for buffer=20 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=20 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. > 2) But now that I've seen that filename, I'm wondering, "What happens i= f=20 > you rename that file?" to either a) something shorter (maybe there are=20 > too many characters in the filename, if you don't have Joliet and/or=20 > other special options allowed that would let you use such a long=20 > filename), or b) to a filename that doesn't have a - directly before th= e=20 > .wav (I've seen it happen that applications of various types, K3b among= =20 > them, choke on filenames with "weird" characters in unusual places, or=20 > 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=20 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=20 found detailed documentation on cdrecord...... Other ideas??? James --=20 gentoo-user@gentoo.org mailing list