|
Exporting to Galaxis GS2OverviewIn order to make a firing script, you need to configure your show with the specifications of your firing system. The easiest way to do this is with the menu item "Show > Set firing system > Galaxis". You can also set the user preference "File > Preferences > Firing system > Galaxis" so that all your new shows will come up pre-configured for Galaxis. For certain advanced techniques, you may want to configure the modules at your launch positions individually. For instructions, please see the Export Overview section. When configuring your launch positions for the Galaxis firing system, use integers starting from 1 for the module addresses (device numbers); specify the first pin (output number) is 1, and number of pins is 100 or however many outputs the module has. Once you've scripted your show and you are ready to export your firing script, click the "File > Export firing script > Galaxis" menu item. The sound track is not embedded in the script, so if you have a sound track you should simply use the same file that you uploaded into Finale. Importing scripts to create visualizations is discussed in detail in Import Show, though for Galaxis GS2 scripts the importing process is so simple you can do it with a single menu command. Brief instructions are given below. Example ScriptThe following files are an example show file that you can load into Finale, plus the exported scripts for Galaxis with and without steppers (you can add the steppers after loading the script into Pyrotech Composer). More explanation of the examples is provided in the Export Examples section. Understanding the Galaxis ScriptThe exported GS2 script is a text file that you can inspect and edit in a text editor, but it is in a format that is difficult to read. The format consists of three header fields, followed by a record of 70 fields for each firing row. All fields are separated by carriage return line feed (\r\n), which makes the script quite long in a text editor. Not all of the 70 fields of each firing row are required. The exported script will contain valid values for the following fields, shown with field numbers counting from 0 (i.e., 0-69). The remaining fields will be empty.
The firing rows are sorted by ignition time. Each firing row represents an effect at a unique ignition time or an additional effect at the last ignition time. Thus each ignition time is represented by one or more sequential rows. The ignition time count (Field #0) is 1 for the first ignition, and increments for each new ignition time. The following "Dt" field (Field #1) is the time delta to the next ignition time, or blank for additional effects at the last ignition time. Galaxis addresses the issue of wireless transmission times by combining rapid sequences of ignition events into short programs ("steppers") triggered by the first ignition time event in the sequence. Finale can export scripts with or without steppers, but if your script contains sequences of events with less than 0.3 seconds between them then you need to export the script with steppers or add the steppers using a command in Pyrotech Composer before downloading to your modules. When converting the script to use steppers, the "Ignition time count" (Field #0), "Dt" (Field #1), "Step cue" (Field #8), and "Step delay" (Field #9) fields are changed to represent the stepper programs. Only the first ignition time in a stepper program counts, so the Ignition time count field is blank for all but the first row in a stepper sequence and any immediately following rows at the same ignition time. The Dt field for stepper rows is blank except for the first row, which contains the delta to the next counted ignition time. The Step cue and Step delay fields of the first row and immediately following rows at the same ignition time are blank; for subsequent rows the Step cue is the Ignition time count of the first row, and the Step delay is the time delta between the row's ignition time and the ignition time of the first row in the stepper sequence. The "SC-ID" field (Field #30) is a unique row ID. Exported scripts contain 10000 for the first row, then 10001, 10002, etc., incrementing for each row. Prior to the 70-field firing row records, the script contains a three field header. The first two header fields are the script format version number and date. The third header field is the next available SC-ID, i.e., 10000 plus the number of firing row records. Importing Galaxis GS2 ScriptsYou can create a visualization of a show scripted with Galaxis Pyrotech Composer simply by importing the GS script with the menu command, "File > Import show > From script > From Galaxis Pyrotech GS2 script." When importing a GS2 format script, the relevant imported fields from the 70-field firing row records in the script are (counting fields from 0): Ignition Time (Field #2), Effect Time (Field #3), Caliber (Field #13), Effect Name (Field #11 or if empty then Field #12), Animation Search Phrase (Field #60 if contains characters other than hex digits, or Field #11), Launch Position (Field #22), Angles (Field #23), and Product ID (Field #42). The GS2 script format and Pyrotech Composer have more than one column for representing the effect name. For best importing results, your GS2 script should contain the entire effect name in Field #11 (Item/Artikel); and if you want to provide a full description of the effect for purposes of specifying the animation, you can include the full description in Field #60 (QS Test/VisualizationID). If a description is found in Field #60, Finale will use that description instead of the effect name to create the simulation. |
