Am 06.01.2012 09:56, schrieb James Warden:
Hi,
If you use my trick described at
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge
you will have no such problem. You can configure audacity to use ALSA
Default instead, and yet have jack under the hood outputting to your
speakers, or your inputs recorded in audacity.
If you go that route, read carefully the whole WIKI page, because the
ALSA PCM definitions will have to be tailored to your particular setup.
Cheers!
J.
------------------------------------------------------------------------
*From:* Jeremy Jongepier <jeremy@xxxxxxxxxxxxxx>
*To:* linux-audio-user@xxxxxxxxxxxxxxxxxxxx
*Sent:* Friday, January 6, 2012 9:06 AM
*Subject:* Re: audacity/jack question (kxstudio 10.04 KDE)
On 01/06/12 07:59, Aaron L. wrote:
> Therefore, I have to reconnect it every time I hit 'stop' or 'pause' in
> Audacity. And it's only there while Audacity is playing.
>
> What am I doing wrong here?
Nothing. That's the default behaviour of Audacity (and afaik of most of
the applications that use PortAudio to talk to JACK).
Best,
Jeremy
Hello Aaron,
qjackctl has an excellent solution for that. There is a patch area, call
it from the button at the bottom, below stop (don't know the english name).
Create an outgoing patch from the PulseAudio sink and an ingoing patch
to the system outputs, and connect them. They will connect in serial
order. These patches accept regular expressions for the jack ports, for
example:
out_port\.[0-9\.]+
Save this patch and activate it. This will create the right connection
on demand. This works for many different audio scenes like magic. It's a
very smart concept.
(As a side note: I only have to deaktivate the automated patching of
qjackctl when I do sond export with ardour. There seem to fight some
deamons :))
Regards,
Georg.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
