[pulseaudio-discuss] I added a wiki section for pulse based projects and software
If you take a look at the bottom of the pulseaudio community page: http://www.pulseaudio.org/wiki/Community you will notice a new section for listing projects based on/around pulseaudio. I don't have access to edit the primary wiki index and couldn't really think of a better spot to put this section. The community page seems to currently be focused on the group of people devving the actual pulse project, but I figured an expansion of the definition might work. Please let me know if you have any complaints/recommendations and I would be happy to reformat or move the section. Matt ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCH] attach X11 properties to Screen, not Display
On Tue, 27.10.09 19:57, Leszek Koltunski (les...@koltunski.pl) wrote: > 1) Formatting corrected > 2) Fallback to screen 0 added. It works: Thanks a lot! Applied. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net 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] setting a volume on a short lived stream
On Thu, 29.10.09 15:43, Jeremy Nickurak (jer...@nickurak.ca) wrote: > > That does rely on applications behaving well. > > What about a short-lived alsa audio program? There should be a way to > apply a match to these too... maybe a history of streams? Or simply a > minimum time that streams live in pavumeter before it disappears? This is admittedly a problem, but I kinda hope that it will fix itself by applications tagging event sounds properly. Even for legacy applications you can do that with minimal work most of the time: http://pulseaudio.org/wiki/ApplicationProperties I certainly would make sense to allow volume changes shortly after a stream died. The low-level technology in PA allows that, it's just that g-v-c and pavucontrol currently do not make use of this. But then again, I am wondering if the time you need to fix g-v-c/pavucontrol this way wouldn't be better spend in fixing the applcitions in question to tag their streams properly. I think generally only event sounds are short-lived anyway (at least noone was ever able to give me a convincing counter-example). Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net 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] setting a volume on a short lived stream
That does rely on applications behaving well. What about a short-lived alsa audio program? There should be a way to apply a match to these too... maybe a history of streams? Or simply a minimum time that streams live in pavumeter before it disappears? On Thu, Oct 29, 2009 at 15:13, Colin Guthrie wrote: > 'Twas brillig, and Brian J. Murrell at 29/10/09 19:55 did gyre and gimble: >> >> How could I set the volume (i.e. with pavucontrol) for a short lived >> audio stream such as the beep that metacity now delivers, for example >> when you echo ^G? >> >> Using PA 0.9.19 now. > > This beeb should be marked with media.role=event and thus should be > adjustable via the "Sound Events" slider in pavucontrol should control your > volume. That said, I'm not 100% certain how metacity produces this sound, > but I suspect it's via libcanberra in which case it's definitely setup like > that. > > 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 mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] setting a volume on a short lived stream
'Twas brillig, and Brian J. Murrell at 29/10/09 19:55 did gyre and gimble: How could I set the volume (i.e. with pavucontrol) for a short lived audio stream such as the beep that metacity now delivers, for example when you echo ^G? Using PA 0.9.19 now. This beeb should be marked with media.role=event and thus should be adjustable via the "Sound Events" slider in pavucontrol should control your volume. That said, I'm not 100% certain how metacity produces this sound, but I suspect it's via libcanberra in which case it's definitely setup like that. 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] setting a volume on a short lived stream
How could I set the volume (i.e. with pavucontrol) for a short lived audio stream such as the beep that metacity now delivers, for example when you echo ^G? Using PA 0.9.19 now. Cheers, b. signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] regression with tsched=0 and small fragments?
> If you compare the output of snd_pcm_dump() for 0.9.15 and 0.9.19 on > your card, is there any obvious difference? > > (snd_pcm_dump() is called as part of the normal setup these days and > dumped to stderr when debug logging is on. the snd_pcm_dump() output > looks like this: http://fpaste.org/X9Vh/) Nah, it's the same output. The Alsa configuration looks like a false lead. I will try to see at what point the error occurred. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Automatic selection of an audio sink depending on value of ENV variable
On Thu, 29.10.09 16:36, Leszek Koltunski (les...@koltunski.pl) wrote: > > > > Look at pulseaudio.desktop and start-pulseaudio-x11. These do exactly that > > just now. > > > > The script would need modified for this use case (as it registers X session > > handler too, not just the publication) but in theory, just running > > start-pulseaudio-x11 on each display should get you the necessary gubbins > > loaded (albeit one of session modules will fail to load, but you can > > probably just ignore that - the error is suppressed anyway). > > > Hmm.. in that case my patch does not finish the job - potential users still > have to modify the /usr/bin/start-pulseaudio-x11 binary in order to load the > modules the right way. > > Couldn't we have something like '/etc/pulse/x11.conf' which would be read by > /usr/bin/start-pulseaudio-x11 ? I could cook something like that together, > but would that be accepted? Comments? I thought about that too. And I think it would make sense. However this should be a .pa file the same way as system.pa and default.pa, maybe called session.pa. However, I am not entirely sure how to implement this best. Just piping that file to pacmd is not enough since we need to do variable substitution. I haven't fully made my mind up on this yet. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] [Fwd: Re: [Jack-Devel] pa vs jack2]
Please find below some details from Jack2 dev nedko on the dbus-specifics, with relation to a recent topic on starting module-jack-sink/source on surrendering control of the sound card to Jack. Patrick Shirkey writes: > Hi, > > I just spotted this on the pa list. > > https://tango.0pointer.de/pipermail/pulseaudio-discuss/2009-October/005302.html > > == > >> I'm sure the Jack folk know better than I on the D-Bus name, but >> jack_control status seems to work fine to tell me when Jack is ready for >> use, and it communicates via dbus as well... > > Last time I checked they had a name they were picking before > actually spawning off the jack audio daemon. As long as things are > that way round this is not useful for PA's needs. > > == > > > Can anyone confirm or deny? Seems to be a bit of a blocker to proper > dbus integration if PA cannot work with the existing jack2 method for > registering a name with dbus. "jack_control status" does not check whether dbus name is owned. It checks whether JACK server is started. There are also a D-Bus signals that are emited when JACK server starts/stops. D-Bus name is reserved when controller is activated and that has nothing to do with whether JACK server is started. The controller object is the one who starts JACK server. It is a persistent endpoint to control and monitor JACK server. So, if pulseaudio needs polling, it can use the org.jackaudio.JackControl.IsStarted() method. If it needs notification mechanism, it should subscribe for the org.jackaudio.JackControl.ServerStarted and org.jackaudio.JackControl.ServerStopped signals. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Automatic selection of an audio sink depending on value of ENV variable
> > Look at pulseaudio.desktop and start-pulseaudio-x11. These do exactly that > just now. > > The script would need modified for this use case (as it registers X session > handler too, not just the publication) but in theory, just running > start-pulseaudio-x11 on each display should get you the necessary gubbins > loaded (albeit one of session modules will fail to load, but you can > probably just ignore that - the error is suppressed anyway). Hmm.. in that case my patch does not finish the job - potential users still have to modify the /usr/bin/start-pulseaudio-x11 binary in order to load the modules the right way. Couldn't we have something like '/etc/pulse/x11.conf' which would be read by /usr/bin/start-pulseaudio-x11 ? I could cook something like that together, but would that be accepted? Comments? ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
