You might try using a named pipe. This would let vsound write to the named pipe (callit output.wav) and let lame read from the named pipe.
Both applications should see it as a file but it would never grow in size. To see how this might work try this: 1. Run screen to get screens running. 2. in screen 1 do: mkfifo myfifo cat myfifo 2. in screen 2 do this: echo "hello world" > myfifo 3. go back to screen run and see that your cat command has printed out "hello world" and returned you to the shell prompt. Note that when using fifos, it is necessary that your read process be started before your write process or else it will fail. So, you would need to create your fifo, start your lame process first and then start your vsound process. Good luck, and may the force be with you. Rudy On Tue, Oct 07, 2003 at 01:44:52PM -0400, Silvio a Beccara wrote: > Hi everybody, > > I was trying to pipe vsound's standard output into LAME for directly encoding > a realaudio stream into an mp3 file, but the -s option of vsound does not > seem to work. I need direct encoding because I cannot afford the big WAV files > that come out of vsound. > > I'm running a Mandrake 9.1 on a dual Athlon system, with KDE as window > manager. The ARTS sound system is running. > > In the first place there was a bug in the vsound script about vsound not > being able to use both 'verbose' (though not invoked) option and the -s > option, but I fixed it. > > Even so, while vsound runs perfectly with a wav file, it does not when trying > to pipe its ouput, not even when redirecting its standard output to a regular > file, e.g. > > vsound -s trplayer -q -n -t 120 \ > http://www.radio.rai.it/live/radio1.ram > foo > > I tried to ask the same question to the vsound developer, but got no reply so > far. > > Could anybody help me, perhaps with some script that could work out on my > system? > > Thank you very much, bye > > Silvio a Beccara - Italy >
