redhexagonal

I'm a bit hazy on the concepts behind O.S.C. the udp system seems to work if i use the adress 127.0.0.1 and port 7400 as it uses in the example. is this the best configuration? i have no idea what the numbers are derived from.

which-udp-adressport-should-i-use

(i'm sending data over UDP to and from max msp to a pluggo made VST in in Ableton Live)

(i'm sending data over UDP to and from max msp to a pluggo made VST  in in Ableton Live)


it's *fairly* irrelevant, as far as i know.

there are several ports that are reserved by the os (for such things as ftp and the like), but those are generally lower numbers.

really, you just need to make sure you are listening on the same port you are sending on, and check your max window for any error messages. if 7400 works, stick with 7400.

it's *fairly* irrelevant, as far as i know.
there are several ports that are reserved by the os (for such things as ftp and the like), but those are generally lower numbers.
really, you just need to make sure you are listening on the same port you are sending on, and check your max window for any error messages. if 7400 works, stick with 7400.
-rob


so what does the adress mean- can i change that?

> 127.0.01 = local host = communication inside a single machine

127.0.0.1 is localhost - that should work on any machine.

> Important note about that : the machines (pc, mac, coffee 

> machine...) should always be in the same ip range. If one is 

> 45.346.09.01, the others should named 45.346.09.xx.

Nope, not true; if the machines have gateways configured, they should 

be able to route UDP packets without any problems.

> Port is the port the machine with that ip adress is listening to. 

On a Mac (or a Linux box), the file /etc/services gives a list of the 

> Important note about that : the machines (pc, mac, coffee  
> machine...) should always be in the same ip range. If one is  
> 45.346.09.01, the others should named 45.346.09.xx.

Nope, not true; if the machines have gateways configured, they should  
be able to route UDP packets without any problems.

> Port is the port the machine with that ip adress is listening to.  
> It can listen to several ports.

On a Mac (or a Linux box), the file /etc/services gives a list of the  
common IP ports and their standard uses.

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.loadbang.net


> > 127.0.01 = local host = communication inside a single machine

> 127.0.0.1 is localhost - that should work on any machine.

on windows a localhost which is not working (I mean 

is often a failure in the tcp/ip stack, and on *nix/linux it should

already be working because some service use this address.

> > Port is the port the machine with that ip adress is listening to.

> On a Mac (or a Linux box), the file /etc/services gives a list of the

> common IP ports and their standard uses.

The lists of the the assigned port can be found at

http://www.iana.org/assignments/port-numbers.

anything about port don't use a port number < 1024 and I will

recommand using a port number in the range 49152 - 65535 which are

On 7/25/07, Nick Rothwell  wrote:
> > 127.0.01 = local host = communication inside a single machine
>
> 127.0.0.1 is localhost - that should work on any machine.

on windows a localhost which is not working (I mean ping 127.0.0.1)
is often a failure in the tcp/ip stack, and on *nix/linux it should
already be working because some service use this address.

> > Port is the port the machine with that ip adress is listening to.
> > It can listen to several ports.
>
> On a Mac (or a Linux box), the file /etc/services gives a list of the
> common IP ports and their standard uses.

The lists of the the assigned port can be found at
http://www.iana.org/assignments/port-numbers. If you don't know
anything about port don't use a port number < 1024 and I will
recommand using a port number in the range 49152 - 65535 which are
dynamic ports.

which UDP adress/port should i use?