Guillaume Cottenceau wrote: > David Walser <[EMAIL PROTECTED]> writes: > >>I'm aware of the current behavior. For normal use, >>one actually just doesn't get sound from KDE all that >>often. I'm just trying to say this isn't as bad in >>practice as it may be in theory. >> > > Maybe, maybe not. At the beginning of arts, I had a large number > of "bug" reported because xmms would not start correctly saying > "busy dsp" because they clicked on "xmms" before 30 secs after > kde2 started. I don't want to come back to this broken behaviour. >
FWIW, in my not-heavily-multimedia usage, I have taken to changing the default arts server timeout (60 sec) to 1 sec and calling mplayer, for instance, without soundwrapper results in only 2-3 second delay (600 MHz Athlon) instead of what is a timeout at, typically, 15 seconds of a program waiting for arts to release. There are a lot of system and window behavior notifications that can use arts, including at the point of opening a window for the gui of a program that uses sound. Only *perhaps*, changing this default timeout of the arts server would sweep a significant portion of the problems under the rug, so to speak. Rolf Pedersen
