TristanShepherd

It seems like sfplay is in every change log and has been a constant problem in MSP?

Anyways, I was using sfplay in a poly~ sampler to trigger a large number of preloaded files. It has been working great, except for the fact that some of the voices will mute but not turn off their busy state when done playing (I am banging [with the right outlet of sfplay~) a message that is sent to the thispoly~ object to switch the mute and busy states. Is this not a dependable way to switch the states? - I don't really want to use ASDR, because I need the samples to play all the way through. This is not a problem until the amount of voices that are set to busy becomes greater than those that are not. Sometimes a massive wave of white noise suddenly replaces all the voices, and doesn't stop until I manually send a mute/busy state off message manually to all the voices in the poly object.

Seems like the noise is related to maxing out memory? But what about the intermittent problem with muting/busy state - for the most part it works perfect, after 30 minutes of playing, the errors accumulate. Tried using voice stealing to help the problem, but it is not reliable enough either. I'm probably pushing the program too hard [50+ cues and 20 voices?)

I was using this patch awhile ago - I think I switched the sfplay to buffers and groove objects (not a great solution, but the busy state problem went away).

sfplay-poly

Without a patch there's no way we can investigate a "sometimes it 

doesn't work". btw, I don't see the problem of using adsr~, you can 

just use the bang outlet of sfplay to trigger the note off.

Without a patch there's no way we can investigate a "sometimes it  
doesn't work". btw, I don't see the problem of using adsr~, you can  
just use the bang outlet of sfplay to trigger the note off.

SFPLAY~ + POLY~?