this is my first patch i ever finished in pd, so there are probably a whole bunch of bugs in it - feedback is welcome.
this keymasher features stutter (q), gater (w), reverser (e), comb filter with lfo (r), bitcrush/sr.redu (t) and a tapestop effect ((z) - on german keyboards).
as obiwannabe told me, there's an issue with the [keyup] object on some systems, maybe someones got an idea to do it another way?
the sampler in the patch is for demonstration purposes only, you can use every audio input you want (and you know the correct tempo for proper fuction...).
hope i added all dependent abstractions - on this way: is ther a possibility to save patches as a kind of "bundle" with all needed abstractions?

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

Hey toxonic,

Your [key]/[keyup] approach is working fine, and much simpler than the crap approach I posted a while back . The reason some keys don't seem to play after others are pressed is because of the order of the effects and the fact that some are reading from buffers. For example, when you activate the reverser, audio is being read into a delay which is being fedback so that you can keep reading the same audio. This prevents anything from the stutter or gater from going into the reverser, because the reverser is still reading from previously recorded audio. You might be able to overcome this by reordering effects and having the buffer-dependent effects be reactivated when an effect that comes before it is turned on.

As for quantizing, something like this might be a good way to start (hope this makes sense):

[metro]
|
| [r close-spigot]
| |
| [0(
| |
| | [1( <--bang this when key is pressed
| | /
[spigot]
|\
|
|

Edit: And while your quantizing, adding a way to put it on auto-pilot and randomizing the effects would be killer!

Hi toxonic, it doesn't work for me (

@ maelstorm: it's not only that the effects don't play, but also the in some combinations there will only 2 key triggering - you can check this, when you connect number boxes to the single [route] outlets....there seem to be a whole of things, that could be done. some while ago i build a similar glitch device in reaktor featuring a sequencer - a combination of sequnecer and randomization would be cool, but a lot of work, i guess. will probably need a while!

@ diplipito: could you describe where the problem is? what does not work? and what patch? the new one, where you can trigger more effects at once or the old one from my first post? or maybe both?

When i load sample and play it, sample is playing without any changes.This happened with both keymashers.

try to open the keymasher subpatch (in my newer upload). in it theres a subpatch with the gui and a second subpatch called [glitch_fx~] (with a load of float-arguments). open the [glitch_fx~] subpatch and have a look at the top / right structure in it. there are 6 number boxes side by side. they should normally switch to 1 when you hit the corresponding key and snap back to zero, when you release the key again. try the q, w, e, r, t, z key - if there doesn't change anything, than there's something not working with the [key]/[keyup] combo on your system i guess (what leads to, that you won't be able to trigger the single effects...).
if thats the problem, you could try using midi. this should be easy to modify the patch: use a [notein] instead of the [key]/[keyup] combo, left outlet to the left inlet of the [pack] and the middle outlet via a [>] object into the right inlet of the [pack]. then you only need to change the arguments of the [route] object to "60 61 62 63 64 65" and you can control the keymasher with your midi-keyboard using midi keys 60-65.

I am idiot ha ha ha ha
I even not knew that i can play with computer keyboard.
Keymasher is nice thing. Thank you man.

that's why i called it a keymasher, dude!
ok, all ambiguities removed, hopefully!

Hey toxonic,

I looked at the number boxes coming out of [route], and I also attached some to the right outlets of your effects subpatches. They're all triggering fine for me; it worked with every combination I tried, including the ones you mentioned having problems with. Have you tried it on a different computer or another keyboard? I wonder if it's an issue with your setup.

mhhhh... no, didn't try, i only have a notebook and no other hardware to try out.
well, i'm content, when it works on others machines, i can also modify it into a "midi masher"... hahaha.
but not sure about this strange behaviour - most of the time i work on winxp (because i bought some software that only works on win) but i should boot up next time to my linux sytem and see if it works there?