• State Suggested Answer
  • Date
    IanSOH
  • Date
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 184 subscribers
  • Views 4055 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

  • 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.

  • 0 in reply to IanSOH

    I agree with Mike.  I believe the profile issue is resolved in the newer code, but using the older show it is still using the older profile.

  • 0 in reply to saranow

    Thank you both for your responses.

    Whenever we have patched these fixtures at any stage in the past the Performance had taken up 40ch, the Profile 34. This only changed after the software and library update, 

    The upshot of whatever change has been made is that we have now had to rebuild all our venue defaults and so on from scratch based from the new software version in order to make sure that these fixtures patch in using the full listed DMX footprint. It also means we will have to reconstruct any returning shows that have been built previously but may need fixtures swapped out in future iterations. There is also the question of what other fixtures have been affected that people just haven't come across yet.

    This is not an ideal result of a software or fixture library update.

  • 0 in reply to saranow

    The Mac Viper Profile 16B Extended fixture in the 2.8.0 beta (build 56) is still a footprint of 29 channels.

    After loading an old show file into 2.8.0, when I go to update the Viper fixture profile, in the list of changes it shows:

    2. DMX Footprint changed from 34 to 29

    -Todd

  • 0 in reply to IanSOH

    Because the newer profile is a smaller footprint, you might not need to redo your patch.

    Just keep the old files as-is with the larger footprint profiles.

    Going forward, decide if you want to switch to the smaller profile or patch the larger footprint using offset. If you go with the smaller profile footprint, it doesn't matter if the unused last 5 channels (as shown on the fixture dmx range) overlap with another fixture address, as they never get data for that fixture from the console.

    -Todd

  • 0 in reply to tdrga

    I'm pretty sure the footprint will go back up again as soon as this is fixed

  • 0 in reply to ueliriegg

    I hope so - as that would be the best resolution (unless you have a show patched consecutively using the smaller profile ranges now)

    -Todd

  • 0 in reply to tdrga

    the manual says 40, so that's the correct number and it should go back there.

  • 0 in reply to IanSOH

    From what you've said it sounds as if the issue is the new software reading an old library (ie the one in the show file) interprets the total wrongly,   but using a new library its ok.

    I don't think its going to effect things very much  at all as old show files will work ok,  but just if you add new fixtures they will not offset correctly automatically and if they are upgraded to the new lib it will probably work correctly anyway if it was working ok for you in a new show file.

    The way it doesn't upgrade the library is there as a way to keep old show files working as is, even if they change the standard lib in the update.  So I don't think the concerns you have will turn out to be an issue.

Related

www.etcconnect.com