[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sc-users] Re: OSC trouble with proce55ing and SC Server

To: sc-users@xxxxxxxxxxxxxxx
Subject: [sc-users] Re: OSC trouble with proce55ing and SC Server
From: rd@xxxxxxxxxxxxxxx
Date: Thu, 5 Jan 2006 14:58:17 -0800 (PST)
List-archive: <http://www.create.ucsb.edu/pipermail/sc-users>
List-help: <mailto:sc-users-request@create.ucsb.edu?subject=help>
List-id: SuperCollider users mailing list <sc-users.create.ucsb.edu>
List-post: <mailto:sc-users@create.ucsb.edu>
List-subscribe: <http://www.create.ucsb.edu/mailman/listinfo/sc-users>, <mailto:sc-users-request@create.ucsb.edu?subject=subscribe>
List-unsubscribe: <http://www.create.ucsb.edu/mailman/listinfo/sc-users>, <mailto:sc-users-request@create.ucsb.edu?subject=unsubscribe>
Reply-to: SuperCollider users mailing list <sc-users@xxxxxxxxxxxxxxx>
User-agent: SquirrelMail/1.4.4

> It doesn't have to do with ports. I let proce55ing listen on port
> 57120, instead of its usual 12000.

scsynth replies to the address the incoming message was sent from.

This is a good design, it allows any number of clients to send
messages and receive any relevant reply.

Ie. you need to listen for the reply on the address you send from.

Ie. I suspect processing is not sending from port 57120 (quite
possibly is binding the send port using a NULL address).

Regards,
Rohan

Prev by Date: Re: [sc-users] Re: More on OSC trouble with proce55ing and SC Server
Next by Date: [sc-users] Re: OSC trouble with proce55ing and SC Server
Previous by thread: [sc-users] Re: [sc-dev] Re: calling the stream upon EventStreamPlayer-stop
Next by thread: [sc-users] Re: OSC trouble with proce55ing and SC Server
Index(es):
- Date
- Thread