You can use the OSC Data Monitor to quickly check if you have communication with OSC (Open Sound Control) sending equipment in your network. It helps you also to organise and make sense of the large stream of different OSC messages send by a system.
2 Minute walkthrough video
Features
- Displays the IP Address of your computer
- Monitor multiple network ports
- Filter specific messages
- Show updates per OSC message (one line per message)
- Clear view
MacOS
The application is available for Apple Silicon (recent Macs) or Apple Intel. The version is signed, so you can use it on any system without too much hassle.
Windows
Windows build is also included, although it’s not signed. You’ll get a dialog that “Windows protect your PC”, press “More Info” and click “Run Anyway”.
Linux
For Linux I recommend to use Processing and build an application yourself if you need it.
Download
The OSC Data Monitor application is available for $9.99. To make it accessible for people with a small budget, you can choose to pay between $6 and $9.99. Thanks in advance for your support.
Get the OSC Data Monitor Application here
I you have no budget, you can also download the source code and run it in Processing (see source code on Github).
About
OSC DataMonitor was developed in Processing with help of the OscP5 and ControlP5 libraries (Thanks Andreas Schlegel (sojamo) for these excellent libraries). You can find the code on Github. You can run in it directly in Processing, when you install the needed libraries.
OSC Explained in 8 minutes
In this video I explain how Open Sound Control (OSC) works. Open Sound Control was introduced as a replacement for MIDI, which is a standard to connect musical equipment. Open Sound Control is a very easy protocol, if you like to connect different software tools with each other within your computer or within your local network.
I’ve just managed to get touchosc (partially) working on iphone (4s) with logictouch template & reaper (5) daw wirelessly. I was going to fix the template, but when I run the osc-datamonitor I get the no jre message…
I’ve installed java 8, which fixed the same issue with touchosc…
Does osc datamonitor require an earlier java?
Also having problems opening the app. It says it requires Java 6 Runtime. Is there a version for newer Java?
No, but you can make it yourself. Processing code is available.
Great work!
Thanks!
Hi, OSC monitor are blocking port when lisening it. Other aplication can not receive OSC message in the same time in the same machine. Is it a bug or correct action?
Thanks for that tool. I have it running fine on Mojave.
However: how do I change the IP address that I want to listen on? I have several OSC-apps running on my computer so I want to listen to my local IP “127.0.0.1” but the data monitor just listens on my LAN address.
Thanks!
New to OSC.
It seems the target software binds to the destination port so I cannot monitor the traffice unless I close down the target software?
it seems not working on Mac OS Catalina, it showed nothing in the app but grey backgorund.
Hello I’ve the same question than Robert Janiaksays:
10-06-2019 at 15:33
Hi, OSC monitor are blocking port when lisening it. Other aplication can not receive OSC message in the same time in the same machine. Is it a bug or correct action?
This is a correct action.
Hi Kasper! Thanks for this software ;-)
I have the simillar background than Nathan Leung:
“it showed nothing in the app but grey backgorund.”
I run OSC Data Monitor in Catalina. Someone dependencie?
Fantastic! Thanks for making this Kasper. I am working at connecting openFrameworks to Unreal Engine – and this was a tremendous help. My only issue – was the blocking (same as comments above) – I missed this part and was debugging for a couple of hours ;) Turned Data Monitor off and everything was working perfectly.
Hi Kasper
thanks for the clear video
I am currently sending OSC messages from Python to my Ableton M4L OSC touchOSC object.
I am trying to send multiple OSC at the same time but it does not seem to work.
I use the OSC TouchOSC in Ableton but not all messages pass through.
Another question is it possible to change the IP address of the Server on the OSC data monitor?
Thank you
Regards
Valerio
The monitor is a monitor, so you can’t change the ip-address.
Thanks for making this and making it available for free.
Hi Kaspar
First of all thank you for that tool!!
I just have one question:
I only can monitor the internal loopback ip: 127.0.0.1
what do i have to do to monitor other IP addresses… Iam using the monitor on a Mac M1 Processor.
Thank you so much in advance
With the monitor you should be able to monitor all the devices in your network (so devices that are visible to your computer).
Of course they have to sent data out (broadcast or specifically to your IP). On the top-left corner you should see the IP-address of your computer.
I Understand what you are saying about being able to monitor IPs on my computer, but I have added a network interface card to my computer and disabling my wifi just monitors the local address. I would like it to monitor the added Network Interface Card, which is where my OSC is coming into my computer through UDP, but it will not select that. Please Advise
You computer only has one IP-address. What do you hook up to your network card? If that device doesn’t hand-out an IP-address it doesn’t work.
Device to device you need a cross-link cable. Or better, use a Router. Connect your computer to the Router, connect your sending device too.
In Windows you can find your ip-address in the command line (cmd) with ipconfig.
Network communication doesn’t work like Midi or USB.
Struggling with monitoring the network. Using the Mac Intel version and I can’t change the IP address. It defaults to 127.x.x.x the laptop loopback IP. It won’t take the network IP of wireless or ethernet networks. Any idea why this is or how to fix it?
Thanks
Mostly your computer get’s an IP-address from a DCHP server and the OSC Data Monitor should show the IP that you see when looking it up in the WiFi settings.
The IP is set at startup of the monitor. Maybe it goes to 127.0.0.1 because there are multiple interfaces (I assume both WiFi as wired?). You could try to switch on off (or remove ethernet) and restart the monitor to see if it show the correct IP.