[Openal-devel] Additional patches...

[Jason Daly]

Daniel PEACOCK wrote:
>
> Hi,
>  
> > FWIW, I took a peek at the Windows implementation, and it doesn't seem
> > to try to adjust process or thread priorities anywhere (I was a little
> > surprised by this). I doubt the Windows scheduler is that much more
> > efficient than Linux's.
>
> The Windows implementation uses a Multimedia Timer to call the 
> appropriate service routine.  The Multimedia Timer runs in its own 
> (Time Critical priority) Thread anyway.
>
> Incidentally the Capture code does not use a Multimedia timer, but 
> instead it creates it's own Thread and waits for messages.  To improve 
> capture latency it was necessary to create smaller WaveIn Buffers 
> *and* to increase the priority of the Capture Thread.
>

Ah, OK.  I just looked for SetPriorityClass()/SetThreadPriority() calls 
and didn't find any.  I didn't think about multimedia timers.

I figured the DS/DS3D paths probably ran Time Critical anyway, I wasn't 
sure about the MMSYSTEM path.

-- 

--"J"

"I'm a castaway stranded in a desolate land,
 I can see the footprints in the virtual sand."
	--Neil Peart

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://opensource.creative.com/pipermail/openal-devel/attachments/20070724/50366689/attachment.html