Patching glitch between Element and Nomad - focus palettes

I'm not sure if this is a software glitch or just a general incompatibility.  I am currently touring a show on an ETC Nomad that was built on an ION.  When we tour, if the venue has an ETC console, we generally patch the show on the house board and then import (merge) the patch onto the Nomad.  It has happened more than once that when the house board is an Element, after we import the patch all of the focus palette information disappears.  I'm not just talking about the positional information of each focus palette, but also which focus palette every light is set to in every cue.

The obvious work around is to manually input the patch into our board at each venue, and this isn't the end of the world, it just seems like there's a handy feature there that doesn't work as it should.  I'm not sure which software version the venues are running on the Element, but I am running the latest version of Nomad.  I also haven't done much troubleshooting because I've been too busy manually patching and getting the show up and running.

Any information would be helpful.

Craig 

  • Hi Craig,


    with the Update to Eos Family Software v2.6, many of the previously exluded functions

    like Palettes were allowed in Element.

    So if you have the customer's update their Element Consoles to v2.6, you won't be having this

    problem anymore.

  • I think the thing I would try doing is import the patch into a new empty show on the nomad, save that and then import that that t saved show patch into the real show. Chances are whatever nasty is buried in the data will get cleaned up by the save from Nomad and the re import.
  • Focus palettes always existed on an element, but presets did not. So: are you sure you were having problems with focus palettes and not with the focus information inside of presets?
  • It's definitely focus palettes that are missing.
  • Unfortunately I can't always ensure that the theatre is running on the latest version, as the patch is often done before I get to the theatre. The workaround is not that difficult, and hopefully as everyone upgrades the problem will eventually go away completely. I will post here if I get any more info about the bug.
  • If it's focus palettes then we're back to zero and have no clue. If it were presets then updates would be the solution, but not with palettes.
    Are there more things you can tell us about your problem?
  • I don't know if I explained well enough my solution earlier, so I'll try to explain better.

    I think its likely to work if you did the process in two steps.

    So instead of just importing their patch data into your show and it not be quite compatible and messing up your FPs, first import just their patches into an empty nomads show, save that show, and then import the patches from that show into your real show.

    That way the file with the patches you are merging with your show will be from the same software and version (as you saved it on nomads) and so any funny stuff in it that messed up your original merge shouldn't be hiding in there.

    If that doesn't work then you could "clean" the data further by saving the patch data in "ASCII show file" format and re importing that.

    It feels as if the original problem is that when its importing the patch data from the element, its actually deleting the fixture type on the channel (which if you were doing by hand is when it warns that all non intensity data is lost) before adding back the fixture type??
  • Thank you for the suggestion. The easiest workaround for me is probably just to patch my system from scratch, though I'm sure your idea will work as well. Mostly I posted because it seems like a bug, and though it may be fixed in the latest Element upgrade, I can't control what version the venue will have before I get there.
Related