
A twelve-part beatslicer mapped to each note of one midi octave. Features independent, realtime control over slice points, looping, amp envelope, pitch & output buss.
Download Here
cheers,
sk.


if this was built in SE , you should try the following , for FLS ...stk wrote:
- Notes:
1. Make sure you read the doco re: waveform view and cpu usage
2. I've been having problems with FL Studio throwing access violation errors - read this for details, and please let me know if it works for you.

*begin dense mode*stk wrote:Cheers.. It actually wasn't orig supposed to be a beatslicer, more a sampler with modulatable loop points.. which it still is, good for mangling
I build in Reaktor. I understand. Somehow, though, I get the impression it's easier in Reaktor than SE. I'd love to see you work in Reaktor one day..stk wrote:basically, when I can be bothered to sit down and convert the RC1 to a stereo signal path (tedious job).
sk

Hi,normal wrote: if this was built in SE , you should try the following , for FLS ...
under options > audio settings ...
un-check ' reset plugins on transport ' ...
may help ...
Well, all the slice points define what part of the waveform will be played with what midi note, nothing special there. But since you can automate their position you could link up, say, an lfo to one (or many), so that each time the slice is triggered it starts or/and ends at a different position.Sickle wrote:*begin dense mode*stk wrote:Cheers.. It actually wasn't orig supposed to be a beatslicer, more a sampler with modulatable loop points.. which it still is, good for mangling
Can you give a working example of how to do that?
Like I have anough time alreadyI build in Reaktor. I understand. Somehow, though, I get the impression it's easier in Reaktor than SE. I'd love to see you work in Reaktor one day..
Cheers!stk wrote:Well, all the slice points define what part of the waveform will be played with what midi note, nothing special there. But since you can automate their position you could link up, say, an lfo to one (or many), so that each time the slice is triggered it starts or/and ends at a different position.Sickle wrote:*begin dense mode*stk wrote:Cheers.. It actually wasn't orig supposed to be a beatslicer, more a sampler with modulatable loop points.. which it still is, good for mangling
Can you give a working example of how to do that?
Switch the slice to looping mode and you can get some crazy, glitchy/stuttery stuff going on.
Or.. load in a more textural sound, set a slice envelope to have a long attack & decay, and automate the slice points with a random lfo. Trigger it with a repeating, long note and you have an interesting texture generator (in that it plays the same sound, but starts & loops it at a randomized point, and plays it either forward or, if the start & end points cross over, in reverse).
Like I have anough time alreadyI build in Reaktor. I understand. Somehow, though, I get the impression it's easier in Reaktor than SE. I'd love to see you work in Reaktor one day..
seriously tho, I would like to give Reaktor a try sometime, would be nice to build devices *while* working on music.

you should put that in your sig, i think nearly every other post of yours has been that recentlynormal wrote:[
if this was built in SE , you should try the following , for FLS ...
under options > audio settings ...
un-check ' reset plugins on transport ' ...
may help ...
heh ...Kriminal wrote:you should put that in your sig, i think nearly every other post of yours has been that recentlynormal wrote:[
if this was built in SE , you should try the following , for FLS ...
under options > audio settings ...
un-check ' reset plugins on transport ' ...
may help ...

Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026