On Wed, 2009-04-22 at 21:14 +0100, Bastien Nocera wrote: > On Wed, 2009-04-22 at 14:51 -0500, Callum Lerwick wrote: > <snip> > > > I don't know what Pidgin uses, but spitting out alert sounds using > > > paplay is unlikely to work well at all. > > > > Why not? Small processes working together is the Unix way. But people > > seem to have forgotten that. > > Because paplay doesn't know it's playing a sound event, music, or audio > from a softphone. I also gave the work-around to avoid the change of > volume with flat-volumes enabled. Well then you GIVE it the ability to do so. Are you not a programmer? Make paplay do this: paplay --role event alert.wav And apparently there IS a way to make it work, with the env variables you keep mentioning. (... why would paplay be playing audio from a softphone?) > > Pidgin doesn't exactly have low latency requirements. > > > > > You need to set the > > > "PULSE_PROP_media.role=event" envvar before launching paplay. Otherwise > > > it thinks paplay is a normal, say, music application and will change the > > > volumes. > > > > > > That's a good use of your patch action: port Pidgin to use libcanberra. > > > > How about a command line interface to libcanberra? > > PULSE_PROP_media.role=event paplay
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
