I have a incoming data from Arduino if a sensor is pressed or not pressed

sometime I have a rapid change between 1 to 0 and then to 1 again all in a small interval of time. I would like to prevent that so if the data went 1 --> 0 --> 1 in less then x ms the output will be a constant 1 rather then 1 --> 0 --> 1

how can I do so in pd?

Thanks

@KMETE This whole thread has some interesting solutions for just about any debounce problems you might have....... https://forum.pdpatchrepo.info/topic/12092/debouncing-was-measure-time-between-two-bangs-events
David.

@whale-av said:

https://forum.pdpatchrepo.info/topic/12092/debouncing-was-measure-time-between-two-bangs-events

I look at the filter patch in that topic. But it seems not doing what I'm looking for.

I would assume that the output will be constant 1 when the toggle is go 1 - 0 - 1 less then 172ms. instead the output is constant 0.

filter2.pd

edit: the metro is simulate a false triggering

@KMETE And how about this: timegate2-demo.pd

Perhaps simpler with [delay].

hjh

@KMETE I think though, that if you want the data to arrive on time, you have to incorporate a [spigot]......
debounce.zip
I could be wrong about that....
David.

@whale-av said:

@KMETE I think though, that if you want the data to arrive on time, you have to incorporate a [spigot]

If I'm reading this correctly, it would do the opposite of what the OP specifies.

The OP says, we're starting at 1. Then at some point, a 0 comes in and a 1 very quickly after it. In that case, the 0 should be suppressed.

The debounce.pd abstraction would pass the 0, and then suppress the 1.

The requirement is to pass through the last of a rapid succession of values, which I believe my [delay] patch does. (Also, with the requirement as stated, it's impossible to do "on time" because you have to wait to see if another value will come in quickly.)

hjh

@ddw_music I was thinking of the first float received....... if the instant of the button press is important?
That first 1 should pass..... and then the door is shut for the specified time.
[spigot] can shut the door after "correct" data has passed..... and [delay] can then be used to re-open it for a future correct button press without any delay to that data.
I agree that [realtime] is probably over-engineering for a debounce.
David.