We have a vista 3 R4 (1679) on Windows system that for some reason stopped outputting sACN after a power loss. Everything looks to be working properly, fixtures are showing intensity in the fixture chooser, DMX views appear to be rendering properly, sACN and network settings appear to be okay. But when I logged into our CueServer, sure enough there’s no sACN being send out onto the network.
Here’s where it gets weird. To diagnose the issue, I downloaded sACNView (a tool that I use frequently) to see what data is being broadcasted onto the network. Sure enough it sees data from the CueServer (which I was expecting as it was still working) as well as the Vista system (which I was not expecting). Sure enough the lights were now working. Even after closing sACNView, vista continues to work.
However, after you reboot the computer, it stops working again. So it appears that you need to open sACNView to “re-enable”, somehow, the output from Vista onto the network.
I already tried reinstalling Vista and that did not seem to work. The firewall has been disabled. Ideally I wouldn’t have to reinstall Windows, I don’t have a huge amount of time this week to do that, but I can if that’s what necessary.
Can you please try this version?
Updates were made in R4.1 to the sACN spec to better respect the network adaptor.
https://vistaforum.chroma-q.com/t/vista-3-r4-1-public-beta-1-now-availible/3187/2
experienced the same issue on 1762. opening sACNView allow for universes to be seen by a third party Arch controller(Cueserver3). Otherwise it doesnt allow information to pass for all universes.
universes arent being seen on network VistaLogs.zip (475.1 KB)
Universes arent being seen on the network.v3s (261.0 KB)
however even opening sACNview it will only see the Universes once you go to 101 on the viewer.
This sounds like you have a multicast / networking issue - not a Vista issue.
What brand and model of switch hardware are you using? Do they support IGMP and are they configured correctly?
Similarly what lighting fixture or DMX nodes are you using that take in the incoming streams of sACN? Do they work ?
Where is sACN viewer running? On the same machine as the cue server? It looks like it from your screenshot?
My gut feeling is that the issue potentially lies within the cueserver software.
I would explore the idea that the software is not correctly subscribing to the appropriate multicast stream. Therefore the switch does not send the sACN traffic to this port.
When you launch sACN viewer this DOES correctly subscribe to the multicast stream and therefore the switch now sends the sACN universes to this port, which cueserver then picks up on since the data is actually coming into the machine.
In summary - it’s possible that the cueserver application has an incomplete or poor implementation of IGMP.
So it is IGMP network based in Ubiquiti as a Layer 3. I would agree with you except that the universes also don’t go to my node in the same manner.
The Node is a RDM10 by Netron. Second Node is a EN4 by Netron. Vista is running on PC with ethernet connection. Cueserver is a standalone hardware device. All devices are connected to switches (PRO-MAX) on the sACN network. sACN View is running on the Vista Computer.
Interestingly enough I can hit all universes directly from Cueserver but even with higher priority Vista’s information isn’t hitting the nodes until sACN View is active with those universes.
It doesn’t make sense to me either. I know Ubiquiti has been fussy with sACN in the past but as the layer 3 networks have been developed I have not seen this issue in my installations. Not saying it is specifically Vista but to me when Cueserver will talk to all the universes and Vista data isn’t; I inquire.
What are your thoughts?
Everything still screams network IGMP issue.
Feel free to submit a support ticket and I’ll give you a call to chat if it’s easier.
Can you screenshot your IGMP settings in the Promax? Do you have IGMP snooping enabled?
In particular your “unknown multicast” action would also be good to know.
From a Vista perspective, we don’t have any known sACN issues.
We are a sender of a multicast protocol - One universe to each appropriate multicast IP address as defined in the sACN protocol.
Lighting consoles don’t care or know about the devices that are on the end of the chain. That’s the job of the network switches and DMX nodes to handle who gets that data when and where. (One of the advantages of sACN and multicast in general - when it works or is configured correctly).
Do you know explicitly how the Cueserver supports sACN?
Most of the time sACN is multicast, but it can also be unicast (although we don’t support this option in Vista). Is there a chance that your Cueserver is actually uncasting sACN (Which is why it would seemingly work?)
