Importing Fixtures

Hey,

So there seems to be a bug in the import section of the EOS. I clear the current show, then I SAVE AS my new show, after which I go into import and pull across the fixtures from my standard House Hang show file (saves a lot of work, thank you ETC!). This all works great, it's when I hit the SAVE command that it all goes sideways. Instead of saving as my new show, it saves on top of the show file I imported the fixtures from. I have gotten smart about this bug and have been backing up my standard House Hang file before I do any importing of fixtures. This has been doing this on our console for a number of versions of software - I just always forget to post this bug when I get a chance. Is this a bug or just a really silly "Feature"

Thanks,

-CTR

 

  • Interesting.  We are on it.  The show file pointer is getting redirected via the import function.  It shouldn't be.  Thanks for letting us know.  Please keep your safety program in place until we can get this addressed.

    Thanks!

     a 

  • I mentioned this in May.

    http://community.etcconnect.com/forums/thread/5863.aspx

    I mentioned this on October 31:

    http://community.etcconnect.com/forums/thread/9951.aspx

     

    BSmith:

    Here is another pertinent tidbit-

    Say you are working on Show A, and you decide to Import an element of Show B.  Your current show will still say "Show A" over the CIA, but if you Save (not Save As) your show will now be saved as Show B. 

    Whenever you Import something from another show, remember to Save As the file you want to remain working on.

    I'm pretty sure this is still true...

    I hope someone is still working on it.

     

  • We've tried to duplicate this behavior today (and I believe the testers did before as well).... and we can't.  But perhaps I'm missing something.  So, step by step:

    File / New

    Save As - File Name 1

    Import/Fixtures - from File Name 2

    Save

    In this instance, the desk is saving to File Name 1.

    I've tried this, as have the testers.  And we are all coming up with the same results.  Are we missing something?  Maybe there is a step that we didn't follow?

    Please advise.

    I'm just curious.  This seems like a lot of extra steps.  Is there some reason that you are not just starting out with a master show file that has your required fixtures in it already?

    (as an FYI, at some stage, we will add the ability to define a master show file as a part of "File/New."  So that when you access this, it actually opens a specific show file..... )

     

  • Ooooh, You almost got me.  I thought for sure I was going to be eatin the crow on this one.

    I just tried this on an Eos Console acting as primary offline.  There was no problem.

    On a whim, I then tried it as a backup to a Master RPU.  This is where the problem occurs.

    Yes, I believe your command sequence would do the trick.



    [edited by: BSmith at 8:36 PM (GMT -6) on Tue, Dec 02 2008]
  • This is indeed still happening. It happened several times to me in the last few days. I am running Eos console as backup to a RPU. It is maddening. I have been trying to remember to save as after an import but I don't always remember.

     

    Tim Wilson 

  • 'kay.  Fair enough.  We will look into it.

    Thanks!

  • So this brings up an interesting point. How many people when creating a new show use <file><new> instead of <clear show> then <save as>? I like to use <clear show> because then when working with the students we get to start from scratch and go through all the settings and talk about each feature such as tracking vs cue only, etc.

    I don't think I would ever use a master show file to build from because it doesn’t give me the opportunity to have the students walk through the board settings so they know why things behave the way they do. I might use it for myself when I do shows but by now I'm use to the <clear show> method by this point.

    -CTR

     

  • Our all-volunteer community theatre uses a master file that includes a default patch for some of the stock fixtures and dedicated dimmers in our rack, like house lights, work lights, subs for the aforementioned, and dimmer-doubled scroller+dimmer fixtures. I find it easier to explain how to repatch from the stock plot using the {Move_To} than to reprogram everything from first principles.
Related