ok, this has happened to me with slackware 10.1 and current, and vector linux since it is based on slackware 10.1. esound sounds really garbled. i ahve posted it on here before but never got a response. i have played with it quite a bit, and i know it has something to do with esd, cuase if i tell xmms to use alsa, oss, or whatever it works fine, but when i tell it to use esd the sound is horrible. teh problem is, i only use the enlightenment window manager and it wants esd for enlightenments sounds.

i know this isnt just my system, cause it is on one laptop that has an intel card, another that has an s3 card, a desktop with an intel card, another desktop with a via chipset, and my friends desktop that i cant remember the card, and it is running vector.

am i stuck at 10.0, cuase i cant have my desktop sounding like this? surely someone else has run into this problem. the best way that i can describe the sound is that a song sounds like it is being played on a record and someone has spilled a coke on it and turned the speed up. it is like the sound is lower, off key, and maybe slower, but maybe the sound demon is trying to fix it so it speeds it up... i have no idea. i cant describe it any better. unusable though. you guys are the only ones i know that can fix this.

ok, no responses again, but i did figure it out. this time, i didnt revert to slackware 10, but i used the slackware 10 package from the slackware package browser. i didnt think it would work before cuase of linkers and things, but it did work on current. i went from using the slackware esound package that was version 2.35 to the slackware 10 version that was 2.34. that did make it sound better, and everthing is good. dont know y building it from source didnt. unless that is the problem. maybe a flaw in the default build... with slackware 10.1's version of gcc, or maybe the cflags,,... im just thinking outloud here. or thinking online.. anyway. using the actually slackware package works. usually it isnt a good idea to use a package that was built for a different version of slack, but in this case it is ok. so it seems to be a problem with the building of the package, then it is packaged as 2.35 and not fully checked. shame on you slackware... shame shame. that is the resolution though.