Feature Request: Merge database information only

I posted this on the FB group last week and ended up eventually using a workaround, but it occurred to me that this might be a problem that others would have as well so I wanted to post it here.

The situation:

I created a base showfile for a theatrical production based on my LightWright import. All the database fields populated with information, plus groups and palettes and magic sheets and such. Unfortunately, the electrician decided to go ahead and patch the show with a blank file rather than putting in addresses on the nice showfile I had already created. So then I had two showfiles. One with all my show data (no cues written yet at this point) and one with a complete patch minus the database information.

Obviously, it was no problem to merge all my normal stuff - groups, macros, palettes, etc - but then I ran into a roadblock when I tried to merge the patch information in. There was no way to just get the database information in to the electricians showfile, and there was no way to just get the address information into my showfile. I tried both ways. I tried the "merge channels" tick box as well in hopes that that might do it, but nothing.

The eventual workaround that was suggested on FB was to export CSV from eos, import the patch into lightwright, export the new patch, open a new showfile, import that new lightwright, then merge that show. It worked with minimal messiness, but was still a pain in the ass that took 25-ish minutes when I feel like it's something that could potentially just be a few clicks on the merge menu. 

So, I'd like to suggest an option on the "advanced" screen in patch merging that would allow for merging/importing of the database information based on channel #/fixture type. AND/OR merging just the address information based on channel/part#s

Parents Reply Children
  • I also noticed that unless there is address/dimmer information in the LW information already, the eos won't make multi-part fixtures. For instance, channel 31 is a leko with a scroller. Two lines in LightWright, but only the dimmer comes in to EOS.

    If I have dimmer numbers in that LW file, the fixture comes in accurately.

    On 99% of my shows, I do prep work in my office creating a base showfile but I don't usually get onsite until focus. I typically don't see dimmer numbers or addresses until weeks after I've created my base file. This means that my lightwright has channel numbers but no dimmer numbers - it'd be great if EOS could figure out multipart fixtures based on a LW import even without the dimmer numbers.
  • We do currently require address/dimmer information as you found. We might be able to improve this logic on the multi-part fixtures and will look into it :)

    Thanks,
    Matt
Related