hey,
i am very new to pd - i am setting up a routing of OSC messages into MIDI and now i am faced with the problem that my OSCs will probably come rapid fire and i need to have a break between my note messages being triggered.. so, what is a function that stops data from flowing for a specified time?

also, i need to make a threshold where only numbers higher than a certain decimal can trigger the MIDI messages.. i read something earlier about a 0/1 function, but i don't quite recall how to use it..

thank for any input!

oh btw - why can't i delete unused object boxes?

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

for threshold:

[moses 64]

any number less than 64 will go to the left outlet, and any number higher will go to the right.

there is also [threshold] ....(i think)

or,

[> 64]
|
[sel 1]

will bang when the number is greater than 64. (to include 64, use [>= 64]

to stop messages, you can use the external [speedlim], or make a similar thing using a [spigot] and a [delay]

@noahcohn said:

also, i need to make a threshold where only numbers higher than a certain decimal can trigger the MIDI messages..

there's also [max], that gives out the higher of two numbers, respectively only numbers, greater than the first argument.

@noahcohn said:

oh btw - why can't i delete unused object boxes?

i can!
try to select the object, you want to delete, by dragging a frame around it with the mouse. if you click on the object box, pd expects you to type in the name of the object, you want to create.

thank you guys! moses and timelim are exactly what i needed..

i have another little puzzle now - what if i want a message triggered only when two other triggers happen at the same time?

you'd probably have to think about that logically and construct something.

hint: the two triggers won't happen at EXACTLY the same time, so you'd probably need to specify the maximum time in which 2 can take place. I'd suggest that below 10 ms is pretty close to the same time.

[delay 10]
|
[0 (

will reset to zero after 10 ms.

hopefully that's enough to get you on your way

ah.. i have an idea - a counter starts at 100 when one function hits - then if trigger 2 hits it adds 100 again making the number higher than 100 only in that case..

thanks for the help!