ending a DirectSound stream using the callback result causes looped buffer

[rossb]

 http://music.columbia.edu/pipermail/portaudio/2009-April/009060.html

Philip Bennefall wrote

I had a bit of trouble with the DirectSound? completion code, if you return complete from your callback and do not call AbortStream? or StopStream? immediately then the last segment starts looping. I assume this is because the DirectSound? secondary buffer is still full of the old audio, and so my solution was to insert some extra silence the size of the buffer in the end and then stop. <<<

[rossb]

resolved by r1443