Date: 22 Jun 1999 12:15:37 +0300 From: Ville-Pertti Keinonen <will@iki.fi> To: Andres <dae@via.ecp.fr> Cc: freebsd-multimedia@freebsd.org Subject: Re: xmms Message-ID: <86lndcr3ye.fsf@not.demophon.com> In-Reply-To: Andres's message of "22 Jun 1999 03:35:56 %2B0300" References: <Pine.BSF.4.10.9906210810110.48239-100000@teligent.se> <376EDC27.D818B336@via.ecp.fr.newsgate.clinet.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
Andres <dae@via.ecp.fr> writes: > sorry to bother you a bit more with this, but i've got another question. > does it work flawlessly? i removed linuxthreads on my system, then > recompiled every related thing, then tried it (xmms compiled without a > glitch, btw). > and it plays mp3 quite fine, but the graphical part (another thread) > doesn't seem very responsive. it takes sometimes a few seconds until it > gets updated or until it responds to one of my commands. That might be due to the fact that FreeBSD threads are not real threads, yet...at least if you're using VoxWare. The VoxWare API is awful. It's almost as bad as the implementation. Non-blocking behavior must be set using SNDCTL_DSP_NONBLOCK, the O_NONBLOCK flag is ignored. The thread library wants file descriptors to be non-blocking, but it expects it to be able to set them using the normal mechanism... The new 'pcm' drivers obey O_NONBLOCK, so if you're using them, the problem is somewhere else. Note that I haven't tested or looked at xmms, so the problem could be somewhere else, in any case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86lndcr3ye.fsf>