From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.ufw2.com([216.163.19.154]) (1636 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Mon, 21 Aug 2000 21:00:20 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from [216.163.21.20] by gate.ufw2.com for speakup@braille.uwo.ca id TAA28852; Mon Aug 21 19:59:29 2000 Received: from hardb ([216.163.21.59]) by mail.ufw2.com (Build 101 8.9.3/NT-8.9.3) with SMTP id TAA00553 for ; Mon, 21 Aug 2000 19:59:56 -0500 Message-Id: <3.0.6.32.20000821200624.00799100@mail.ufw2.com> X-Sender: bharding@mail.ufw2.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 21 Aug 2000 20:06:24 -0500 Subject: Re: piping arecord into lame In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: speakup@braille.uwo.ca From: Brent Harding List-Id: Terminating lame should be ok anyways. At 08:37 PM 8/21/00 -0400, you wrote: >Hey Geoff - > >I have a question for you concerning piping arecord into lame. How do you >terminate arecord without also terminating lame? When I record a sound >source I often do not know its duration before I begin, so I have been >terminating arecord with ^c at the appropriate time. However, that seems >to terminate lame also when I pipe arecord into lame on the same command >line... How do you handle that? > >Chuck. > > >My web site is http://www.mhonline.net/~chuckh >Winter will ask what we did all summer. > > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >