Re: [pulseaudio-discuss] [PATCH] Fix crash on jack server shutdown
On Sun, 2010-03-14 at 16:29 -0400, Daniel Chen wrote: > On Sun, Mar 14, 2010 at 3:50 PM, David Henningsson > wrote: > > @Daniel T Chen: let me know if you want this patch as a merge proposal as > > well. There is no bug in Launchpad AFAIK. > > For release tracking purposes, please file a bug and also propose a > merge. Thanks! Thank you David for your work on this =) ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Volume jumps to 100% on KDE startup in KDE 4.4.0-4.4.1
'Twas brillig, and Dwight Paige at 14/03/10 21:15 did gyre and gimble: > On 03/14/2010 01:43 PM, Colin Guthrie wrote: > > >> >>> I have installed the pulseaudio packages in>Main>Testing [version >>> 1.0.21]. No problems to report so far. I wonder if there are >>> corresponding packages in Fedora? >> >> I believe the updates have already been shipped in Fedora. I don't >> follow the updates there very closely so can't say for certain. "rpm -q >> --changelog pulseaudio" will probably tell you more. > > I gave wrong version # for pulseaudio packages in Mandriva. It's 0.9.21. > And Fedora pulseaudio packages are also 0.9.21. Fedora KMix [version > 3.6-alpha2 updated from Redhat/Fedora KDE-testing repo] is indeed > showing alsa controls currently. > > Also upon further investigation I may not have the problem I thought I had. > > I did a fresh install of Fedora 12 x86_64 formatting both / and /home > partitions so all files would be fresh/default. Sound behavior is > different from my original Fedora 12 install [still have that too]. > It shows the original/default volume in KMix [Master Channel] as 21%. It > also had some channels muted like front, center, surround, and LFE which > I had to unmute all to hear sound. This 21% volume was actually to low > so I installed and opened pavucontrol and set Output devices to 31% > which set KMix Master Volume to 61% which is good for me. Just FYI, the disparity here is because the PA UIs offer volumes up to 150% (IIRC) which includes software amplification. The raw ALSA value in Kmix does not offer this. > Now here's one thing that seems strange to me. When I logout or reboot > with KMix open when it plays the shutdown sound volume automatically > lowers to 22% and I can barely hear log out sound. When I log back in > with KMix open volume is again 61% until login sound plays when volume > lowers automatically to 22% and when login sound finishes volume returns > to 61%... Don't know if this is what it's supposed to do or not. Pulseaudio expects full control over the mixer levels and what you are seeing here is a feature called "Flat Volumes" in action. At some point the volume of the logout sound has been saved to be 22% (perhaps not exactly that but some value). In order to achieve that result, PA will try whenever possible to use h/w volume adjustments rather than software. As PA is a mixer, it will take the loudest volume of any running stream and use that as the hardware volume and then attenuate in software any other streams so that they are set to their relative values. e.g. say I have a stream running at 50%, then the h/w will be set to 50% and the stream will not be attenuated at all in software. If I then play a second stream at 75%, the h/w volume will increase to that value and the current running stream @50% will be attenuated in software so that it stays at 50% overall. So it's not exactly unusual to see the h/w volume jump around. What is more interesting is why the logout sound is played more quietly... Can you make sure the "System Sounds" slider in pavucontol has a sensible value? > After a number of reboots I added Redhat/Fedora KDE repo and installed > KDE 4.4.1 from kde-testing. And shutdown/startup sound behavior > remained. ie. lowering automatically to 22% when startup sound started > and after startup sound finished volume automatically changed to the 61% > I had set. It probably now relates to the per-application saved volumes. It's correctly saving/restoring the volume for the logout sound the real question is how/where it was set in the first place! > At any rate my NEW Fedora install certainly has a volume level, except > for startup/shutdown sound, that I find very usable. Will see if > anything changes as I try more apps and tests. > > I don't know what changed in my original Fedora install to cause > startup/shutdown volume to shoot to 100%. I'm probably just going to > move what little data I have there to new Fedora partition and see what > happens. Chances are trashing your ~/.pulse folder in the existing setup will have much the same effect as a reinstall... you may have to do the same for the "kdm" user too if there is such a user - there is for gdm, but don't know that much about kdm personally. > Hope this all makes sense. Let me if it doesn't or more info or test are > desired. It's kinda expected behaviour in a way, so it makes sense. There are a few unknowns relating to how the data got there in the first place but the generally described behaviour sounds plausible enough. If possible try and grab "pacmd ls" when the shutdown sound is playing as it will say what "stream-restore.id" is being used for the logout sound itself which may explain where the lower volume setting came from. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [ht
Re: [pulseaudio-discuss] Volume jumps to 100% on KDE startup in KDE 4.4.0-4.4.1
On 03/14/2010 01:43 PM, Colin Guthrie wrote: I have installed the pulseaudio packages in>Main>Testing [version 1.0.21]. No problems to report so far. I wonder if there are corresponding packages in Fedora? I believe the updates have already been shipped in Fedora. I don't follow the updates there very closely so can't say for certain. "rpm -q --changelog pulseaudio" will probably tell you more. I gave wrong version # for pulseaudio packages in Mandriva. It's 0.9.21. And Fedora pulseaudio packages are also 0.9.21. Fedora KMix [version 3.6-alpha2 updated from Redhat/Fedora KDE-testing repo] is indeed showing alsa controls currently. Also upon further investigation I may not have the problem I thought I had. I did a fresh install of Fedora 12 x86_64 formatting both / and /home partitions so all files would be fresh/default. Sound behavior is different from my original Fedora 12 install [still have that too]. It shows the original/default volume in KMix [Master Channel] as 21%. It also had some channels muted like front, center, surround, and LFE which I had to unmute all to hear sound. This 21% volume was actually to low so I installed and opened pavucontrol and set Output devices to 31% which set KMix Master Volume to 61% which is good for me. Now here's one thing that seems strange to me. When I logout or reboot with KMix open when it plays the shutdown sound volume automatically lowers to 22% and I can barely hear log out sound. When I log back in with KMix open volume is again 61% until login sound plays when volume lowers automatically to 22% and when login sound finishes volume returns to 61%... Don't know if this is what it's supposed to do or not. After a number of reboots I added Redhat/Fedora KDE repo and installed KDE 4.4.1 from kde-testing. And shutdown/startup sound behavior remained. ie. lowering automatically to 22% when startup sound started and after startup sound finished volume automatically changed to the 61% I had set. At any rate my NEW Fedora install certainly has a volume level, except for startup/shutdown sound, that I find very usable. Will see if anything changes as I try more apps and tests. I don't know what changed in my original Fedora install to cause startup/shutdown volume to shoot to 100%. I'm probably just going to move what little data I have there to new Fedora partition and see what happens. Hope this all makes sense. Let me if it doesn't or more info or test are desired. -- Thanks, Dwight Paige ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] Fix crash on jack server shutdown
On Sun, Mar 14, 2010 at 3:50 PM, David Henningsson wrote: > @Daniel T Chen: let me know if you want this patch as a merge proposal as > well. There is no bug in Launchpad AFAIK. For release tracking purposes, please file a bug and also propose a merge. Thanks! ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] [PATCH] Fix crash on jack server shutdown
On sink unlinking, existing sink inputs are moved, which in turn calls
a get latency callback, which references the jack client. Therefore,
make sure the sink is unlinked before the client is closed. Failure to
do so might lead to SIGSEGV.
This patch simply moves the call to pa_sink_unlink above
jack_client_close, which fixes the problem.
Steps to reproduce:
1. Disable autospawn and kill PA
2. Start jack server
3. Start PA
4. Load module module-jack-sink
5. Start a stream (e g Rythmbox) and run it through the jack sink.
6. Shutdown the jack server. Now PA crashes with SIGSEGV.
@Daniel T Chen: let me know if you want this patch as a merge proposal as
well. There is no bug in Launchpad AFAIK.
>From fa2dcce3201753bff94adba99b6bc36a7eaf57f9 Mon Sep 17 00:00:00 2001
From: David Henningsson
Date: Sun, 14 Mar 2010 20:20:12 +0100
Subject: [PATCH] Fix crash on jack server shutdown
On sink unlinking, existing sink inputs are moved, which in turn calls
a get latency callback, which references the jack client. Therefore,
make sure the sink is unlinked before the client is closed. Failure to
do so might lead to SIGSEGV.
---
src/modules/jack/module-jack-sink.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/modules/jack/module-jack-sink.c b/src/modules/jack/module-jack-sink.c
index 9f3e071..e4467d3 100644
--- a/src/modules/jack/module-jack-sink.c
+++ b/src/modules/jack/module-jack-sink.c
@@ -475,12 +475,12 @@ void pa__done(pa_module*m) {
if (!(u = m->userdata))
return;
-if (u->client)
-jack_client_close(u->client);
-
if (u->sink)
pa_sink_unlink(u->sink);
+if (u->client)
+jack_client_close(u->client);
+
if (u->thread) {
pa_asyncmsgq_send(u->thread_mq.inq, NULL, PA_MESSAGE_SHUTDOWN, NULL, 0, NULL);
pa_thread_free(u->thread);
--
1.7.0
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Volume jumps to 100% on KDE startup in KDE 4.4.0-4.4.1
'Twas brillig, and Dwight Paige at 14/03/10 18:19 did gyre and gimble: > Thanks for the reply. Ok, I've got PulseAudio enabled in Mandriva. It is > showing PulseAudio devices not Alsa. And it appears I've reported > incorrectly. I set KMix>Playback Devices [only output shown] to 50% and > rebooted and it was still at 50% upon login. I believe PulseAudio is > working as expected in Mandriva so far. If I run across something in > Mandriva that seems wrong I'll post it here or file a bug report. So > this appears to be strictly happening in Fedora for me. Great :) FWIW, the kmix in Fedora may be a pure ALSA one or an older version of my kmix work. I spoke to the Fedora guy in charge of those pacakges just the other day and he was in the process of updating the kmix patches. If your kmix in Fedora there are configuration settings that prevent it from restoring the sound on login. My integrations patches automatically disable this now but older versions wont. So I suspect that it's simply a matter of manually configuring kmix to not save/restore settings until it is updated with the latest version of my patches. > I have installed the pulseaudio packages in >Main>Testing [version > 1.0.21]. No problems to report so far. I wonder if there are > corresponding packages in Fedora? I believe the updates have already been shipped in Fedora. I don't follow the updates there very closely so can't say for certain. "rpm -q --changelog pulseaudio" will probably tell you more. > Now I'm going to login to Fedora and check some things. Will post back > here later today. Cool -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Volume jumps to 100% on KDE startup in KDE 4.4.0-4.4.1
Thanks for the reply. Ok, I've got PulseAudio enabled in Mandriva. It is showing PulseAudio devices not Alsa. And it appears I've reported incorrectly. I set KMix>Playback Devices [only output shown] to 50% and rebooted and it was still at 50% upon login. I believe PulseAudio is working as expected in Mandriva so far. If I run across something in Mandriva that seems wrong I'll post it here or file a bug report. So this appears to be strictly happening in Fedora for me. I have installed the pulseaudio packages in >Main>Testing [version 1.0.21]. No problems to report so far. I wonder if there are corresponding packages in Fedora? Now I'm going to login to Fedora and check some things. Will post back here later today. Original Message Subject: Re: [pulseaudio-discuss] Volume jumps to 100% on KDE startup in KDE 4.4.0-4.4.1 Date: Sun, 14 Mar 2010 11:58:28 + From: Colin Guthrie Reply-To: General PulseAudio Discussion To: pulseaudio-discuss@mail.0pointer.de 'Twas brillig, and Dwight Paige at 13/03/10 01:34 did gyre and gimble: In KDE 4.4.0 [Mandriva 2010.0 x86_64] and KDE 4.4.1 [Fedora 12 x86_64]. When I log out and log back in or reboot when KDE starts sound volume levels jump to painfully loud 100% in KMix and pavucontrol. Why is this? Do you have a Mandriva bug report about this? If so can you link it? (I've got a couple 100% bugs (mostly invalid ones) but couldn't identify this particular issue in the ones that I checked against. Is this a KDE, pulseaudio, or alsa issue? As per example I believe that openSuSE 11.2 does not use pulseaudio by default for KDE apps [it does for Gnome]. I can confirm that this sound jumping to 100% on boot/login does not happen in My openSuSE/KDE 4.4.1 partition. I checked and so far pulseaudio is not even installed in my openSuSE/KDE 4.4.1. It could be a number of things. I've not got a KDE 4.4 install to hand so not 100% sure but does kmix here show PulseAudio devices or Alsa devices? You should be able to tell pretty easily from the names of the tabs... In the pre-PulseAudio enabled Kmix, it would be responsible for restoring volume levels on a per-user basis. After I integrated support for PA into KMix I'm pretty careful to not save/restore volumes. Work around is to disable or remove pulseaudio: http://forums.fedoraforum.org/showthread.php?t=237705&page=2 That's the whimps way out - real men find the issue - so thanks for helping to debug :D That doesn't necessarily mean that pulseaudio is at fault or does it? Could this be a driver issue? It's unlikely to be a driver issue. Something is ultimately causing this. In order to debug, can you: 1. Edit your /etc/pulse/daemon.conf 2. Change log-level to "debug" 3. Do a fresh boot and make the issue happen. 4. Shut down (very important. 5. Startup again. 6. Post the output of "grep pulse /var/log/messages" to a Mandriva bug report against the pulseaudio pacakge (it'll be assigned to me automatically). If possible can you mark the times where you rebooted in the log extract with some suitible annotation as it'll help show where and when things happen. Before you do any of the above tho', can you try the pulseaudio pacakges from the Mandriva main/testing repository? These will be going out as official updates in a week or so so you're really just getting a preview. This updated package does include some fixes to ignore volume changes when the user is not logged in and I'm wondering if some kind of race condition is causing your user-specific volume preferences to be clobbered by some system wide shutdown task before you get a change for PA to exit after logging out. One way to test this theory is to not shutdown directly, but to logout first and wait a couple minutes before actually shutting down from the Display Manager instead. Alternatively, (and I've not used KDM for a while), it could be the display manager the one triggering the problem if it tries to play sound when login is ready and starts PA for itself. If this is the case the updated PA package will almost certainly fix the issue. To test without upgrading boot to runlevel 3, and and login and type startx. This approach of logging in vs. the KDM route should avoid the race. Hope all this info helps. Col ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Problem when loading module-always-sink or module-alsa-sink
On Sun, Mar 14, 2010 at 3:57 AM, Tanu Kaskinen wrote: > la, 2010-03-13 kello 14:59 -0300, Maginot Junior kirjoitti: >> So I tried to ran pulseaudio with - option, this is the output: >> >> $ LANG=c pulseaudio - >> >> I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted >> I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted >> D: core-rtclock.c: Timer slack is set to 50 us. >> I: core-util.c: Failed to acquire high-priority scheduling: No such >> file or directory >> I: main.c: This is PulseAudio 0.9.21 >> D: main.c: Compilation host: i686-pc-linux-gnu >> D: main.c: Compilation CFLAGS: -g -O2 -Wall -W -Wextra -pipe >> -Wno-long-long -Winline -Wvla -Wno-overlength-strings >> -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op >> -Wsign-compare -Wformat-security -Wmissing-include-dirs >> -Wformat-nonliteral -Wold-style-definition -Wpointer-arith -Winit-self >> -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes >> -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations >> -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align >> -Wstrict-aliasing=2 -Wwrite-strings -Wno-unused-parameter -ffast-math >> -Wp,-D_FORTIFY_SOURCE=2 -fno-common -fdiagnostics-show-option >> D: main.c: Running on host: Linux i686 2.6.30.2 #2 SMP Wed Jan 27 >> 17:14:41 BRST 2010 >> D: main.c: Found 1 CPUs. >> I: main.c: Page size is 4096 bytes >> D: main.c: Compiled with Valgrind support: no >> D: main.c: Running in valgrind mode: no >> D: main.c: Running in VM: yes >> D: main.c: Optimized build: yes >> D: main.c: All asserts enabled. >> I: main.c: Machine ID is avant. >> I: main.c: Using runtime directory /home/maginot/.pulse/avant-runtime. >> I: main.c: Using state directory /home/maginot/.pulse. >> I: main.c: Using modules directory /usr/lib/pulse-0.9.21/modules. >> I: main.c: Running in system mode: no >> W: pid.c: Stale PID file, overwriting. >> I: main.c: Fresh high-resolution timers available! Bon appetit! >> I: cpu-x86.c: CPU flags: MMX SSE SSE2 SSE3 SSSE3 SSE4_1 >> I: svolume_mmx.c: Initialising MMX optimized functions. >> I: remap_mmx.c: Initialising MMX optimized remappers. >> I: svolume_sse.c: Initialising SSE2 optimized functions. >> I: remap_sse.c: Initialising SSE2 optimized remappers. >> I: sconv_sse.c: Initialising SSE2 optimized conversions. >> D: memblock.c: Using shared memory pool with 1024 slots of size 64.0 >> KiB each, total size is 64.0 MiB, maximum usable slot size is 65496 >> D: database-gdbm.c: Opened GDBM database >> '/home/maginot/.pulse/avant-device-volumes.i686-pc-linux-gnu.gdbm' >> I: module-device-restore.c: Sucessfully opened database file >> '/home/maginot/.pulse/avant-device-volumes'. >> I: module.c: Loaded "module-device-restore" (index: #0; argument: ""). >> D: database-gdbm.c: Opened GDBM database >> '/home/maginot/.pulse/avant-stream-volumes.i686-pc-linux-gnu.gdbm' >> I: module-stream-restore.c: Sucessfully opened database file >> '/home/maginot/.pulse/avant-stream-volumes'. >> I: module.c: Loaded "module-stream-restore" (index: #1; argument: ""). >> D: database-gdbm.c: Opened GDBM database >> '/home/maginot/.pulse/avant-card-database.i686-pc-linux-gnu.gdbm' >> I: module-card-restore.c: Sucessfully opened database file >> '/home/maginot/.pulse/avant-card-database'. >> I: module.c: Loaded "module-card-restore" (index: #2; argument: ""). >> I: module.c: Loaded "module-augment-properties" (index: #3; argument: ""). >> N: alsa-util.c: Disabling timer-based scheduling because running inside a VM. >> E: fdsem.c: Assertion 'pa_atomic_dec(&f->data->waiting) >= 1' failed >> at pulsecore/fdsem.c:283, function pa_fdsem_before_poll(). Aborting. >> >> >> Like you may notice, it finishes with an error line: E: fdsem.c: >> Assertion 'pa_atomic_dec(&f->data->waiting) >= 1' failed at >> pulsecore/fdsem.c:283, function >> >> After tweaking around a little I first disabled module-always-sink >> from /etc/pulse/default.pa > > Before disabling module-always-sink, was your default.pa the default one > shipped with the official pulseaudio 0.9.21 tarball? If it was, then > disabling module-always-sink shouldn't help anything, because the crash > happens before loading that module is even attempted. The crash probably > happens in module-udev-detect. > > Since the second try didn't crash, this apparently doesn't happen > always. But on the third try it crashed in the same place (probably), so > I guess you can reproduce this reliably enough to produce a stack trace. > So, please file a bug that has a link to this mailing list thread and > the stack trace. Instructions for filing bugs can be found at > > http://pulseaudio.org/wiki/Community#BugsPatchesTranslations > > Getting a stack trace of pulseaudio can be a bit tricky, but that link > has instructions for that too. > > Loading module-udev-detect is part of the default start-up procedure, > and it apparently works reliably for pretty much everybody, so I'm > afraid that if the stack t
Re: [pulseaudio-discuss] Volume jumps to 100% on KDE startup in KDE 4.4.0-4.4.1
'Twas brillig, and Dwight Paige at 13/03/10 01:34 did gyre and gimble: > In KDE 4.4.0 [Mandriva 2010.0 x86_64] and KDE 4.4.1 [Fedora 12 x86_64]. > When I log out and log back in or reboot when KDE starts sound volume > levels jump to painfully loud 100% in KMix and pavucontrol. Why is this? Do you have a Mandriva bug report about this? If so can you link it? (I've got a couple 100% bugs (mostly invalid ones) but couldn't identify this particular issue in the ones that I checked against. > Is this a KDE, pulseaudio, or alsa issue? As per example I believe that > openSuSE 11.2 does not use pulseaudio by default for KDE apps [it does > for Gnome]. I can confirm that this sound jumping to 100% on boot/login > does not happen in My openSuSE/KDE 4.4.1 partition. I checked and so far > pulseaudio is not even installed in my openSuSE/KDE 4.4.1. > It could be a number of things. I've not got a KDE 4.4 install to hand so not 100% sure but does kmix here show PulseAudio devices or Alsa devices? You should be able to tell pretty easily from the names of the tabs... In the pre-PulseAudio enabled Kmix, it would be responsible for restoring volume levels on a per-user basis. After I integrated support for PA into KMix I'm pretty careful to not save/restore volumes. > Work around is to disable or remove pulseaudio: > > http://forums.fedoraforum.org/showthread.php?t=237705&page=2 That's the whimps way out - real men find the issue - so thanks for helping to debug :D > That doesn't necessarily mean that pulseaudio is at fault or does it? > Could this be a driver issue? It's unlikely to be a driver issue. Something is ultimately causing this. In order to debug, can you: 1. Edit your /etc/pulse/daemon.conf 2. Change log-level to "debug" 3. Do a fresh boot and make the issue happen. 4. Shut down (very important. 5. Startup again. 6. Post the output of "grep pulse /var/log/messages" to a Mandriva bug report against the pulseaudio pacakge (it'll be assigned to me automatically). If possible can you mark the times where you rebooted in the log extract with some suitible annotation as it'll help show where and when things happen. Before you do any of the above tho', can you try the pulseaudio pacakges from the Mandriva main/testing repository? These will be going out as official updates in a week or so so you're really just getting a preview. This updated package does include some fixes to ignore volume changes when the user is not logged in and I'm wondering if some kind of race condition is causing your user-specific volume preferences to be clobbered by some system wide shutdown task before you get a change for PA to exit after logging out. One way to test this theory is to not shutdown directly, but to logout first and wait a couple minutes before actually shutting down from the Display Manager instead. Alternatively, (and I've not used KDM for a while), it could be the display manager the one triggering the problem if it tries to play sound when login is ready and starts PA for itself. If this is the case the updated PA package will almost certainly fix the issue. To test without upgrading boot to runlevel 3, and and login and type startx. This approach of logging in vs. the KDM route should avoid the race. Hope all this info helps. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio and Skype
'Twas brillig, and Mark Greenwood at 14/03/10 09:56 did gyre and gimble: > If I enable pulseaudio, skype automatically sets all the audio > options to be pulseaudio - there is no option in this version to use > ALSA if pulse is enabled, which is sensible enough I guess. Yeah this is definitely sensible. I'm hoping the Skype guys will remove the whole dropdown selectors when PA is detected to avoid people expecting that alsa and pulse can play nicely together in a system without one or other ultimately being locked out at some point. > But although I can make calls, and the other end can hear me and I > can hear them, the other end can also hear themselves - as loud as me > with a slight delay. They all say it's so offputting that they can't > hold a conversation. Interesting > If I turn my microphone down, the other end says the echo goes away - > but they can't hear me either. Moving the microphone away from the > speakers isn't an option as this is on a laptop. Hmm, it's strange that this is somehow different on PA vs. Non-PA the code for echo cancellation should be the same regardless. > Now, I wouldn't be here asking daft questions about closed source > software - except that it all works fine when pulseaudio is not > involved. It almost appears as if there's some echo cancellation > which is broken when pulseaudio is in the mix, or that possibly pulse > is feeding the incoming voice conversation back into skype somehow. > > Any ideas on how to go about making it work? There were some skype related fixes in the stable-queue branch recently. I believe all these fixes are in the PPA you mention for Ubuntu. I don't think these are related but there are lots of misc bugfixes between 0.9.19 and 0.9.21+stable-queue anyway, so it's always best to use that version. Let us know how you get one with that one. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio and Skype
On Sunday 14 Mar 2010 10:35:27 Paul Menzel wrote: > Dear Mark, > > > Am Sonntag, den 14.03.2010, 09:56 + schrieb Mark Greenwood: > > […] > > > I'm running Skype 2.1 beta and Pulseaudio 0.9.19 on Kubuntu 9.10. > > […] > > > Any ideas on how to go about making it work? > > have you read [1] which is referenced by [2]. > > But before you report back with the debug information, could you please > try the current release 0.9.21 or the one from Git (master or > stable-queue). It should not be too hard to build that packages with > `git-buildpackage` or `dpkg-buildpackage`. > Thanks. I specifically didn't want to report it as a bug because of [1]. I was wondering if anyone would be able to tell me 'just do this...'. There is an ubuntu PPA for version 0.9.21 so I will install that and test it, though of course I am reliant on the patience of my freinds for skype testing :-) Mark > > Thanks, > > Paul > > > [1] http://pulseaudio.org/wiki/UbuntuBugs > [2] http://pulseaudio.org/wiki/Community#BugsPatchesTranslations > ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio and Skype
Dear Mark, Am Sonntag, den 14.03.2010, 09:56 + schrieb Mark Greenwood: […] > I'm running Skype 2.1 beta and Pulseaudio 0.9.19 on Kubuntu 9.10. […] > Any ideas on how to go about making it work? have you read [1] which is referenced by [2]. But before you report back with the debug information, could you please try the current release 0.9.21 or the one from Git (master or stable-queue). It should not be too hard to build that packages with `git-buildpackage` or `dpkg-buildpackage`. Thanks, Paul [1] http://pulseaudio.org/wiki/UbuntuBugs [2] http://pulseaudio.org/wiki/Community#BugsPatchesTranslations signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Pulseaudio and Skype
Hi All, I know pulse and skype have a chequered history, but I've done a lot of googling and I can't find any other description of this particular problem. I'm running Skype 2.1 beta and Pulseaudio 0.9.19 on Kubuntu 9.10. Firstly, skype works fine if I disable pulseaudio. (That's just for information, not a comment). If I enable pulseaudio, skype automatically sets all the audio options to be pulseaudio - there is no option in this version to use ALSA if pulse is enabled, which is sensible enough I guess. But although I can make calls, and the other end can hear me and I can hear them, the other end can also hear themselves - as loud as me with a slight delay. They all say it's so offputting that they can't hold a conversation. If I turn my microphone down, the other end says the echo goes away - but they can't hear me either. Moving the microphone away from the speakers isn't an option as this is on a laptop. Now, I wouldn't be here asking daft questions about closed source software - except that it all works fine when pulseaudio is not involved. It almost appears as if there's some echo cancellation which is broken when pulseaudio is in the mix, or that possibly pulse is feeding the incoming voice conversation back into skype somehow. Any ideas on how to go about making it work? Thanks, Mark ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
