The import effects dialog allows the user to import effects from other sequences in the currently open sequence. This option should be used when importing purchased sequences from different vendors.
The Import Effect dialog supports multiple sequence file formats. xLights, Light-o-rama S4, S5, SuperStar, Vixen 2, Vixen 3(limited), HLS, LSP, VSA File formats are all supported.
The following example describes how to use this function to import an effects from an xLights XML sequence.
First ensure that you have created or opened an existing sequence that has the models added to the sequencer that you wish to import to. Note you must select a View first. If there are no models or groups displayed on the Sequencer, then you won’t be presented with any models to import to.
This process can be used to
Import effects from a xLights sequence from another user
Import effects from another of your (e.g. older) xLights sequence into an existing xLights sequence
Create a new directory and unzip the sequence files to that directory. It is recommended to create this directory within your show folder. The zip file should contain the xlights_rgbeffects.xml, the sequence.xml and any other required files(image, shader, etc files). Change the show folder in xLights to point to the new directory. Copy the music file to the new folder if missing.
Open the sequence, click on Render All and Save the sequence. You should be able to see how the lights flow in the layout window. Study the sequence and determine which models you wish to copy to your own models.
Look for the correct quantity of elements in the donor sequence that will match your elements. For example If you have 4 windows but the donor sequence has 8, pick the 4 windows that you want to copy.
Make a note of the names of each donor model you want to copy to a model of your own layout. Watch the sequence several times.
Make sure you have the appropriate music file in your own media show directory. Close the sequence you were watching, go to the controller tab and change the show folder back to your own directories.
If importing into a new sequence, then
Create a new musical sequence, select timings and add your display elements or select a view.
Save the sequence.
Open the sequence you want to import into, add your display elements or select a view.
Select Import, Import Effects
Select the file type of XML by changed the dropdown at the bottom right. Select the donor sequence xLights XML.
A model mapping window is displayed. On the top left is a list containing the timing tracks to import. On the left are the models and model groups from YOUR layout/sequencer tab("Model"). 'Blue' items are Model Groups. On the right is a list of models/groups/submodels ("Available") that contain effects from the sequence being imported. Click and drag a model name from the right list to the ‘Map To’ column in the row that you want to import the model to. You may also highlight the "Map To" cell and double click on a "Available" model to map it or highlight a "Available" model and double click the "Map To" cell.
Models in the "Available" list will turn gray when used. These items can still be used multiple times even when grayed out.
When done, select "Save Mapping", and save the XMAP file. This XMAP file can then be loaded in the future when mapping another sequence from the same layout.
Click OK when done.
Change the File Type drop-down to SUP. Then select the SuperStar Sequence File.
The SuperStar Import Dialog will then appear. Select the xlights model to import the SuperStar file onto.
xLights will create pictures from the SuperStar files. The next dialog asks the user to select a folder to save these pictures files too. In the file name field set the 'base' file name. This 'base' name is used as the file name root of all the saved image files. In most cases just set the 'base' name to the SUP file name.
The SUP file will then be imported to the specified model as picture and morph effects.
Importing a LOR sequence follows the same steps as described above. However, depending on the LOR hardware setup, channel definitions in LOR and correspondingly in xLights need to align. See discussion within Tutorials Section, Coming Over from LOR.