New to sACN Viewer...

I have to confirm described behavior. Customer in studio runs Ion configured to 60 sACN universes. Each universe represent one rail and to each is patched only few channels. Network is designed with sACN just because of merging behavior of sACN. On the same network was running ChamSys console. Each console was controlling its own luminaries. In the rig were some moving heads. When operator on Ion changed sACN Viewer window, moving head goes to reset. It happened even on universe where Ion had no luminaries patched, only viewer was looking there.

Eos version was 2.7.4.

The same setup have customer in 2 other studios for 2 years. There were no problems before, but sACN View was used only as standalone program running on notebook on on console. They had before on network Avolites, MA and ChamSys consoles together with Ion too. Ion is always running as Primary Master without any Backup console (standalone). They use Ion for studio luminaries and other consoles for moving heads in their productions.

Have to assume it is bug with sACN Output Viewer implemented to console.:(

Regards

Karel

I have to confirm described behavior. Customer in studio runs Ion configured to 60 sACN universes. Each universe represent one rail and to each is patched only few channels. Network is designed with sACN just because of merging behavior of sACN. On the same network was running ChamSys console. Each console was controlling its own luminaries. In the rig were some moving heads. When operator on Ion changed sACN Viewer window, moving head goes to reset. It happened even on universe where Ion had no luminaries patched, only viewer was looking there.

Eos version was 2.7.4.

The same setup have customer in 2 other studios for 2 years. There were no problems before, but sACN View was used only as standalone program running on notebook on on console. They had before on network Avolites, MA and ChamSys consoles together with Ion too. Ion is always running as Primary Master without any Backup console (standalone). They use Ion for studio luminaries and other consoles for moving heads in their productions.

Have to assume it is bug with sACN Output Viewer implemented to console.:(

Regards

Karel

What you are describing is a different one than what the original post describes. The original post describes a UI issue, what you describe is an issue with the signal the being received by the fixtures. This post sounds more like what you are experiencing.

Mike A has a good comment in that thread explaining what is likely going on. You should contact technical support and work with them to verify your network is properly setup for multicast.

Thanks Matthew, my problem is more likely the one you are referring to. I will double check the way I have setted up the IGMP. Problem for this installation was that I need switch with 48 ports that according to place (public TV studio with occasional life broadcasting) where is installed needs to be able run 24/7.