@dbini said:

would be perfect if it could update dynamically

 I can see it being useful to be able to choose which network it should use (and use the IP the computer has for that network) but dynamically updating seems like it could be annoying. 

Example: If I've got a LAN with no internet access set up for NDI and Isadora's using that properly, then I switch my computer in network settings to use my WiFi instead of the internet-less LAN in order to use IzzyCast or the RTMP Streamer actor or the Screen Capture actor to scrape a website, if Isadora followed my computer's network settings automatically then Isadora would be doing the opposite of what I'd actually want. 

There's some thought that needs to be put in here as to default behavior, dialogs, warnings, and what makes sense to allow automatically vs what should be required to be done manually. Overall I don't think it's ideal to have a workflow that involves switching between networks multiple times in the first place, so I'd want to just be able to manually select which network Isadora should use and I'd never want it to change anything about that automatically. This solves the major problem of the use case where I've got multiple networks running on my computer and need to disable all but one of them before launching Isadora to ensure that Isadora starts up and uses the network I want it to use, but I'm curious what workflows and use cases would involve needing to automatically switch between networks, or to switch between networks repeatedly.

@dbini said:

Am I right in thinking that Isadora scans for IP address on startup, and then sticks with that address?

 Also yes, this is the current behavior. It's also the same for the OSC Port selected in Isadora Settings/Preferences. This is locked in at startup and changes to it will only take effect after you quit and re-launch Isadora.

@dbini

There's an existing feature request for this and I've added the text of your post here to it.