From: Peter Howell Subject: Re: scripting the "rec" function for a fixed time. Date: 25 Feb 2003 19:44:08 -0500 Sender: linux-newbie-owner@vger.kernel.org Message-ID: <1046220248.15520.27.camel@smeagle> References: <5.1.0.14.1.20030224184821.01eb7e30@celine> <03022506145301.00602@unix.pa3gcu> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <03022506145301.00602@unix.pa3gcu> List-Id: Content-Type: text/plain; charset="us-ascii" To: pa3gcu@zeelandnet.nl Cc: linux-newbie@vger.kernel.org On Tue, 2003-02-25 at 01:14, pa3gcu wrote: > > "rec" is not a stock linux command, and I cannot readily identify a package > > that includes that application (just trying to match on "rec" turns up > > several hundred hits in the Debian package database). So I'd suggest you > > tell us a bit more about your setup, including enough information that we > > can identify and take a look at the package that includes this command. > > rec is an unix command altho' not well supported, slackware 8 has it included. > > rec --help shows a lot but thses are relavant to the question; > -c, --channels=CHANNELS specifies the number of sound channels in FILE > -d, --device=DEVICE use DEVICE for input/output > -f, --format=FORMAT specifies bit format of sample > FORMAT is either s, u, U, A, a, or g > -r, --rate=RATE sample rate in hertz of FILE > -s, --size=SIZE interpret size of sample > > I think this one could be an help -s xxxxxxxb > SIZE is either b, w, l, f, d, or D Alas no :-( size isn't the file size. It's really the width of each sample. eg b for 8 bits, w for 16 bits.... It appears that rec does not buffer the sound, but instead writes it directly to the file. It's inelegant, but I suppose I could kill the application after a specified delay. There are two problems with implementing that for me. Firstly, I don't think I could do that in perl, which I'm most familiar with because there doesn't appear to be an easy way to spawn a process and continue running the scipt. Secondly, I don't know how to run a process and get it's process id, which I'd need to kill it. Ok, just did a little rtfm. I guess I could use ps and extract the id. Now I guess I'd better learn some bash scripting - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs