Re: [pulseaudio-discuss] Not only autospawning, but all PA daemon startup of any kind appears impossible with PA trunk
'Twas brillig, and Nix at 29/05/10 11:19 did gyre and gimble: Things get clearer. (Sorry for the delay: jobhunting hell.) On 17 May 2010, Tanu Kaskinen told this: That seemed strange, because the X11 properties are set automatically, and the user probably usually doesn't know anything about the existence of the X11 properties. That means that if an user sets an address for a remote server in client.conf, that won't have any effect if start-pulseaudio-x11 is used (and it is used in most cases), and the user won't have any idea why it's not working. As opposed to now, where I do in fact run start-pulseaudio-x11, and had no idea why it wasn't working until I looked at the source code :/ Yeah, clearly that is not a good situation :s 16:50 coling tanuk, but the way it works is that the PULSE_SERVER prop actually contains multiple addresses... a local socket, a tcp6 address, a tcp4 address etc. Ah, yes, I forgot about this feature. This surely makes it even *more* important that the server starts when the client asks it to, because you might be starting a server earlier on the preference list than the one you're already using. But your comments below make the rationale clearer: I just wish there was a less aggravating way to do it. Well that's a tricky situation to resolve. If I ssh to another machine, I specifically want the earlier (higher preference) servers in the list to fail so that I fall back to network and get the sound out of my local machine. The last thing I want is for PA to think Hmm, I'm connected, but not to the first server and try and spawn one. That said, local socket paths in the PULSE_SERVER var are prefixed with the dbus machine id. If the machine id == this machine, and we cannot connect to the server, it's pretty likely that we need to start a local server. I not sure under what circumstances this logic would fail - su'ing to another user while the X11 props are there and the server died will break, but it's quite a corner case. 17:30 coling i.e. the idea is that if a default server is specified in client.conf, then the daemon wont be started and the x11 modules wont load and the x11 prop wont be set. Aha, so the idea is that PULSE_SERVER should specify your local server, then every remote server it might possibly want, in preference order, More or less by by default, it is used to specify the *same* PA server, accessible via different means. e.g. local, tcp6 and tcp4. That way local apps, running locally will use a local socket and remote apps running after SSHing to a remote machine will use some tcp variant. and that it should get set after PA itself starts. How strange. How else can we know what the patch to the local socket will be without starting PA (or at lease using the client libraries)? These settings are a reflection of the running server, not a pointer to where it should be. If the server crashes, the configuration *should* die with it, but that is not always possible. The x11-publish module will remove the X11 properties when shut down cleanly, but a crash.. (Also sort of impractical if you have a server that serves several hundred desktops: what's PULSE_SERVER going to do, specify them all? The order would differ between users, so in pradtice you still need to dynamically compute it.) Not sure what you mean by a server that serves several hundred desktops. On such a scale, it's very unlikely that the desktop machine itself would be responsible for starting the daemon and thus any configuration would have to be written on top of PA, not be part of it. But perhaps I don't understand your setup? (But still, a server that won't start because an environment variable is set telling *client* programs where to look for that very server? What a horrible idea.) I don't necessarily disagree, but the same logic that applies to autospawning, (triggered by the *client*) should really apply to how the server itself is started too, so there is some logic in keeping them tied together like that. 16:26 mezcalero tanuk: the start-pulseaudio-x11 script should probably refuse to do anything if there is already a server configured by some means Agreed. I suspect the right way to detect this is to *try to connect to it*, not just to use PULSE_SERVER as an (easily erroneous) promise that the server is already running. It's sort of strange for a PA server to do this (which is normally the responsibility of the client), so perhaps what we need is a pulseaudio ping program (part of pactl probably), and have start-pulseaudio-x11 run that to see if the server is already up, rather than have pulseaudio itself check for any such thing. It takes a tiny bit longer, but who cares if startup forks one more time? It's not as if we start up every five minutes. Ohh, have you not read Lennart's systemd stuff - beware the forks!!! :p But seriously, I think the pulse server variable should be checked to see if it
Re: [pulseaudio-discuss] console volume control
'Twas brillig, and Brandon Kuczenski at 23/05/10 21:01 did gyre and gimble: Would it be appropriate to write an ncurses (do people still use ncurses?) client that uses pactl as a backend? maybe something more integrated would be desirable. If an ncurses interface was written, please use libpulse and not a command line wrapper around pactl... it'll be far easier anyway :p 'pavucontrol' works from a local terminal but doesn't seem to work when logged in remotely- I get a gnome dialog [so it's not an X problem] saying 'connection refused' I don't know off-hand what's wrong. What's the setup? So far I know that you have a server and a client, and X is running on the client, and you are trying to run pavucontrol on the server. The only client-server relationship is in X. I was expecting to control the remote machine's volume control using a dialog that would appear on the local machine's display: classic X11 forwarding. Ahh but Pulse piggy backs on to the X11 protocol so that if you ssh to a remote machine and run an app, you will get both the display and the audio that app produces on your *local* machine. I guess your expectation is understandable, but by the same token, more people prefer things to work seemlessly. If you want to know more about how this process works, see here: http://colin.guthr.ie/2009/08/sound-on-linux-is-confusing-defuzzing-part-2-pulseaudio/ You can always ensure that you run pax11publish -r first and that way a remote PA daemon will be used instead. But this is not important or desirable to me anymore since I suspect I can accomplish my task using pactl. Bear in mind that even if you do ssh to a remote machine, if the X11 properties on the root window are set as they are by default, then pactl will control the PA deamon on your local machine via the network protocol. pacmd will likely not work as it uses a different interface. If you read and understand the above article, this should make sense :) 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] Pull request: Various small fixes
'Twas brillig, and Tanu Kaskinen at 24/05/10 13:38 did gyre and gimble: On Mon, 2010-05-10 at 15:33 +0300, Kaskinen Tanu wrote: Hello, I've been sitting on a bunch of fixes, mostly for my own D-Bus code. Now I've pushed (most of) them to Gitorious: git://gitorious.org/~tanuk2/pulseaudio/pulseaudio.git Ping? According to http://pulseaudio.org/wiki/Community#BugsPatchesTranslations the preferred method of submitting patches is by filing tickets, and the next best choice is sending them to the mailing list. So, if pulling from Gitorious isn't so hot, please tell me so and I'll file tickets (or send the patches to the mailing list or whatever, in case the wiki is outdated). Branches are good. Lennart's been away and I've been a bit busy (and not really playing much with master anyway), but if he doesn't pull then in soon, I promise I'll do it by the weekend :) 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] How to contribute
Hello all, I'm new on this mailing list. I'm working at Intel and we will probably have to bring some contributions to pulseaudio. I'd like to know the good way to bring contributions to the project. I've already read the coding style page (http://www.pulseaudio.org/wiki/CodingStyle) but would like to know if there is a specific process to follow. Or if it's just git-cloning the project, create a local branch and push it when the work is done. Thanks for your help Regards, Sylvain - Intel Corporation SAS (French simplified joint stock company) Registered headquarters: Les Montalets- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] PulseAudio Applet Gnome icon
Hello, I have Debian Squeeze OS with Gnome, I installed PulseAudio and it works great. The version is Package: pulseaudio (0.9.21-1). I have a little problem with PulseAudio Applet icon on the system try, there is not any icon: http://i45.tinypic.com/v6q8o5.png Where I can config it? Thanks and regards -- Josu Lazkano ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] M-audio fasttrack pro: fix input device string
On 2010-05-25 01:26, Lennart Poettering wrote: On Wed, 19.05.10 01:00, David Henningsson (launchpad@epost.diwic.se) wrote: Heya, Sometimes the input device shows up at device ID 0, and sometimes device ID 1, so try both. Humpf. Why is that so? The driver authors presumably have a reason for this assignment, and before we merge something like this we should figure out what's going on and how we should label this. We currently label that mapping Analog Streo Channel A. It appears to me that that mapping label might not be accurate anymore after such a change. AFAIK this sound card is just using the standard USB Audio drivers. I don't have access to this particular hardware either, so I'm not in a position to debug the drivers ATM. So I can't answer your question and my guess is that it varies between hardware revisions. Perhaps David Kågedal, who wrote the initial profile, knows more about this? // David ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] PulseAudio Applet Gnome icon
'Twas brillig, and Josu Lazkano at 01/06/10 09:45 did gyre and gimble: Hello, I have Debian Squeeze OS with Gnome, I installed PulseAudio and it works great. The version is Package: pulseaudio (0.9.21-1). I have a little problem with PulseAudio Applet icon on the system try, there is not any icon: http://i45.tinypic.com/v6q8o5.png Where I can config it? The PulseAudio Applet I'm guessing is padevchooser? If so, this is not longer supported or recommended for general usage. It sets strange settings that interfere with proper usage and thus was deprecated a couple years ago. But to answer the question, it likely uses the audio-card icon. This should be part of your icon theme - it's used in several other places too. 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] How to contribute
Hi Sylvain, 'Twas brillig, and Pichon, SylvainX at 01/06/10 09:26 did gyre and gimble: I’m new on this mailing list. Welcome aboard! I’m working at Intel and we will probably have to bring some contributions to pulseaudio. Excellent :D I’d like to know the good way to bring contributions to the project. I’ve already read the coding style page (http://www.pulseaudio.org/wiki/CodingStyle) but would like to know if there is a specific process to follow. Following the coding style is very much recommended Lennart (IRC: mezcalero) has special powers to spot // comments in code . he really doesn't like them - /* */ all the way :p Personally I'd have preferred to have the super power of invisibility or xray vision, but I guess you can't pick and and choose what radio-active bug bites will do to you Or if it’s just git-cloning the project, create a local branch and push it when the work is done. Yeah, just clone it and then push it back to a publiccally available git repository somewhere and then ask for a pull request on the list - preferably including at least a general overview and a shortlog of the changes. A full log with diffs is also fine. Alternatively, git email direct to the list is also perfectly acceptable. Attaching patches to specific tickets is fine too, but Trac is a bit weird when adding attachments as it doesn't seem to send out email notifications to the list for attachments, so probably best to avoid this route (or add a comment to the bug after attaching to ensure someone notices :p) If the changes are relatively trivial/uncontroversial then I can merge them in. If they are more fundamental then I usually defer to Lennart to do the merging/reviewing etc. seeing as he is the PA guru. Feel free to hang out in IRC at #pulseaudio. I'm coling there. I look forward to your contributions! Cheers 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 Applet Gnome icon
2010/6/1 Colin Guthrie gm...@colin.guthr.ie: 'Twas brillig, and Josu Lazkano at 01/06/10 09:45 did gyre and gimble: Hello, I have Debian Squeeze OS with Gnome, I installed PulseAudio and it works great. The version is Package: pulseaudio (0.9.21-1). I have a little problem with PulseAudio Applet icon on the system try, there is not any icon: http://i45.tinypic.com/v6q8o5.png Where I can config it? The PulseAudio Applet I'm guessing is padevchooser? If so, this is not longer supported or recommended for general usage. It sets strange settings that interfere with proper usage and thus was deprecated a couple years ago. But to answer the question, it likely uses the audio-card icon. This should be part of your icon theme - it's used in several other places too. 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 Thank you for you reply Col, now I have a beautiful panel, xD. Why is not recommended to use it? I use it to change between my laptop speakers and a bluetooth headset. Is there any command line option to change between thoose two devices? Thanks and regards. -- Josu Lazkano ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] How to contribute
Hi, Thanks a lot for the quick and complete answer! And I agree with you, I would have preferred xray vision as well :-) Sylvain -Original Message- From: pulseaudio-discuss-boun...@mail.0pointer.de [mailto:pulseaudio-discuss-boun...@mail.0pointer.de] On Behalf Of Colin Guthrie Sent: Tuesday, June 01, 2010 1:47 PM To: pulseaudio-discuss@mail.0pointer.de Subject: Re: [pulseaudio-discuss] How to contribute Hi Sylvain, 'Twas brillig, and Pichon, SylvainX at 01/06/10 09:26 did gyre and gimble: I’m new on this mailing list. Welcome aboard! I’m working at Intel and we will probably have to bring some contributions to pulseaudio. Excellent :D I’d like to know the good way to bring contributions to the project. I’ve already read the coding style page (http://www.pulseaudio.org/wiki/CodingStyle) but would like to know if there is a specific process to follow. Following the coding style is very much recommended Lennart (IRC: mezcalero) has special powers to spot // comments in code . he really doesn't like them - /* */ all the way :p Personally I'd have preferred to have the super power of invisibility or xray vision, but I guess you can't pick and and choose what radio-active bug bites will do to you Or if it’s just git-cloning the project, create a local branch and push it when the work is done. Yeah, just clone it and then push it back to a publiccally available git repository somewhere and then ask for a pull request on the list - preferably including at least a general overview and a shortlog of the changes. A full log with diffs is also fine. Alternatively, git email direct to the list is also perfectly acceptable. Attaching patches to specific tickets is fine too, but Trac is a bit weird when adding attachments as it doesn't seem to send out email notifications to the list for attachments, so probably best to avoid this route (or add a comment to the bug after attaching to ensure someone notices :p) If the changes are relatively trivial/uncontroversial then I can merge them in. If they are more fundamental then I usually defer to Lennart to do the merging/reviewing etc. seeing as he is the PA guru. Feel free to hang out in IRC at #pulseaudio. I'm coling there. I look forward to your contributions! Cheers 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 - Intel Corporation SAS (French simplified joint stock company) Registered headquarters: Les Montalets- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] M-audio fasttrack pro: fix input device string
David Henningsson launchpad@epost.diwic.se writes: On 2010-05-25 01:26, Lennart Poettering wrote: On Wed, 19.05.10 01:00, David Henningsson (launchpad@epost.diwic.se) wrote: Heya, Sometimes the input device shows up at device ID 0, and sometimes device ID 1, so try both. Humpf. Why is that so? The driver authors presumably have a reason for this assignment, and before we merge something like this we should figure out what's going on and how we should label this. We currently label that mapping Analog Streo Channel A. It appears to me that that mapping label might not be accurate anymore after such a change. AFAIK this sound card is just using the standard USB Audio drivers. I don't have access to this particular hardware either, so I'm not in a position to debug the drivers ATM. So I can't answer your question and my guess is that it varies between hardware revisions. Perhaps David Kågedal, who wrote the initial profile, knows more about this? I haven't seen it switch between device IDs, so I have no idea. But I didn't really use it a lot with my linux machine, so the testing has been light. But it worked without problem. -- David Kågedal ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] PulseAudio Applet Gnome icon
'Twas brillig, and Josu Lazkano at 01/06/10 13:11 did gyre and gimble: Thank you for you reply Col, now I have a beautiful panel, xD. Why is not recommended to use it? I use it to change between my laptop speakers and a bluetooth headset. It's not recommended because it changes settings that apps connect directly to different servers rather than using the recommended tunnel approach. In your use case it doesn't matter too much, but the technique still means that the stream you want to move has to be configured before it's established rather than moving it live. The fallback/default option in pavucontrol works in a similar way (it is different internally, but the net result to the user is the same). But using pavucontrol to move live streams is much better. You can move them back and forth quite happily. PA should remember which apps should play on which device by default. Is there any command line option to change between thoose two devices? There are command line tools but they are complex to use. pactl is the primary 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
