29 Oct
2010
29 Oct
'10
4:21 a.m.
hi...
i have looked into the alsa-jack plugin. i think i fixed the main
problem which made it cause xruns.
git://hochstrom.endofinternet.org/alsa-plugins.git
its working quite reliably here now.
with the small fix on the xrun front. i looked at the basic usability.
i removed the pid and weird stuff from jack client name. and added an
option to configure the client name.
------------------------------------------------------------------
pcm.jack {
@args [ NAME ]
@args.NAME {
type string
default "alsa-jack"
}
type plug
slave {
pcm {
type jack
client_name $NAME
playback_ports {
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
}
capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
}
}
-----------------------------------------------------------------
this makes jack:client_name devices available.
the noauto git branch also contains a more flexible not autoconnecting
version. use with your favourite patchbay.
------------------------------------------------------------------
pcm.jacknoauto {
@args [ NAME ]
@args.NAME {
type string
default "alsa-jack"
}
type plug
slave {
pcm {
type jack
client_name $NAME
}
}
}
-----------------------------------------------------------------
mplayers alsa backend works fine with this.
after a bit of mucking around, i built a 32bit version here on my 64bit
machine and had 32bit skype connected to my 64bit jackd.
would be nice if this could get some testing with jack2 and stuff.
--
torben Hohn
29 Oct
29 Oct
4:47 a.m.
On 10/29/10 04:21, torbenh wrote:
hi...
i have looked into the alsa-jack plugin. i think i fixed the main
problem which made it cause xruns.
git://hochstrom.endofinternet.org/alsa-plugins.git
its working quite reliably here now.
with the small fix on the xrun front. i looked at the basic usability.
i removed the pid and weird stuff from jack client name. and added an
option to configure the client name.
------------------------------------------------------------------
pcm.jack {
@args [ NAME ]
@args.NAME {
type string
default "alsa-jack"
}
type plug
slave {
pcm {
type jack
client_name $NAME
playback_ports {
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
}
capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
}
}
-----------------------------------------------------------------
this makes jack:client_name devices available.
the noauto git branch also contains a more flexible not autoconnecting
version. use with your favourite patchbay.
------------------------------------------------------------------
pcm.jacknoauto {
@args [ NAME ]
@args.NAME {
type string
default "alsa-jack"
}
type plug
slave {
pcm {
type jack
client_name $NAME
}
}
}
-----------------------------------------------------------------
mplayers alsa backend works fine with this.
after a bit of mucking around, i built a 32bit version here on my 64bit
machine and had 32bit skype connected to my 64bit jackd.
very cool!
would be nice if this could get some testing with
jack2 and stuff.
Tested with jackdmp 1.9.6 (32bit) works so far.
..but I could not get your .asoundrc working. It fails with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
I've only replaced 'libasound_module_pcm_jack.so' and kept all other
/usr/lib/alsa-lib/*.so from default-debian. Could that be an issue?
here's the .asoundrc I'm using:
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
best,
robin
5 a.m.
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus <robin(a)gareus.org> wrote:
..but I could not get your .asoundrc working. It fails
with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p
5:08 a.m.
On 10/29/10 05:00, Paul Davis wrote:
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus
<robin(a)gareus.org> wrote:
I hazard a guess that it's just mplayer with a misleading error message.
I prefixed torben's config with
pcm.!default {
type plug
slave { pcm "jack" }
}
and once I remove the
type plug
slave { pcm {
from Torben's config and directly use "type jack" without any
'slaves'
it works just fine.
robin
..but I could not get your .asoundrc working. It
fails with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p
1:07 p.m.
On Thu, Oct 28, 2010 at 11:08 PM, Robin Gareus <robin(a)gareus.org> wrote:
On 10/29/10 05:00, Paul Davis wrote:
i don't think so. i think its you not telling mplayer to use the
correct ALSA device.
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus
<robin(a)gareus.org> wrote:
I hazard a guess that it's just mplayer with a misleading error message. ..but I could not get your .asoundrc working. It
fails with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p I prefixed torben's config with
pcm.!default {
type plug
slave { pcm "jack" }
}
which confirms my guess since this now makes the default ALSA device
be the JACK one, and thus apps which open "default" (which they should
if no other device name is given by the user) will get the JACK one.
probably worth reading this, part of my ongoing efforts to flesh out
the JACK FAQ .....
http://jackaudio.org/routing_alsa
2:42 p.m.
On 10/29/10 13:07, Paul Davis wrote:
On Thu, Oct 28, 2010 at 11:08 PM, Robin Gareus
<robin(a)gareus.org> wrote:
Mmh I don't follow. You're say it should work, no?
The problem here is the parsing of the inline 'pcm { .. }' with
@args and $NAME.. If i remove this part or simply do a separate
definition of pcm.jackraw instead of using it inline in pcm.jack it works.
But then the jack-ports are just named "alsa-jack_P*" or "(null)_P*"
and
I don't see the client name(s).
On 10/29/10 05:00, Paul Davis wrote:
i don't think so. i think its you not telling mplayer to use the
correct ALSA device.
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus
<robin(a)gareus.org> wrote:
I hazard a guess that it's just mplayer with a misleading error message. ..but I could not get your .asoundrc working. It
fails with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p I prefixed torben's config with
pcm.!default {
type plug
slave { pcm "jack" }
}
which confirms my guess since this now makes the default ALSA device
be the JACK one, and thus apps which open "default" (which they should
if no other device name is given by the user) will get the JACK one. From Torben's 'git log 'I see that he only
changed jack/pcm_jack.c and
it's 1.0.23 otherwise. Still, the issue could be
related that I did not
install all of alsa-plugins but only libasound_module_pcm_jack.so ?!
Anyway the new jack-plug works (tested with skype, firefox/flash &
mplayer) for half a day.
For day-to-day usage I moved away from jack-plug a while ago and am
using snd_aloop with alsa_in/out - it's a bit more heavy on CPU usage
but much more robust.
One remaining issue with jack-plug that I don't have with snd_aloop is
that some clients (fi. firefox) do not close the audio-device.
If the client is still connected to alsa/jack-plug and I re-start jackd,
sound becomes unavailable until the client (here: firefox) is also
restarted.
ciao,
robin
3:01 p.m.
On Fri, Oct 29, 2010 at 02:42:48PM +0200, Robin Gareus wrote:
On 10/29/10 13:07, Paul Davis wrote:
no. i just copied over the jack plugin. and i am on squeeze too.
this is not the issue.
please post your complete .asoundrc
i think your default entry is just a bit wrong.
On Thu, Oct 28, 2010 at 11:08 PM, Robin Gareus
<robin(a)gareus.org> wrote:
Mmh I don't follow. You're say it should work, no?
The problem here is the parsing of the inline 'pcm { .. }' with
@args and $NAME.. If i remove this part or simply do a separate
definition of pcm.jackraw instead of using it inline in pcm.jack it works.
But then the jack-ports are just named "alsa-jack_P*" or "(null)_P*"
and
I don't see the client name(s).
From Torben's 'git log 'I see that he only changed jack/pcm_jack.c and
it's 1.0.23 otherwise. Still, the issue could be related that I did not
install all of alsa-plugins but only libasound_module_pcm_jack.so ?! On 10/29/10 05:00, Paul Davis wrote:
i don't think so. i think its you not telling mplayer to use the
correct ALSA device.
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus
<robin(a)gareus.org> wrote:
> ..but I could not get your .asoundrc working. It fails with
>
> [AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
> '/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p
I hazard a guess that it's just mplayer with a misleading error message. I prefixed torben's config with
pcm.!default {
type plug
slave { pcm "jack" }
}
which confirms my guess since this now makes the default ALSA device
be the JACK one, and thus apps which open "default" (which they should
if no other device name is given by the user) will get the JACK one.
Anyway the new jack-plug works (tested with skype, firefox/flash &
mplayer) for half a day.
For day-to-day usage I moved away from jack-plug a while ago and am
using snd_aloop with alsa_in/out - it's a bit more heavy on CPU usage
but much more robust.
One remaining issue with jack-plug that I don't have with snd_aloop is
that some clients (fi. firefox) do not close the audio-device.
If the client is still connected to alsa/jack-plug and I re-start jackd,
sound becomes unavailable until the client (here: firefox) is also
restarted.
i guess there is not much we can do.
what does pulse do under these circumstances ?
but since the goal is just to never stop jack, this issue will be
ignored ;D
ciao,
robin
--
torben Hohn
3:15 p.m.
On 10/29/10 15:01, torbenh wrote:
I dunno. I never used pulseaudio.
no. i just copied over the jack plugin. and i am on squeeze too.
this is not the issue.
thanks for the info.
please post your complete .asoundrc
i think your default entry is just a bit wrong.
attached.
Anyway the new
jack-plug works (tested with skype, firefox/flash &
mplayer) for half a day.
For day-to-day usage I moved away from jack-plug a while ago and am
using snd_aloop with alsa_in/out - it's a bit more heavy on CPU usage
but much more robust.
One remaining issue with jack-plug that I don't have with snd_aloop is
that some clients (fi. firefox) do not close the audio-device.
If the client is still connected to alsa/jack-plug and I re-start jackd,
sound becomes unavailable until the client (here: firefox) is also
restarted.
i guess there is not much we can do.
what does pulse do under these circumstances ? but since the goal is just to never stop jack, this
issue will be
ignored ;D
fair enough.
Well there's two reasons for stopping JACK from time-to-time:
- save battery power when traveling and not listening to audio
- debugging some JACK apps.. where I need sound *and* gdb
(otherwise
`jackd -t 600000 -r -n debug -d dummy` and
JACK_DEFAULT_SERVER=debug gdb ...
does the trick)
In my case those events occur much more frequently than I wish to
re-start firefox and other non-jack apps :)
Anyway it's probably just me and I'm happy with snd_aloop.
robin
3:49 p.m.
On Fri, Oct 29, 2010 at 03:15:00PM +0200, Robin Gareus wrote:
On 10/29/10 15:01, torbenh wrote:
see jack-dev for the thread on jack_suspend.
this is probably another usecase for it.
i guess there is not much we can do.
what does pulse do under these circumstances ?
I dunno. I never used pulseaudio.
but since the goal is just to never stop jack,
this issue will be
ignored ;D
fair enough.
Well there's two reasons for stopping JACK from time-to-time:
- save battery power when traveling and not listening to audio - debugging some JACK apps.. where I need sound *and*
gdb
(otherwise
`jackd -t 600000 -r -n debug -d dummy` and
JACK_DEFAULT_SERVER=debug gdb ...
does the trick)
this reminds me that alsa_out is missing an option for the servername :)
alsa_out -d jack:aout -n3 seems to work nicely.
so with a servername option, it could operate in a jack_diplomat like
way.
In my case those events occur much more frequently than I wish to
re-start firefox and other non-jack apps :)
Anyway it's probably just me and I'm happy with snd_aloop.
robin
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack is already a plug.
your pcm.!default wraps it with another plug.
i only have:
pcm.!default jack:default
pcm.jack {
@args [ NAME ]
@args.NAME {
type string
default "alsa-jack"
}
type plug
slave {
pcm {
type jack
client_name $NAME
playback_ports {
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
}
capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
}
}
pushing args to the default doesnt work, i guess.
pcm.!default {
@args [ NAME ]
@args.NAME {
type string
default "alsa-jack"
}
type plug
slave {
pcm {
type jack
client_name $NAME
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
}
}
--
torben Hohn
2:34 p.m.
On Fri, Oct 29, 2010 at 05:08:03AM +0200, Robin Gareus wrote:
On 10/29/10 05:00, Paul Davis wrote:
like paul said. you didnt change the default device.
use:
mplayer -ao alsa:device=jack
or
mplayer -ao alsa:device=jack=mplayer
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus
<robin(a)gareus.org> wrote:
I hazard a guess that it's just mplayer with a misleading error message. ..but I could not get your .asoundrc working. It
fails with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p
I prefixed torben's config with
pcm.!default {
type plug
slave { pcm "jack" }
}
and once I remove the
type plug
slave { pcm {
from Torben's config and directly use "type jack" without any
'slaves'
it works just fine.
this wraps a plug device in another plug device.
i actually dont know how smart this is ;)
i have
pcm.!default jack:alsa-default
it will only work fine for the default. the jack plug it self, is not
very flexible, and many clients would complain that they dont do float
and fixed SR...
robin
--
torben Hohn
2:41 p.m.
On Fri, Oct 29, 2010 at 4:34 PM, torbenh <torbenh(a)gmx.de> wrote:
On Fri, Oct 29, 2010 at 05:08:03AM +0200, Robin Gareus
wrote:
Torben, works here, with jack1 0.120 (SVN) gentoo 64bit.
Thanks for the update.
Regards,
Alex.
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
On 10/29/10 05:00, Paul Davis wrote:
like paul said. you didnt change the default device.
use:
mplayer -ao alsa:device=jack
or
mplayer -ao alsa:device=jack=mplayer
On Thu, Oct 28, 2010 at 10:47 PM, Robin Gareus
<robin(a)gareus.org> wrote:
I hazard a guess that it's just mplayer with a misleading error message. ..but I could not get your .asoundrc working. It
fails with
[AO_ALSA] alsa-lib: pcm_hw.c:1293:(snd_pcm_hw_open) open
'/dev/snd/pcmC0D0p' failed (-16): Device or resource busy
you're not opening the JACK device, clearly - this message references
/dev/snd/pcmC0D0p
I prefixed torben's config with
pcm.!default {
type plug
slave { pcm "jack" }
}
and once I remove the
type plug
slave { pcm {
from Torben's config and directly use "type jack" without any
'slaves'
it works just fine.
this wraps a plug device in another plug device.
i actually dont know how smart this is ;)
i have
pcm.!default jack:alsa-default
it will only work fine for the default. the jack plug it self, is not
very flexible, and many clients would complain that they dont do float
and fixed SR...
robin
--
torben Hohn
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
4937
days inactive
4937
days old
linux-audio-user@lists.linuxaudio.org
10 comments
4 participants
participants (4)
-
alex stone -
Paul Davis -
Robin Gareus -
torbenh