I think I posted about this previously on the facebook pages.
I have a venue tomorrow thats is using Artnet in-house, but I usually try to use sACN wherever possible.
Whenever I use Artnet in a touring venue, whether on my NX2, NX1 or wherever, I always seem to have a problem where the DMX would keep pausing for a few seconds as if it is losing connection to the Artnet nodes repeatedly. Work for 30 seconds, stop for 20 seconds, work for 30 seconds, stop for 20 seconds etc etc
Everything is configured correctly, I have tried variations of whether I am broadcasting or aiming for a specific IP address, but it keeps happening.
Is this something like a refresh rate issue, or is there an underlying problem elsewhere? Any suggestions welcome, but I am very wary of using Artnet in venues now.
(I’m using 4.10.1271 so I can still use older playback wings at home for programming as I am on W10).
Software Version: 4.10.1271
NX Console Type or PC OS Version: NX2, NX1, NXP
Thank you for your description of the issue. When all devices on the network are implementing Art-Net correctly, it can be a very efficient and reliable system.
You shouldn’t need to use either of these methods. The broadcast and “override” options, are there to help deal with receiving devices that don’t have an up-to-date Art-Net implementation. In normal use, you should have broadcast off, and override off. ONYX will then be able to discover the Art-Net devices on the network, which should respond and tell ONYX which universes they need. ONYX will send these specific universes to these specific devices.
What Art-Net receivers are on this network? What is the topology? Is Art-Net being “daisy-chained” through devices, or does each device on the network connect back to a central Ethernet switch?
Ah okay. It has been a while since I have used Artnet due to previous issues, so it might be I was using the incorrect configuration.
At this venue, there are multiple NA DigiNet S 1 to 4 Artnet splitters, although this is the first time in this venue.
Previous places where I have had issues include the artnet system in the Royal Albert Hall, but they were easily able to convert the modes on their network to sACN when required.
Artnet Sync is swicthed off, and I believe that their network is being daisychained through various switches and devices.
I’ll try starting again from scratch with their network tomorrow. My floor package is running sACN to an EN12 on stage using the remote network port, and the house rig (which is a different IP range) will be outputting artnet to their house system from the EtherDMX port. I’ve not had any issues running this way with both ports outputting sACN, but not sure about Artnet and sACN. (I can easily switch my EN12 to Artnet so there arent two protocols, but I think I’ve had the same problem with that).
I will keep you posted and follow your directions with turning everything else off unless it is absolutely required.
Thank you for the information. I believe these devices have a good implementation, so no worries there.
Thank you for the information. As a general rule, I wouldn’t recommend daisy-chaining Art-Net through more than 10 Ethernet switches/Ethernet “thru” ports. Depending on the data on the network, you could start to encounter latency. When daisy-chaining is required, it is best to convert back to DMX, and daisy-chain the DMX universe.
This should be absolutely fine. On NX2, you can just output sACN from the Remote Network port, and just output Art-Net from the EtherDMX network port.
This behavior is usually called by a switch setting called broadcast or broadcast storm protection.
Art-Net runs better with unicast but there are some Art-Net nodes that don’t support it well.
I’d start with broadcast off and you will probably ok.
