Hi list,
I am struggling with this for many years, and looks like cannot solve the issue of the tcpsend object which disconnects by itself. Would be easy to reconnect if I had an outlet with the info if connected or not like netsend has. Is there any solution to keep it connected stable?
Any hints welcome.
Best, Popesz
Hey Csaba
On Thu, 2023-10-26 at 19:51 +0200, Csaba Láng wrote:
I am struggling with this for many years, and looks like cannot solve the issue of the tcpsend object which disconnects by itself.
Which [tcpsend] are you talking about? There are two flavors around:
- mrpeach (unmaintained)
- iemnet (recommended)
Would be easy to reconnect if I had an outlet with the info if connected or not like netsend has.
I checked iemnet's [tcpsend] and it has only one outlet whose sole purpose is to indicate whether it is connected or not.
Is there any solution to keep it connected stable?
It appears that the outlet only sends 0, if the disconnect was initiated by [tcpsend] itself. It happily stays at 1, if the other end quits the connection. This is clearly a bug and should be reported:
https://git.iem.at/pd/iemnet/-/issues
Until this gets fixed, you could:
replace [tcpsend] with [tcpclient]. Its third outlet reports the connection state correctly.
use [netsend -b] from Pd which reports connection state correctly on the first outlet
Actually, I don't quite see the purpose of [tcpsend] as [tcpclient] covers all its capabilities. Probably it is there only for historic reasons.
Roman
-
Csaba Láng -
Roman Haefeli