I found a way to solve the problem using pipes from a Debian website. I hope it is the solution he is looking for. If he cats the output of /dev/dsp and tee off as many outputs as he desires, then he can successfully avoid the exclusivity lock on the /dev/dsp. I have a hardware as well as a software background, so like Linux, there is alway two or more ways to solve the problem. I only recommend the 2nd soundcard because a 20 or 30 dollar soundcard can do a lot more than software bound piping and semaphores which are prone to zombieism or other software glitches. Adam -----Original Message----- From: Bruce Marshall <bmarsh@bmarsh.com> Subj: Re: [SLE] Two processes recording from LINE-IN? Date: Sat Oct 1, 2005 5:08 pm Size: 1K To: SLE <suse-linux-e@suse.com> On Saturday 01 October 2005 04:59 pm, Jorge Fábregas wrote:

On Saturday 01 October 2005 4:31 pm, Adam Vazquez Kb2jpd Internet Mobile w/

Treo wrote:

...

Nothing prevents you from running multiple instances of sox, for example.

That's exactly what I want to do, but it seems it's not the way you say. I 'm trying to use multiple instances of sox to record the same source (LINE-IN) (just to different files). I'm not interested in multiple sound cards. I just want to record my LINE-IN with two sox processes but it seems sox will lock the device. I did the google thing and couldn't find anything.

Jorge

Isn't this just a timing problem... where your 2nd execution of sox is starting before the first is finished??? If so, and the programs truely are back-to-back, a simple script to check if sox is already running and loop until it quits would do it. Would seem to me that carefully specifying the startup in cron jobs would also do it. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com