>>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 ? >
#3? Dont' run the sound daemons for the wm's? No wrappers needed. ;-) (Did that to get real working on 8.1 and KDE still plays it's startup music...) -randy
