oscalculator setup: midi to osc 2020

i don't know the other program, but it looks like it's sending OSC through TCP and not through UDP. so you should remove 3032 from OSC UDP RX Port in Eos. the TCP port in eos is currently hard-coded as 3032, so you don't need to configure it on the Eos side.

in eos setup you can disable String Rx and String Tx, it has nothing to do with OSC.

you're trying to send from one application to the other, both runnnig on the same computer, right? in the OSC Routes try replacing osc.tcp://localhost:3032 by using your actual IP address instead of localhost, e.g. osc.tcp://192.168.1.11:3032.

i don't know the other program, but it looks like it's sending OSC through TCP and not through UDP. so you should remove 3032 from OSC UDP RX Port in Eos. the TCP port in eos is currently hard-coded as 3032, so you don't need to configure it on the Eos side.

in eos setup you can disable String Rx and String Tx, it has nothing to do with OSC.

you're trying to send from one application to the other, both runnnig on the same computer, right? in the OSC Routes try replacing osc.tcp://localhost:3032 by using your actual IP address instead of localhost, e.g. osc.tcp://192.168.1.11:3032.

I was reading about yhard-coded 3032. That's why i figured this wasn't a personal mistake. This tutorial is just dated. 

I enable the String RX because it's what both the tutorials for OSCalculator and Luminosus tell you to do.

Yes I'm running nomad, I've already tried using the IP address, but that didn't work either and this is what was recommended for nomad.

I'll try turning off the string rx and removing 3032 from eos as you have said and see what happens. 

until maybe two years ago the String setting controlled both String and OSC, but then those two settings were split, so now the OSC Rx and String Rx settings are independent.

Great thanks, I tried the IP again and it worked this time. I think it was a combination of that and removing 3032 from the udp like you said.