On Wed, 30 May 2001, Christoph Reichenbach wrote:
> > But, it seems that the problem is corrected by Sleep'ing for 100ms after
> > the sched_yield you put in, which gives the (crappy) scheduler plenty of
> > time to let the sound thread run for a bit.
>
> > I agree that we should wait on a conditional varable, but Im not sure how
> > to do that myself.
>
> The thing is that I don't see _what_ we should be waiting for. If the
> sound server responds to the above request, this means that it's working
> and already in full swing. 100 ms later, the sound server is in exactly
> the same condition as before, at least as far as I can tell...
I don't understand it either now that you've made it more clear. Things
seem to be correct more consistently than without the Sleep, though. Let's
see what Taylor's results are.
My lack of expertise as a developer is really showing on this problem :(
--
http://www.clock.org/~matt
