Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and?as?the default ALSA plugin doesn't seem to work right.... ?
On Tue, 20.11.07 16:55, Kevin Williams ([EMAIL PROTECTED]) wrote: > > On November 20, 2007 03:14:47 pm Lennart Poettering wrote: > > The suspend timeout is controlled via the "timeout" parameter of > > module-suspend-on-idle. > > I commented that line out now and it still doesn't help in anyway ! > > Running xine with verbose mode gives me the following messages: > > *** PULSEAUDIO: Unable to connect: Invalid argument > *** PULSEAUDIO: Unable to connect: Invalid argument > AFD changed from -2 to -1 It seems that the PA backedn of xine is passing invalid arguments to one of the libpulse API functions, which then returns PA_ERR_INVALID. Any chance you could debug this? i.e. find out which function it exactly is that returns the error and what the parameters are that are passed to it? > My guess is that, pulseaudio is not fast enough to respond to the clients > requests as hitting next/previous with a brief pause say 6-7 seconds > does not Uh? PA not "fast" enough? Unlikely. I don't see any way how "speed" should come into play here. > produce any error message nor does make it the app crash. Hitting > next/previous in quick succession gurantees the error messages followed by a > craash. Hitting next/previous with a gap less than 6 seconds produces the > error message most of the time. But, anything less than 3 secs would > definitely produce those errors. Looks a bit like a memory corruption issue to me. > As I've mentioned before, all the apps work fine when using alsa or arts > without pulseaudio. Hitting next/previous in rapid succession doesn't cause > any problems and it works. > > Any pointers ? Should you need more info I'd be glad to provide. Flameeyes, maybe you have an idea of what is going on? Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Kevin Williams wrote: > The error message I get is "Audio output unavailable. The device is busy. > Xine > engine parameter:". > After a while, the error message changes to "xine was unable to > initialize any audio drivers" !! FWIW, I occasionally get this in Amarok when using the xine+pulse backend. It's probably the same root cause but I've not had enough time to try and track it down yet either. Col ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as?the default ALSA plugin doesn't seem to work right.... ?
On Tue, 20.11.07 14:14, Kevin Williams ([EMAIL PROTECTED]) wrote: > > Thanks a lot for the detailed response. I really appreciate it. > > On November 19, 2007 09:58:37 pm Lennart Poettering wrote: > > My educated guess is that some of your apps use PA natively, others > > don't but hardcode are configured to use the raw ALSA devices, or raw > > OSS devices. Now, PA closes all devices after a short time of > > idle. So, what might happen to you is that you first use a native > > app. That causes PA top open the device. If you then use a non-native > > app, then it won't work. But after the idleness timeout it will > > suddenly and magically start to work, because PA closed the devices. > > Voila ! That explains the weird behaviour seen with all the apps. But, if the > option "exit-idle-time" is responsible then, I don't have it set in > daemon.conf ! exit-idle-time is unrelated to this. The suspend timeout is controlled via the "timeout" parameter of module-suspend-on-idle. > The error message I get is "Audio output unavailable. The device is busy. > Xine > engine parameter:". > After a while, the error message changes to "xine was unable to > initialize any audio drivers" !! > > Any ideas ? No, unfortunately not. It would be helpful if you could get your hands on some more verbose Xine debug output, though. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Lennart Poettering <[EMAIL PROTECTED]> writes: > Last time I checked F8 KDE sets PA up as session-daemon. Last time I tried it wasn't working, I admit it was some time ago, but as I don't really want to enter again the details of KDE configuration on Gentoo, I'll gladly live myself as it is, it works just fine for me as systemwide daemon. > If you run PA as system daemon, than you should use a different > "default.pa", because you certainly don't want to load > module-x11-publish or module-gconf. As you said, to use systemwide instance you need to be more aware of the insight, so I leave those as an exercise to the reader. Actually if you want to use systemwide in Gentoo, the simplest thing is to disable both gnome and X flags for PulseAudio, so that the two modules aren't built at all. In case of gnome flag (gconf module) a warning is displayed after installation. -- Diego "Flameeyes" Pettenò http://farragut.flameeyes.is-a-geek.org/ pgpW3MW8pgBMk.pgp Description: PGP signature ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Tue, 20.11.07 12:15, Andrzej Wasowski ([EMAIL PROTECTED]) wrote: > On Tue, 20 Nov 2007, David Kågedal wrote: > >> My use case is that I connected the good speakers to my closet server >> that has no console login. I then want to be able to redirect my >> laptop streams to the speakers, either using multicast or a tunnel. > > I have a feeling that Lennart somehow undervalues this use of pulseaudio as > an actual network audio server, but given the amount of emails on embedded > systems in this ML, it seems to me that this is the main reason for which > people come to pulseaudio these days. This was at least my reason ... Uh. That's certainly not the case. Making PA a good networked sound server required me to make PA a lot more complex then it would be necssary if it was local-only. Also note that very networkish stuff like module-zeroconf-browse was added by me in 0.9.7 only, i.e. there's a lot of work happening in that area. Networked sound always has been a priority for me and it continues to be. What I am trying to say is that people shouldn't use the system daemon mode if they are not fully aware of the implications of that. i.e. you lose hotplug, you lose SHM data transfer, the whole policy stuff makes no sense anymore, auth becomes a bigger issue, and so on. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Tue, 20.11.07 11:46, Diego 'Flameeyes' Pettenò ([EMAIL PROTECTED]) wrote: > Lennart Poettering <[EMAIL PROTECTED]> writes: > > > I know that Gentoo sets up PA this way. This is against my > > recommendation. > > Hey now! *I* set it as systemwide, but that's my choice. The ebuild > gives you the tools of handling it in any way you want, either as > session instance or systemwide instance. As KDE and session instance > don't seem to work that well, I go for systemwide. Last time I checked F8 KDE sets PA up as session-daemon. > As I do use it, I do make sure that it works, but in pure Gentoo spirit > I don't force anything on users. They have the tool, they configure it. > > Actually, the configuration files are untouched from the default shipped > by PulseAudio, so... :) If you run PA as system daemon, than you should use a different "default.pa", because you certainly don't want to load module-x11-publish or module-gconf. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Tue, 20 Nov 2007, David Kågedal wrote: My use case is that I connected the good speakers to my closet server that has no console login. I then want to be able to redirect my laptop streams to the speakers, either using multicast or a tunnel. I have a feeling that Lennart somehow undervalues this use of pulseaudio as an actual network audio server, but given the amount of emails on embedded systems in this ML, it seems to me that this is the main reason for which people come to pulseaudio these days. This was at least my reason ... Andrzej -- Andrzej Wąsowski, http://www.wasowski.org___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Diego 'Flameeyes' Pettenò wrote: > Lennart Poettering <[EMAIL PROTECTED]> writes: > >> I know that Gentoo sets up PA this way. This is against my >> recommendation. > > Hey now! *I* set it as systemwide, but that's my choice. The ebuild > gives you the tools of handling it in any way you want, either as > session instance or systemwide instance. As KDE and session instance > don't seem to work that well, I go for systemwide. > > As I do use it, I do make sure that it works, but in pure Gentoo spirit > I don't force anything on users. They have the tool, they configure it. > > Actually, the configuration files are untouched from the default shipped > by PulseAudio, so... :) And I'll confirm that PA works just fine with the per-session daemon started using the gnome-session autolauncher. Cheers, Rémi ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Lennart Poettering <[EMAIL PROTECTED]> writes: > I know that Gentoo sets up PA this way. This is against my > recommendation. The only use case for running PA as system-wide > instance is thin clients, where the users using PA are not local. If > that's the only focus of Gentoo than great. But the last time I looked > this wasn't quite the only focus of Gentoo. ;-) My use case is that I connected the good speakers to my closet server that has no console login. I then want to be able to redirect my laptop streams to the speakers, either using multicast or a tunnel. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Lennart Poettering <[EMAIL PROTECTED]> writes: > I know that Gentoo sets up PA this way. This is against my > recommendation. Hey now! *I* set it as systemwide, but that's my choice. The ebuild gives you the tools of handling it in any way you want, either as session instance or systemwide instance. As KDE and session instance don't seem to work that well, I go for systemwide. As I do use it, I do make sure that it works, but in pure Gentoo spirit I don't force anything on users. They have the tool, they configure it. Actually, the configuration files are untouched from the default shipped by PulseAudio, so... :) -- Diego "Flameeyes" Pettenò http://farragut.flameeyes.is-a-geek.org/ pgpyZVLvRxWcI.pgp Description: PGP signature ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Thu, 15.11.07 11:59, Kevin Williams ([EMAIL PROTECTED]) wrote: > > On November 15, 2007 06:17:07 am Diego 'Flameeyes' Pettenò wrote: > > This sounds like a message coming from xine, or at least it is quite > > similar from the xine message expressing the same problem. If this is > > the case, make sure that you're not using hw:0 as device in the xine > > configuration; ideally you should be using the PulseAudio output > > directly (although I know already that the version shipped with 1.1 > > isn't all that good, nor is 1.2 version perfect; I'm working on it). > > I do get similar messages from the audio apps like mplayer, avidemux, rezound > etc. Repeatedly clicking on the play button (which triggers the same message > box every time the play/next/previous button is pressed) a few times makes it > work. Sometimes, relaunching the app is the only way to get it working. > > As far as xine configuration is concerned, I've configured "auto" for both > audio and video and "default" for audio device. I've also tried specifying > alsa and pulseaudio plugin as the output but, to no avail. I get the similar > messages about the audio device not being available. My educated guess is that some of your apps use PA natively, others don't but hardcode are configured to use the raw ALSA devices, or raw OSS devices. Now, PA closes all devices after a short time of idle. So, what might happen to you is that you first use a native app. That causes PA top open the device. If you then use a non-native app, then it won't work. But after the idleness timeout it will suddenly and magically start to work, because PA closed the devices. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Thu, 15.11.07 11:48, Kevin Williams ([EMAIL PROTECTED]) wrote: > > On November 15, 2007 05:46:49 am Colin Guthrie wrote: > > I'm not 100% sure but with 0.9.7 pa I don't think there are many reasons > > to run PA system wide any more. User switching is supported so that > > switching from one user to another work pretty well (tho' I have to > > admit I've not personally tested this!) > > Does that mean, a systemwide instance is not recommended and wouldn't work as > expected, likely to cause problems ? It's not recommended. But it should work as expected -- if you know what you do and set everything up properly. It boils down to this: Lennart isn't especially keen on helping you fixing problems caused by setting up system-wide setup incorrectly. It's more difficult to set up, and more difficult to get right. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Tue, 20.11.07 03:49, Lennart Poettering ([EMAIL PROTECTED]) wrote: > If you use PA this way then local authentication works by membership > in the group pulse-rt. What you described sounds like authentication > errors. So please make sure that all users who try to access PA are in > that group. Oops, that group is "pulse-access", not "pulse-rt". Sorry for the confusion. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On Thu, 15.11.07 02:05, Kevin Williams ([EMAIL PROTECTED]) wrote: > I have installed pulseaudio from the cvs repo and have configure the PA > daemon > to run as a system wide instance. To ensure all the apps work without needing > to configure each of them individually, I have set the pulseaudio as the > default ALSA plugin in /etc/asound.conf following the guide "Perfect Setup". > > PA lauches without any problems. But, the problem shows up when I launch any > of the multimedia apps. Sometimes, I see a message which says "Audio device > not available. May be it is in use by another application". I'm pretty sure, > there're no other apps at that same time yet, I receive those messages, don't > know why !?? If you set up PA as a system-wide instance you need to configure things differently than when using it per-session. If you run it as system-wide daemon than you are expected to understand very well what is happening. I do not recommend to run it as system daemon. I know that Gentoo sets up PA this way. This is against my recommendation. The only use case for running PA as system-wide instance is thin clients, where the users using PA are not local. If that's the only focus of Gentoo than great. But the last time I looked this wasn't quite the only focus of Gentoo. ;-) If you use PA this way then local authentication works by membership in the group pulse-rt. What you described sounds like authentication errors. So please make sure that all users who try to access PA are in that group. Again, if you use PA as system daemon, then it is your own fault if things don't work as expected. You are expected to know what you do if you run PA in this mode. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On 17 Nov 2007, Kevin Williams stated: > On November 16, 2007 07:59:35 pm Nix wrote: >> Well it works for me without any of the problems you've mentioned. >> >> Which apps are you seeing this behaviour with? How are they talking to >> the sound system? (ALSA, OSS, native PulseAudio...) > > Well, the way I've setup is launch pulseaudio as the systemwide daemon with > alsa-sink module while ALSA is configured to use pulseaudio as the default > driver. Likewise, only alsa-sink isn't working for me so it's defaulting to oss-sink. (But it used to work with alsa-sink.) > The above setup works perfectly well, if I stop using pulseaudio and leaving > alsa as the only audio server. With pulseaudio as the system daemon the > earlier mentioned problmes start to appear. Almost all the apps complain > about the audio device being not available. Amarok also, complains the same > but, at times it doesn't and there's no sound output though, I can see that > the file is being played. Just checking here: if you set up /etc/asound.conf to use device pulse by default, and set up PulseAudio to use alsa without specifying a different device, I suspect you'll get an infinite regression. :) Personally I've set up alsa to use pulse in my ~/.asound.conf, and left the systemwide one alone: that seems to work. > I've just setup pulseaudio to launch as per user instance and quite > surprisingly (or may be not ?), all the apps are working just perfect ! :-) Weird. My explanation must be wrong, then, but I don't know what the real explanation might be. -- `Some people don't think performance issues are "real bugs", and I think such people shouldn't be allowed to program.' --- Linus Torvalds ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On November 16, 2007 07:59:35 pm Nix wrote: > Well it works for me without any of the problems you've mentioned. > > Which apps are you seeing this behaviour with? How are they talking to > the sound system? (ALSA, OSS, native PulseAudio...) Well, the way I've setup is launch pulseaudio as the systemwide daemon with alsa-sink module while ALSA is configured to use pulseaudio as the default driver. I have left all the multimedia apps at their default audio setup which happens to be auto for most while, I've setup the others to use alsa as the default audio driver. For eg. xine and all the apps using the xine engine use the "auto" setup for audio while, I've setup mplayer and avidemux to use alsa. The above setup works perfectly well, if I stop using pulseaudio and leaving alsa as the only audio server. With pulseaudio as the system daemon the earlier mentioned problmes start to appear. Almost all the apps complain about the audio device being not available. Amarok also, complains the same but, at times it doesn't and there's no sound output though, I can see that the file is being played. I've just setup pulseaudio to launch as per user instance and quite surprisingly (or may be not ?), all the apps are working just perfect ! :-) I guess, the problem lies with pulseaudio running as the system daemon !? Anyways, thank everyone for your help, I really appreciate it. Kevin > On 15 Nov 2007, Kevin Williams uttered the following: > > On November 15, 2007 05:46:49 am Colin Guthrie wrote: > >> I'm not 100% sure but with 0.9.7 pa I don't think there are many reasons > >> to run PA system wide any more. User switching is supported so that > >> switching from one user to another work pretty well (tho' I have to > >> admit I've not personally tested this!) > > > > Does that mean, a systemwide instance is not recommended and wouldn't > > work as expected, likely to cause problems ? > > Well it works for me without any of the problems you've mentioned. > > Which apps are you seeing this behaviour with? How are they talking to > the sound system? (ALSA, OSS, native PulseAudio...) ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On 15 Nov 2007, Kevin Williams uttered the following: > On November 15, 2007 05:46:49 am Colin Guthrie wrote: >> I'm not 100% sure but with 0.9.7 pa I don't think there are many reasons >> to run PA system wide any more. User switching is supported so that >> switching from one user to another work pretty well (tho' I have to >> admit I've not personally tested this!) > > Does that mean, a systemwide instance is not recommended and wouldn't work as > expected, likely to cause problems ? Well it works for me without any of the problems you've mentioned. Which apps are you seeing this behaviour with? How are they talking to the sound system? (ALSA, OSS, native PulseAudio...) -- `Some people don't think performance issues are "real bugs", and I think such people shouldn't be allowed to program.' --- Linus Torvalds ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Kevin Williams wrote: > I have installed pulseaudio from the cvs repo and have configure the PA > daemon > to run as a system wide instance. To ensure all the apps work without needing > to configure each of them individually, I have set the pulseaudio as the > default ALSA plugin in /etc/asound.conf following the guide "Perfect Setup". I'm not 100% sure but with 0.9.7 pa I don't think there are many reasons to run PA system wide any more. User switching is supported so that switching from one user to another work pretty well (tho' I have to admit I've not personally tested this!) > PA lauches without any problems. But, the problem shows up when I launch any > of the multimedia apps. Sometimes, I see a message which says "Audio device > not available. May be it is in use by another application". I'm pretty sure, > there're no other apps at that same time yet, I receive those messages, don't > know why !?? Are the users in the relevant group for accessing pulse? IIRC the default is "pulse-access" Col ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
Kevin Williams <[EMAIL PROTECTED]> writes: > Sometimes, I see a message which says "Audio device not > available. May be it is in use by another application". I'm pretty > sure, there're no other apps at that same time yet, I receive those > messages, don't know why !?? This sounds like a message coming from xine, or at least it is quite similar from the xine message expressing the same problem. If this is the case, make sure that you're not using hw:0 as device in the xine configuration; ideally you should be using the PulseAudio output directly (although I know already that the version shipped with 1.1 isn't all that good, nor is 1.2 version perfect; I'm working on it). -- Diego "Flameeyes" Pettenò http://farragut.flameeyes.is-a-geek.org/ pgpwLyvy9CSgS.pgp Description: PGP signature ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On November 15, 2007 05:46:49 am Colin Guthrie wrote: > I'm not 100% sure but with 0.9.7 pa I don't think there are many reasons > to run PA system wide any more. User switching is supported so that > switching from one user to another work pretty well (tho' I have to > admit I've not personally tested this!) Does that mean, a systemwide instance is not recommended and wouldn't work as expected, likely to cause problems ? > Are the users in the relevant group for accessing pulse? IIRC the > default is "pulse-access" Yes, the user is a member of the pulse-access group. Thanks for the reply. Kevin > Kevin Williams wrote: > > I have installed pulseaudio from the cvs repo and have configure the PA > > daemon to run as a system wide instance. To ensure all the apps work > > without needing to configure each of them individually, I have set the > > pulseaudio as the default ALSA plugin in /etc/asound.conf following the > > guide "Perfect Setup". > > I'm not 100% sure but with 0.9.7 pa I don't think there are many reasons > to run PA system wide any more. User switching is supported so that > switching from one user to another work pretty well (tho' I have to > admit I've not personally tested this!) > > > PA lauches without any problems. But, the problem shows up when I launch > > any of the multimedia apps. Sometimes, I see a message which says "Audio > > device not available. May be it is in use by another application". I'm > > pretty sure, there're no other apps at that same time yet, I receive > > those messages, don't know why !?? > > Are the users in the relevant group for accessing pulse? IIRC the > default is "pulse-access" > > Col > > ___ > 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
Re: [pulseaudio-discuss] Pulseaudio as a systemwide deamon and as the default ALSA plugin doesn't seem to work right.... ?
On November 15, 2007 06:17:07 am Diego 'Flameeyes' Pettenò wrote: > This sounds like a message coming from xine, or at least it is quite > similar from the xine message expressing the same problem. If this is > the case, make sure that you're not using hw:0 as device in the xine > configuration; ideally you should be using the PulseAudio output > directly (although I know already that the version shipped with 1.1 > isn't all that good, nor is 1.2 version perfect; I'm working on it). I do get similar messages from the audio apps like mplayer, avidemux, rezound etc. Repeatedly clicking on the play button (which triggers the same message box every time the play/next/previous button is pressed) a few times makes it work. Sometimes, relaunching the app is the only way to get it working. As far as xine configuration is concerned, I've configured "auto" for both audio and video and "default" for audio device. I've also tried specifying alsa and pulseaudio plugin as the output but, to no avail. I get the similar messages about the audio device not being available. FYI, I've compiled KDE-3.5.8 with "--without--arts" since, I didn't want multiple audio servers piggy back riding each other ! The apps work fine otherwise when I'm not using pulseaudio thus, using the alsa drivers directly. Thanks for the reply. Kevin > Kevin Williams <[EMAIL PROTECTED]> writes: > > Sometimes, I see a message which says "Audio device not > > available. May be it is in use by another application". I'm pretty > > sure, there're no other apps at that same time yet, I receive those > > messages, don't know why !?? > > This sounds like a message coming from xine, or at least it is quite > similar from the xine message expressing the same problem. If this is > the case, make sure that you're not using hw:0 as device in the xine > configuration; ideally you should be using the PulseAudio output > directly (although I know already that the version shipped with 1.1 > isn't all that good, nor is 1.2 version perfect; I'm working on it). ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
