[PlanetCCRMA] Why doesn't Audacity use jack in CCRMA?

Hector Centeno hcengar@gmail.com
Sun Apr 8 17:43:01 2007


Yes, Audacity needs that Jack native back end! Before I used to build
my own stable version of Audacity with Portaudio/Jack support (after
doing some needed hacking) but since recent changes in Portaudio I
couldn't do it any more. Now I'm using Audacity Beta (1.3.3) which
comes wih it's own Portaudio source and builds without any problems.
It's quite stable and has very good new features.



On 4/8/07, Fernando Lopez-Lezcano <nando@ccrma.stanford.edu> wrote:
> On Sun, 2007-04-08 at 16:14 -0400, Jason Russler wrote:
> > I dunno, but when I try to set the Fedora Extras build of Audacity to
> > use JACK it crashes both jackd and Audacity.  Could be an x86_64 thing
> > or it could be the reason that CCRMA doesn't build in JACK support.
> Audacity currently comes from Fedora Extras, not the Planet CCRMA repo
> (ie: I'm not currently building it). Most probably (I have not looked)
> the packager is not using a newer version of portaudio with better Jack
> support as I used to do - if that's the case it would probably qualify
> as a bug to report to Fedora's bugzilla.
> In any case support for Jack through portaudio is pretty lousy (for
> example you can only "connect" to another Jack client using the
> Preferences menu, and you can only see clients that had already started
> when Audacity was launched, very lame). Audacity sorely needs a native
> Jack audio backend...
> -- Fernando
> >
> > On 4/8/07, Timo Sivula <timo.sivula@gmail.com> wrote:
> > > Hi,
> > >
> > > I must have missed the discussion, but I am sure there must be a good reason for this?
> > >
> > > Timo
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma