Never mind, I saw the answer in the list of new features
8. NEW: Added option to play files from memory instead of disk which is useful in high-end audiophile environments. (file is loaded in a background thread to system memory (capped at 256 MB) and played from there)
However, I still think that any benefit to be had from RAM playback and indeed the whole reason for RAM playback is to limit, reduce or stop RAM traffic while playing music. Otherwise its just a buffer.
This is only an idea, so no need to get hostile:
If I have a list of 3 songs [or any amount] in the "Now Playing" list there should be a grayed out section showing me which songs will be sent to RAM. Then I can select any amount of songs within the MB limit to truely load to RAM without additional songs being loaded in the background.
For example I have these songs in the Now Playing list:
A - 120MB
B - 90MB
C - 97MB
D - 90MB
I should be able to pick or drag expand the grayed out area to any song until the limit is full. From there when I hit play only those songs will be loaded to RAM and when they are done, playback will stop. This may sound like an inconvenience but any Audiophile or person who swears by RAM playback will gladly accept this imo. Furthermore, the amount allocated for RAM playback should be user adjustable to account for the various amounts of free RAM any user is liable to have....Joe may have 3 whole Gigs of free RAM while John has only 256MB. In this case Joe could load a whole CD's worth of flac to RAM.
