--- Guillaume Cottenceau <[EMAIL PROTECTED]> wrote:
> Eugenio Diaz <[EMAIL PROTECTED]> writes:
>
> > --- Guillaume Cottenceau <[EMAIL PROTECTED]> wrote:
> > > Eugenio Diaz <[EMAIL PROTECTED]> writes:
> > >
> > > > Why does the menu launcher use /usr/bin/soundwrapper to lauch xmms?
> > > >
> > > > This is not necessary, and may even cause problems, since xmms uses its
> > > > own plugin libraries to access esd or artsd.
> > >
> > > And what if arts plugin is in use and you launched gnome?
> >
> > You mean the artsd daemon, right? If so, well, what then?
> >
> > It does not matter, since xmms will use whatever internal output plugin it
> is
> > configured to use, so what is the point in running it throught
> soundwrapper?
>
> Because from the packager point of view, I don't know which sound daemon
> you will use, and the default uses OSS -> this doesn't work under Gnome
> and KDE for which their sound daemon sits on the dsp.
Ok I am sorry, my bad. So if you configure xmms to use OSS output plugin and
then run it throught soundwrapper it works fine every (artsd, esd or no daemon)
time. I tested it with artsd, and works fine. My confusion came from when I did
the test using the OSS plugin and running xmms throught esddsp, and it failed
because of an unrelated problem I have with esd (see the other thread about esd
and SIGPIPE).
=====
________________________
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
