[sc-users] Re: SwingOSC: unexpected behaviors

Andrea Valle valle at di.unito.it
Fri Mar 2 18:52:06 PST 2007


On 2 Mar 2007, at 18:14, Sciss wrote:

> hmmm, this is weird. obviously the TCP connection cannot be  
> established ("Primitive '_NetAddr_Connect' failed"), but why...?  
> maybe try with a port different than 57111?
>
> also maybe check if there are any firewall message(?). like in /var/ 
> log/ipfw.log (or go System Preferences -> Sharing -> Firewall ->  
> Other Options -> Open Protocol.
>
> let me know if it works
>
> Am 02.03.2007 um 18:06 schrieb Andrea Valle:
Thanks Sciss.

As you suggested I booted SwingOSC from terminal with:

andrea-valles-computer:/Applications/SuperCollider_f andreavalle$  
java -jar SwingOSC.jar -t 11111 -i -L
SwingOSC v0.5. receiving TCP at address 127.0.0.1:11111

I changed port to 11111 (randomly). Then  as before:
g = SwingOSC.default;
g.addr.isConnected;  // --> false

So
g.connect;

generates this, in which there's no trace of 11111 (57111 instead)

Could not connect socket
ERROR: Primitive '_NetAddr_Connect' failed.
Failed.
RECEIVER:
Instance of NetAddr {    (0D9F93E0, gc=28, fmt=00, flg=00, set=02)
   instance variables [4]
     addr : Integer 2130706433
     port : Integer 57111
     hostname : "127.0.0.1"
     socket : nil
}
CALL STACK:
	MethodError-reportError   0DC844B0
		arg this = <instance of PrimitiveFailedError>
	Nil-handleError   0DC84450
		arg this = nil
		arg error = <instance of PrimitiveFailedError>
	Object-throw   0DC843F0
		arg this = <instance of PrimitiveFailedError>
	Object-primitiveFailed   0DC84390
		arg this = <instance of NetAddr>
	NetAddr-connect   0DC84330
		arg this = <instance of NetAddr>
		arg disconnectHandler = nil
	SwingOSC-connect   0DC842D0
		arg this = <instance of SwingOSC>
	Interpreter-interpretPrintCmdLine   0DC84270
		arg this = <instance of Interpreter>
		var res = nil
		var func = <instance of Function>
	Process-interpretPrintCmdLine   0DC84210
		arg this = <instance of Main>



Assuming you meant Sharing-->Firewall-->Advanced-->Opend log,  
ipfw.log is empty, i.e. contains:

===== Log file is empty =====


Opening the crash log (as I did following your instructions to get  
via system prefs the ipfw.log),  the only info  I can recognize is  
when I tried to use udp instead of tcp.

Andrea Valle

CIRMA - DAMS
Università degli Studi di Torino
--> http://www.semiotiche.it/andrea/
--> andrea.valle at unito.it

Andrea Valle

CIRMA - DAMS
Università degli Studi di Torino
--> http://www.semiotiche.it/andrea/
--> andrea.valle at unito.it


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.create.ucsb.edu/pipermail/sc-users/attachments/20070302/b715a0fd/attachment-0001.htm


More information about the sc-users mailing list