[PD] dumpOSC problems "couldn't create"

Jack jack at rybn.org
Mon Jul 21 17:26:12 CEST 2008


Thanx for the link Claude.
It seems there is no way to force to close the connection (wait 10 mn  
or reboot the computer or change the port), it's a pity.
++

Jack


Le 20 juil. 08 à 12:34, Claude Heiland-Allen a écrit :

> Jack wrote:
>> Le 19 juil. 08 à 17:25, zmoelnig at iem.at a écrit :
>>> Quoting Claude Heiland-Allen <claudiusmaximus at goto10.org>:
>>>
>>>> [dumpOSC 5555] needs to be able to bind to network port 5555, if
>>>> something else is already using it (or if the previous user of  
>>>> the  port
>>>> hasn't timed out completely) then dumpOSC will fail to create.
>>> which btw, is by design and not a bug.
>>> it is the very same behaviour as the [netreceive] object has.
>> This is a real problem with [netreceive]. For example when Pd  
>> crash,  if you open your last patch, Pd can't create your  
>> [netreceive] with  the same port. Is it possible to force to close  
>> connection on this  port to solve the problem ?
>> ++
>
> http://lists.puredata.info/pipermail/pd-list/2007-06/050710.html
>
>> Jack
>>> and before i forget it: have i already said that i would advice
>>> everybody to _not_ use [dumpOSC] (as part of the OSCx library) and
>>> instead use mrpeach's [udpreceive] and [unpackOSC]?
>>>
>>> fadrm
>>> IOhannes
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>>
>>>
>>> _______________________________________________
>>> Pd-list at iem.at mailing list
>>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/  
>>> listinfo/pd-list
>> _______________________________________________
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/ 
>> listinfo/pd-list
>





More information about the Pd-list mailing list