Subject: | Re: audacity |
---|---|
From: | Steve Pelikan <> |
Date: | Thu, 19 May 2005 13:10:38 -0400 |
Rich: The audio i/o in Audacity is done with a "portable audio" library that provides an interface to the various hardwares/ operating systems that the program can run on. So there is, at least in theory, an extra layer of processing going on and a first guess is that Audacity isn't more efficient than a made-for-one-system recording program. Still, the portaudio library is just providing a callback mechanism and probably isn't taking much time or resources. The best bet would be to do some timing tests or profiling. I haven't really got a clue how to do this sort of test. Cheers! Steve P ________________________________________________________________________ ________________________________________________________________________ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: no FAQ for a beginner?, Rich Peet |
---|---|
Next by Date: | Fwd: Gray Jay sounds needed, Doug Von Gausig |
Previous by Thread: | Re: audacity, Rich Peet |
Next by Thread: | Re: where are the frogs calling?, Catarina N Moreira (Student) |
Indexes: | [Date] [Thread] [Top] [All Lists] |
The University of NSW School of Computer and Engineering takes no responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the naturerecordists mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU