Importing Lightwright into Ion

We recently got a newly renovated facility complete with an Ion lighting console. I am trying to import information from LightWright 4 into the Ion, and nothing is working.

The equipment:

  • Lightwiright 4 - Macintosh - OSX 10.5
  • EOS Family Offline 1.7 - Macintosh

Action to Date:

I have found, and read the wiki article on importing information into the EOS, and I would expect it to be the same for the ION, but so far - no success. I have been unable to import anything of any kind regardless of the technique.

  • Only files ending in .txt seem to be found by the software. (ASC and CSV extensions are not displayed.)
  • I have exported the data from LightWright as described in the wiki article (including the order of the fields). The Software indicates "success", but patch is still empty.
  • I tried editing the Device Type values to be "Dimmer" instead of "Light" - same result
  • I tried a comma delimited version of the file - same result.
  • I tried an ASC-II softpatch export - same result
  • As a test, I patched a few channels, and then exported them from the software, then tried to import them again - same result, no channels patched at all.

I am now at a loss. It seems clear from the wiki and forum posts that others are having some success, I would appreciate any help others can offer. A sample file that works for others might be helpful, I could then use it as a test and for comparison.

Thanks,

 

 

 

Parents
  • I don't know what all you are trying to export, but I have had success at exporting my patch from Lightwright 4 to ION.

    In Lightwright go to File, export, ASCII Soft Patch.  Select your system then click ok and save your file.

    Then locate this file and add the ".asc" extension to the filename.

    This file should now be readable by EOS, ION, etc.  by going to File, Import, USITT ASCII, and then either "Import as Custom Fixtures" or as "Library Fixtures".

    I just tried it again in the offline editor but know it has worked at the console for me as well.

  • I discovered the issue: the text file must have windows style line endings (CR/LF) instead of Mac (CR).  LW will output whatever line endings are standard for your system.  If you have a text editor where you can change line endings (like BBEdit or TextWrangler) you can convert the LW text file to an Eos readable file.

    Interestingly, device type seems to get imported in to text 4 on Eos, and template doesn't get imported at all.

    -Josh

  • RESOLVED!

    I am happy to report that the members of the Forum have found the answer. To sum up:

    • Lightwright ASC-II Softpatch files can be imported via the Files>Import>ASCII><either method>
      Keep in mind that the file must end in ".asc"
    • Lightwright data export works as described in the wiki, however, to be successfully read, line endings will need to be converted to the windows standard of <CR/LF> from the Mac standard of <CR>
    • Only conventional fixtures are imported regardless of the approach, however the Lightwright import seems to import more information than the ASCII approach.

    Many thanks to all who helped me to resolve this confusion.

Reply
  • RESOLVED!

    I am happy to report that the members of the Forum have found the answer. To sum up:

    • Lightwright ASC-II Softpatch files can be imported via the Files>Import>ASCII><either method>
      Keep in mind that the file must end in ".asc"
    • Lightwright data export works as described in the wiki, however, to be successfully read, line endings will need to be converted to the windows standard of <CR/LF> from the Mac standard of <CR>
    • Only conventional fixtures are imported regardless of the approach, however the Lightwright import seems to import more information than the ASCII approach.

    Many thanks to all who helped me to resolve this confusion.

Children
  • If you have Lightwright 5.0.2 or later, the Export window has an option to set the line ending. The default is whatever platform you're running LW5 under, the option lets you choose the "other" kind. So if you're using Windows, the option will be to use Macintosh line endings. If you're running Mac, the option will be to use Windows line endings.

    LW5 automated actions will save this setting, no matter which platform you run it under, it will use the line ending recorded into the automated action.

  • John, even if you export the LW file in the right format, if you amend the file in Excel or Numbers you still have to save the file from there with correct extension.

    So...Thanks for the tip about text wrangler, Josh. One less reason I need that windows machine.

    -M

Related