Hello,

I am trying to detect a specific range of midi note and send them using OSC.
The thing is, my range is big and therefore I am receiving a lot of OSC message.

I am using a snare drum, using PureData I saw that the drum midi note is usually between 48 and 49, I am looking for a solution to detect when the drum has been hit or not.

When I am hitting the drum, sometimes, PureData detect and send 48.2 / 48.4 / 48.5 (for example) so I receive three "hit" instead of only one.... I searched for a timer in order to send only one OSC message in an interval but can't find anything .. A timer or any other idea coming in your mind..

I hope I was clear enough...
Here is my patch :
Fiddle_OSC.pd

Thank you for your help and advices,
Greg

@Glhd2 Hi, instead of fiddle~ you can use sigmund~ with the flag "notes", which outputs pitch only at the beginning of a note rather than continuously, which you can then round with [int] and pass through the two moses as you did to detect values within a range.

Hope this helps.

Hey weightless,

Thank you for your answer.
Unfortunatelly, I tried this morning and sigmund is not as accurate as fiddle and therefore there are some hit it doesn't even detect...

Do you know how to use Spigot?
I was thinking maybe I can use it to send the note every 500ms ... with a metro object as a condition... What are your though?

@Glhd2 Hi, my suggestion was based on the fact that the help file for fiddle~ itself suggests to use sigmund~ instead, even with continuous pitch output in which case it'll act the same as fiddle~. But of course, use what works best for you

Here is how I'd do it. It outputs a note only after a specific time has passed since the last output. You can play with the delay time until you find a value that fits your input.

debounce.fiddle.pd

Thank you very much, it does work perfectly !

However, one last question, based on my patch, do you know if it is possible to outputs a note only when a bang is detected ?

I am struggling since this morning trying to find a way to convert a bang to 0 and 1 so I can use it with spigot... I think I am missing a point there... Why can't we use it in this way ?

Bang off -> 0
Bang on -> 1

It seems so logical in my head but not for Pd I guess ..

@Glhd2 Perhaps something like this:
(assuming the bang comes before the note)

@Glhd2 maybe

[int]
|
[change]

to filter the range to one value

@weightless thank you it does work !
However, I don't know why but sometimes even if the value change I don't receive the OSC message ... Strange.. Anyway, I will try to calculate this failure rate in order to access the viability of the process or not.

Thank you very much for your precious help !

@Balwyn Thank you for your help but I already tried a [change] unfortunately it is not precise enough... Because sometimes the note will change from 54.23 to 54.30 and it will not be detected...

But [int] will remove the fractional part so 54.23 = 54 and 54.30 = 54

@Balwyn exactly !

So when i'll hit the drum two times (54.23 and 54.30) the value wouldn't change so there will be only one OSC message sent : 54 !
And because I hit two times I would like to have two OSC messages !

If you have (or are willing to download) the cyclone externals you could use the "onebang" object and attach that to a metro, or to a delay from its own output.

@nineofkings [onebang] can be easily implemented as a vanilla abstraction. In fact there's [once] (I think from iemlib library) which is a vanilla abstraction. You can use a [spigot 1] to let the bang through, and then close that [spigot]. You can use a right inlet in the abstraction to open the [spigot], hence reset the abstraction.

Thank you for help, I will try that later could be a good option !