Certainly if the frequency was 48043 it'd answer why there are more samples then there should be, and they back up. However it'd backup 43 samples a second, 8k samples would need 180 seconds or so.
It says it's documented as 48043. I don't suppose you know if that's Nintendo docs, or someone measured the clock and got 48043 (just a thought that for a console you get a batch of clocks with some variance, but just code for that variance.)
Looking at the code there a few interesting items, eg there's a timing loop for how quickly the AI drains a sample, given it's using the OSGetTime that's bound to be somewhat bogus.
Perhaps the solution is to monitor the backlog and tweak the resampling slightly to try and track the actual consumption rate, as most people probably can't tell if 1% more or less samples come out a second. probably band it to have 3 resamplers. One at normal speed, one at slightly faster, and one slightly slower.
As the buffer passes certain thresholds switch resampling to use a little more or less.
I think I've worked out what happened to Xaudio2. I think it's a build issue, and related to if the directX sdk is available. The move to vs2013 means the wdk 8.1 is used, which changes xaudio around, see this MS article,
http://msdn.microsoft.com/en-US/windows/desktop/ee663275.aspx
I suspect it's something to do with point 8, which talks about using the old sdk header and .lib file for xaudio on win7.
It says it's documented as 48043. I don't suppose you know if that's Nintendo docs, or someone measured the clock and got 48043 (just a thought that for a console you get a batch of clocks with some variance, but just code for that variance.)
Looking at the code there a few interesting items, eg there's a timing loop for how quickly the AI drains a sample, given it's using the OSGetTime that's bound to be somewhat bogus.
Perhaps the solution is to monitor the backlog and tweak the resampling slightly to try and track the actual consumption rate, as most people probably can't tell if 1% more or less samples come out a second. probably band it to have 3 resamplers. One at normal speed, one at slightly faster, and one slightly slower.
As the buffer passes certain thresholds switch resampling to use a little more or less.
I think I've worked out what happened to Xaudio2. I think it's a build issue, and related to if the directX sdk is available. The move to vs2013 means the wdk 8.1 is used, which changes xaudio around, see this MS article,
http://msdn.microsoft.com/en-US/windows/desktop/ee663275.aspx
I suspect it's something to do with point 8, which talks about using the old sdk header and .lib file for xaudio on win7.