|
|
Feb 13, 2011 at 9:12pm
Is there any way to confirm udpreceive successful binding?
udpreceive posts an error/warning if it can’t bind, but is there an IN PATCHER flag that i can use to try again?
if not, I would like to make a request/suggestion of adding another outlet for such a flag.
|
|
|
Feb 13, 2011 at 9:30pm
Maybe you could test the connection after instantiating it by sending a test message to localhost on the same port.
-A
|
|
|
Feb 14, 2011 at 12:22am
Thank you for your help. I have a patch doing just that now thanks to your suggestions and guidance.
One more question about this for anyone with an answer. It seems like Max is OK with 2 udpreceives on the same port in some cases, what are those cases? Is there a simple rule that i should keep in mind to determine when max will or will not bind successfully?
|
|
|
Feb 14, 2011 at 9:29am
It seems a bit intermittent to me, I usually set up one patch as a UDP receiver and send to all other patches
|
|
|
Feb 14, 2011 at 10:24am
I have some abstractions that depend on receiving data from a particular UDP port. To make sure the data is still received in case the user has multiple copies of the abstraction open and the latter ones fail to bind, I connect a send object directly to the udpreceive, and the subsequent receive object to the rest of the patch. That way there will always be at least one object bound, which can share data with all the other copies of the abstraction.
|
|
|
Feb 15, 2011 at 7:34pm
Thank you, i ended up pinging to check if it is unbound or bound multiple times. in either of those cases, i change ports and try again.
|
