audio clip retriggering itself

[mowgli]

After having issues while synching visuals to an audio clip, I've been doing some testing just triggering a single wav file, no visuals involved.
While the clip is already playing, when I retrigger the clip and it starts playing, shortly after, about half a second, it retriggers on its own, making the sound glitch. The clip's trigger beat snap is set to none and the clip is set to play on timeline mode.

The transport timeline doesn't reflect the retrigger though, it runs smoothly while the glitchy retrigger happens so the playhead position is no longer in synch with the audio coming out. This is making it impossible to synch visuals properly as they go out of synch as soon as the glitch retrigger happens.

If I launch the clip for the first time it takes about half a second to actually start playing, this is extremely evident when launching it with visuals as the visuals appear straight away and then the sound begins.

[mowgli]

This was happening without a soundcard, with the audio coming through my computer's speakers. I decided to connect my Novation Audio Hub to test and just the act of plugging it, without actually routing the audio to it fixed the problem. The computer froze for a bit as I plugged it in and then miraculously all is fine.
The mysterious world of technology will kill me one day.

[Zoltán]

Were you using the Directsound driver for your speakers?

[mowgli]

Nope, Realtek

[Zoltán]

Ok, but via Windows audio, DirectSound or ASIO?

[mowgli]

Whatever Resolume defaulted to. The dropdown in Audio Output Device uses the same name for both Windows Audio and DirectSound so it's impossible to know which one is on unless you select it yourself which I didn't.
Definitely not ASIO, that appears under a different name.

[Zoltán]

Resolume uses the first available sound device in the list, so that should be Windows audio driver.

Was this a short Wav file?
Could be something with buffering.

[mowgli]

yes, it was a short wav