Maybe someone can help... I'm having a hard time telling if the read ahead is actually enabled and working properly.
The Options and Stuff dialog says XMPlay version 18.104.22.168 at the bottom (just downloaded today). Running under Windows 7 Ultimate 64 bit.
I added ReadAhead=1024 to xmplay.ini right under the [XMPlay] header. Restarted XMPlay. Note I set the read ahead to a very large size (a Gig) to accommodate some pretty large files in my library (longer duration and/or 24 or 32 bit, 96 KHz, etc.).
I'm playing a 8:02 duration 24 bit 44.1 KHz uncompressed PCM wave file, size 124.7 MB. It's coming off a NAS box, via a Windows shared drive.
I look at Task Manager: The xmplay.exe process shows 12,076 K memory usage. Memory usage is 5.48 GB of 16 GB total physical memory, cached is 8476 MB.
In the playlist, XMPlay moves to the next file, 20:04 duration, 311.2 MB in size.
I look again at Task Manager: No change at all to the process or overall memory usage numbers. Shouldn't I see increases when moving to the bigger file? Or would XMPlay allocate the entire 1024 MB read ahead cache when it starts up?
I tried another test: I was playing another similar 20 minute wave file, and let it get a couple of minutes into it. I would assume by now it should have had a chance to read ahead for most, if not all of the file.
I started streaming some video from the NAS drive, and also copied a couple of large files around for a minute. Enough that prior to read ahead it would have overloaded the NAS and/or network and interrupted the music playback.
I would have expected the read ahead would allow playback to continue uninterrupted from the read ahead buffer. But it was interrupted just as before I had enabled the read ahead.
So by the numbers in Task Manager and the observed performance I'm not getting that it's working. What do you think? Am I missing something, or not understanding how this is supposed to work, or what? Is there some other way to tell if this is working as designed?
Thanks in advance,