There is a way, use parenthesis to start each process in a subshell, so arecord runs in one shell, lame in another. Make sure the shell that runs lame has the sigint signal trapped out so lame doesn't receive it. something like this (untested untried might not work) might work; (arecord -M)|(trap 0 1;lame options) might do it. You don't want the sigint going to lame only to arecord. Somebody on this list might be better at bash than I am and can work something. Regards, Kerry. On Tue, Aug 22, 2000 at 01:55:36PM +1000, Geoff Shang wrote: > Hi Chuck: > > urrr. I don't. Never thought about that one. hmmm. yeah and I've seen > some programs get annoyed about files made this way. It's interesting that > aplay will play files recorded by arecord when it's terminated by > control-C, but the vocoder program I use for example doesn't like them. > > I don't know what to do there. You might do better with say record in the > sox package, but I don't know for sure. Anyone else with ideas? Oh I > guess you could kill the arecord process from another console, but I > haven't tried that. > > Geoff. > > > -- > Geoff Shang <gshang10 at scu.edu.au> > ICQ number 43634701 > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- -- Kerry Hoath: kerry at gotss.eu.org Alternates: kerry at emusys.com.au kerry at gotss.spice.net.au or khoath at lis.net.au ICQ UIN: 8226547
