Hi
I set up a pixel mapping installation yesterday and all went well, we had 24 Lumiverse's running over 4 different processors, wiith each processor having itsr own IP address.
We tried restarting Resolume and its lost the connections to the processors. They are highlighted red
I can see the processors are connected by viewing their GUI in a web browser by typing in their IP addresses.
Is their any obvious reason why Resolume would not pick up the processors, while they can be connected to in the browser?
DMX not finding target IP's after restart
Re: DMX not finding target IP's after restart
could you post some screenshots of what is highlighted red?
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Re: DMX not finding target IP's after restart
unfortunately I'm not on site at the moment, but have asked for someone to send one over.
In the meantime from memory its shows red on the Arena Preferences DMX tab. I think under the target IP section
In the meantime from memory its shows red on the Arena Preferences DMX tab. I think under the target IP section
-
- Posts: 388
- Joined: Sat Oct 29, 2011 22:24
- Location: Las Vegas, NV
Re: DMX not finding target IP's after restart
Does you computer have more than one network port? Resolume defaults to whichever port is designated as #1 on your system. You have to disconnect the network cable that is not connected to the Lumiverses, start Resolume and you should be fine.
Re: DMX not finding target IP's after restart
its an old mac book with ethernet
so has wifi as well, but this was disabled.
As far as I could see it was only using the ethernet
so has wifi as well, but this was disabled.
As far as I could see it was only using the ethernet
Re: DMX not finding target IP's after restart
Yea this happens when resolume is unable to poll the node. I would unicast to the exact ip since you know that. More reliable then just selecting the name I've noticed.
Re: DMX not finding target IP's after restart
It's interesting that Resolume would be able to reach the node via typing its IP directly, but not poll it.
The theory is that we send an query to all IPs on the network, and then get the names if any Art-Net nodes are present. If we don't get the name, theoretically, we shouldn't be able to reach it directly either.
Drazkers, if you run into this regularly, would you mind sharing how we could recreate that?
The theory is that we send an query to all IPs on the network, and then get the names if any Art-Net nodes are present. If we don't get the name, theoretically, we shouldn't be able to reach it directly either.
Drazkers, if you run into this regularly, would you mind sharing how we could recreate that?
Re: DMX not finding target IP's after restart
I personally suspect it's the hardware as I've run into it only with the artnet nodes we did for the datsik tour. When first setting up you'll see the nodes, everything works dandy. Restart or come back the next day the name will be red and won't function. If you unicast the ip it works, I personally blamed the hardware and not resolume since I personally would just see it with one product. I usually stick to unicasting an ip anyways since being able to ping the ip via terminal is a good check.