2 Jul
2004
2 Jul
'04
7:41 a.m.
Hello all,
I've been trying out the newly improved JACK support in Audacity and
can confirm that it does work. If other people could give this some
testing I'm sure it would help solidify the feature. Please consider
joining the audacity-devel list and sending feedback.
To build Audacity with JACK support you need to do this:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/audacity login
(hit the enter key when it asks for a password)
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/audacity co
audacity
(the above is all one line)
cd audacity
./configure --with-portaudio=v19 --without-portmixer
(edit src/Makefile and add this to the end of the LIBS line if it's
not there):
-lasound -ljack
Then make and make install as usual. Start JACK, start Audacity and
you should have a JACK option in Preferences under Audio I/O. You may
need to disable the VU meters to get reliable playback on a slow
machine - that option is on each meter's drop-down menu.
Cheers
Daniel
2 Jul
2 Jul
11:37 a.m.
I've been trying out the newly improved JACK
support in Audacity and
can confirm that it does work. If other people could give this some
testing I'm sure it would help solidify the feature. Please consider
joining the audacity-devel list and sending feedback.
Hi Daniel,
I just tried it, and it doesn't work for me. I follow the steps you
describe. But when I start audacity, it complains that it cannot
open the alsa device (because the running jackd is using it)
debian:/home/demo/audacity-1.2.1cvs20040702# /usr/local/bin/audacity
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0c failed:
Device or resource busy
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
Device or resource busy
In the preferences, jack is selected, but when I try to play a sound,
an error dialog pops up:
"Error while opening sound device. Please check the output device settings
and the project sample rate."
The project sample rate is set to 48000, which jackd is running at...
Any idea?
Maarten
12:21 p.m.
when I start audacity, it complains that it cannot
open the alsa device (because the running jackd is using it)
debian:/home/demo/audacity-1.2.1cvs20040702#
/usr/local/bin/audacity ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open)
open /dev/snd/pcmC0D0c failed: Device or resource busy
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p
failed: Device or resource busy
I got that the first time - after selecting JACK in the I/O
preferences and restarting Audacity it was OK.
In the preferences, jack is selected, but when I try
to play a
sound, an error dialog pops up:
"Error while opening sound device. Please check the output device
settings and the project sample rate."
Maybe try stopping JACK, starting it and then starting Audacity again.
The project sample rate is set to 48000, which jackd
is running
at...
I've been using 44100 for all my tests - maybe that's the problem. I
also built portaudio v19 before building Audacity; that may make a
difference. From the audacity source directory created in the cvs
checkout, it's just:
cd lib-src/portaudio-v19
./configure
make
make install
then build Audacity as described.
Please report your experience on the audacity-devel list and hopefully
it can be sorted out.
http://lists.sourceforge.net/lists/listinfo/audacity-devel
Cheers
Daniel
3:35 p.m.
Hallo,
Daniel James hat gesagt: // Daniel James wrote:
I've been trying out the newly improved JACK
support in Audacity and
can confirm that it does work.
...
cd audacity
./configure --with-portaudio=v19 --without-portmixer
So, does that imply, that portaudio now has working Jack support??
Ciao
--
Frank Barknecht _ ______footils.org__
3:46 p.m.
Frank Barknecht wrote:
Hallo,
Daniel James hat gesagt: // Daniel James wrote:
I put in an enhancement request for Gentoo users. If anyone else want's
to pony on to that request maybe it will get done a bit sooner.
http://bugs.gentoo.org/show_bug.cgi?id=55898
- Mark
I've been trying out the newly improved JACK
support in Audacity and
can confirm that it does work.
...
cd audacity
./configure --with-portaudio=v19 --without-portmixer
So, does that imply, that portaudio now has working Jack support??
Ciao
5 Jul
5 Jul
7:07 a.m.
./configure
--with-portaudio=v19 --without-portmixer
So, does that imply, that portaudio now has working Jack support?? 
8:33 p.m.
Daniel James wrote:
I can confirm that it works with Audacity for playing back multitrack
projects - I haven't done any recording with it yet. It seems to play
back more smoothly than the native ALSA support, which gives me skips
in the audio on this machine. (Using OSS emulation with the same
hardware and drivers sounds perfect.)
If you do a CVS checkout of Audacity HEAD as described, you can build
and install this version of portaudio-v19 separately - it's in the
lib-src directory. Indeed, it seems you do have to do this first to
get Audacity to support JACK properly.
Okay, before I go get all excited that Audacity is now JACKable,
I need to ask a few questions...
If I want to build the new version, do I need to uninstall any
older version(s) I have installed? If yes, how do I do that?
Is there some way to store my old Audacity version in a safe
place so I can go back to it if things don't work out with the
new version?
Are there are any project data incompatibilities with previous
versions of Audacity?
I'm really looking forward to a JACKable Audacity. I just want
to make sure I don't mess up my setup which I kinda have working
now...
Thanks for any info forthcoming. :-)
Peace,
~Jos~
./configure --with-portaudio=v19 --without-portmixer
So, does that imply, that portaudio now has working Jack support??
6 Jul
6 Jul
6:37 a.m.
Okay, before I go get all excited that Audacity is now
JACKable,
I need to ask a few questions...
If I want to build the new version, do I need to uninstall any
older version(s) I have installed? If yes, how do I do that?
You can specify an alternative installation directory at configure
time, I think, using the option --prefix=/usr/local/bin/audacitycvs/
or whatever.
Is there some way to store my old Audacity version in
a safe
place so I can go back to it if things don't work out with the
new version?
If you have your original Audacity binary in /usr/bin then it
shouldn't be affected by having a binary in another location, as far
as I can tell. I once had one version in /usr/bin and another in
/usr/local/bin and it worked OK.
Are there are any project data incompatibilities with
previous
versions of Audacity?
There have been some reports on the audacity-devel list of problems
with projects going between 1.2.1 and CVS versions, as I recall. I
wouldn't use the CVS version for serious work - it's just too
untested.
I'm really looking forward to a JACKable Audacity.
I just want
to make sure I don't mess up my setup which I kinda have working
now...
I do know that feeling. I tend to be quite conservative with the
software on my studio machine because reliability is all-important.
Last time I did a professional recording job, the mixing desk power
supply failed at the end of the last session, but the Linux box ran
perfectly!
Cheers
Daniel
8:53 p.m.
On 06-Jul-2004 Daniel James wrote:
} > Okay, before I go get all excited that Audacity is now JACKable,
} > I need to ask a few questions...
} >
} > If I want to build the new version, do I need to uninstall any
} > older version(s) I have installed? If yes, how do I do that?
}
} You can specify an alternative installation directory at configure
} time, I think, using the option --prefix=/usr/local/bin/audacitycvs/
} or whatever.
You can just not install it. Run it from the directory you compiled it in.
{I do this with snd as well as a few other programs. I helps if you install it
once. Then you can be sure that the program's libraries are there. You can do
different configurations pretty easily this way.}
----------------------------------
E-Mail: RickTaylor(a)Speakeasy.Net
Date: 06-Jul-2004
Time: 17:37:14
This message was sent by XFMail
----------------------------------
7492
days inactive
7496
days old
linux-audio-user@lists.linuxaudio.org
8 comments
6 participants
participants (6)
-
Daniel James -
Frank Barknecht -
Jos Laake -
Maarten De Boer -
Mark Knecht -
RickTaylor＠Speakeasy.Net