Greetings.

Is there a viable substitute for [change]? Something that can hold back the torrent of sensor data as well as change does, but without the "stopping repeating numbers" aspect?

What's happening is that I am using it to select notes but if I quickly jump from one note to the next (this is before the data has been turned to midi) my patch plays the existing note once, before it plays the next note so on fast passages or with drums especially, it "flams" between two notes. When I take change out, the problem disappears, but the torrent of sensor data that change was holding back, slows everything down to a crawl.

Any insight? And by the way, my project would not be so far ahead were it not for this forum. Thank you. I hope to contribute one day, once I figure out where everything is. Cheers!

Onyx

I'm not so sure I fully understand, but maybe [speedlim] will work.

Actually, this topic may be the solution
http://puredata.hurleur.com/sujet-2377-non-audio-threshold
But I don't know what the "X" represents.

IMHO the "X" represents two crossed connections between the [t f f] and the [> ] objects.

ah, i see. i will try that and i will try speedlim at various points in the chain. thank you.

Speedlim didnt work. I need something like [oneshot] or [onebang] except for numbers instead of bangs. Somethinglike spigot but much faster, allowing only one number from the stream to come thru.

I have managed to slow down the sample rate enough that I can hear exactly what i am going for, masked by a hailstorm of sensor born bangs. Maybe some means of putting a [change]-like object on each analog input (of which there are 8 fsrs)that can stop the data but won't make the first note repeat. I'll try anything.

ok i found it.

what was happening was that the sensors were streaming loads of data to my note making patch, which was causing havoc. i used [change] to "stop" the streams, but it ended up creating note "jumps" which screwed up which notes were supposed to be triggering. so after alot of research and tinkering i used the [threshold] object. i tried it before as well and it didnt work because the data stream was a flow of 0 bangs, from what i can understand and pressing the key would make it go to 1 which made the calculation for threshold, between "0" and "1", so i multiplied it by 3 first, then set the arguments to [thrreshold 3 2 1 2] and ran both outs to a toggle object. it aint pretty but it does exactly what i want.

thank you for the insight. i am posting the simple patch here for posterity.

cheers,

onyx

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