28 Oct
2012
28 Oct
'12
8:02 p.m.
Hi!
Please forgive me for my bad english.
I'm looking for a solid Linux distro which, once installed, Jack and
Pulseaudio will be working together in a transparent way. This is because
we have many audio applications, some using Pulseaudio, some using Jack
(example: Chromium playing Youtube videos, Audacity, Rivendell, Totem,
etc.), and they must work simultaneously.
Right now, I'm using Ubuntu 11.04 with lowlatency kernel. Qjackctl is
automatically started after log in; we use pulseaudio-module-jack to route
the Pulseaudio applications to the Jack sound server. But sometimes Jack is
stopped accidentally by the user, or Jackd stop itself when the CPU is at
100%, and the users don't know with the computer has no audio.
This configuration is very fragile. I'm looking for a way to configure Jack
and Pulseaudio, so they run when the computer starts, a normal user can't
stop them, and they can be robust enough to resist the normal use.
KXStudio 12.04 is an excellent and very robust distro, Jack and Pulseaudio
works transparently, but my users are used to the Gnome 2 interface.
Thanks you for your advices!
28 Oct
28 Oct
8:11 p.m.
For what usage do you need pulseaudio?
It might work for you OOTB using Ubuntu Studio Precise LTS or Quantal.
On my machine pulseaudio always failed, IOW it doesn't work for Precise
and Quantal too.
Even if you like PA, you should reconsider to disable it for serious
audio work.
9:27 p.m.
On Mon, October 29, 2012 7:11 am, Ralf Mardorf wrote:
Ralf, this advice is out of date.
On any distro you can install the jack-sink modules and PA will gracefully
reconnect to jack when jack is started.
Otherwise you can run "pulseaudio -k" from the commandline to temporarily
disable pulseaudio when you are running jack. In qjackctl this can be
added as a preliminary startup command in the preferences section.
--
Patrick Shirkey
Boost Hardware Ltd
28 Oct
28 Oct
8:18 p.m.
Jack & PA work together fine under UbuntuStudio 12.04, using the jack
plugin for PA. You can use Gnome or any other interface for it (I use
xfce myself), they are independent of whatever desktop environment you
use. Nothing is going to stop a user from killing either Jack or PA,
though, as these are not typically run as root for a user session.
On Sun, Oct 28, 2012 at 4:02 PM, Luigino Bracci <lbracci(a)gmail.com> wrote:
--
Brett W. McCoy -- http://www.brettwmccoy.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world."
-- Jelaleddin Rumi
8:42 p.m.
On Sun, October 28, 2012 1:18 pm, Brett McCoy wrote:
No they are not run as root normally. Pulse can be but I am not sure about
jack... or rather I am not sure what problems would be encountered.
Running pulse as system is not recommended unless more than one user may
be logged in at once that will both need sound (two x-sessions) because
there is a loss of useability (some features go away).
There are some things that could happen to pulse that would make it work a
lot better with Jack... when pulse finds out jack is taking away one of
it's hardware ports, it would be really nice if pulse transferred all it's
settings for that port to the jack sink/source ports. Such as if it is
default (very big that one), number of channels, levels, and even name.
Even better if there is a stream using that port it should transfer to the
jacksink as well. If these things were implemented starting and stopping
jack would be a non-event as far as the pulse user was concerned... or at
worst only a short pause in sound.
--
Len Ovens
www.OvenWerks.net
9:19 p.m.
On Sun, October 28, 2012 1:50 pm, Paul Davis wrote:
Ya, but if I loose a port and also get a jack-sink that says a lot too.
Pulse should be able when it detects jack-sink/source be looking for what
port is configured that it no longer has access to.
On the other hand, I would be happy if the jackbridge could be set as
default whenever it shows up and if the module that detects jack would at
least pass parameters to the two modules (source/sink) such as number of
channels and naming. If Pulse finds a port blocked that it is sending a
stream to, it could look for the new default and switch the stream there.
I wish my coding skills were at a place I could patch it.
--
Len Ovens
www.OvenWerks.net
8:28 p.m.
On Sun, October 28, 2012 1:02 pm, Luigino Bracci wrote:
My first question would be: Do you need jack? If you are doing mostly
pulse stuff (or all) then you will get better use of just pulse. If you
must have jack for your sound IF to work (fire wire for example) then I
would suggest a script when the user logs in that starts jack.
Note: I have an interest in what the workflow(s) are that you are doing
that requires this configuration, because I help with Ubuntustudio and
would like it to handle as many things as it can right out of the box. Or
with minimal setup anyway.
KXStudio 12.04 is an excellent and very robust distro,
Jack and Pulseaudio
works transparently, but my users are used to the Gnome 2 interface.
Gnome 2 is dead (well at least no longer supported) so the next best thing
would be xfce. (which is what ubuntustudio uses these days) It should not
be too hard to install Kxstudio and add xfce either directly or by
installing installing xubuntu-desktop (I think) or ubuntustudio-desktop.
Then at login (in lightdm) select the xfce session. I am not sure which DE
Kxstudio uses, but if they are using gnome3 you may be able to just
install xfce-panel and mess with what gnome starts at the beginning of
session... but that would be for advanced users :)
--
Len Ovens
www.OvenWerks.net
4542
days inactive
4543
days old
linux-audio-user@lists.linuxaudio.org
9 comments
6 participants
participants (6)
-
Brett McCoy -
Len Ovens -
Luigino Bracci -
Patrick Shirkey -
Paul Davis -
Ralf Mardorf