Random track hanging/freezing for a couple of seconds at a time

[ninjagaijin]

Not sure how to diagnose this but:

I haven't used WACUP in a while, but today when I started using the latest preview build, I'm getting random freezes every couple of minutes when playing my DJ mixes. The playback just hangs and then starts playing again a couple of seconds later.

I'm not having issues with playing the files with foobar.

It's off a HDD but there are no errors when checking the HDD health with various HDD checking software.

If I can do anything to help diagnose the cause please let me know.

[dro]

Is the HDD maybe spinning down since you mention it happening after a few minutes? As it could be the OS is buffering things to a point before it then runs out of data (though that could just be a rubbish idea) also what file type(s) are you seeing this happen with? As for the other software mentioned, I don't know if that does full file buffering or not which might be why it's behaving whereas I'm not & currently I don't have any accessible HDDs to try to hookup to see what might be going on if it ends up being a reproducible issue with timeouts, etc.

[ninjagaijin]

HDD not spinning down AFAICT
Files are flac or wav

I've never had this issue with previous WACUP versions, only the current

The file I was mainly struggling with:
Length: 5373.7 seconds
2 Channel(s) @ 44100 Hz
Samples: 236978035
Format: Signed 16 bit PCM WAV

[dro]

I'm not sure why as I don't intentionally mess with things especially at a low level to try to keep drives alive. Neither of those file types are handled with input plug-ins that can offer full file buffering (it's a request that isn't likely going to happen any time soon). Most likely it's just that because it keeps reading data from the drive as needed to keep playback going which is enough to prevent the OS from turning it off as a best guess but why it happens now doesn't make much sense as the input plug-ins haven't drastically changed in how they work compared to mp3 playback which goes via a different input plug-in now by default.