Re: Lessons learnt DMX over IP.. Part(1) there is standards / there is no standards
I would tend to agree with natf. If the controller's design is such that the processor has to examine every multicast packet on the network, then there's going to be a saturation point where the total number of packets exceeds the processor's ability to inspect them. Beyond that point packets are going to get randomly dropped.
If that is the problem then the possible solutions are to segment the network in such a way that no controller sees more packets than it can process, or use gmp-aware switches so that only subscribed-to packets are sent to each port, or go to unicast.
But it brings up a point that one specification that's rarely mentioned is how many universes can be present on the LAN before a controller chokes.
The Sandevices E680/E681/E682 Pixel Controllers, part of the[SIZE="3"] [COLOR="red"]P[/COLOR][COLOR="orange"]I[/COLOR][COLOR="blue"]X[/color][COLOR="lime"]E[/COLOR][COLOR="magenta"]L[/COLOR] [COLOR="red"]P[/COLOR][COLOR="lime"]R[/COLOR][COLOR="blue"]O[/COLOR][COLOR="red"]J[/COLOR][COLOR="magenta"]E[/COLOR][COLOR="cyan"]C[/COLOR][COLOR="red"]T[/COLOR]
[url]www.sandevices.com[/url][/SIZE] <-email jim at