Importing patch from LW

I am trying to import a patch from LW 5.  And I seem to be doing something wrong.  I chose to export the data as a data file:  then choose to export all worksheet data, I pick the tap seperated file type.  Under options I export data by channel, export field laber as first record, strip channel(), check fill blank fields with:

Then I check the following categories to export: Purpose,Channel, Dimmer, Instrumet Type,Color, Template and Circuit name.  However when I try to import a LW file on the EOS nothing is imported.  I know I am being a bonehead.  But any help would be appreciated.

Thanks

Jeff

 

 

 

Parents
  • Jeff,

    I see you've already been to the knowledge base article http://community.etcconnect.com/wikis/products/knowledgebase-importing-lightwright-data-into-eos.aspx

    Note, all the indicated fields must export, and you must export column headers.  The columns can be in any order.  Eos looks at the column headers in your text file and maps its database fields accordingly.  It also makes sure only device type=light rows are read.  Currently, you cannot change the field mapping.  You can hack it a bit, however.  Say you want Eos text 1 to be Position instead of Circuit Name.  Export Position from LW, open the text file in a text editor, and change the "Position" header to "Circuit Name."  Similarly, if you want EOS to patch the first channel of your movers from LW, change the device type to "Light" using find and replace in the text file.  In Eos patch, change the channels type, and you will be patched correctly.

    Also note, your text file needs to have Windows style line endings.  LW has an export option for this if you are on a Mac.

    HTH,
    Josh

  • Hi Josh,

    Thanks for writing back I think I have tried exactly what you wrote above, but the patch and txt notes are not imported into the EOS.  I am getting very upset.  I do not really need to do this for a few weeks, but I was hopeing it would be very simple.  I am sure it just something I am doing wrong

    Jeff

  • My method for getting the LW5 patch to Ion OLE is as follows:

    - In LW5, File - Export Data - ACSII Softpatch, in my case I send the file to a folder in the Ion file system labeled "LW Patch".

    - In Ion OLE, I navigate to Display - File - Import - USITT ACSII - Import as Library Fixtures - Show File Archive, navigating to the file and completing the import.

    - I then save the imported file as a new .esf file, later doing a merge with a Basic file (system size, setup settings, etc...) and can also merge with any ASCII cues I need to import.  

    I am not attempting to import any of the text data from LW, as about the only thing that would be useful would be to populate the channels with actual text labels, as well as possibly labeling Subs.  No way in OLE to do either, so I don't try to get overly complicated.

    Steve B.

     

     



    [edited by: Steve Bailey at 3:42 PM (GMT -6) on Wed, Feb 2 2011]
Reply
  • My method for getting the LW5 patch to Ion OLE is as follows:

    - In LW5, File - Export Data - ACSII Softpatch, in my case I send the file to a folder in the Ion file system labeled "LW Patch".

    - In Ion OLE, I navigate to Display - File - Import - USITT ACSII - Import as Library Fixtures - Show File Archive, navigating to the file and completing the import.

    - I then save the imported file as a new .esf file, later doing a merge with a Basic file (system size, setup settings, etc...) and can also merge with any ASCII cues I need to import.  

    I am not attempting to import any of the text data from LW, as about the only thing that would be useful would be to populate the channels with actual text labels, as well as possibly labeling Subs.  No way in OLE to do either, so I don't try to get overly complicated.

    Steve B.

     

     



    [edited by: Steve Bailey at 3:42 PM (GMT -6) on Wed, Feb 2 2011]
Children
No Data
Related