23 Sep
2012
23 Sep
'12
1:08 p.m.
Hello,
currently I have set up a ALSA <-> JACK connection with the loopback
device approach as described here:
http://www.penguinproducer.com/2011/11/jack-alsa-bridge-kit/
This works fine, except for one problem: Simultaneous playback of
multiple applications using the ALSA loopback device to channel the
audiostream to JACK fails with this error:
Device or resource busy
The setup in my asound.conf is quite simple:
# Audio _to_ JACK
pcm.jack_playback {
type plug
slave.pcm "hw:Loopback,0,0"
}
# Audio _from_ JACK
pcm.jack_capture {
type plug
slave.pcm "hw:Loopback,0,1"
}
pcm.playback_loop {
type plug
slave.pcm "hw:Loopback,1,0"
}
pcm.capture_loop {
type plug
slave.pcm "hw:Loopback,1,1"
}
pcm.jack_audio {
type asym
playback.pcm "jack_playback"
capture.pcm "jack_capture"
}
I thought that "type plug" should autoconfigure the device in use
accordingly. I tried to make a manual configuration with dmix but it
didn't work and I'm not sure if it is necessary. The alsa documentation
states that dmix is used when the device has no hardware mixer and I'm
quite sure that a virtual loopback device has none.
best,
semkath
23 Sep
23 Sep
3:04 p.m.
On Sun, Sep 23, 2012 at 7:08 AM, Sebastian Rose <s.rose(a)semkath.de> wrote:
I thought that "type plug" should
autoconfigure the device in use
accordingly. I tried to make a manual configuration with dmix but it didn't
work and I'm not sure if it is necessary. The alsa documentation states
that dmix is used when the device has no hardware mixer and I'm quite sure
that a virtual loopback device has none.
dmix is the only way to do that, unless you include running PulseAudio with
the loopback device.
its also getting pretty silly when you're trying to use ALSA dmix or
PulseAudio to mix multiple non-JACK-aware applications into a psuedo-device
that communicates with JACK, given that device sharing is (partially) what
JACK was intended for in the first place.
4:51 p.m.
On 23/09/12 15:04, Paul Davis wrote:
On Sun, Sep 23, 2012 at 7:08 AM, Sebastian Rose
<s.rose(a)semkath.de> wrote:
Since I don't use PulseAudio I will give dmix another shot, thanks.
I thought that "type plug" should
autoconfigure the device in use
accordingly. I tried to make a manual configuration with dmix but it didn't
work and I'm not sure if it is necessary. The alsa documentation states
that dmix is used when the device has no hardware mixer and I'm quite sure
that a virtual loopback device has none.
dmix is the only way to do that, unless you include running PulseAudio with
the loopback device. its also getting pretty silly when you're trying
to use ALSA dmix or
PulseAudio to mix multiple non-JACK-aware applications into a psuedo-device
that communicates with JACK, given that device sharing is (partially) what
JACK was intended for in the first place.
Silly: yes. But if I want to use Flashplayer and Skype at the same time
and don't want to use different soundcards (quite a recording hassle for
podcast production, for example) and use a decent audio interface with a
good microphone, I'm stuck with this choice.
5:11 p.m.
On Sun, 23 Sep 2012 16:51:34 +0200
Sebastian Rose <s.rose(a)semkath.de> wrote:
Silly: yes. But if I want to use Flashplayer and Skype
at the same
time and don't want to use different soundcards (quite a recording
hassle for podcast production, for example) and use a decent audio
interface with a good microphone, I'm stuck with this choice.
Here is what I'm using very successfully to run kde, skype and some
games over jack/hdsp instead of the built in intel-hda. It was written
by falktx, of kxstudio fame.
It comes in three parts:
http://dl.dropbox.com/u/879835/.asoundrc
http://dl.dropbox.com/u/879835/jacklib.py
http://dl.dropbox.com/u/879835/aloop-daemon.py
It actually makes audio on my system a dream to work with, and allows
me to route it around as I wish. One could conceivably create even
more loopback devices for specific apps, but this has worked great so
far.
--
Joakim
6:37 p.m.
On 23/09/12 17:11, Joakim Hernberg wrote:
On Sun, 23 Sep 2012 16:51:34 +0200
Sebastian Rose <s.rose(a)semkath.de> wrote:
Ah, thanks a lot for your asoundrc file. I was on the right track with
my dmix setup, but I didn't think about the fact that the JACK loopback
side for simultaneous playback needed format and rate specifications. So
basically it goes dmix -> dsnoop for one direction and dsnoop -> dmix
for the other (in case that there are multiple applications that
simultaneously recording via the ALSA layer). Your setup doesn't cover
the last part, but I grant it's a pathological case since nothing comes
to mind (maybe Mumble and Skype simultaneously for whatever reason).
Silly: yes. But if I want to use Flashplayer and
Skype at the same
time and don't want to use different soundcards (quite a recording
hassle for podcast production, for example) and use a decent audio
interface with a good microphone, I'm stuck with this choice.
Here is what I'm using very successfully to run kde, skype and some
games over jack/hdsp instead of the built in intel-hda. It was written
by falktx, of kxstudio fame.
It comes in three parts:
http://dl.dropbox.com/u/879835/.asoundrc
http://dl.dropbox.com/u/879835/jacklib.py
http://dl.dropbox.com/u/879835/aloop-daemon.py
It actually makes audio on my system a dream to work with, and allows
me to route it around as I wish. One could conceivably create even
more loopback devices for specific apps, but this has worked great so
far.
4242
days inactive
4242
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Joakim Hernberg -
Paul Davis -
Sebastian Rose