On Wed, Feb 03, 2010 at 10:05:28PM +0100, Jan Stary wrote: > On Feb 03 16:10:48, Jacob Meuser wrote: > > I wonder if these problems would go away if jack support were dropped > > from portaudio. only working with 32-bit sounds suspicious. > > That's another thing: why is jack and esound in the dependencies > of audacity (in 4.6)? Neither of them seems to ever be running anyway.
jack -> portaudio-svn -> audacity esound -> wxWidgets -> audacity audacity itself doesn't depends on those, but packages audacity depends on depends on them. > > I've used audacity with jack before, but if it's messig things up > > for more normal/casual use, it can go. > > The problem I was describing occurs without jack running. but with portaudio built with jack support, there is more complication for portaudio and it's dependents, even if jack is not running. > > ardour only uses jack, so the functionality I want will be replaced anyway. > > Sorry, you lost me: > the functionality of jack is gonna be replaced? > ardour is gonna be replaced? a jackd client can get the output of other jackd clients. when audacity is using jackd, it's possible to record other jackd client output. same with ardour running on jackd. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
