Is there any likelyhood of Nomad being able to utilise a second ip address as the consoles can? Or is that a purposeful limitation?
Is there any likelyhood of Nomad being able to utilise a second ip address as the consoles can? Or is that a purposeful limitation?
If your computer had two network adaptors like the console, I don't see why it wouldn't work. It's the same software.
but I'm no expert.
No, Nomad currently only handles one NIC
You say currently.. ...? Are there plans to introduce it?
I have no idea, I'm not suggesting anything. I'm just stating the current situation
What's the difference between Nomad on a PC & Nomad on an EOS console that prevents this?
Same software. Same OS.
ETC promised years ago that they will solve the problem, annoying.
What were you actually wanting to do with the second ip address.
I'm asking as at least on Mac Nomads you can have 2 ip addresses. I have a wired LAN connection that goes to my sACN/Artnet stuff and on the wifi I can control Nomads with oscRFR and iRFR (classic).
That's precisely what I was hoping to be able to do. Rig control on one ip and remote access on a second ip. Not available on pc Nomad as far as I'm aware.
I want to switch of sACN on wireless, I'm on mac.
I tried this on a windows 10 notebook with Nomads and it actually works for me.
Its a little strange in that it doesn't show the second network on the setup but it seems that if when you do the setup you have the wifi off so you select the wired interface for the rig then if later on you bring the software up with the wired interface connected and the wifi connected it quite happily receives OSC over the wifi and sends to the rig on the wired LAN.
It does kind of make sesne that as long as EOS knows where to send the DMX to, that its not going to explicitly say only accept OSC on the networks you are sending DMX on, so it probably simply isn't fussed about adding a filter to the socket listen to restrict to a specific network.
This was implemented for Nomad in 3.1.0.
www.etcconnect.com