On Mon, 3 Dec 2001, Matt wrote:

> On Fri, 30 Nov 2001, Alexander R Angas wrote:
>
> > Speaking of timeSetEvent() - have a look at what I'm about to put into CVS
> > (which will solve the linking problem BTW). This has millisecond resolution
> > and should set a lightweight event object every 17ms (as close to 16.6667 as
> > possible). The event sound server waits on this object and then immediately
> > calls do_sound() to play the next waiting MIDI command when the object is
> > signalled. Yet when using this, I only get reasonable sound speed when I
> > drop the timer value from 17 to about 7 or 8. Even then it's not as smooth
> > as the polled server when it's working properly. What does that say about NT
> > scheduling? Or perhaps my event SS code (which I don't _think_ is faulty but
> > could be!) How does it sound on your speed machine, Matt?
>
> It does sound a bit slow on my machine. The code looks fine, other than
> you are specifying a 2ms timer accuracy to timeSetEvent and you really
> want 1ms.

Something else -- have you tried using TIME_CALLBACK_FUNCTION instead of
the Win32 Event stuff? The event-based stuff will have the same latency
problems -- but I don't think the CALLBACK_FUNCTION would. I tried doing a
simple change, but got really weird results.

Let me know your thoughts on this and if you already tried it.



Reply via email to