pencilina

I'm working on a pluggo that uses sfplay~ which plays back sound files at different speeds. I've tested it in Bidule and Digital Performer and it causes huge CPU spikes in both hosts even with high (1024) host buffers. Running 2 instances of it causes the audio to breakup. The same patches that its based on work great in max and I run lots of them at the same time. Does anyone have any experience trying to get sfplay~ to behave in a VST plug in. Should it work? Any tips or suggestions?

sfplay-causing-cpu-spikesgliches-in-vst

BTW, I built the same vst on my windows laptop and it seems to work OK. So again, I'm really curious. Is anyone successfully using sfplay~ in a multiple instances of a pluggo on a mac?

BTW, I built the same vst on my windows laptop and it seems to work  OK. So again, I'm really curious. Is anyone successfully using sfplay~ in a multiple instances of a pluggo on a mac?

funny that you mention this now. i was recently trying to make a simple multisampled instrument in pluggo on mac. i am using a poly~ object that uses sfplay~ with one central sflist~. the plugin glitches enormously in every host i have tried regardless of how many voices are being used. playing one note at a time causes the same problems.

i have tried various buffer size settings in sfplay~ with no change. even with signal and i/o vector sizes matching what the plugin allegedly uses, the patch works great in max.

so i ask the community: is sfplay~ thoroughly unreliable within plugins? buffer~ is more than i need and would take a chunk of ram (using around 300 megs of audio files, currently). am i out of luck here?

funny that you mention this now.  i was recently trying to make a simple multisampled instrument in pluggo on mac.  i am using a poly~ object that uses sfplay~ with one central sflist~.  the plugin glitches enormously in every host i have tried regardless of how many voices are being used.  playing one note at a time causes the same problems.

i have tried various buffer size settings in sfplay~ with no change.  even with signal and i/o vector sizes matching what the plugin allegedly uses, the patch works great in max.

so i ask the community: is sfplay~ thoroughly unreliable within plugins?  buffer~ is more than i need and would take a chunk of ram (using around 300 megs of audio files, currently).  am i out of luck here?

sfplay~ causing CPU spikes/gliches in VST