Hi Chris,
Incidently the problem is at the beginning of the unlooped sound only, not
as I typo'ed below. Also, if I run sound 1 unlooped for testing, then
there's no problem with sound 2.
I've set the flags to force hardware and software buffers only, with no
effect on it. I've set just about every other usable combination of flags as
well, with no effect.
I tried your volume suggestion but it seemed to have no effect on the problem.
Your suggestion about garbage being left behind in the primary buffer is
interesting. Sound two is actually briefer than I said and I can't honestly
tell by ear if the pop is at the beginning or at the end. I'm too worn out
by it at the moment to scope it or look at a recording of it, to check :)
I would like to try your suggestion of padding the primary buffer with
silence. How should I do that? Is there a programatic way to clear or zero
the primary buffer or pointers? I could load and play a short wav of silence
as well, at the end of sound 1, but may run into time constraints with that.
I might try making the looped wav smaller than the unlooped one with trailing
silence on the unlooped one, here too in a minute. Or perhaps is there a way
to load a long wav of silence into the primary buffer to clear it, without
playing it?
Thanks,
Jim