From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.util.phx.redhat.com (8.13.1/8.13.1) with ESMTP id k3H6BdxS005549 for ; Mon, 17 Apr 2006 02:11:39 -0400 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.11.6) with ESMTP id k3H6BdP3023370 for ; Mon, 17 Apr 2006 02:11:39 -0400 Received: from vscan02.westnet.com.au (vscan02.westnet.com.au [203.10.1.132]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k3H6BZvc006543 for ; Mon, 17 Apr 2006 02:11:36 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 9325911C53E for ; Mon, 17 Apr 2006 14:12:48 +0800 (WST) Received: from vscan02.westnet.com.au ([127.0.0.1]) by localhost (vscan02.westnet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20712-14 for ; Mon, 17 Apr 2006 14:12:48 +0800 (WST) Received: from data.home (dsl-58-6-126-19.qld.westnet.com.au [58.6.126.19]) by vscan02.westnet.com.au (Postfix) with ESMTP id 0EBED11D3A8 for ; Mon, 17 Apr 2006 14:12:47 +0800 (WST) Received: from geoff by data.home with local-esmtp (Exim 3.12 #1 (Debian)) id 1FVMxP-00014a-00; Mon, 17 Apr 2006 16:11:31 +1000 Date: Mon, 17 Apr 2006 16:11:30 +1000 (EST) From: Geoff Shang To: Linux for blind general discussion In-Reply-To: <20060417053107.GA25940@d172-104.uoregon.edu> Message-ID: References: <20060417053107.GA25940@d172-104.uoregon.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-RedHat-Spam-Score: 0 X-loop: blinux-list@redhat.com Subject: Re: Recording NLS-format cassettes X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.5 Precedence: junk Reply-To: Linux for blind general discussion List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2006 06:11:40 -0000 Hi, sox is your friend. It can be used to do pretty much all of this. When I've done this, I've recorded the audio in at 44.1kHz 16-bit stereo, then resampled down to 22.05kHz to halve the speed. If your device has some aliasing when playing 22.05kHz material, you could always use sox to resample back up to 44.1kHz, but use the resample effect or something else more complex, not the simple rate conversion as it will leave these aliasing effects in place. But I'm getting ahead of myself. First, the side-splitting. there's a few ways you can do this: 1. Use the avg or pick effects in sox. The version of sox you have will determine which of these effects actually works for you. I've had problems with both in various versions of sox, so have an experiment, but one of them should work. 2. Alternatively, if you use ALSA, I know that arecord used at least to have a feature where you could record the left in one channel and the right in the other. hmmmm ok the help doesn't mention it, but it's the -I option. Though it appears to only record in raw data, not as a wav file. Still, sox could fix that if you wanted. Having done that, you can use the reverse effect on the backwards files: sox side3.wav side3forward.wav reverse sox side4.wav side4forward.wav reverse For trimming, I usually use soundgrab to edit manually, but you may be able to get Sox's trim effect to work for you. To halve the speed, you use one of the resampling methods. In my experience, the quick and dirty rate effect is good enough for halving the rate from 44.1kHz to 22.05kHz, but you should test it for yourself: sox -r 22050 side1.wav side1slower.wav rate or\ sox -r 22050 side2.wav side2slower.wav resample There's about 4 different resample effects, check out the sox manpage for the lowdown on all of them. I usually also normalise so that I can set my levels at a safe level and can have the files as loud as they can be without distorting. Best to do this as your last step so that other effects don't cause the audio to distort. Example: sox side1slower.wav -e stat -v sox -v side1slower.wav side1louder.wav 1.0 is as loud as it can go, so if it's at 1.0 already, there's no point and it may have in fact distorted somewhere. Got no thoughts about detecting tones etc, I'd be interested to know if anyone else has any. For actually slicing up files, I've not used it, but qwavcut from the Quelcomm tools may help if you can get something to detect these tones. They're useful programmes to have anyway, I use qwavinfo and qwavjoin regularly. qwavsilence may also help you: http://www.etse.urv.es/~dmanye/quelcom/quelcom.html Hope this all helps. Geoff. -- Geoff Shang Phone: +61-418-96-5590 MSN: geoff@acbradio.org Make sure your E-mail can be read by everyone! http://www.betips.net/etc/evilmail.html Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html