i think the loading time is the time for the buffer to fill at startup, so...probably not... did you try polybuffer~ instead of 200 buffers tho ?

I would like to try out Polybuffer~ Does it also switch between my RAM and the harddrive in an intelligent way?

The loading time also happens when all the buffers are empty. It has to do something with having a poly~ with 200 voices (They are all muted with a loadbang in the poly, but still). Since a note on switches a loop on and an aftertouch of that same note switches it off, I don't see another option as to work with targets instead of letting poly~ choose the voices. Because I send note offs before the aftertouch. Any idea on this? I would love to have just a 32 voices poly~

I could be wrong about the newer SSDs, but you'd probably have a hard time playing 200 files from disk. Not to mention that groove's buffers are all loaded into RAM too. sfplay~ plays from HD, but most of the other playback objects are buffer-based.

So all of that is to say polybuffer will exclusively use RAM.

Hi the only vague way I can see is to use dynamic loading, for example (pseudo code):

1. identify note number 2. load relevant file into one of TEN [sfplay~] objects* 3. send note on, play file 4. clear [sfplay~] after note-off 5. rinse and repeat

*This is based on the assumption that you are using a MIDI keyboard to playback files, so a vital question is "what is your maximum polyphony requirement?", as Rodrigo points out, 200 voices is a big demand on Max, RAM or HDD. Will all these files be played together at any time? I can get to around 40-60 voice polyphony on my main workstation, and the CPU begins to redline.

Also, do the loop-points and timestretch have to vary dynamically? If not, edit your files offline.

HTH Brendan