[ANSWERED - firewall settings] OSC not working following upgrade to Isadora4

[njh74]

Hi all,

Wondering if you could share some light on this behavior. We have an installation that transmits stringified JSON data over a local network via OSC into our Isadora file. We've been using this system just fine for the last year with no issues of stability or data loss. However, upon our recent upgrade into Isadora 4, Isadora no longer autodetects, or manually detects any data coming from our server. We've verified that Isadora 3 still functions as expected, even while I4, with the same configuration does not. 

Were there any major changes to the OSC system under the hood in the update? Or any configuration changes we should make? Any advice would be greatly appreciated. Thanks.

[mark]

@njh74

First, please add your system information to your signature line as requested in this pinned post. It really helps us if we know more about your setup, e.g., what platform and what version of macOS.

That said, there should not have been any major changes to OSC – what changes were made can be seen in the Isadora 4 Release Notes (search for OSC).

I just did a test with Isadora 4.0.1 on both macOS and Windows where I send messages from a computer running Isadora 4 to another computer using Isadora 4. The messages were received just fine. I also tested with an app on my phone called GyrOSC. It also works perfectly for macOS and Windows, as does TouchOSC on an iPad. So it does not seem to be some kind of issue with OSC in general.

Let's cover some basic things.

First, open Isadora 3. What is the OSC port set to in the Isadora Preferences?

Now quit Isadora 3 and open Isadora 4. Check the OSC port. Is it the same?

Second, I assume you are sending to addresses defined in the Stream Setup window. One of the changes we did make was to ensure that invalid, non-ASCII characters would be rejected by that Window, because OSC only allows the use of ASCII. Could it be that your OSC address patterns use a non-ASCII character?

Can you share a screenshot of the Stream Setup window so we can see the addresses? Have you looked carefully at the Stream Setup? Or are you possibly using addresses like /isadora/1, /isadora/2, etc.?

Is the patch something you are willing to post here so we can examine it? If not, please open a ticket so you can privately share the patch with us.

Best Wishes,
Mark

[njh74]

@mark

First off -> signature updated. Thanks for the reminder!

Second, thanks for the help and information -> we did verify all configuration was unchanged between I3 and I4. I managed to solve it yesterday after checking Windows Firewall settings. During the upgrade, they had gotten messed up and weren't allowing any incoming data on private networks. After enabling data transmission, OSC resumed complete functionality. Apologies for the raised issue!