• State Suggested Answer
  • Date
    IanSOH
  • Date
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 184 subscribers
  • Views 4058 views
  • Users 0 members are here

Channels dropped when patching Mac Viper Profiles and Performances.

Hi,

Apologies if this has been dealt with before. I did search but couldn't find anything.

We are using software version 2.7.3 Build 10, fixture Library Version 2.7.3.2. Both recently updated.

When we patch in Viper Performances or Profiles, it seems that 5 channels are being dropped. Despite the library saying that the Performance in 16bit Extended should have 40ch, only 35ch end up being patched . With the Profile it patches in 29 instead of the listed 34. This is then compounded when patching in multiple fixtures. We can get around it by using the offset, but with multiple venues and multiple operators it's a bit of a mission to make sure everyone is across it.

Pics attached of patching multiples with and without using the offset..

I do understand that these 5 channels are the "reserved" ones and effectively do squat, however, the base fixture should probably be as the manufacturers list, with editing done on an as needs basis if you need the room in your patch.

Thanks in advance.

Ian

Parents
  • 0

    OK, another interesting thing that we have found out. When building a new file with the new software the fixtures patch fine. When trying to patch them in a showfile that was originally built on an earlier software version, the bug pops up. 

    Hope this helps with any bug catching. 

  • 0 in reply to IanSOH

    You might be getting caught out by the safety feature that stops library updates changing  an existing show unexpectedly ie the fixture lib is now correct but wasn't at the time the show file used the fixture.

    From the manual

    When a new library is installed on Eos either from a software update or a separate fixture library file from the ETC website, changes in library data will not automatically update your show files. This is to prevent library changes from affecting a functional show file.

    Using the {Fixtures} softkey in patch will open up the list of fixtures used in the current show file. In this view, you will be able to tell which fixtures in the currently loaded show file differ from the desk’s fixture library. For fixtures that have a library update, the {Update Lib} softkey will display in white, and for fixtures that don’t have an update, the {Update Lib} softkey will be grayed out.

Reply
  • 0 in reply to IanSOH

    You might be getting caught out by the safety feature that stops library updates changing  an existing show unexpectedly ie the fixture lib is now correct but wasn't at the time the show file used the fixture.

    From the manual

    When a new library is installed on Eos either from a software update or a separate fixture library file from the ETC website, changes in library data will not automatically update your show files. This is to prevent library changes from affecting a functional show file.

    Using the {Fixtures} softkey in patch will open up the list of fixtures used in the current show file. In this view, you will be able to tell which fixtures in the currently loaded show file differ from the desk’s fixture library. For fixtures that have a library update, the {Update Lib} softkey will display in white, and for fixtures that don’t have an update, the {Update Lib} softkey will be grayed out.

Children
No Data
Related

www.etcconnect.com