[Bug 773681] directsoundsink: High cpu usage on windows x86

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=773681

--- Comment #23 from Nirbheek Chauhan <nirbheek.chauhan at gmail.com> ---
(In reply to Nicolas Dufresne (stormer) from comment #5)
> Wow, both the code before and after seems odd. I see that DirectSound do
> have a mechanism to notify playback position reliably.
> 
> https://msdn.microsoft.com/en-us/library/microsoft.directx_sdk.
> idirectsoundnotify8.idirectsoundnotify8.setnotificationpositions(v=vs.85).
> aspx
> 
> We could use this function, or even better, implement a clock on top of that
> (async timers could be scheduled this way).

This API is totally useless because you can't schedule notifications during
playback (they must be scheduled in stopped state), and while looping in the
buffer, the events that you scheduled along the way will only be triggered
exactly once.

The only real solution is to use (fix) our WASAPI elements and get rid of our
directsound elements once they're in a good state.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.