25 Oct
2009
25 Oct
'09
9:02 a.m.
Hi,
I've recently bought an Edirol FA66 firewire sound interface and it
works fine with FFADO 2.0-rc2 on my 64 bit Debian testing box.
However I just can use it with jackd-aware software, whilst all other
programs, first of all web browsers with (Adobe's) flash plugin etc.
etc., continue to play only through my onboard AC97 soundcard via
ALSA.
I've googled searching a solution to route alsa output to jackd,
setting an .asoundrc like in:
http://alsa.opensrc.org/index.php/Jack_(plugin)
or also in:
http://ubuntuforums.org/showthread.php?t=644667
but with no result until now.
Anyone here have perhaps some more hints to get alsa route its output to jackd?
Thanks in advance for answering.
--
toglimi.hamradio(a)toglimi.quipo.it
ANTI-SPAM: please cut "toglimi." for my real e-mail address.
Pentium4 3.00GHz, Linux 2.6.30.8-2-x86_64 on Debian GNU/Linux squeeze/sid
Registered Linux user #291116 http://counter.li.org
25 Oct
25 Oct
12:02 p.m.
2009/10/25 HamRadio <hamradio64(a)gmail.com>
Hi,
I've recently bought an Edirol FA66 firewire sound interface and it
works fine with FFADO 2.0-rc2 on my 64 bit Debian testing box.
However I just can use it with jackd-aware software, whilst all other
programs, first of all web browsers with (Adobe's) flash plugin etc.
etc., continue to play only through my onboard AC97 soundcard via
ALSA.
I've googled searching a solution to route alsa output to jackd,
setting an .asoundrc like in:
http://alsa.opensrc.org/index.php/Jack_(plugin)
or also in:
http://ubuntuforums.org/showthread.php?t=644667
but with no result until now.
Anyone here have perhaps some more hints to get alsa route its output to
jackd?
Thanks in advance for answering.
Could you paste the .asoundrc you have?
For eg., mine is standard because I don't use the plugin when I'm using
external interface:
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
}
capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
ctl.mixer0 {
type hw
card 0
}
And also ensure that the plugin exists:
~$ locate libasound_module_pcm_jack.so
7:51 p.m.
On Sun, Oct 25, 2009 at 10:54 PM, Jonathan E. Brickman
<jeb(a)joshuacorps.org>wrote;wrote:
Greetings, HamRadio.
Hi! Another hint:
In Linux Mint 7 / ubuntu jaunty, I compiled (configure and make only) the
alsa-plugins that I got from the alsa project page.
(First I installed libasound2-dev from the ubuntu repos).
Then I copied these two files (the .so alone was not enough) to
/usr/lib/alsa-lib:
.../jack/libasound_module_pcm_jack.la
.../jack/.libs/libasound_module_pcm_jack.so
I created the .asoundrc file with this content:
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
}
It works for me to hear to youtube videos, jamendo and the like.
See
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/84900
Cheers, Pablo
Anyone here have perhaps some more hints to get
alsa route its output to
jackd?
Thanks in advance for answering.
27 Oct
27 Oct
3:55 p.m.
Many thanks to everyone for your valuable suggestions.
My problem was due to missing libasound2-plugins package.
Now alsa output is correctly routed to jack, but the perfect setup
should be having in alsamixer (and equivalent mixers) one control for
feeding one soundcard and another control for feeding the other.
I wonder if this could be achieved...
5:40 p.m.
Pablo Fernandez <pablo.fbus(a)gmail.com> writes:
Anyone here have perhaps some more hints to get alsa
route its output
to jackd?
Yes, you use pulseaudio, which can exit through JACK. The ALSA JACK
plugin has a very bad reputation and has never really worked great.
Pulseaudio will then show up as a JACK client so all your ALSA apps will
transmit to pulseaudio, which then exits in JACK land.
--
Esben Stien is b0ef@e s a
http://www. s t n m
irc://irc. b - i . e/%23contact
sip:b0ef@ e e
jid:b0ef@ n n
11:29 p.m.
New subject: ALSA to pulseaudio
On Tue, Oct 27, 2009 at 7:15 PM, Jonathan E. Brickman
<jeb(a)joshuacorps.org> wrote:
Well, it is clear that I have to do something
different than pure
Jack/ALSA. I'll try Pulse, although Pulse's reputation for low latency
isn't exactly stellar.
the ALSA jack plugin has poor latency too. anything that has to
intermediate between a "push" model API (where the app gets to decide
when and how much data to read/write) and a "pull" mode (where
something other than the app makes those decisions) has to have enough
buffering to deal with the app's intentional and unintentional
behaviour. it probably isn't as latency inducing as pulse's default,
but its not a replacement for using JACK directly.
What should my asound.conf (.asoundrc) look like, to
route all ALSA apps' output through Pulse?
if you distro didn't set this up and you want it to work, i suggest
you switch distros to one that does. you may get advice from this or
other lists about how to do this, but configuring PulseAudio to be the
default audio I/O system is a challenge most for distro packagers, not
users. if you then add in the fact that you actually want pulse to
talk to JACK ... now you're out of even distro packaging territory.
what you are trying to do is just not recommended practice. JACK
targets pro-audio/music creation workflows. it is not intended to be a
desktop sound server.
28 Oct
28 Oct
2:26 p.m.
New subject: ALSA to pulseaudio
On Tue, Oct 27, 2009 at 10:29:10PM -0400, Paul Davis wrote:
On Tue, Oct 27, 2009 at 7:15 PM, Jonathan E. Brickman
<jeb(a)joshuacorps.org> wrote:
If ALSA gets its part right, the resulting latency will
just depend on how the app uses the ALSA interface, as it
does for a normal ALSA device. If the app does so in the
same way as e.g. Jack's backend, there should not be any
additional latency at all.
If ALSA can make a low-latency interface on top of an
interrupt routine or thread that runs every period and
is triggered by the soundcard, then (as a Jack client)
it should be able to provide the same low-latency
interface on top of the process callback which just
looks like a soundcard interrupt handler in user space.
There is no essential difference between the two.
Ciao,
--
FA
Well, it is clear that I have to do something
different than pure
Jack/ALSA. I'll try Pulse, although Pulse's reputation for low latency
isn't exactly stellar.
the ALSA jack plugin has poor latency too. anything that has to
intermediate between a "push" model API (where the app gets to decide
when and how much data to read/write) and a "pull" mode (where
something other than the app makes those decisions) has to have enough
buffering to deal with the app's intentional and unintentional
behaviour. it probably isn't as latency inducing as pulse's default,
but its not a replacement for using JACK directly.
7:19 p.m.
New subject: ALSA to pulseaudio
"Jonathan E. Brickman" <jeb(a)joshuacorps.org> writes:
What should my asound.conf (.asoundrc) look like, to
route all ALSA
apps' output through Pulse?
This is like the first line in the pulseaudio documentation.
http://www.pulseaudio.org/wiki/PerfectSetup#ALSAApplications
--
Esben Stien is b0ef@e s a
http://www. s t n m
irc://irc. b - i . e/%23contact
sip:b0ef@ e e
jid:b0ef@ n n
5553
days inactive
5556
days old
linux-audio-user@lists.linuxaudio.org
11 comments
7 participants
participants (7)
-
Esben Stien -
fons＠kokkinizita.net -
HamRadio -
Jonathan E. Brickman -
Pablo Fernandez -
Paul Davis -
Ray Rashif