• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    jasoneweber
  • Date
  • Replies 5 replies
  • Subscribers 186 subscribers
  • Views 3172 views
  • Users 0 members are here

New to sACN Viewer...

I was exploring the new sACN viewer on my Eos, and noticed that the "output" field will sometimes flicker to zero while the "sACN" field remains constant.

Is that normal or should I be worried about some loose connection?

Parents Reply Children
  • 0 in reply to Matthew Dews
    Set-up
    - EOS 4000 "Classic", v. 2.7.2
    - Primary


    From what you said it seems like a non-issue. I have not experienced any odd behaviors with the equipment.

    In this instance, I had just replaced a couple of Net3 Gateway ports that are hard wired to ports around the building and was testing them with a Apollo Smart Move to make sure everything worked as expected. While my tech was wandering the building with the Smart Move, I was exploring sACN Viewer for the first time and saw that odd "flicker." I was worried that my port replacement could be a factor, but then when I tested other ports (to do my testing, I configured the ports all with a unique universe) the sACN Viewer showed the same flicker. On each test the Smart Move had full control as expected.

    I figured that this "flicker" was either normal or a sign of impending doom. So, I thought I would put it out to the world (since there was no immediate issue) and see what folks had to say. :)
  • 0 in reply to Matthew Dews

    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

  • 0 in reply to KarelB

    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. Slight smile

  • 0 in reply to Matthew Dews

    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. 

Related

www.etcconnect.com