16 May
2009
16 May
'09
10:59 a.m.
Esben Stien wrote:
Pulseaudio addresses so many of the issues we have.
Perhaps. It's also worth noting that it creates a whole new bag of
irritations too.
It works absolutely perfectly with JACK and I
don't understand that so
many people are frustrated with it.
You're a lucky guy. Pulseaudio most definitely does not work well with
JACK here. My experience with it has been so dismal that the first thing
I do in any Ubuntu system is to disable Pulseaudio (along with a raft of
other stuff).
On a stock Ubuntu Studio 9.04 JACK will not launch until Pulseaudio has
been disabled. This is major pain, because Ubuntu (GNOME?) has coupled
its desktop to the server. I can't safely remove Pulseaudio, but I can
disable it according to a set of instructions I found with a Google
search. After that everything is smooth sailing.
Btw, 'killall pulseaudio' doesn't work. The server is set up for
persistence, so the daemon simply relaunches itself, staying in the way
of a successful JACK start.
No application EVER should use ALSA or OSS directly.
Please enlighten me why. It seems all these reports are based on not
really knowing what pulseaudio is. Most people don't find the mixer,
to my understanding;), which is a distro issue.
On my notebook Pulseaudio recognizes a master output and a PCM channel.
It doesn't see the Mic/Line inputs at all, they only show up after I
disable Pulseaudio and establish ALSA as my primary sound manager.
JACK is the answer to professional needs, but it
severely lacks many
of the features that pulseaudio possesses, for non professional use.
My needs are professional, ergo I do not need or want Pulseaudio. More
to the point, I don't want it to be a major pain to move out of my way.
I realize that that's not actually a Pulseaudio problem, it's the
distro's fault. Alas, Pulseaudio will end up taking the heat from users
facing a similar dilemma.
Best,
dp