David K?gedal <davidk at lysator.liu.se> writes: > Lennart Poettering <lennart at poettering.net> writes: > >> On Fri, 30.10.09 08:15, Brian J. Murrell (brian at interlinx.bc.ca) wrote: >> >>> On Fri, 2009-10-30 at 02:11 +0100, Lennart Poettering wrote: >>> > >>> > This is admittedly a problem, but I kinda hope that it will fix >>> > itself by applications tagging event sounds properly. >>> >>> I'm sceptical. >>> >>> > 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. >>> >>> In the meanwhile, is there anything I can do manually to effect this? >>> Command line is just fine with me in the interim. >> >> You can just tag your streams properly via env vars, as already >> pointed out, and then use the system sound slider: >> >> $ PULSE_PROP='media.role=event' metacity > > The code on http://pulseaudio.org/wiki/ApplicationProperties seems to > set this instead: > > $ PULSE_PROP_media.role=event metacity > > Does both work, or am I just confused? And by the way, neither is mentioned in http://pulseaudio.org/wiki/FAQ#WhatenvironmentvariablesdoesPulseAudiocareabout -- David K?gedal
