* piping arecord into lame
@ Charles Hallenbeck
` Geoff Shang
0 siblings, 1 reply; 8+ messages in thread
From: Charles Hallenbeck @ UTC (permalink / raw)
To: Speakup Distribution List
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: piping arecord into lame
piping arecord into lame Charles Hallenbeck
@ ` Geoff Shang
` Kerry Hoath
` Charles Hallenbeck
0 siblings, 2 replies; 8+ messages in thread
From: Geoff Shang @ UTC (permalink / raw)
To: speakup
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@scu.edu.au>
ICQ number 43634701
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: piping arecord into lame
` Geoff Shang
@ ` Kerry Hoath
` Charles Hallenbeck
` Charles Hallenbeck
1 sibling, 1 reply; 8+ messages in thread
From: Kerry Hoath @ UTC (permalink / raw)
To: speakup
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@scu.edu.au>
> ICQ number 43634701
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
--
Kerry Hoath: kerry@gotss.eu.org
Alternates: kerry@emusys.com.au kerry@gotss.spice.net.au or khoath@lis.net.au
ICQ UIN: 8226547
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: piping arecord into lame
` Geoff Shang
` Kerry Hoath
@ ` Charles Hallenbeck
1 sibling, 0 replies; 8+ messages in thread
From: Charles Hallenbeck @ UTC (permalink / raw)
To: speakup
Perhaps it is more of a problem on this relatively slow system, where lame
takes longer to handle its input than it might on a faster system. This is
a 133 MHz 5x86 with only 16MB memory, and while it does a lot of things
pretty well, it takes its sweet time about it! <g>
Chuck.
On Tue, 22 Aug 2000, 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.
>
>
>
My web site is http://www.mhonline.net/~chuckh
Winter will ask us what we did all summer.
^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <Pine.LNX.4.21.0008212035160.3784-100000@hudson.mhonline.ne t>]
* Piping arecord into lame
@ Charles Hallenbeck
0 siblings, 0 replies; 8+ messages in thread
From: Charles Hallenbeck @ UTC (permalink / raw)
To: Speakup Distribution List
Well I give up!
I have spent the day reading about subshells and trapping the kill signal,
and experimenting with same, and have not been able to successfully
interrupt only the "arecord" process leaving "lame" to finish processing
data sent to it through a pipe.
This is really not a proper thread for this list, but if anyone has been
able to do that, I would appreciate knowing how. Meanwhile I will just
contine to arecord to a file and then as a second and subsequent task I
will process that file with "lame". Every variation of piping I have
tried always loses the last few seconds of data.
Off it goes to the back burner!
Chuck.
My web site is http://www.mhonline.net/~chuckh
Winter will ask us what we did all summer.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
piping arecord into lame Charles Hallenbeck
` Geoff Shang
` Kerry Hoath
` Charles Hallenbeck
` Charles Hallenbeck
[not found] <Pine.LNX.4.21.0008212035160.3784-100000@hudson.mhonline.ne t>
` Brent Harding
` Charles Hallenbeck
Piping " Charles Hallenbeck
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).