2 Aug
2012
2 Aug
'12
11:18 a.m.
hi all,
i have an alsa-only application i would like to integrate into my
jack-based setup. i found this page on the jack website, which
suggests ways to do this:
http://jackaudio.org/routing_alsa
but the page the first method links to
(http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge)
no longer exists.
does anyone here have a link or an idea how to do this?
the second method is easier, but doesn't sound too reliable.
thanks,
--
robin
http://fu.ac.nz - Auckland's Free University
2 Aug
2 Aug
11:27 a.m.
On Thu, 2 Aug 2012 17:09:51 +1200
Robin Paulson <robin.paulson(a)gmail.com> wrote:
hi all,
i have an alsa-only application i would like to integrate into my
jack-based setup.
Hi, this works fine for me:
https://wiki.archlinux.org/index.php/JACK#Playing_nice_with_ALSA
renato
12:49 p.m.
New subject: routing alsa to jack - what about Skype
On Thu, Aug 02, 2012 at 11:29:21AM +0200, renato wrote:
On Thu, 2 Aug 2012 17:09:51 +1200
Robin Paulson <robin.paulson(a)gmail.com> wrote:
Okay, but what about skype?
First of all, under Debian I needed to install
libasound2-plugins.
With this in place, running jackd and a JACKified .asoundrc
audio Adobe Flash videos under Firefox gets to the audio
hardware.
Having installed alsa-oss, the following produces sound:
aoss bplay somefile.wav
However invoking
skype
does not locate the audio device, and
aoss skype
emits an error message:
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libaoss.so'
from LD_PRELOAD cannot be preloaded: ignored.
This problem remains after replacing the previous 32-bit
client by a new 64-bit client.
FWIW, I found this snippet in ~/.Skype/shared.xml
<VoiceEng>
<AudioLib>1</AudioLib>
<MicBoost>
<_1>-1</_1>
<Default.20device.20.28default.29>0</Default.20device.20.28default.29>
</MicBoost>
<MicVolume>
<_1>100</_1>
<Default.20device.20.28default.29>20</Default.20device.20.28default.29>
</MicVolume>
</VoiceEng>
Any tips would be welcome.
Joel
hi all,
i have an alsa-only application i would like to integrate into my
jack-based setup.
Hi, this works fine for me: renato
--
Joel Roth
3 Aug
3 Aug
1:34 a.m.
On 2 August 2012 21:29, renato <rennabh(a)gmail.com> wrote:
is it persistent when the audio stops? the current method i am using
is not, when the application stops making noise it gets disconnected
from jack, which is rather annoying
--
robin
http://fu.ac.nz - Auckland's Free University
2 Aug
2 Aug
5:36 p.m.
On Thu, Aug 02, 2012 at 05:09:51PM +1200, Robin Paulson wrote:
hi all,
i have an alsa-only application i would like to integrate into my
jack-based setup. i found this page on the jack website, which
suggests ways to do this:
http://jackaudio.org/routing_alsa
but the page the first method links to
(http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge)
no longer exists.
does anyone here have a link or an idea how to do this?
the second method is easier, but doesn't sound too reliable.
There is also a
third method now, thanks to Fons Adriaensen: I haven't
given it a try yet, but my understanding is that it aims to address the
lack of persistence when using the jack alsa plugin. You can get it
here:
http://kokkinizita.linuxaudio.org/linuxaudio/downloads
hth
Cheers,
S.M.
10:23 p.m.
On Thu, Aug 02, 2012 at 11:36:08AM -0400, S. Massy wrote:
There is also a third method now, thanks to Fons
Adriaensen: I haven't
given it a try yet, but my understanding is that it aims to address the
lack of persistence when using the jack alsa plugin. You can get it
here:
http://kokkinizita.linuxaudio.org/linuxaudio/downloads
This is not 'a third method'. The zita-a2j and zita-j2a
apps are replacements for the alsa-in and alsa-out clients
that come with jack. They can be used in the same way as
those, e.g. together with the ALSA loop device. The main
difference is that they do not degrade audio quality.
Note that you only need the ALSA loop device when the
app you want to connect is one of those crippled ones
that only accept 'soundcards' as an ALSA device. If not
all you need to connect an ALSA app to Jack is ALSA's
jack plugin.
Ciao.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
3 Aug
3 Aug
1 a.m.
On 3 August 2012 08:23, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Thu, Aug 02, 2012 at 11:36:08AM -0400, S. Massy
wrote:
This is not 'a third method'. The zita-a2j and zita-j2a
apps are replacements for the alsa-in and alsa-out clients
that come with jack. They can be used in the same way as
those, e.g. together with the ALSA loop device. The main
difference is that they do not degrade audio quality.
Note that you only need the ALSA loop device when the
app you want to connect is one of those crippled ones
that only accept 'soundcards' as an ALSA device. If not
all you need to connect an ALSA app to Jack is ALSA's
jack plugin.
the problem is, as far as i can tell, the alsa_in and alsa_out devices
are not persistent. i.e. as soon as audio stops, the connection to
jack breaks. so, the user needs to re-start the audio, then re-connect
in patchage/whatever. but i might be wrong
--
robin
http://fu.ac.nz - Auckland's Free University
4530
days inactive
4530
days old
linux-audio-user@lists.linuxaudio.org
6 comments
5 participants
participants (5)
-
Fons Adriaensen -
Joel Roth -
renato -
Robin Paulson -
S. Massy