It's been a few years since I even looked at sfplay~ for any "heavy lifting" as far as sampler instruments go... However, since most commercial samplers today are disk-streaming based, I wonder if anyone has any reports on sfplay~ performance with current hardware (you know, S-ATA, 8 MB cache, and so on...)? With the addition of playback speed, sfplay~ seems a pretty decent candidate for certain sampler functions...
Also, looking at the documentation, it looks as though either the "open" or "preload" message will cause sfplay~ to load the sample "head" into RAM (disk buffer?), based on the disk buffer size. Given a large disk buffer size, is the playback of this first portion handled in essentially the same way (by MaxMSP, not me) as playing from the buffer~ object? I guess what I'm asking is whether, given a hefty disk buffer size, sfplay~ can compete with play~/buffer~ in any way, shape, or form.
Sorry for what sounds like a "newbie" question. I assure you, it's not. What I'm after is the "inside dirt" on sfplay~... I'm really drawn to the simplicity of file-handling in sfplay~/sflist~, and of course the potential for minimizing RAM usage, but I don't want to get into a huge programming job just to find it's not up to the task when it comes to playback.