posted 05 December 2012 13:03            

1a) If I want to monitor messages being sent to kyma in Osc Monitor what Host name and port number should be keyed in.

1b) Could someone share the command line prompt required to keep send+Dump Osc actively running? As it stands when the program is run it seems to be executed once and stop rather than be continuously monitoring Osc messages and displaying.

or

2) Does anyone know of any alternative Osc message monitoring software similar to Midi Monitor? Preferably with some documentation

cheers

Rafe

posted 07 December 2012 06:31            

quote:

---

Originally posted by rafe:
I have been looking at Osc monitoring software, Osc Monitor and the terminal application, send + dump Osc from CNMAT but neither have documentation. I am not able to get either software to operate correctly. Osc monitor gives error messages no matter which "local host" and port number i attempt to monitor. And Send+Dump Osc requires some command line knowledge to run which I haven't any knowledge of.

1a) If I want to monitor messages being sent to kyma in Osc Monitor what Host name and port number should be keyed in.

1b) Could someone share the command line prompt required to keep send+Dump Osc actively running? As it stands when the program is run it seems to be executed once and stop rather than be continuously monitoring Osc messages and displaying.

or

2) Does anyone know of any alternative Osc message monitoring software similar to Midi Monitor? Preferably with some documentation

cheers

Rafe

---

I am not aware of any "OSC snooper" style tools. Unlike a MIDI monitor where it is possible to "listen" to a MIDI port and then display the activity, OSC commands are "point to point", meaning that the sender directs the command to a specific destination. (OSC can be used "multicast" but that is rare and not universally supported). Specifically the sender directs the message to a specific IP address and port number.

This presents a number of problems when trying to monitor OSC. For example suppose you wish to monitor OSC activity directed at the Pacarana using you Mac. The Mac would have to somehow intercept messages intended for the Pacarana. The kind of OSC monitoring tools that are readily available are not capable of doing this. They can only monitor OSC messages directed at their computer's IP address and whichever port you set them to monitor.

What you need is a fairly sophisticated tool called a "network monitor". These allow low-level "snooping" of network activity. OSX even has one built-in, its a command line program called "tcpdump". Unfortunately using these requires a good understanding of how networking works at the lowest levels. So there is a steep learning curve but its also very comprehensive and useful.

I think if your primary goal is confirming what your OSC sending application is actually sending then the easiest approach is to use of of the OSC monitoring tools you mention (or something like Native Instrument's Reaktor that has an OSC monitor built-in) and redirect the OSC to the monitor while testing/confirming. This is very easy to do in the Lemur because can use the Lemur's preferences to change the assignment for the OSC output you have assigned to your script or widget. Once you are satisfied that your script/template is sending what you wish to send you can then switch the OSC assignment back to KymaConnect/Pacarana.