David Walser <[EMAIL PROTECTED]> writes:
> Mister little less newbie doesn't know why it doesn't
> work when he changes the output plugin, because he
> doesn't know that wherever in Mandrake he clicks Xmms,
> he's running soundwrapper xmms
I don't think we have a really decent solution for this problem.
Do you really think it's better
1- do nothing, e.g. 99% of users which are under KDE will have
the nice msg "sound card busy" and they need to guess they
have to change the outpout plugin to "arts" (something they
don't even know what it is)
2- keep a soundwrapper but instead of using esddsp or artdsp,
dynamically change the contents of ~/.xmms/config behind the
back of the user according to the plugin currently in use?
I would favor -2- of course but as I said I don't know if this is
really better. It seems your original mail favored -1-? Which I
don't agree with, of course.
I'd enjoy having the opinion of other persons on this ML ?
PS : it would help people follow the discussion if you would
answer the mails adding your comments *after* the relevant
part of the mail, not before
>
> --- Guillaume Cottenceau <[EMAIL PROTECTED]> wrote:
> > David Walser <[EMAIL PROTECTED]> writes:
> >
> > > If xmms-esd and xmms-arts both work (which people
> > say does, maybe I'll get
> > > lucky with 8.2), the xmms package shouldn't be
> > shipping with it's
> > > /usr/lib/menu/xmms entry saying "soundwrapper
> > xmms" It should just be
> > > "xmms"
> >
> > no because mister newbie doesn't know how to
> > manually change the
> > plugin. the correct way would be to dynamically
> > change output
> > plugin entry of ~/.xmms/config according to what
> > sound server is
> > currently running but I find that too dangerous.
--
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
