MPC-Tutor wrote:I really can't see this happening, it must be a complete CPU hog and it's not really what that functionality was intended for IMO, it's just the reality of working in standalone mode, there has to be limits and one of the challenges of working in any hardware sampler is learning how to workaround the limitations.
I think you need to look at why you need to do this in the first place, what are you trying to achieve by timestretching individual samples across a keygroup? Is it necessary? Can you achieve it in other ways? For example in the OP, he's wanting to timestretch a vocal sample, but is there a reason that it must be performed in a keygroup program across a note range? Can he not just selectively timestretch individual samples as required? Or replicate in a DRUM program? Patch Phrase?
Just wanna be able to take single sample and use as playable poly Instruments or loops where pitched samples keep their original length across wider range than 16 levels...Microsampler/Ableton/Beatmaker 3 style.. Workarounds for this are vibe killers & life’s short

On one track/keygroup the cpu hit should be no issue on a keygroup with like 6-voice poly...no different from having warp active on 6 separate samples simultaneously..