[XACT] Cue looping gaps when not handled by ALDevice about fna HOT 4 CLOSED

Yeah, it's probably about 16ms off since that's when you're calling AudioEngine.Update.

If you want you can try to incorporate AL looping into the Cue looping setup, but note that there's no real way to detect loopback, only buffer lengths. You'd have to base new variations on when, according to the Cue timer, the sound is likely to have looped, and then apply new variations, in addition to turning off loops at the right time and swapping out sounds if loops include randomized tracks.

from fna.

This is definitely an accuracy issue, but I'll leave this up to you. My solution for this internally is to just write FACT, but that's a multi-month task and I imagine you'll want a fix sooner than that, and the one thing I've got that does looping in this way doesn't need this level of accuracy so I can't really put it in as a priority.

from fna.

Yea, that makes sense to me. Should be able to find some solution on our end.

from fna.

Closing as WONTFIX for the existing audio implementation, and FIXED in the FAudio rewrite coming up.

Note that even in Microsoft's XACT runtime there are still tiny gaps (and sometimes even overlaps) for variations on loop, FAudio just makes it act similarly to that.

from fna.