18 Oct
2011
18 Oct
'11
11:44 p.m.
Hello,
I've been trying to find a way to create an alsa to jack bridge. I found
instructions at the following URL:
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge
I compiled the aloop module and it works fine, but when I try setting up
the asoundrc as described, and use the device, I get.
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:654: audio open error: Invalid argument
Does anyone know what this uninformative error mean? Has anybody ever
had luck with a similar setup?
Thanks.
Cheers,
S.M.
--
19 Oct
19 Oct
12:43 a.m.
On Tue, Oct 18, 2011 at 05:46:12PM -0400, S. Massy wrote:
Interesting page !
I compiled the aloop module and it works fine, but
when I try setting up
the asoundrc as described, and use the device, I get.
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:654: audio open error: Invalid argument
Does anyone know what this uninformative error mean? Has anybody ever
had luck with a similar setup?
I get similar errors, except that the second one is
'Device or resource busy' instead of 'Invalid argument'.
Maybe it's the dmix on top of all the rest. I've seen
other cases where dmix wouldn't mix (pun not intended)
with its peers.
Ciao,
--
FA
1:27 a.m.
Hi Fons, *
On 10/19/2011 12:43 AM, Fons Adriaensen wrote:
On Tue, Oct 18, 2011 at 05:46:12PM -0400, S. Massy
wrote:
Interesting page !
> I compiled the aloop module and it works fine, but when I try setting up
> the asoundrc as described, and use the device, I get.
> ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> aplay: main:654: audio open error: Invalid argument
>
> Does anyone know what this uninformative error mean?
I don't.
> Has anybody ever
> had luck with a similar setup?
yes, aloop + alsa_in/alsa_out work just fine here since over a year.
I only use the snd-aloop module from the alsa-drivers. All other alsa
kernel stuff is from the original kernel.
The only problem is: the device needs to be closed during
suspend/resume; otherwise the systems hangs on resume. I've added
killall alsa_in alsa_out; kill -HUP `lsof -t /dev/snd/pcmC1D*`; and
restart commands to /etc/pm/sleep.d/ for that. I can't use `alsa
force-unload` because that'd kill jackd, too.
I get similar errors, except that the second one is
'Device or resource busy' instead of 'Invalid argument'.
The loopback devices 'ploop', 'cloop' can only be accessed by one
process at a time. If you try to start multiple processes accessing them
you'll get a 'Device or resource busy'. Maybe the device-order changed
with the aloop module being loaded during boot and your jackd is using
on it.. that happened to me at first.
Multiple clients can connect to -dLoopback to play/record via dmix.
jackd -d alsa -d hw:2
alsa_out -j ploop -dploop
aplay -dLoopback some_file.wav &
aplay -dLoopback some_other_file.wav &
The .asoundrc from the alsa-wiki, configures -dLoopback as default.
so `aplay some_file.wav` works just the same.
Maybe it's the dmix on top of all the rest.
I've seen
other cases where dmix wouldn't mix (pun not intended)
with its peers.
you must mean /selected peers/. I'm not one of them :-p
The .asoundrc from the page works fine without modifications:
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge#aso…
Cheers!
robin
2:12 a.m.
On Wed, Oct 19, 2011 at 01:27:22AM +0200, Robin Gareus wrote:
Hi Fons, *
On 10/19/2011 12:43 AM, Fons Adriaensen wrote:
Would you mind sharing your asoundrc just
to make sure? Here, I'm stuck
with the "invalid argument" error message, which is singularly
unhelpful.
Cheers,
S.M.
On Tue, Oct 18, 2011 at 05:46:12PM -0400, S.
Massy wrote:
Interesting page !
> I compiled the aloop module and it works fine, but when I try setting up
> the asoundrc as described, and use the device, I get.
> ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
> aplay: main:654: audio open error: Invalid argument
>
> Does anyone know what this uninformative error mean?
I don't.
> Has anybody ever
> had luck with a similar setup?
yes, aloop + alsa_in/alsa_out work just fine here since over a year.
I only use the snd-aloop module from the alsa-drivers. All other alsa
kernel stuff is from the original kernel.
2:43 a.m.
On 10/19/2011 02:13 AM, S. Massy wrote:
[..]
Would you mind sharing your asoundrc just to make
sure?
I am using the ~/.asoundrc from
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge#aso…
without modification.
1:06 p.m.
----- Original Message -----
I compiled the aloop module and it works fine, but when I try setting up
the asoundrc as described, and use the device, I get.
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:654: audio open error: Invalid argument
Does anyone know what this uninformative error mean? Has anybody ever
had luck with a similar setup?
-----
Hi, I use this setup as described in the wiki page (I wrote that page myself ;) and have
no issue.
You should provide the version numbers of libasound and alsa, how they were installed,
etc.
Version mismatch can cause this kind of problems I think.
J.
9:32 p.m.
On Wed, Oct 19, 2011 at 04:06:53AM -0700, James Warden wrote:
----- Original Message -----
I compiled the aloop module and it works fine, but when I try setting up
the asoundrc as described, and use the device, I get.
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:654: audio open error: Invalid argument
Does anyone know what this uninformative error mean? Has anybody ever
had luck with a similar setup?
-----
Hi, I use this setup as described in the wiki page (I wrote that page myself ;) and have
no issue.
You should provide the version numbers of libasound and alsa, how they were installed,
etc.
Version mismatch can cause this kind of problems I think.
Well, libasound is a
Debian package from Squeeze and is 1.0.13. The
drivers are from kernel 2.6.33.7.2-rt30, apart from aloop which is from
release 1.0.24 of alsa-drivers. Aloop compiles and loads fine and seems to
work when used standalone, but once the asoundrc is in place, I get the
error described earlier.
Cheers,
S.M.
10:54 p.m.
----- Original Message -----
From: S. Massy <lists(a)wolfdream.ca>
To: James Warden <warjamy(a)yahoo.com>
Cc: "linux-audio-user(a)lists.linuxaudio.org"
<linux-audio-user(a)lists.linuxaudio.org>
Sent: Wednesday, October 19, 2011 9:34 PM
Subject: Re: [LAU] Alsa to jack bridge and asoundrc
On Wed, Oct 19, 2011 at 04:06:53AM -0700, James Warden wrote:
----- Original Message -----
I compiled the aloop module and it works fine, but when I try setting up
the asoundrc as described, and use the device, I get.
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:654: audio open error: Invalid argument
Does anyone know what this uninformative error mean? Has anybody ever
had luck with a similar setup?
-----
Hi, I use this setup as described in the wiki page (I wrote that page myself ;) and have
no issue.
You should provide the version numbers of libasound and alsa, how they were installed,
etc.
Version mismatch can cause this kind of problems I think.
Well, libasound is a
Debian package from Squeeze and is 1.0.13. The
drivers are from kernel 2.6.33.7.2-rt30, apart from aloop which is from
release 1.0.24 of alsa-drivers. Aloop compiles and loads fine and seems to
work when used standalone, but once the asoundrc is in place, I get the
error described earlier.
Cheers,
S.M.
-----
For the driver version, try
cat /proc/asound/version
For libasound2 stuff:
dpkg -l libasound2
dpkg -l libasound2-plugins
It is probably best when they all match.
J.
PS: I use debian sid.
4787
days inactive
4788
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Fons Adriaensen -
James Warden -
Robin Gareus -
S. Massy