anybody got a working patch, or suggestions for one, that will debounce a signal...? [i.e. not pass a signal which occurs within a set amount of time to, and within a set range of, the previous signal sent.]
this is for control data, not audio signal, of course. bonk~ has a debounce function built into the object, so i am curious how to implement it outside of bonk~.
best, d.
ok ok....
found something in the examples.....
[number]-----[sig~]----[threshold~]------[snapshot~]------> | [metro]
threshold~ has a debounce function. i'll play around with it to see if it will do what i want, which is to debounce the wobbly MIDI input from a Chaos Pad so i can map its surface out into 30 toggle-able buttons. i didn't think this would be so tricky! other sugestions still welcome.
d.
derek holzer wrote:
anybody got a working patch, or suggestions for one, that will debounce a signal...? [i.e. not pass a signal which occurs within a set amount of time to, and within a set range of, the previous signal sent.]
this is for control data, not audio signal, of course. bonk~ has a debounce function built into the object, so i am curious how to implement it outside of bonk~.
best, d.
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
Maybe 'speedlim' or 'ignore' from maxlib (http://www.akustische-kunst.org/puredata/maxlib/) are of some use for you:
changing data, so that values change every <time> ms at a maximum (is also part of 'cyclone')
schorter time than <time> ms
Olaf
derek holzer schrieb:
anybody got a working patch, or suggestions for one, that will debounce a signal...? [i.e. not pass a signal which occurs within a set amount of time to, and within a set range of, the previous signal sent.]
this is for control data, not audio signal, of course. bonk~ has a debounce function built into the object, so i am curious how to implement it outside of bonk~.
best, d.
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list