Find IP address of device sending OSC data

Yes, there is a way to find out from which ip the osc message is coming from.

But,

You'll have to write an external which opens up a new socket and handles the data parsing itself. Caus every time you receive/send and osc paket you are, sending/receiving an ethernet frame. and inside that frame there is always the information from which ip address this paket was sended. Always. And still i keep asking me again and again why they havent implemented that inside the osc paket, the information is always there.

Unfortunetly, the udpsend / udpreceive filters that information and i do not know if you can access a socket in mxj. In js it is not possible.

However,

In the next weeks we are releasing a firt version of our "magic protocol" which was developed to use the high bandwith of an ethernet connection in combination with the osc protocol. But it also has some extras which gives the users a lot more comfort. With "magic protocol" you can do everything you can with osc. You can even use native osc, native midi and transport it via ethernet, usb or whatelse. But there is no need to assign ip addresses or any other network settings. Also it "sees" other devices and automatically connects them, virtually and physically. Even when using it in complicated network enviroments or when having to devices directly connected, you do not need to assign any setup.

Unfortunetly, the first version which also comes as an external, is just there to connect our hardware, a keyboard with highres data. The reason why we developed the protocol.

In the next months however we are releasing the second release of our protocol. In this you'll get an external which lets you use the amazing functions. Also we provide an sdk and a framework for every development system so you can access our protocol inside your "normally" programmed applicaton.

In your case, if you just send osc data to a patcher containing our external it will put out the data with ip information in addition.

And, in your case, as an example of our protocol. Having it running in, for example, touchosc and inside your patcher, you can easily see from where the data is coming and beyond that you can use routing, mapping and encapsulation functions.

Also having two patchers running our "magic protocol" external, both patcher running on different machines but connected thru a network, you can simply pass max lists, symbols and messages between these to patchers ..

The best,

The "magic protocol" is a sub-product of the development of our keyboard and offers a lot more comfort ... And it will be all released OPEN SOURCE ...

Simon
www.endeavour.de