Date: 03 Mar 2000 01:09:24 +0100 From: Michael Hohmuth <hohmuth@innocent.com> To: John Reynolds~ <jreynold@sedona.ch.intel.com> Cc: wsanborn@uswest.net, questions@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: xmms 1.0.1 uses 95% cpu Message-ID: <87itz4q5hn.fsf@olymp.sax.de> In-Reply-To: John Reynolds~'s message of "Thu, 2 Mar 2000 11:21:35 -0700 (MST)" References: <20000223215739.B326@marder-1> <38BE3C3C.17337.42ADED6@localhost> <14526.45359.533982.635973@hip186.ch.intel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ I have missed the beginning of the thread -- I hope I do not miss the point completely. ] John Reynolds~ <jreynold@sedona.ch.intel.com> writes: > which version of xmms? 0.9.5.1 is the one I've reverted to, but the latest one > in the ports tree, 1.0.1, sucks even worse for performance. > > With 0.9.5.1 the scope and volume controls update and "respond" normally to > mouse events, etc. It just chews the crap out of CPU. With 1.0.1, the scope > updates about once per second and the volume/seek controls are completely > unresponsive (just as was mentioned in a previous posting on this topic). I believe that you are experiencing a driver problem: XMMS 1.0 uses select() or poll() which some sound drivers do not implement. I fixed this particular problem by implementing poll() for the ES1370/ES1371 PCI driver in FreeBSD-STABLE (used by the Soundblaster AudioPCI 128, for example). See bug report kern/16709 for my patch. > Does 4.0 suffer this problem too? I have no idea. 4.0 has a new, different sound driver. Michael -- hohmuth@innocent.com, hohmuth@sax.de http://www.sax.de/~hohmuth/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87itz4q5hn.fsf>