I can confirm that this continues to happen even when using the
1:0.9.22-0ubuntu1 version from the
http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu channel.
Any further ideas?
b.
signature.asc
Description: OpenPGP digital signature
___
It seems inevitable that my pulse audio server
(0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 on Ubuntu Maverick)
will start sounding crackly and stuttery when an application wants to
send notification type sounds.
When this happens, about the only useful thing I see in the -vvv
output is:
D:
On 11-04-12 12:00 PM, Sean McNamara wrote:
Hi,
Hi,
Can you give an example of what application(s) in particular trigger
this?
Skype for example, when somebody sends an IM, or logs on. Skype pops up
a notification and emits a sound event. Or when I generate a keyboard
sound event, like
On 11-04-12 12:52 PM, Sean McNamara wrote:
I can't tell from your PA logs which soundcard you are using to play
back notifications and rhythmbox sound?
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfe024000 irq 22
Yes, this one.
or
1 [U0x46d0x8c5
Tanu Kaskinen tanuk at iki.fi writes:
I had a look at some point at the peak detection resampler... I think
the peak detection flag that you mentioned earlier doesn't do anything
else than force the resampler of the source output to be the peak
detection resampler.
So it seems that there is
Maarten Bosmans mkbosmans at gmail.com writes:
It looks like you have pavucontrol open on the laptop
Yes, I do.
(twice).
Heh. You are right.
As it
connects to all the sources to display a vumeter, an audio stream from
the desktop to the laptop is necessary.
Ahhh. Of course.
This is
I have a laptop (Ubuntu 10.10) who's sound I would like to go to my workstation
(also Ubuntu 10.10) so on the laptop in paprefs I have selected Make
discoverable PulseAudio network sound devices available locally enabled.
The moment I select that, watching a packet dump (i.e. tcpdump) reveals a
Maarten Bosmans mkbosmans at gmail.com writes:
This alone should not result in a significant amount of packets, only
a couple of mDNS requests.
Indeed, that was my expectation also.
I assume you also loaded module-zeroconf-publish on the other machine.
No, in fact it appears to be
Paul Menzel paulepanter at users.sourceforge.net writes:
You already posted the same question to the list four weeks ago [1].
Yes, it would seem you are correct. That was about a different release of
Ubuntu. I had hoped that third party pieces that I had to gather together at
that time to
Paul Menzel paulepanter at users.sourceforge.net writes:
Did you try to record something or use the microphone?
No.
Maybe it is related to ticket #758 [1] which commit [2][3][4] in ALSA
fixed for me kind of. What CODEC chip do you have in your system?
Is this the answer to that question:
Daniel Chen seven.steps at gmail.com writes:
Considering just the Lucid case, the fix for this symptom was only
committed Tuesday, so I don't think it conceivably could have made it
into Lucid.
Well, I suppose that's fair enough. I had just figured that since the same
procedure fixed the
I was so hoping that the PA on Ubuntu Lucid was going to be much more stable
than previous releases but alas, I don't think it's to be. Currently installed
on a machine here is 0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 which
presumably is some form of 0.9.22.
I have it currently running
306MB of VM seems a bit excessive for a sound daemon, yes?
$ cat /proc/6828/status
Name: pulseaudio
State: S (sleeping)
Tgid: 6828
Pid:6828
PPid: 1
TracerPid: 0
Uid:1001100110011001
Gid:1001100110011001
FDSize: 256
Groups: 4 20 24 25 29 30 44 46 106
First a general question so that I am not totally OT here... :-)
In a situation where you have a single physical seat (i.e. one keyboard and
monitor) but you might have multiple logical seats (i.e. where one user logs
in,
then physically goes away, and a second users logs in on a second X
I have a(one of a number of)Ubuntu Karmic systems here running pulseaudio
0.9.19. On this particular system, PA wants to eat as much CPU as is
available. It will use up near 100% on this system when it's otherwise idle.
This particular machine is the only one of several, as I say, with this
I have a machine that has multiple interfaces and thus multiple addresses. I
have enabled PA (0.9.19) to share the devices out via the network and when I
start the PA server, I briefly see devices from it on my local machines
pavucontrol application but they disappear quite quickly.
For the
Hi,
I have a USB webcam that has a microphone, but of course, no output
capabilities. When PA starts it seems to get stuck trying to open the
PCM device for this thing, but none exists:
I: main.c: This is PulseAudio 0.9.19
D: main.c: Compilation host: i486-pc-linux-gnu
D: main.c: Compilation
On Sat, 2009-12-12 at 21:04 +0100, Michał Sawicz wrote:
ALSA applications feed Pulse, and it's Pulse that decides where will the
stream go.
Which is fine for single audio stream applications, but as OP mentioned,
his app has two different reasons to want audio. One for the telephone
ring
While pulseaudio (0.9.19) seems to remember the volume of every app I
use, it does not seem to remember the volume I set in Volume Control for
a running mplayer.
That is, I start mplayer, open the Volume Control, reduce the volume,
quit mplayer, start it again and it starts again at full.
On Fri, 2009-11-13 at 13:46 +, Colin Guthrie wrote:
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/mplayer/current/SOURCES/mplayer-pulse-initial-volume.patch?view=markup
and
http://lists.mplayerhq.hu/pipermail/mplayer-users/2009-October/077999.html
That was an easy
On Thu, 2009-10-29 at 21:13 +, Colin Guthrie wrote:
This beeb should be marked with media.role=event and thus should be
adjustable via the Sound Events slider in pavucontrol should control
your volume. That said, I'm not 100% certain how metacity produces this
sound, but I suspect
On Fri, 2009-10-30 at 18:43 +0100, Lennart Poettering wrote:
Dude. This is nonsense.
To you maybe.
WMs such as metacity are xinerama-aware and have been about
forever.
Guess I am showing my age because I have to admit that the last time I
tired Xinerama was wy before metacity was
On Fri, 2009-10-30 at 16:36 +0100, Lennart Poettering wrote:
Uh. What distro is this?
Ubuntu's latest: Karmic.
metacity has been supporting libcanberra for
ages. Please ask your distributors to update their packages from time
to time,
2.28.0 would be the latest I'd imagine. Must be in
On Fri, 2009-10-30 at 19:28 -0400, Daniel Chen wrote:
On Fri, Oct 30, 2009 at 7:26 PM, Lennart Poettering
lenn...@poettering.net wrote:
Dunno, maybe the PA backend for libcanberra is not installed? Ubuntu
really should install that by default. It's kinda disappointing if
they don't.
On Sat, 2009-10-31 at 03:27 +0100, Lennart Poettering wrote:
Hmm, how come this wasn't installed? Is your machine a pristine
installation?
If my guess about what you mean by pristine installation is right,
then I'd probably have to answer no. It's grown up through various
Ubuntu releases
On Fri, 2009-10-30 at 23:01 -0400, Daniel Chen wrote:
Do you have ubuntu-desktop installed?
I didn't. I do recall removing that at one time because there was a
dependency it sucked in that I didn't like. I've just re-installed it
(and the 10 dozen extra packages it brought in). Let's see
How could I set the volume (i.e. with pavucontrol) for a short lived
audio stream such as the beep that metacity now delivers, for example
when you echo ^G?
Using PA 0.9.19 now.
Cheers,
b.
signature.asc
Description: This is a digitally signed message part
Disclaimer: I don't really have any skin in this game so you can tell me
I'm stupid or whatever you want, however...
On Mon, 2009-10-26 at 16:05 +0100, Lennart Poettering wrote:
Yepp, and I'd argue the non-xinerama setup is useless.
/me looks over from his primary display (with it's separate
On Wed, 2009-09-23 at 10:22 -0400, Peter Hurley wrote:
The reason PA unloads the BT device module is here:
I: module-bluetooth-device.c: FD error: POLLERR
D: module-bluetooth-device.c: IO thread failed
Ahhh. Yes, couldn't see the trees from the forest.
Your options moving forward:
Hi all.
I have a bluetooth dongle on a machine with PA 0.9.18 (Ubuntu Karmic) on
it and a headset paired successfully. From the PA debug (-) output,
it appears that PA sees the headset but then removes the bluetooth
module, for whatever reason:
I: module.c: Unloading module-bluetooth-device
On Thu, 2009-07-02 at 13:35 +, Dan Chen wrote:
Timothy J Massey tmassey at obscorp.com writes:
Basically, I cannot keep PA up and running under Ubuntu 9.04.
You want to look towards Luke Yelavich's PPA:
https://launchpad.net/~themuso/+archive/ppa
The symptoms stem from Ubuntu issues
So, I have pulseaudio 0.9.15 and bluez 0.41 installed and everything
seems to look good for getting this headset to work with pulse.
pavucontrol sees it. I hear beeps in the headset when I adjust the
volume in the Output Devices tab of pavucontrol. I just can't seem to
hear any audio that I
On Wed, 2009-06-24 at 14:18 -0400, Brian J. Murrell wrote:
opreport error: basic_string::erase
So, this appears to be an oprofile 0.9.3 bug. I have rolled up an
0.9.4 .deb here and installed it and get much better results. Although,
I'm not sure how useful they are:
$ sudo opreport -l /usr
My apologies for responding so tardily here. I somehow missed this
response from Lennart.
On Sun, 2009-06-07 at 01:32 +0200, Lennart Poettering wrote:
Hmm, something causes PA to enter a spinning loop here.
Indeed.
This is not accessible anymore as it seems.
Hrm. I just tried it and it
On Wed, 2009-06-24 at 16:58 +0100, Colin Guthrie wrote:
Although most of the patches should be wrapped up in .30 now IIRC, so
you'll need to look at the history.
So is that to say that if I use a .30 (say, 2.6.30 final) that I should
have all of the patches that Lennart was referring to?
On Sun, 2009-06-07 at 01:32 +0200, Lennart Poettering wrote:
Hmm, could you try to play around with oprofile a bit to find out
where exactly PA starts to spin?
http://pulseaudio.org/wiki/HowToUseOProfile
I tried this. I had to use the --no-vmlinux option:
$ sudo opcontrol --no-vmlinux
Some further information...
When I have started an audio stream that has caused PA's CPU usage to
shoot up, here is what PA is saying while it's CPU hogging, and just
prior to my pausing the stream again to alleviate the CPU usage:
...
D: alsa-sink.c: Requested volume: 0: 63% 1: 63%
D:
On Sat, 2009-05-30 at 19:12 -0400, Brian J. Murrell wrote:
Was any of this helpful? Given that I have disabled tunnelling and the
problem still reproduces, it must be something other than tunnelling,
yes? Any other ideas? What can I do to help track it down?
I've also discovered that once
On Thu, 2009-05-28 at 14:40 -0400, Brian J. Murrell wrote:
Done. pacmd ls is at http://brian.interlinx.bc.ca/pacmd_ls2.txt if you
want to inspect.
I've left it here at 100% of a core in case you want me to do any
further inspection.
Currently pulseaudio is reporting a fair number
On Wed, 2009-05-27 at 21:31 +0200, Lennart Poettering wrote:
Hmm, please try to reproduce this harder. The load limiter only becomes
active when the load produced by PA is very high for a longer time.
As I write this, PA is consuming an entire core:
Cpu0 : 14.9%us, 3.7%sy, 7.4%ni,
As an additional data point...
Another long pause of rhythmbox (i.e. I got up and left the room and
came back an hour later) followed by a resume while PA was in this CPU
consumption and PA is now, no longer consuming gobs of CPU.
I didn't happen to notice how long after the pause that PA
On Wed, 2009-05-27 at 01:10 +0200, Lennart Poettering wrote:
Could you please to the following:
1) Add a system load monitor applet to your panel, so that you can monitor if
your CPU is idle or not.
2) Terminate PA in a terminal:
$ pulseaudio -k
3) In the same terminal start PA with
I have started to see something happening quite reproducibly (as in near
100%) for some strange reason. Nothing here has changed, but this has
started happening.
I have rhythmbox playing. I pause. I resume. I get all kinds of
crackling, then it starts playing, then pulseaudio quits.
Just
On Sun, 2009-05-03 at 11:01 -0400, bzb...@gmail.com wrote:
In addition to tcp port 4713. You also need to open the port assocated
with Zeroconf/Bonjour Multicast DNS in opensuse's firewall configuration.
Why can't people trim?
Two lines of meaningful text vs. 13 lines of digest boilerplate
On Thu, 2009-03-26 at 15:30 -0400, Brian J. Murrell wrote:
I am using 0.9.15~test5-0ubuntu1~ppa2 on Ubuntu Jaunty and something I
have been finding is that when I pause rhythmbox (which terminates the
pulseaudio stream) and then unpause (which starts a stream) the master
output goes up to 100
On Thu, 2009-04-16 at 21:26 +0200, Lennart Poettering wrote:
Heya!
Hi,
So you want to get BT audio working with PA?
I'd be happy just to have BT audio working in any manner at all, but for
over a year it's been a non-starting struggle.
Then please make sure to
run the following minimal
On Fri, 2009-04-17 at 14:37 +0100, Colin Guthrie wrote:
Well you probably would, but come on! Do you honestly expect things to
work all by themselves?
Of course not.
A lot of people put in very hard work to get
things to work, and all you can do is complain about how this hard work
On Fri, 2009-04-17 at 16:12 +0200, Lennart Poettering wrote:
If you plug them in 'dmesg' will tell you.
All dmesg tells me about mine is:
[86520.608481] Bluetooth: Generic Bluetooth USB driver ver 0.3
lsusb says:
Bus 001 Device 015: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth
b.
I am using 0.9.15~test5-0ubuntu1~ppa2 on Ubuntu Jaunty and something I
have been finding is that when I pause rhythmbox (which terminates the
pulseaudio stream) and then unpause (which starts a stream) the master
output goes up to 100%.
b.
signature.asc
Description: This is a digitally signed
I'm trying out 0.9.15-test3 (from the Ubuntu PPA) and have gotten hit
by this:
D: alsa-sink.c: Requested volume: 0: 79% 1: 79%
D: alsa-sink.c: Got hardware volume: 0: 80% 1: 80%
D: alsa-sink.c: Calculated software volume: 0: 100% 1: 100%
I: module-device-restore.c: Storing volume/mute for
On Fri, 06 Mar 2009 01:07:33 +, Colin Guthrie wrote:
If you can get a backtrace for that it would be helpful.
I will see what I can do. That said, it's quite easy to reproduce. I
reproduce it by playing a stream in rhythmbox and then opening the volume
control applet and then just
On Sun, 22 Feb 2009 17:44:14 +0100, Lennart Poettering wrote:
I have added a a few paragraphs to the end of
http://pulseaudio.org/wiki/BrokenSoundDrivers.
Looks like the website is broken:
Not Found
The requested URL /wiki/BrokenSoundDrivers was not found on this server.
Apache Server at
On Thu, 12 Feb 2009 09:35:17 +, Colin Guthrie wrote:
To be honest, you really need to try the 0.9.15 test version with
module-position-event-sounds disabled.
Yeah. I understand what you are saying.
But the reality is that I already only get 4-5h of sleep a night trying
to manage all of
I posted a bug about this in trac (http://pulseaudio.org/ticket/438) but
my attempts to try to explain and get confirmation of the un-
intuitiveness (in the least) of this problem seem to have gone
unanswered. Perhaps I am not following some proper process to re-open a
ticket. I was hoping to
I am finding that frequently, on Ubuntu Intrepid (pulseaudio
0.9.10-2ubuntu9.2), pidgin (1:2.5.2-0ubuntu1) will play one of it's
sounds through the pulseaudio server but the connection will not end with
the end of the sound as it normally does -- as evidenced by the volume
control.
Normally
On Mon, 15 Dec 2008 16:08:05 +, Brian J. Murrell wrote:
So nobody has any ideas regarding stuttering sound quality?
I've tried increasing the priority of the sound server. No help.
I've checked the FAQ and couldn't find anything about stuttering there
either.
I've googled and seen all
On Mon, 15 Dec 2008 16:08:05 +, Brian J. Murrell wrote:
Hrm. My otherwise and previously working pulseaduio (0.9.10-2ubuntu9.1)
seems to have started occasionally stuttering today with rhythmbox.
FWIW, I have opened bug #435 about this. To summarize the bug so far,
Creative Labs cards
I've got an interesting problem. I have a file which file reports as
being:
/home/brian/tmp/msg0001.wav:RIFF (little-endian) data, WAVE audio, GSM
6.10, mono 8000 Hz
sox reports the file as being:
Sample Size: 16-bit (2 bytes)
Sample Encoding: GSM
Channels : 1
Sample Rate:
On Mon, 15 Dec 2008 16:08:05 +, Brian J. Murrell wrote:
Hrm. My otherwise and previously working pulseaduio (0.9.10-2ubuntu9.1)
seems to have started occasionally stuttering today with rhythmbox.
I should add, that this does not seem to correlate so much with system
load either. I just
On Fri, 2008-12-12 at 13:17 +0100, Lennart Poettering wrote:
On Thu, 11.12.08 22:48, Brian J. Murrell (br...@interlinx.bc.ca) wrote:
I've noticed a number of times on my Ubuntu Intrepid machine that Pidgin
seems to get it's pulseaudio connection hung up. Normally I only see a
listing
On Wed, 2008-12-10 at 19:37 +0100, Lennart Poettering wrote:
Practically not. Theoretically yes.
Heh.
pax11publish is a simple tool to store PA server data in the X11
root window (i.e. attach the PA data to the X display).
Right. But how do I programatically effect the same thing as
I've changed my ekiga configuration to send it's ringing (i.e. sounds
like a telephone ringing) sound to ALSA via the Default device rather
than naming the device specifically. Since I have the:
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
.asoundrc stuff configured, ekiga's audio
On Wed, 2008-12-10 at 10:01 -0500, Sean McNamara wrote:
Are you running PA in realtime mode? Does top say that its priority is RT?
Nope. It says it's 20.
Yeah, it sounds like PA is stuck in a tight loop trying to access
ALSA. I've never encountered this before, and I've used Intrepid a
On Wed, 2008-12-10 at 11:29 -0500, Sean McNamara wrote:
Hi again Brian,
Hi,
Well, you can't find this out for sure without getting pulseadudio to
stop looping like it is. But you can just restart PulseAudio with
`killall -9 pulseaudio; pulseaudio --start`. Then restart any apps
that are
Hi All,
One thing that sprang to mind with pulseaudio's network protocol is a
coupling with VNC. Pulseaudio can bring the audio from a VNC server to
client enhancing the whole remote desktop experience.
Certainly I could, once I have logged into a remote desktop simply
change the sound server
On Tue, 2008-12-09 at 23:21 -0500, John A. Sullivan III wrote:
Yes, FreeNX or the original NoMachine NX is a little lighter.
But will FreeNX or the original NoMachine NX remote the sound to the
thin client too?
This is
designed for pretty heavy many to one machine usage, i.e., serving up
66 matches
Mail list logo
