Ah yes, you are right. [timeout( is for TCP. I think I got that mixed up with UDP previously closing itself after some sort of unknown host return etc which we removed to make it "fire and forget."
On Jun 4, 2021, at 4:17 PM, pd-list-request@lists.iem.at wrote:
Message: 3 Date: Fri, 04 Jun 2021 16:17:29 +0200 From: Roman Haefeli <reduzent@gmail.com mailto:reduzent@gmail.com> To: Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> Cc: Pd-List <pd-list@lists.iem.at mailto:pd-list@lists.iem.at> Subject: Re: [PD] UDP server with Pd Message-ID: <2aed329cdb23e198c96f658f05a81ce4f276bf84.camel@gmail.com mailto:2aed329cdb23e198c96f658f05a81ce4f276bf84.camel@gmail.com> Content-Type: text/plain; charset="utf-8"
On Thu, 2021-06-03 at 19:51 +0200, Dan Wilcox wrote:
You could try a longer connection timeout via the [timeout f( message.
Isn't the 'timeout' method only affecting TCP sessions? In UDP nothing at all is sent when using 'connect' method. It internally sets destination address and port, I believe.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/