Last night we experienced the following bug on our Apex system. For some context, our main is an Apex processor unlocked to 50k and an Apex 10 also unlocked to 50k as our backup. We also unicast our data to our Zacktrack servers which then output to our rig.
We had a failure with our main Zacktrack server and had to fall over to the backup, this worked fine except for one universe which did not output from the console correctly. This universe has 4 lights on it. When Zacktrack engaged the lights, they would move and track as normal but would not output. When Zacktrack released the lights, they would just point at the ceiling. This appeared to me to be a sACN priority problem. During the show we removed the unicast destinations on that universe and reset them, but this made no difference. At the end of the show, we did some additional troubleshooting and managed to fix the problem by removing the uncast destinations and changing the output to muticast and them back to unicast. As soon as we did this, we regained control of the fixtures and that universe again.
This looks like a bug to me.
[locked by: Nick.Gonsman at 2:02 AM (GMT -5) on Mon, Apr 14 2025]
