From owner-freebsd-multimedia Mon Jul 7 07:34:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15714 for multimedia-outgoing; Mon, 7 Jul 1997 07:34:54 -0700 (PDT) Received: from fledge.watson.org (root@FLEDGE.PC.CC.CMU.EDU [128.2.36.53]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15708 for ; Mon, 7 Jul 1997 07:34:50 -0700 (PDT) Received: from localhost (robert@localhost) by fledge.watson.org (8.8.5/8.6.10) with SMTP id KAA06071; Mon, 7 Jul 1997 10:34:31 -0400 (EDT) Date: Mon, 7 Jul 1997 10:34:31 -0400 (EDT) From: Robert Watson To: "Daniel M. Eischen" cc: freebsd-multimedia@freebsd.org Subject: Re: Burning Audio CD scripts In-Reply-To: <199706281313.IAA05533@iworks.InterWorks.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 28 Jun 1997, Daniel M. Eischen wrote: > > Hi, > > I've found your burn_audio/convert2cdr scripts by searching the > mailing list archives. Thanks! > > One question. Did you use cdd to read audio files? I noticed > your burn_audio scripts wanted .cdr files, while cdd produces > .cda files. Is the raw format produced by cdd, the same thing > as the format you expect with the .cdr files? So I'd be able > to read an audio track with: > > cdd -r -noed -t 1 /usr/local/cd > > And rename the resulting /usr/local/cd/track-01.cda to track-01.cdr > to make it compatible with your burn_audio scripts? I have not sued cdd to generate .cda files -- most of the audio files I've burned have been generated on a Linux machine using cdd, however. Generally I use my CDR to burn data disks for myself, but occasionally I make audio CD's for others, hence having written the scripts. I believe cdd supports capture to .wav files, which my conversion scripts (should also have been attached to the message) will convert to cdr files using sox. If in doubt, generate a track both ways, and see if the files are the same or not. At the time I wrote the scripts, a FreeBSD port of cdd was not available, so I didn't really experiment with it much (other than to discover that my machine generates little-endian data files by default, which cds are not :). Let me know when you find out, and I'll post modified scripts/instructions to use the information. thanks, Robert Watson