17 Jan
2013
17 Jan
'13
11:46 p.m.
Hi
I've chosen the option 3 (route PulseAudio to JACK while JACK is
running) of this guide:
http://jackaudio.org/pulseaudio_and_jack
BTW, http://trac.jackaudio.org/ is down since yesterday.
It used to work fine in the past but I'm having an issue just after
using Stretchplayer (and therefore jack).
I'm on Debian testing (Gnome 3.4.2). I can't see anymore the audio
applet. In Settings»Audio I see that there's no output device.
The applications that are trying to use Pulseaudio are listed but of
course no sound is produced.
jackd is not running.
pulseaudio-module-jack is installed and my ~/.pulse/default.pa contains
the following lines:
load-module module-native-protocol-unix
load-module module-jack-sink channels=2
load-module module-jack-source channels=2
load-module module-null-sink
load-module module-stream-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-suspend-on-idle
set-default-sink jack_out
set-default-source jack_in
How can I debug this problem?
Thanks in advance
--
Federico
18 Jan
18 Jan
midnight
On Fri, January 18, 2013 10:47 am, Federico Bruni wrote:
Hi
I've chosen the option 3 (route PulseAudio to JACK while JACK is
running) of this guide:
http://jackaudio.org/pulseaudio_and_jack
BTW, http://trac.jackaudio.org/ is down since yesterday.
It used to work fine in the past but I'm having an issue just after
using Stretchplayer (and therefore jack).
I'm on Debian testing (Gnome 3.4.2). I can't see anymore the audio
applet. In Settings»Audio I see that there's no output device.
The applications that are trying to use Pulseaudio are listed but of
course no sound is produced.
jackd is not running.
pulseaudio-module-jack is installed and my ~/.pulse/default.pa contains
the following lines:
load-module module-native-protocol-unix
load-module module-jack-sink channels=2
load-module module-jack-source channels=2
load-module module-null-sink
load-module module-stream-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-suspend-on-idle
set-default-sink jack_out
set-default-source jack_in
How can I debug this problem?
Thanks in advance
There is a bug in Pulseaudio that is stopping pa from releasing the audio
device.
The temporary solution until it is fixed and released is to disable
autospawn and restart pa.
edit ~/.pulse/client.conf
add
autospawn = no
restart pulse with
pulseaudio -k
pulseaudio -D
or maybe with
pasuspender -- jackd
If that fails you may need to completely kill pulse or just restart the
machine to get it to release the audio device. Once you have disabled
autospawn it should only need to be done once and only if you have already
been using pulse to listen to a some audio.
--
Patrick Shirkey
Boost Hardware Ltd
6:23 a.m.
On 01/18/2013 01:00 AM, Patrick Shirkey wrote:
On Fri, January 18, 2013 10:47 am, Federico Bruni wrote:
We have noticed a problem with audio reservation in Fedora. Ian has has
some success with this patch (as have I) but I'm at a loss to understand
why, it just seems to work...
http://lists.freedesktop.org/archives/pulseaudio-discuss/2013-January/01585…
Hi
I've chosen the option 3 (route PulseAudio to JACK while JACK is
running) of this guide:
http://jackaudio.org/pulseaudio_and_jack
BTW, http://trac.jackaudio.org/ is down since yesterday.
It used to work fine in the past but I'm having an issue just after
using Stretchplayer (and therefore jack).
I'm on Debian testing (Gnome 3.4.2). I can't see anymore the audio
applet. In Settings»Audio I see that there's no output device.
The applications that are trying to use Pulseaudio are listed but of
course no sound is produced.
jackd is not running.
pulseaudio-module-jack is installed and my ~/.pulse/default.pa contains
the following lines:
load-module module-native-protocol-unix
load-module module-jack-sink channels=2
load-module module-jack-source channels=2
load-module module-null-sink
load-module module-stream-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-suspend-on-idle
set-default-sink jack_out
set-default-source jack_in
How can I debug this problem?
Thanks in advance
There is a bug in Pulseaudio that is stopping pa from releasing the audio
device.
The temporary solution until it is fixed and released is to disable
autospawn and restart pa.
edit ~/.pulse/client.conf
add
autospawn = no
restart pulse with
pulseaudio -k
pulseaudio -D
or maybe with
pasuspender -- jackd
If that fails you may need to completely kill pulse or just restart the
machine to get it to release the audio device. Once you have disabled
autospawn it should only need to be done once and only if you have already
been using pulse to listen to a some audio.
6:26 a.m.
On 01/18/2013 07:23 AM, Brendan Jones wrote:
On 01/18/2013 01:00 AM, Patrick Shirkey wrote:
This is another patch that fixes a similar problem:
http://lists.freedesktop.org/archives/pulseaudio-discuss/2013-January/01589…
On Fri, January 18, 2013 10:47 am, Federico Bruni wrote:
We have noticed a problem with audio reservation in Fedora. Ian has has
some success with this patch (as have I) but I'm at a loss to understand
why, it just seems to work...
http://lists.freedesktop.org/archives/pulseaudio-discuss/2013-January/01585…
Hi
I've chosen the option 3 (route PulseAudio to JACK while JACK is
running) of this guide:
http://jackaudio.org/pulseaudio_and_jack
BTW, http://trac.jackaudio.org/ is down since yesterday.
It used to work fine in the past but I'm having an issue just after
using Stretchplayer (and therefore jack).
I'm on Debian testing (Gnome 3.4.2). I can't see anymore the audio
applet. In Settings»Audio I see that there's no output device.
The applications that are trying to use Pulseaudio are listed but of
course no sound is produced.
jackd is not running.
pulseaudio-module-jack is installed and my ~/.pulse/default.pa contains
the following lines:
load-module module-native-protocol-unix
load-module module-jack-sink channels=2
load-module module-jack-source channels=2
load-module module-null-sink
load-module module-stream-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-suspend-on-idle
set-default-sink jack_out
set-default-source jack_in
How can I debug this problem?
Thanks in advance
There is a bug in Pulseaudio that is stopping pa from releasing the audio
device.
The temporary solution until it is fixed and released is to disable
autospawn and restart pa.
edit ~/.pulse/client.conf
add
autospawn = no
restart pulse with
pulseaudio -k
pulseaudio -D
or maybe with
pasuspender -- jackd
If that fails you may need to completely kill pulse or just restart the
machine to get it to release the audio device. Once you have disabled
autospawn it should only need to be done once and only if you have
already
been using pulse to listen to a some audio.
2:21 p.m.
On Thu, January 17, 2013 10:26 pm, Brendan Jones wrote:
On 01/18/2013 07:23 AM, Brendan Jones wrote:
> On 01/18/2013 01:00 AM, Patrick Shirkey wrote:
>>
>> On Fri, January 18, 2013 10:47 am, Federico Bruni wrote:
>>> load-module module-jack-sink channels=2
>>> load-module module-jack-source channels=2
The bug mentioned below is not consistent with the configuration shown
above though. The above configuration would normally be used with jackd
and not jackdbus.
>> There is a bug in Pulseaudio that is stopping
pa from releasing the
>> audio
>> device.
>> autospawn = no
>>
>>
>> restart pulse with
>>
>> pulseaudio -k
>> pulseaudio -D
>>
>> or maybe with
>>
>> pasuspender -- jackd
Or add:
pasuspender sleep 1 &
to qjackctl as the "Execute script on Startup"
You would probably have to log out and in to make sure both jackdbus and
pulseaudio are restarted... though it can be done manually too.
> We have noticed a problem with audio reservation
in Fedora. Ian has has
> some success with this patch (as have I) but I'm at a loss to understand
> why, it just seems to work...
I am told the bug is that pulse releases the device with one hand and then
noticed the device is free with the other and so picks it up again. There
is a fix in, but I don't know how long it will take before it shows up in
release.
--
Len Ovens
www.OvenWerks.net
12:53 p.m.
On Fri, 18 Jan 2013 07:23:17 +0100, Brendan Jones
<brendan.jones.it(a)gmail.com> wrote:
On 01/18/2013 01:00 AM, Patrick Shirkey wrote:
This has got nearly the quality of a conspiracy :D. I know people who are
banned on at least one list, a long time ago, when they were writing about
issues with pulseaudio and systemd. People who serious reported bugs were
abused with "Ponyland" mockery of the main coder. ALSA was blamed, when
pulseaudio didn't work. And no, I'm not banned, I'm not affected, since I
neither use pulseaudio nor systemd. It now emerges that those so called
trolls were right? They were no trolls? Pulseaudio still isn't working,
but mailing lists again get spammed with mails about pulseaudio? This is a
running gag. How about removing pulseaudio? It's good for nothing! Jack
and ALSA are working very good without pulseaudio. Strange that stable
distro releases have it as a hard dependency. Is pulseaudio really
important again on jack devel and Linux audio lists? When will this ever
stop? Beta software for the basic parts of the OS simply shouldn't be used
for stable environments.
Regards,
Ralf
On Fri, January 18, 2013 10:47 am, Federico Bruni wrote:
We have noticed a problem with audio reservation in Fedora. Ian has has
some success with this patch (as have I) but I'm at a loss to understand
why, it just seems to work...
http://lists.freedesktop.org/archives/pulseaudio-discuss/2013-January/01585… Hi
I've chosen the option 3 (route PulseAudio to JACK while JACK is
running) of this guide:
http://jackaudio.org/pulseaudio_and_jack
BTW, http://trac.jackaudio.org/ is down since yesterday.
It used to work fine in the past but I'm having an issue just after
using Stretchplayer (and therefore jack).
I'm on Debian testing (Gnome 3.4.2). I can't see anymore the audio
applet. In Settings»Audio I see that there's no output device.
The applications that are trying to use Pulseaudio are listed but of
course no sound is produced.
jackd is not running.
pulseaudio-module-jack is installed and my ~/.pulse/default.pa contains
the following lines:
load-module module-native-protocol-unix
load-module module-jack-sink channels=2
load-module module-jack-source channels=2
load-module module-null-sink
load-module module-stream-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-suspend-on-idle
set-default-sink jack_out
set-default-source jack_in
How can I debug this problem?
Thanks in advance
There is a bug in Pulseaudio that is stopping pa from releasing the
audio
device.
The temporary solution until it is fixed and released is to disable
autospawn and restart pa.
edit ~/.pulse/client.conf
add
autospawn = no
restart pulse with
pulseaudio -k
pulseaudio -D
or maybe with
pasuspender -- jackd
If that fails you may need to completely kill pulse or just restart the
machine to get it to release the audio device. Once you have disabled
autospawn it should only need to be done once and only if you have
already
been using pulse to listen to a some audio.
2:30 p.m.
On Fri, January 18, 2013 3:18 am, Ralf Mardorf wrote:
I'm not affected, since I
neither use pulseaudio nor systemd.
Yet you are an expert on all things about them both, I am amazed :)
This is a
running gag. How about removing pulseaudio? It's good for nothing!
Good for nothing that you do. There are some people who need it and need
to be able to connect it to jack. There are certainly people who are
better of with no pulse.
Jack
and ALSA are working very good without pulseaudio.
To say Jack and alsa have no bugs is not really correct either. Is it
software? it has bugs.
Strange that stable
distro releases have it as a hard dependency. Is pulseaudio really
important again on jack devel and Linux audio lists? When will this ever
stop? Beta software for the basic parts of the OS simply shouldn't be used
for stable environments.
I see announcements for alpha software on here often, whats the problem?
--
Len Ovens
www.OvenWerks.net
2:54 p.m.
On Fri, 18 Jan 2013 15:30:18 +0100, Len Ovens <len(a)ovenwerks.net> wrote:
If it's good for people they should use it. Why are the pulseaudio users
whining if it's good for them?
I didn't claim that there are no bugs, I suffer from several bugs myself,
but ALSA and JACK are anyway good, they are very good. They don't cause
such issues as pulseaudio does, arts or any other sound server never did
cause such much issues as pulseaudio does. Pulseaudio is the only hard
dependency of them, ALSA, JACK, ARTS etc. are/were optional.
An alpha, beta ... sequencer or what ever isn't needed for basics of the
OS. If Qtractor shouldn't work it's ok, if audio is broken regarding to a
buggy hard dependency it's something completely different.
Regards,
Ralf
--
FreeBSD 9.1-RELEASE amd64
On Fri, January 18, 2013 3:18 am, Ralf Mardorf wrote:
No and I don't have anything against systemd, when it's automatically
installed and set up by a distro.
Regarding to pulseaudio I'm also not an expert, I only know many people
who tested Linux and then decided to use Windows, because of pulseaudio
issues.
I'm not affected, since I
neither use pulseaudio nor systemd.
Yet you are an expert on all things about them both, I am amazed :) This is a
running gag. How about removing pulseaudio? It's good for nothing!
Good for nothing that you do. There are some people who need it and need
to be able to connect it to jack. There are certainly people who are
better of with no pulse. Jack
and ALSA are working very good without pulseaudio.
To say Jack and alsa have no bugs is not really correct either. Is it
software? it has bugs. Strange that
stable
distro releases have it as a hard dependency. Is pulseaudio really
important again on jack devel and Linux audio lists? When will this ever
stop? Beta software for the basic parts of the OS simply shouldn't be
used
for stable environments.
I see announcements for alpha software on here often, whats the problem?
20 Jan
20 Jan
2:02 p.m.
Il 18/01/2013 01:00, Patrick Shirkey ha scritto:
There is a bug in Pulseaudio that is stopping pa from
releasing the audio
device.
The temporary solution until it is fixed and released is to disable
autospawn and restart pa.
edit ~/.pulse/client.conf
add
autospawn = no
This solved the issue temporarily, but then PulseAudio stopped working
because it couldn't find the device anymore.
I guess it's because of ~/.pulse/client.conf. Can it contain just that
line? Or should I copy the file from /etc/pulse and then edit it?
I'd prefere being able to include /etc/pulse/client.conf e then add the
line. Or maybe change /etc/pulse/client.conf, hoping that in case of
update I'll be warned about the new config file (as it happens with
other debian packages).
My concern is: I don't want my ~/.pulse/client.conf to be out-of-date
wrt the pulseaudio package.
Finally, I've reset my configuration (only ~/.pulse/default.pa) and
couldn't reproduce the error.
Doing more testing...
--
Federico
2:51 p.m.
Il 20/01/2013 15:03, Federico Bruni ha scritto:
Finally, I've reset my configuration (only
~/.pulse/default.pa) and
couldn't reproduce the error.
Doing more testing...
Ok, I could reproduce the error.
In Qjack I have a default profile and a firewire profile. As long as I
use the alsa profile, applications using jack and applications using
PulseAudio work fine together.
The I tried to switch to firewire.
I first noticed that jack was not able to do the switch and kept running
with alsa (respawn?):
$ ps ax | grep jack
12154 ? S<Lsl 3:33 /usr/bin/jackd -T -ndefault -dalsa -dhw:0
-r48000 -p128 -n3
I had to kill the process and start (q)jack again.
Then I stopped jack and tried VLC: no sound. No output device in the
Audio settings. In this case jack is not respawned:
$ ps ax | grep jack
12917 ? S 0:00 /bin/sh /usr/bin/qjackctl
12925 ? S 0:09 /usr/lib/qjackctl/qjackctl.real
13430 pts/3 S+ 0:00 grep jack
Are you sure it's a bug in PulseAudio?
Or rather a wrong configuration?
--
Federico
3:45 p.m.
Il 20/01/2013 15:03, Federico Bruni ha scritto:
This solved the issue temporarily, but then PulseAudio
stopped working
because it couldn't find the device anymore.
Well, I reproduced this error too.
Actually, PulseAudio doesn't start up when I start the machine (I had to
force the shutdown because of a freeze).
In ~/.xsession-errors I find:
E: [pulseaudio] main.c: Daemon startup failed.
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127:
RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)
jack and pulse are not running:
$ ps ax | grep jack
5937 pts/0 S+ 0:00 grep jack
$ ps ax | grep pulse
5940 pts/0 R+ 0:00 grep pulse
I can't start pulseaudio manually:
$ pulseaudio -D
E: [pulseaudio] main.c: Daemon startup failed.
$ pulseaudio --start
E: [pulseaudio] main.c: Daemon startup failed.
--
Federico
4:52 p.m.
Il 20/01/2013 16:46, Federico Bruni ha scritto:
I can't start pulseaudio manually:
$ pulseaudio -D
E: [pulseaudio] main.c: Daemon startup failed.
$ pulseaudio --start
E: [pulseaudio] main.c: Daemon startup failed.
This is due to ~/.pulse/default.pa (which contains the lines which make
PulseAudio work with Jack).
mv .pulse/default.pa .pulse/default.pa.bak
Then I could launch pulseaudio.
Curiously, it seems that PulseAudio not running was also responsible for
strange weird behaviour of other applications: very slow path completion
in the terminal and very slow opening of menus in Thunderbird.
Has anyone experienced the same?
--
Federico
18 Jan
18 Jan
12:19 a.m.
On Thu, January 17, 2013 3:47 pm, Federico Bruni wrote:
Hi
I've chosen the option 3 (route PulseAudio to JACK while JACK is
running) of this guide:
http://jackaudio.org/pulseaudio_and_jack
BTW, http://trac.jackaudio.org/ is down since yesterday.
Ja, I noticed that too. I was looking for some info on netjack.
It used to work fine in the past but I'm having an issue just after
using Stretchplayer (and therefore jack).
I'm on Debian testing (Gnome 3.4.2). I can't see anymore the audio
applet. In Settings»Audio I see that there's no output device.
The applications that are trying to use Pulseaudio are listed but of
course no sound is produced.
jackd is not running.
pulseaudio-module-jack is installed and my ~/.pulse/default.pa contains
the following lines:
load-module module-native-protocol-unix
load-module module-jack-sink channels=2
load-module module-jack-source channels=2
load-module module-null-sink
load-module module-stream-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-suspend-on-idle
set-default-sink jack_out
set-default-source jack_in
How can I debug this problem?
Thanks in advance
There are some interesting things with PA (Pulseaudio). If PA starts while
a device is busy with another application (like jackd) that device will
not be available to pulse even after Jackd is stopped and the device is
available. pulseaudio -k will make it rescan the devices... well actually
it kills PA and when PA restarts (normally runs respawn) it rescans.
It would seem you are using jackd and not jackdbus then?
module-jackdbus-detect would normally start module-jack-sink/source when
it detects jack is present and stop them when jackdbus stops. (I am not
suggesting you run that way unless you want to run dbus) qjackctl can be
set to run dbus or not, I would check to see if it is checked or not. For
how you have things set up it should not be checked.
If you do want to use module-jackdbus-detect... I would wait for wait for
the bug fix :) (though there is a work around)
--
Len Ovens
www.OvenWerks.net
4433
days inactive
4436
days old
linux-audio-user@lists.linuxaudio.org
12 comments
5 participants
participants (5)
-
Brendan Jones -
Federico Bruni -
Len Ovens -
Patrick Shirkey -
Ralf Mardorf