this is a sequenced beat slicer with a [bonk~] based slice-analysis engine.
i partwise borrowed this idea from saturno in a technical issues thread (http://puredata.hurleur.com/sujet-3178-graphical-data-structure-plotting-signal).
@ saturno: i hope, you don't get this wrong and you'll like this patch though.... i didn't want to leech your idea, but this sounded so interesting to me, that i couldn't wait for your patch..... and i'm still looking forward to your patch.
i also stole the [bonk~] analysis engine from a patch of tim vets.
thank you both! hope you don't mind!

i thought i'd share it here, maybe someone likes it! enjoy!

edit: the second version - see attachment 2!

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

Hi toxinic!
First off, congrats for this patch, it makes pretty amazing sounds.

BUT, you said you wanted some feedback, so here's some.
I m having problems with the GUI. Everything seems to be working fine, in terms of controling the patch and affecting the sound, BUT i can't see any changes in the value of most controls. In fact, only bangs and toggles seem to work on the GUI level. All the sliders and number2's do not move at all. this is quite annoying, especially for someone who is trying to learn how to use this patch (like me for instance!).
Although my laptop isn't too young now, it's not that weak (i have 1GB in ram and a core 2 duo processor), and i run Pd in windows.

Has anybody experienced the same problem?
And, does anybody know how we could solve this GUI problem? this could be interesting for future patches with a complex interface.

hi pamelapopo.
i'm sorry, but i'm afraid i cant help you at all.
i use a much older machine (fujitsu siemens amilo pro, 512 mb ram, 1,7 ghz pentium-m prozessor, windows xp) and it's all working fine here. all gui elements do what they should here. did you try to load an other sampel loop into chop suey? if this does not work, i assume, it's got something to do with your machines setup, since you are the first, who reports that kind of bug. hope you will figure it out!

Hey pamelapopo,

Does this happen in other patches? I've heard people have problems with sliders suddenly crapping out on them, but I get the impression it's rare and unpredictable. I've never had the problem myself. I don't know if it's been fixed yet, but it seems to be a bug with Pd.

Thank you both for your replies.
I haven't tried loading a different sample, but i ll let you know i soon as i do.
And yes, this has happened to me a few times before, but very rarely. One thing i have noticed that could be a reason to it is that Pd doesn't seem to enjoy having too many GUI controls moving at the same time. Especially when you have a visual bang somewhere that blinks very rapidly, that sucks up a lot of the "GUI power" and may result in other controls being either very sluggish or even staying completely still.
What is surprizing in toxonic's patch is that there seems to be only one bang that 's active on it's own (the one for the beat). That shouldn't normally be too much for Pd to handle.

I wonder if maybe the slider being used for the position is causing the problem. Try going into the waveform display part of the patch (right click->open on the main GUI, right click->open on the waveform) and disconnect the patch cord connected to the slider. Or if you still want to see it, make the argument for [unsig~] larger.

http://puredata.hurleur.com/sujet-3280-sliders-display-their-value

... also drew attention to the depth of downloadable .wav (or other audio format) files.

Hey toxonic,

i have a suggestion to make: It would be really cool to make each step (a slice with effets, one of the sixteen things you know what i mean) assignable to a midi note. So you are not limited to a prearragend pattern but you could improvise. Should beo that much work.

indeed, that sounds interesting... i'll give it a chance when i have a little time. i will upload it here. thaks.

Hi toxonic,
very good work. I like it.
Maybe it would be good to show the absolute number of slices or limit the number in the first row(slice). It is sometime a little difficult to get the number of actually slicers.

this patch is awesome

nvm

thank you toxonic!

Wow. That is awesome. So much fun to play with.

On to feedback:

+1 on the randomiser.
Is there a reason it only goes to 16 steps? 32 would be nuts.
Record feature! =)

Thanks again toxonic great work.

if anyone wants to explain to me, how to record what i play in chopsuey? i have linux/ubuntu and my audacity does not recognize pd-extended.
or alternative how to record in pd what i play.

wow. thanks a lot.

thank you! this is great.
i have only one problem though. i can't seem to find the bonk guts. i'd like to check it out so that i can learn something from this great patch. could you help me finding it?:)

very neat patch. lots of fun to play with and perfect for some reversed engineering