Import patch data into Ion

Hi Pat,

Sorry, but the short answer is no. 

The USITT ASCII standard 3.0 includes a "Text" keyword which only modifies cues, subs and groups.  There is no support in the basic standard for channel labels.  It is possible to get them only if the manufacturer of the source writes out a manufacturer-specific keyword with associated data in the ASCII file, and the receiving manufacturer knows how to interpret this keyword and data.  I can't tell you if VW Spotlight exports the user fields, but I do know that Ion doesn't have any information on VW Spotlight specific keywords.  Sorry.

Ann 

Thanks for the response Ann!  Although I am not at my console right now, I think I remember seeing an import of Lightwright format files.  Would it be possible from that file?

 Thanks again,

Pat
 

Lightwright creates two types of files that Eos/Ion can read, although the data is limited.     

1) Use the Export function in LW and save as an ASCII show:  Only the standard ASCII patch is exported into an .asc file, so you won't get any of the labels that you want.  This ASCII show must be imported into Eos/Ion using the Import->ASCII function, NOT the Lightwright function. 

2) Use the Export function in LW and save as Data:  This exports to a .txt file, which can be imported into Eos/Ion using the Import->Lightwright function.  The fields that we import are as follows:

Device Type                 Only devices with type “Light” are imported.

Channel                        Channel

Dimmer                         Dimmer

Purpose                        This becomes the Notes field.

Circuit Name                This becomes the Text 1 field.

Circuit#                          This becomes the Text 2 field.

Color                              This becomes the Text 3 field.

Template                       This becomes the Text 4 field.

I don't know if this will meet your needs, but if you try it, let me know how it works for you. 

 Ann

Lightwright creates two types of files that Eos/Ion can read, although the data is limited.     

1) Use the Export function in LW and save as an ASCII show:  Only the standard ASCII patch is exported into an .asc file, so you won't get any of the labels that you want.  This ASCII show must be imported into Eos/Ion using the Import->ASCII function, NOT the Lightwright function. 

2) Use the Export function in LW and save as Data:  This exports to a .txt file, which can be imported into Eos/Ion using the Import->Lightwright function.  The fields that we import are as follows:

Device Type                 Only devices with type “Light” are imported.

Channel                        Channel

Dimmer                         Dimmer

Purpose                        This becomes the Notes field.

Circuit Name                This becomes the Text 1 field.

Circuit#                          This becomes the Text 2 field.

Color                              This becomes the Text 3 field.

Template                       This becomes the Text 4 field.

I don't know if this will meet your needs, but if you try it, let me know how it works for you. 

 Ann

afoster:

The fields that we import are as follows:

Device Type                 Only devices with type “Light” are imported.

Channel                        Channel

Dimmer                         Dimmer

Purpose                        This becomes the Notes field.

Circuit Name                This becomes the Text 1 field.

Circuit#                          This becomes the Text 2 field.

Color                              This becomes the Text 3 field.

Template                       This becomes the Text 4 field.

I would actually hope that more than the device type "Light" are imported -- the other types, Moving Light, Device, Practical, and Power all contain patch and purpose information that would be useful to have in the console.

I also imagine that any field could be mapped to the text fields.  Putting position name information, for example, would be a great asset to the query feature.

 -Josh 

I also imagine that any field could be mapped to the text fields.  Putting position name information, for example, would be a great asset to the query feature.

But the query feature is not fully supported with ION, only with the EOS console.... right?

You can access Query on the ION.  Due to lack of hard key, the work around I found is to write a macro in the macro editor and use the keyboard shortcuts to get the command to appear on the command line.

Alternatively, going on what BSmith said, to save having to look up the keyboard shortcut, turn scroll lock off on your keyboard and type in Query (i'm yet to try this, but I'm told it works)

Cheers 

Side Note:  We will be adding Query into Ion in an upcoming release.

Thanks!

a