Re: [pulseaudio-discuss] More on the native protocol complexity
Hi, sorry for the late reply.. On Fri, Apr 23, 2010 at 6:10 PM, Rafal Wojtczuk ra...@invisiblethingslab.com wrote: Again, can I have a simple sound sharing over network protocol, pretty pretty please ? Raw audio frames + simple synchronization, anyone ? stupid question, but.. is GStreamer out of your scope here? Regards Regards, Rafal Wojtczuk The Qubes OS Project http://qubes-os.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] On SHM related Bus errors
Hi, There has been some discussion about bus errors and SHM of late. I've just seen my first bug report on the topic! https://bugs.kde.org/show_bug.cgi?id=236524 Extract (5 is the lowest number in the call stack due to the crash handler) Application: KNotify (knotify4), signal: Bus error [KCrash Handler] #5 0x7f071225df5e in pa_shm_create_rw () from /usr/lib64/libpulsecommon-0.9.21.so #6 0x7f0712252676 in pa_mempool_new () from /usr/lib64/libpulsecommon-0.9.21.so #7 0x7f07152a8958 in pa_context_new_with_proplist () from /usr/lib64/libpulse.so.0 #8 0x7f0718c33d08 in Phonon::PulseSupport::PulseSupport (this=0x6de530) at /usr/src/debug/phonon-4.4/phonon/pulsesupport.cpp:712 This happens after a resume from suspend. What kind of thing can cause this? Non writable SHM area? Full up? What is the best way to go about debugging this? 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
[pulseaudio-discuss] Problems with mplayer in Ubuntu 10.04
Hello everyone! I have Ubuntu 10.04 (AMD64), cleanly installed on a new system I bought, an Intel Pentium Dual Core E6500 with an Asrock P5B-DE mother board, 3 GB of DDR2 memory. This mother board comes with an HDA Intel onboard audio card, HDA Intel, that has the Via VT1708S codec. This onboard audio card does not have the ability to do hardware mixing as it seems. I also have a TV tuner which is connected via the line-in port. Even if capturing is enabled in alsamixer, for the linein, I cannot hear any sound (no hw mixing). This is why I workaround the issue with the loopback-module provided by PulseAudio. Everything else seems to work fine, PulseAudio mixes all audio streams nicely. The problem is with mplayer. I cannot play *any* sound with it, and worse, it causes PulseAudio to go bonkers. Once I start mplayer, I cannot hear any sound, from any application. I tested mplayer from the default Ubuntu repositories [1] and a much newer build from the RVM Ubuntu PPA repository [2] (the author of SMPlayer, if I am not mistaken). Both behave quite much the same. Usage scenario #1: 1. No sounds playing. 2. Start mplayer -ao pulse video_with_audio.avi. Expected result: video plays together with audio. Actual result: video plays without any audible sound. More info: if I try to play other sounds with other apps (say vlc or gnome system sounds), they all seem to work fine, but I can no longer hear them, just like with mplayer. Mplayer seems to work fine - no errors, but I cannot hear anything. pavucontrol shows the mplayer (and other audio streams). The VU meter indicates proper audio stream activity, all is fine. No volume is muted/low, no stream is suspended (pacmd ls), nothing shows wrong. Semi-workarounds: - pulseaudio --kill. This restarts the PulseAudio system and then it works fine again. - change card profile (say from stereo to 7.1 and back). This makes PulseAudio output sound again. If I do this while mplayer plays the video file, I can hear its own audio stream fine. This means that only the initialization of mplayer makes pulseaudio go bonkers. Usage scenario #2: 1. Start vlc video_with_audio.avi. (making sure it is configured to use PulseAudio output). Sound plays fine. 2. Start mplayer -ao pulse another_video_with_audio.avi. Expected result: I can see both videos playing and I can hear both audio streams mixed. Actual result: I can see both videos playing, but no sound. Even the sound from vlc goes mute. Again, there are no indications of errors from any of the players, nor from pacmd ls, nor from pavucontrol. I can see both audio streams playing fine. Same semi-workarounds apply. Usage scenario #3: 1. Start mplayer -ao alsa/jack/etc. It's all the same as -ao pulse, with some notable differences: a) mplayer from default Ubuntu repos allows the use of -ao esd, which no longer breaks PulseAudio and the audio stream *almost* plays fine. It does not play fine, because after a few random seconds it stops - I can no longer hear sound. If I seek within the file with mplayer, then it resets some buffers and I can hear the audio stream again, and so on. At least it doesn't break PA. ;) b) mplayer from RVM Ubuntu PPA ... behaves with -ao esd as it does with -ao pulse. However, -ao oss works fine. I can hear the audio stream with no problems. Nonetheless, -ao oss manages to take over PulseAudio and that means any sounds coming from PulseAudio are not heard by me. Once I stop mplayer the situation does not 'recover', I need to kill pulseaudio or change the card profile back and forth. Usage scenario #4: 1. Start mplayer. No -ao pulse, no video/audio file, just so we can see its command line help. Expected result: I get the mplayer help and that there's no sound output, and that it does not affect PulseAudio. Actual result: mplayer somehow manages to break PulseAudio once again, irrespective of -ao pulse, irrespective of giving it any video/audio file to play. WTF? moment here. Debugging the problem: 1. Starting mplayer with -msglevel all=9 shows no errors at all. 2. pacmd ls and other lists/infos from pacmd do not show errors/problems. 3. pacmd set-log-level 4 does, finally, show errors in /var/log/syslog. The gist of the problem lies in: pulseaudio[8713]: client.c: Created 30 Native client (UNIX socket client) pulseaudio[8713]: client.c: Freed 30 Native client (UNIX socket client) pulseaudio[8713]: protocol-native.c: Connection died. pulseaudio[8713]: module-udev-detect.c: /dev/snd/controlC0 is accessible: yes pulseaudio[8713]: last message repeated 10 times pulseaudio[8713]: client.c: Created 31 Native client (UNIX socket client) pulseaudio[8713]: protocol-native.c: Protocol version: remote 16, local 16 pulseaudio[8713]: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1 pulseaudio[8713]: protocol-native.c: SHM possible: yes pulseaudio[8713]: protocol-native.c: Negotiated SHM: yes pulseaudio[8713]: module-augment-properties.c: Looking for .desktop file for
Re: [pulseaudio-discuss] Problems with mplayer in Ubuntu 10.04
Hi, Just for clarity to others reading, we discussed and tried to debug this issue a lot on IRC already, so I'm familiar with the problem. 'Twas brillig, and Mihai Sucan at 09/05/10 12:06 did gyre and gimble: 4. somehow i think that mplayer -ao pulse does pretty much the same as it does mplayer -ao oss from the rvm Ubuntu PPA. The latter did take control of the sound card, via OSS. The former does somehow take control of the sound card, pulseaudio looses it, then mplayer happily goes on to use pulseaudio for subsequent audio stream output, but now ... pulseaudio is silenced. Well mplayer -ao oss will bypass pulse completely and, as you say, basically hog the sound h/w. You can theoretically use: padsp mplayer -ao oss and that should redirect oss output via PA too, but this may or may not work overly reliably (aka YMMV). The interesting thing about the report is that when PA stops outputting audible sound, the vumeters are properly moving up and down which means that the sinks are not suspended, nor are the sinks unloaded and replaced with a Dummy Output (null-sink) because they've been unloaded. In other words everything seems setup to work correctly but the reasons are eluding us! One thing you don't mention above, but is included in your debug output is the fact that the alsa mixer output is not any different before vs. after the problem. My initial hypothesis was that mplayer was somehow flipping the digital output switch in alsa, thus causing it to seem like it had simply stopped working. However analysis of the amixer output seems to kill this idea. So if anyone else has any bright ideas, please speak up! 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] Problems with mplayer in Ubuntu 10.04
Hello Colin! Thanks for your clarifications. Le Sun, 09 May 2010 14:23:14 +0300, Colin Guthrie gm...@colin.guthr.ie a écrit: Hi, Just for clarity to others reading, we discussed and tried to debug this issue a lot on IRC already, so I'm familiar with the problem. 'Twas brillig, and Mihai Sucan at 09/05/10 12:06 did gyre and gimble: 4. somehow i think that mplayer -ao pulse does pretty much the same as it does mplayer -ao oss from the rvm Ubuntu PPA. The latter did take control of the sound card, via OSS. The former does somehow take control of the sound card, pulseaudio looses it, then mplayer happily goes on to use pulseaudio for subsequent audio stream output, but now ... pulseaudio is silenced. Well mplayer -ao oss will bypass pulse completely and, as you say, basically hog the sound h/w. You can theoretically use: padsp mplayer -ao oss and that should redirect oss output via PA too, but this may or may not work overly reliably (aka YMMV). The result of calling padsp mplayer -ao oss is the same: 1. I can see now mplayer with OSS emulation in pavucontrol, vu meter is fine, audio stream activity, etc. 2. I hear no sound, pulseaudio is borked/hogged. 3. Changing the card profile back and forth does make it work, while mplayer is running. So, no luck. Best regards, Mihai -- Mihai Sucan http://www.robodesign.ro ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Autospawn Contention
Hi, I'm trying to debug a really annoying problem and I think I've come across a bit of a race condition during startup/login relating to autospawning. If an application probes for PA before enabling support for it, and if PA is not running then it will try to autospawn it. Sensible so far, but if, during the time between trying to connect and running the autospawn, some other application has jumped in and grabbed the autospawn lock, the first application fails to launch PA and thus fails to connect and thus PA is detected as not available. This can then cause problems with sound devices being hogged etc. etc. if the app in question falls back to direct output or similar. All in all, it's pretty messy. Is there something we can do to prevent this problem? I'm thinking like something to detect the reason for failure as being autospawn lock failure. This autospawn code could then check for an autospawn lock (owned by another process) and wait for it to be released then say OK, I'm done and attempt the connection again (knowing that someone else has done (or at least tried!) the autospawn for us). Now, the confusing thing is that I believe that this whole process is already done. The autospawn lock is acquired in a blocking capacity. This means that unless the autospawn lock totally fails (which I believe is not likely?), it will be acquired. And if it is acquired, then running pulseaudio --start should succeed fine if it's not already running. Basically, I've had a look at the autospawn locking stuff and I can't see anything immediately obvious that would result in a failure during initial connection unless the whole lock stuff fails. FWIW, the problem I'm trying to debug is here: https://bugs.kde.org/show_bug.cgi?id=232068 The problem I find is that the backtrace indicates that PulseAudio support has NOT been detected - e.g. it tried to connect but then failed. However, a connection is clearly running in another thread. One thing that may be relevant is that this process creates two PA connections and that may in some capacity get in the way (although the initial probe should happen before any attempt to connect to the daemon for the actual audio output). Now there is the crash itself too, which is probably unrelated, but should be fixed too. The main problem I'm interested in is the fact that PA is not being detected as available properly. 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] Problems with mplayer in Ubuntu 10.04
On 2010-05-09 13:06, Mihai Sucan wrote: The problem is with mplayer. I cannot play *any* sound with it, and worse, it causes PulseAudio to go bonkers. Once I start mplayer, I cannot hear any sound, from any application. I tested mplayer from the default Ubuntu repositories [1] and a much newer build from the RVM Ubuntu PPA repository [2] (the author of SMPlayer, if I am not mistaken). Both behave quite much the same. I'm not sure, but this could be worth a look: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580113 ...to see if that is what you have encountered as well, or if it is related. // David ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Problems with mplayer in Ubuntu 10.04
Hello David! Thanks for your reply. Le Sun, 09 May 2010 20:26:38 +0300, David Henningsson launchpad@epost.diwic.se a écrit: On 2010-05-09 13:06, Mihai Sucan wrote: The problem is with mplayer. I cannot play *any* sound with it, and worse, it causes PulseAudio to go bonkers. Once I start mplayer, I cannot hear any sound, from any application. I tested mplayer from the default Ubuntu repositories [1] and a much newer build from the RVM Ubuntu PPA repository [2] (the author of SMPlayer, if I am not mistaken). Both behave quite much the same. I'm not sure, but this could be worth a look: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580113 ...to see if that is what you have encountered as well, or if it is related. The problem does not seem to be related with mine - the mplayer release in Ubuntu repos is much older and I get no errors from MPlayer. In the early days I did get this warning: bt_audio_service_open: connect() failed: Connection refused (111) ... but that was simply because of the bluez-alsa package. I found online info that removing the package solves this minor issue. I removed the package and, indeed, I no longer see the warning. (I do not use bluetooth, so the package removal does not affect my usage.) Other ALSA-based applications play sounds fine, for example Flash Player 10.0. Best regards, Mihai -- Mihai Sucan http://www.robodesign.ro ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] lost all but front L/R channels
I just realized I am only hearing sound out of my front Left and Right speakers. I'm not sure when this started - perhaps after upgrading to Fedora 11. I know in Fedora 10 I had analog from front and rear outputs of my SB Live. I can switch the cables on the sound cards and hear front signal out the rear speakers so I know it's happening within the card. When I run pavumeter I see the remixed signal going out all five channels, and it changes appropriately when I slide rear/front in gnome-volume-mixer, but I hear nothing out the rear. I thought perhaps the rear channel on the soundcard broke, but I get the same result listening to the S/PDIF output. I tried running gamix which once upon a time gave me the ability to change volume on rear independently from the front, but now seems unable to do that. It's like there is a hidden volume control on the other channels that pulseaudio doesn't know about, or I would see the rear muted in pavumeter, right? Thanks, Kyle ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] lost all but front L/R channels
I had profile Output Analog Surround 5.1 + Input Analog Stereo. I also tried 5.0. This is pulseaudio-0.9.15. Perhaps this is a known issue addressed since then? I just tried switching to Digital stereo output and the hardware device disappeared! And now there is no way to switch back... On 05/09/2010 04:06 PM, Tomasz Torcz wrote: On Sun, May 09, 2010 at 02:15:08PM -0500, Kyle Davenport wrote: I just realized I am only hearing sound out of my front Left and Right speakers. I'm not sure when this started - perhaps after upgrading to Fedora 11. I know in Fedora 10 I had analog from front and rear outputs of my SB Live. I can switch the cables on the sound cards and hear front signal out the rear speakers so I know it's happening within the card. Well F11 is quite old and will receive updates for little over one month only. Consider upgrade to F13 :) As for your problem, what hardware profile do you have selected in pavucontrol/gnome-volume-control? Is it really 4.0 or other multichannel? Or maybe you have too old system to have profile selection in place... ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Problems with mplayer in Ubuntu 10.04
'Twas brillig, and Mihai Sucan at 09/05/10 19:27 did gyre and gimble: In the early days I did get this warning: bt_audio_service_open: connect() failed: Connection refused (111) ... but that was simply because of the bluez-alsa package. I found online info that removing the package solves this minor issue. I removed the package and, indeed, I no longer see the warning. Do you have any customisations to your ~/.asoundrc? Perhaps you can test with a fresh user account? 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
[pulseaudio-discuss] config for 2 cards - 1 for pulse; 1 for AC-3 Passthru
Hi All, I've been trying to figure out for some time how to configure my family home theater PC for analog pulse audio out and ALSA digital pass thru for Xine. I'm running Ubuntu 10.04. I've been having some success by removing the pulse library from xine. The issue is that sometimes something happens to the digital port and I no longer get digital sound. The workaround has been to switch the audio output to a second unused but present sound card and reboot. After one or two repeats toggling the sound output between cards I can again have digital sound through one port and analog through another on the same sound card. I had another thought which would be to blacklist my Soundblaster card (which supports the digital passthru) from Pulse and have the analog from Pulse through the onboard sound. Any thoughts on how to fix my initial problem or configure the second scenario? -Scott ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Fixing git branches
On Sat, 2010-05-08 at 14:30 +0100, Colin Guthrie wrote: I've just done a git cherry and pushed 5 patches to master (although one of those I'd only just committed to stable-queue so really master only had 4 missing commits). Excellent, thank you! For some reason I thought stable-queue had diverged more. That git cherry may become handy at some point, thanks also for letting me know about it. -- Tanu Kaskinen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
