You need to post the poly~ file as well,

Cheers

Roger

Oops, minor slip there... Here it is:

Aaarhhhhh!!!!

I've found a way to make my patch click-free now, but every time I run it, it crashes max. For the life of me, I can't figure out why this is happening. It worked just fine, and now there is no way in hell it will run for more than a few seconds at the time. I suspect there's something fishy going on between max and the audio driver. I'm using Fireface UC with the latest drivers, and I've noticed a few times earlier that max can crash when I switch to this sound card... Here is the patch:

and here is the poly~ file:

minimum~ and maximum~ are your friend for this...

Thanks, guys! Stable now. You've saved me a sleepless night :-)

hey kflak

can you post your final patch? id like to have a look

thanks

Hi, johnr,

I didn't do much more than set the range of the random generators to fall very comfortably into the length of the samples I wanted to use (I knew exactly which ones I wanted to use, so this was not a problem). Nest stage in the process would be to make it more dynamic in order to keep swapping soundfiles, for example. This is where I suppose I'll need the minimum~ and maximum~ objects, and convert some of the information to signals (specifically the information to the groove~ object)

Here's the patch:

and here's the abstraction:

great; thanks.

if you havnt already, you may also want to take a look at the Granular Toolkit.. you can create some very intense glitch/stutter type loopers with that.

john

If you make a max patcher that crashes max please do send it to support@cycling74.com. This way we are more likely to notice and fix it! :)

Meanwhile, we did notice the patcher above that demonstrates this groove~ crash (thanks!). Tim's fix for it should be in Max 6.0.4 once it is released.

Rob

johnr: Will defintely take a look at it :-)

Rob: Will keep it in mind for the future!