Hi all,
CC'ing the bug, so everything is recorded.
On Thu, Jan 20, 2005 at 01:05:20AM +0100, [EMAIL PROTECTED] wrote:
> Esteban Manchado Velázquez zoso-at-foton.es |bugs-debian| wrote:
> >Hi all,
> >
> > It seems that the problem could easily be fixed calling psi as "esddsp
> >psi". Perhaps we could make a fake /usr/bin/psi that would call psi as
> >"/usr/bin/psi.real", "esddsp /usr/bin/psi.real" or "artsdsp
> >/usr/bin/psi.real", depending on "esd" or "artsd" being present.
> >
> > Do you like the idea?
>
> Well, to be honest, not really.
> Emulating a sound device on top of another API makes things slow and
> prone to breakage. Psi has the possibility to use whatever program you
> like for playing sounds, so I would suggest to make use of it. Ideally I
> would create a simple shell script which takes a sound file as an
> argument and calls the appropriate sound player, esdplay with esound for
> example. This shell script should then be the default for playing sounds
> with psi.
>
> The main problem for such a script is the same as mentioned above: How
> do I detect which program to use? There are several possibilities. I
> could grep "dpkg -l" or I could grep "dpkg --get-selections" or I could
> test for the existence of esdplay/artsplay (is this the correct binary?)
> (but on which path: Debian default path, all paths in $PATH, whatever).
> Is there a Debian way for this problem? Opinions? Thoughts?
I would just do a "ps ax | grep whatever", as you can have both installed.
The really important thing is whether you have one of them _running_, not if
you have them _installed_.
> BTW, if there was such a "sound playing script" this script could be
> used for all programs which need to output sound, not just for psi. You
> could for example use the same script in Mozilla when a sound is played
> on a new message arrived. Cf sensible-browser, sensible-editor,
> sensible-editor. How does one introduce sensible-audioplayer?
Yes, that sounds really good. sensible-* are into debianutils, so I guess
we can file a bug against that package (_and_ write the script, of course) :-)
BTW, should it manage only wav/au files, or "any" kind of sound file? I
guess it should manage "any" kind of file, calling mpg321 or whatever, but
that would raise the bar... and, if not, we should probably call it
sensible-wavplayer or sensible-soundplayer, so people don't think it's a full
blown audio player...
--
Esteban Manchado Velázquez <[EMAIL PROTECTED]> - http://www.foton.es
EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es
signature.asc
Description: Digital signature
