Discussion:
Adjusting DirectSound acceleration and notification
(too old to reply)
Lars Munch
2004-02-25 15:20:54 UTC
Permalink
Hi

I have noticed that on some systems (or sound drivers) my
notification handler set with SetNotificationPositions is triggered from
other sources than by the buffer it was intended for. By reducing the
sound acceleration to "basic acceleration" (in dxdiag.exe) everything
works as intended (I guess this is a buggy sound driver??). I can live
with no acceleration for my program, I just want it to be stable. How can
I reduce the acceleration from my program?

Any pointers are appreciated.

Thanks
Lars Munch
Chris P. [MVP]
2004-02-25 20:00:37 UTC
Permalink
Post by Lars Munch
Hi
I have noticed that on some systems (or sound drivers) my
notification handler set with SetNotificationPositions is triggered
from other sources than by the buffer it was intended for. By
reducing the sound acceleration to "basic acceleration" (in
dxdiag.exe) everything works as intended (I guess this is a buggy
sound driver??). I can live with no acceleration for my program, I
just want it to be stable. How can I reduce the acceleration from my
program?
It seems to be a combination of buggy drivers and issues within DirectX
itself. Rather than altering the acceleration it is better to work around
the issue in code to determine whether the notification event you received
was really yours or not. You can do this by checking the location of the
Play cursor in your notification handler to see whether it really needs more
data or not.

Loading...