OSC port 1234 stopped working, other ports work fine

trevorn1

This isn't too much of a problem, but I've been using bitfocus companion with isadora and Zoom OSC and I'm no longer able to have Isadora recieve OSC messages on port 1234 and I switched to another port and it's fine, does anyone know why that would be?

I checked my firewall, tested other ports, and tried other apps and I can't get port 1234 to work. I switched to a different port and everything is working fine now but it just seemed odd. I know you can only have one listener on each port, thought I was keeping that one clear, won't work on any application.

Thanks!

Trevor

Woland

@trevorn1 said:

does anyone know why that would be?

Something else must be using that port. QLab maybe? OSCulator?

trevorn1

@woland Doesn't seem to be, but surely something has grabbed ahold of it. I see now that's a tough thing to figure out. Not sure if there's a way to discover what has grabbed that port, but definitely a problem/issue on my computer and not Isadora. Thanks for such a quick reply, it should be fine, I'll poke around a bit more and see who's taking up that port.

Thanks again!

- Trevor

mark

@trevorn1 said:

. I see now that's a tough thing to figure out.

Actually, you can find out pretty easily do it from the Terminal.

Restart your machine and open a Terminal window. (Don't open Isadora!)

Enter the following command.

lsof -i4UDP:1234

and hit return. The result will show you what process is using the port. When Isadora is running on my machine, it says

COMMAND  PID      USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
Isadora 1073 mconiglio   42u  IPv4 0xd3288f011e6d613d      0t0  UDP *:search-agent

If the process using the command is mysterious, you can try using Activity Monitor to look for the matching PID (Process Identifier) number.

Best Wishes,
Mark