0
0

I recently tried increasing the size of the FMod buffers (all the way up to 2 seconds) in order to stop occasional stuttering that occurs when the system has a lot of disk activity (caused, I believe by elevator seeks).

What actually happened was that the interuptions got worse, and the effect was more unpleasant. It changed from a two or three event stutter to a longer hiatus with complete dropouts.

Since FMod is double buffered and the disk activity doesn’t last for anywhere near 4 seconds I can’t quite see what’s going on here.

The application containing FMod can be set to high priority with no change in the effects.

Phil

  • You must to post comments
0
0

I’ve tried both now, and the results are identical.

This is clearly a microsoft bug (feature) – I suspect that there is some pretty inefficient ring 0 code in the disk interupt handler that is stopping any app from running, no matter what its priority.

Rule #1 – If it doesn’t work, always suspect microsoft first.

Phil

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.