This is a beat slicer that slices a sample into 2, 4, 8 or 16 slices and then mixes the slices randomly. The number of slices can be changed during playback, the change won't take place until the next slice, so it is possible to start with an unsliced loop, slice it in half... then in 4ths etc.

There is also a 'random' option that randomly plays slices of 1/2 1/4 1/8 or 1/16 length.

tell me what you think!

http://www.pdpatchrepo.info/hurleur/sampleplayer.pd

fun to play with, nice loop shuffler! loaded an amen into it and had my fun!

Its more fun when you get like 3 of them at once.. I am working on making it an abstraction that lets you force a global BPM so files of different lengths don't screw it up.

new version

this time.. you can get two or more going at the same time. Left inlet sets bpm, and a bang to the right inlet will send a 'START'

I tried to set up some sort of intelligent 'length' setting, and it works more or less, but it is really sloppy. Is there any better way to set that up other than using all of those spigots?

Right now the length detection is set up for 160 bpm.. It would be pretty simple to set it up so that it changes with the bpm.. but i've not gotten there yet.

also.. I converted it to an abstraction

http://www.pdpatchrepo.info/hurleur/multislice.zip

i am pretty sure i included the wrong abstraction

here is the right one

http://www.pdpatchrepo.info/hurleur/randslicebpm.pd

I think a better approach would be to have the user input the number of bars and beats and slice it up from there. Your approach just assumes too much, such as 4/4 measures and predefined tempo. This makes it less flexible. I like the *idea* of an intelligent beat detection, but it would require some analysis of the audio file to be more user-friendly. I've tried doing this with [bonk~], but I find it's still a little to fiddley to be reliable. You'd still have to allow for the user to fix [bonk~]'s mistakes.

well.. this way it is easier to change loops on the fly. You can still fix it if it doesn't do it right

anyway.. it just decides how many beats to give it based on how long the sample is. it really isn't detecting beats or anything fancy like that.

Thanks for the reply though!

Is there a way to give some sort of prompt after selecting a file that asks for the input of beats/bars before the file is sent to the looper? That would make things alot smoother the way I imagine them.

I might do it something like this.

http://www.pdpatchrepo.info/hurleur/promptforbeats.mmb.pd

nifty.. I might just end up doing something like that