Is there any way for GoButton to ignore consecutive OSC messages?

[Daniel Piñeiro]

Hello everyone! 

I’m working on a show that uses OSC (over UDP) to control GoButton, specifically to trigger hits. To ensure message delivery, I resend each message twice with a 30 ms interval, but sometimes GoButton processes more than one of them. Is there any way to make GoButton ignore identical messages received within a very short period of time? I have enabled Cue List Double Tap Protection, but it seems this does not affect incoming OSC messages. 

Thank you very much for your help and for this wonderful application!

[Brent Lord]

Hi Daniel --

Go Button does automatically discard duplicate OSC messages received within a 0.2 second window. The messages need to have arrived from the same client (IP address + port) and that client needs to have sent no other messages in-between (e.g. no repeat `/connect` message between your hit trigger messages).

You are right that "Cue List Double-Tap Protection" won't work for what you need. That setting only guards against physical on-screen taps. There is also "Min. Seconds Between Each GO", but that applies to just a GO, which means only the cue list and not hits.

Go Button does listen on TCP. If you are finding your UDP connection unreliable, are you able to send your messages with TCP instead and then only send each message once?

Brent

[Daniel Piñeiro]

Hi Brent! 

Thank you very much for your reply. I have tried making the TCP connection, and it works, but I am experiencing TCP connection drops at regular intervals (between 3 and 7 minutes apart), consistently. I have tried sending the OSC message /thump every 15 seconds, but the drops still occur. I'm not sure if Gobutton or my router is causing them. I couldn't find any keepalive function in the documentation — does one exist? 

Anyway, UDP already works perfectly, repeating the messages within the timeframes you indicated. 

Thanks and regards

[Brent Lord]

You shouldn't need to do anything special on the Go Button side to keep the TCP connection alive.

The "/udpKeepAlive" OSC command is something different from a true TCP "keepalive". In Go Button, that UDP command just exists to prevent client settings like "always reply" from expiring after the automatic UDP client timeout.

If you continue to have issues with your network reliability, please feel free to reach out to us at sup...@figure53.com. We'd be happy to help you troubleshoot.

Brent

[Daniel Piñeiro]

Thank you for your response. I finally found the problem, which was basically on my end.

 I didn't realize that in TCP, when sending /thump, Gobutton responds with a string, and I wasn't taking care for that. As a result, my TCP buffer was filling up after a few minutes, and this is what was causing the TCP connection to drop. 

As you said, I don´t need to do anything special to keep the TCP connection alive. 

Thanks again for your help!

Best regards!