Hey,

I'm experimenting with a patch where a bang is sent every time a number exceeds a certain threshold (which is set to happen relatively infrequently).

I am then sending that bang out in a send object message.

Infrequent Trigger

Bang

Send x

When I set-up a receive object message and connect a bang to it, though, the receive message bangs very frequently (though not constantly), while the send object is only sending infrequent bangs.

Receive x

Bang

Does anyone know why that might be?

Best
Jess

@Jess It could be that you are using [send pd] and [receive pd]...... ?
Pd uses that send/receive address for internal messages.
But perhaps there are others and you are unlucky?
What is the name you are using...... we will see if it does the same for us.
Or you could attach a [print] to your receive to see what is actually arriving and that could give you clues.
David.

ah, great thanks!

I had a dot in the name, perhaps it didn't like that. I've just renamed it and it synchs fine now

thanks for your help

@Jess That's interesting. What was the name?
David.

hmm, you know I'm not sure that was what fixed it!! I tried loading it again this morning and had the same issue even with the new name.

I restarted PD and set-up a new receive object and it seems to be working again now, I'll keep an eye on it for a bit to see if was a glitch or if it's a persistent problem. I'm feeding the patch that creates the send object with arduino sensor data, perhaps that's making it jumpy/temperamental

thanks for your help, I'll come back with more details if it happens again

Best
Jess

@Jess Just curious: what test did you perform to conclude that the bangs you are sending are infrequent?

Yes, and maybe try the following:

• As Whale-av says print the sender and receiver
• Test with a cord instead of s/r
• Maybe you're using a "sel 1" object on the sender and not the receiver (to make a bang from a toggle)?
• Post the patch here, this is strange indeed

And another idea: if you're using [>=] or similar to detect threshold, make sure it's followed by a [change]?

There might also be a hidden send within the properties of a graphical bang.