Total found:2990
To create and export a script for the ShangYi-TECH firing system, please follow these three steps: Design the show. Address the show (“Addressing > Address show”). Export the script (“File > Export > Export firing scripts“). Step 3 creates the script file, which is a CSV file that you can import into the ShangYi-TECH software. Figure 1 – ShangYi-TECH control panel Table 1 – File format and encoding File format Extension Text encoding Field delimiter End-of-line Text .CSV UTF-8 with BOM (0xef 0xbb 0xbf) Comma CRLF The script contains rows for the firing events, i.e., unique combinations of module, pin, and ignition-time. Multiple effects can be combined on a single cue. The special characteristics of the script are shown in the following table: Table 2 – Special characteristics Special characteristics Description Sort order of rows Rows sorted by segment and then by effect time. What rows represent Each row represents a unique firing event, a module/pin/event-time combination. For example, a chain of five shells will be one row, not five. A pair of shells shot together from the same position will be one row, not two, even if the shells are different effects. A flight of shells shot together from multiple positions with the same module-pin using scab wire is still one row. Events at different times are necessarily different rows, even if their addresses are the same. For example, two flame projector shots at different times, triggered by the same module-pin address, will be two rows because they are at different times. Header The file contains a single header row with the column names in Chinese (域,点火时间,,地址,篇章), in the same format as the CSV data rows themselves. Multi-hit pins Non-pyro effects like flames and relays can be triggered multiple times on the same module-pin address. The standard pyro addressing functions in Finale 3D assign pins sequentially, so it may be easiest to address multi-hit pins in Finale 3D by editing the script table by hand and then locking the edited rows so the show can be re-addressed for pyro without affecting them. Universes A single script file for the show may contain multiple numbered universes (01-99), each universe applying to the corresponding controller. The universe in the ShangYi-TECH script file corresponds to the Universe column of the script window in Finale 3D. For most firing systems, Finale 3D exports each universe of script events as a separate exported script file, but for the ShangYi-TECH firing system, Finale 3D will export a combined script file that includes the events for all ShangYi-TECH universes, with the universes specified in the script file in the first column (see Table 4 below). Minimum separation between cues None required; millisecond resolution supported. Module specifications Supports 100 modules (numbered 0-99), each module with 32 pins (numbered 0-31). Segments ShangYi-TECH supports dividing a show into multiple segments corresponding to songs. By default, every song file you add to your show in Finale 3D corresponds to a separate segment, beginning with zero for the first and counting up. See segments for instructions. Finale 3D provides an export option for ShangYi-TECH to export the script as a “One segment for entire show”, in which case the segment number will be zero for all rows in the exported file, or as “Multiple segments”, in which case the segment numbers correspond to the segment numbers of the songs. ShangYi-TECH requires that the segments begin with zero and count up consecutively — no gaps. This requirement applies to each universe separately, based on the events in each universe. For example, if a show has three songs defining segments 0, 1, and 2, and has two universes 01 and 02, then each universe must contain events in segments consecutively, beginning with zero. It would be an error if universe 01 contained events in segments 0, 1, and 2 while universe 02 contained events only in segments 0 and 2. Timecode FSK timecode files for ShangYi-TECH contain a segment number embedded in the timecode signal along with the timing information. The segment number must correspond to the segment number in the associated script file. If you have a show with multiple songs, each song representing a segment, then you should export the show from Finale 3D using the “Multiple segments” export option, which will generate multiple script files, one for each song. To generate the associated audio files that include the song audio on one channel and the timecode on the other channel, use the function, “File > Export > Export soundtrack…” and choose “Fire Pioneer FSK (one file per segment)” for one of the tracks. That will generate multiple WAV files, one for each song, with the embedded segment numbers corresponding to the segment numbers in the script file. If you want verify any timecode file is correct or ascertain what segment number it contains, please try the function, “File > Tools > Analyze timecode in soundtrack file…” This function works on all timecode files, whether they are generated from Finale 3D or from other software. Table 3 – Export options Option name Description Segments Either “Multiple segments” or “One segment for entire show” After the header, each row in the script has a number of fields separated by the comma character. The names of these fields and their descriptions are the following: Table 4 – Specifications of script fields Field name Description 域 Universe (controller number), formatted as two digits with leading zero, from 01-99. 点火时间 Event Time, e.g., 00:02.981. <blank> Blank, reserved for future use. 地址 Firing system address, formatted as 0000, where the first two digits are rail (00-99) and the second two digits are the pin (00-31). 篇章 Segment integer from 0 to 249. An example script is shown below. 域,点火时间,,地址,篇章 02,02:07.760,,0000,3 02,02:17.760,,0001,3 02,02:27.760,,0002,3 02,02:37.760,,0003,3 01,02:47.760,,0004,3 01,02:57.760,,0005,3 01,01:37.760,,0000,5 01,01:47.760,,0001,5 01,01:57.760,,0002,5 01,02:07.760,,0003,5 Figure 1 – Example ShangYi-TECH script Table 5 – Example files Download link Explanation test-shangyi-tech.csv Example exported file (CSV) test-shangyi-tech.fin Example show file
Various firing systems have the capability of dividing a script into sequences that are independently triggered. Most firing systems call this semi-automatic firing and use Tracks—a firing position property and script field—for this purpose (see the semi-automatic firing article). However, Fire Pioneer, ShangYi-TECH, SBC Spectra Series, and SBC TX3600P firing systems do not use Tracks. Instead, they rely on Finale 3D’s segment functionality, which is based on songs or segment markers. For timecode some of these firing systems use FSK timecode that contains embedded segment numbers. This article explains how configure segments for these firing systems. Segments can be defined either by songs or segment markers. Songs: Default segment numbers are assigned automatically at export starting from 0 for the song with the earliest start time, unless specified manually in the Songs window. Segment markers: Default segment numbers are assigned automatically at export starting from 0 for the segment marker with the earliest start time, unless specified manually in the Keyframes window. Use either songs or segment markers—not both. If segment markers are present, they take precedence and songs will be ignored for segment purposes. How Segments Are Assigned Segment Method Triggered By Behavior Songs Adding songs via “Music > Add song or soundtrack” Default segment numbers are assigned automatically for each song, starting from 0 for the earliest start time song and increasing by 1, unless specified manually in the Segment column in the Songs window. Segment markers Adding segment markers via “Show > Segments > Add segment start marker” Default segment numbers are assigned automatically for each segment start marker, starting from 0 for the first segment start marker and increasing by 1, if not specified manually in the Segment column of the Keyframes window. Using Songs to Assign Segments If your show contains one or more audio tracks, Finale 3D will assign segment numbers automatically based on the start times of the songs. Alternatively, segment numbers can be assigned manually. Segment numbers can be any integer (starting at 0 by default) and do not need to be consecutive. Multiple songs can share the same segment number if you want them to be grouped into a single segment. When using songs as segments, each segment begins at the start time of the corresponding song and ends at the start time of the next song, or the end of the show. Steps: Add one or more audio files via “Music > Add song or soundtrack” (see Figure 1). (Optional) Open the Songs window (via the Window menu on the main menu bar) to set the segment numbers manually if you want to (see Figure 2). When exporting your script using “File > Export > Export firing system script file(s)”, be sure to choose the appropriate segment option in the script export options dialog: For Fire Pioneer, select One script file per segment For ShangYi-TECH, select Multiple segments For SBC Spectra Series and TX3600P, select One segment per song or segment marker When exporting your soundtrack using “File > Export > Export soundtrack”, select the Fire Pioneer FSK (one file per segment) option. Note: both Fire Pioneer and ShangYi-TECH use Fire Pioneer FSK timecode. Figure 1 – A show with two songs where each song represents a segment. Figure 2 – The songs window allows manual overrides of the segment number assignments (optional). Using Segment Markers to Assign Segments If you want full control over segment timing or are not using multiple songs, you can define segments using segment markers. Segment start markers define the beginning of each segment. Finale 3D will assign segment numbers automatically for each segment. Alternatively, segment numbers can be assigned manually. Segment numbers can be any integer (starting at 0 by default) and do not need to be consecutive. Each segment defined by a segment start marker must have a unique segment number. A segment continues until the next segment start marker or until the end of the show, unless segment end markers are used. Steps: Choose “Show > Segments > Add segment start marker” (a vertical dotted line will appear in the timeline, see Figure 3). (Optional) Add segment end markers to explicitly define segment end times. If no segment end markers are added, each segment extends to the next segment start marker or the end of the show. (Optional) Open the Keyframes window (via the Window menu on the main menu bar) to assign a segment number in the Segment column or to delete a marker (see Figure 4). If no number is entered, a default segment number will be assigned automatically at export, starting with 0 for the earliest time keyframe. Finale 3D does not impose limits on segment numbers, but your firing system may — consult your firing system documentation for supported ranges. When exporting your script using “File > Export > Export firing system script file(s)”, be sure to choose the appropriate segment option in the script export options dialog: For Fire Pioneer, select One script file per segment For ShangYi-TECH, select Multiple segments For SBC Spectra Series and TX3600P, select One segment per song or segment marker When exporting your soundtrack using “File > Export > Export soundtrack”, select the Fire Pioneer FSK (one file per segment) option. Note: both Fire Pioneer and ShangYi-TECH use Fire Pioneer FSK timecode. Figure 3 – A show without music using segment start/end markers to define segments. Figure 4 – Segment markers and their (optional) manually assigned segment numbers are listed in the Keyframes window.
Hi DrewFinale, I haven’t had time to try since my last message, I’m very busy about writing the fireworks for the French national day which is approaching.. I’m currently using my sister’s computer to work on Final 3D while I wait for more time to find a solution. Thanks for your help! I’ll let you know as soon as I have time to try.
Hi Grothus, I hope all is well. Were you able to get Finale 3D running using the instructions in my previous post or did you find another solution?
Feature Request: Add ability to specify type (or subtype, or other field currently allowable as a filter) for a given position; automatically filter effects list when position is selected. The functionality that filters the events window to the appropriate effects when selecting a DMX position is great, and it got me thinking… Could it be possible to do the same for pyro effects? I’ve got positions that are intended to be specific to certain types of items (shells, single shots, cakes, slices, etc.). For folks that shoot display shells, they likely do the same for different sized shells because of distance requirements. I heavily rely on the filtering available in the effects window, but I repeatedly select the same filters over and over again as I move between positions. Adding the ability to set a default filter for a position (from the Position Details window) would make this automatic. It wouldn’t be a required field (not every position is expected to be exclusive to a type), and the filtering shouldn’t prevent the user from manually overriding (clearing the selected filter, doing additional filtering, etc.). Thanks for considering! Rich (Finale user since 2014)
Pyro_341800000 wrote: Has there been any progress on the water cake effects? No, I’m sorry, we haven’t yet made the necessary improvements to the 3D environment to support water cakes.
Thank you!
The shell break pattern is called “Ear”. However, these colored smoke effects also require the use of the custom effect editor. Currently, colored smoke can’t be created exclusively using VDL. Here is a link for a Finale 3D show file which contains these effects: https://finale3d.com/wp-content/uploads/2025/05/七彩祥云.fin
https://drive.google.com/file/d/1Tk5vA-SmOQSJrbdfLMLmoGO04XIwK64a/view?usp=sharing May I ask what effect in the video?I tried waterfall but the distance of waterfall didnt spit out this far.
Feature Request: Limited duration “step up” to next version (with constraints) I saw the racking functionality and CobraCon and was blown away. I also know I’m never going to be a candidate for Pro, and I expect I’m part of a class of folks in the same boat. I shoot one show a year large enough to benefit from some of the Pro features (like the new racking functionality), but don’t have customers to bill to help cover the costs. I understand the importance (and challenge) of differentiating features and not cannibalizing a higher margin product, but enabling customers to use more advanced features (and get additional revenue from them when you otherwise wouldn’t) would be a win on both sides. My proposal builds on the functionality you have (time based subscriptions, temporary trials like PyroJam, etc.) and enable users with an active subscription to a “lesser” product (Hobbyist? Lite?) to purchase a short-term “step up” to the next version. This would be limited in frequency (once per subscription-year?) and duration (30 days?). I’d love it to be free, but acknowledge this would add costs/overhead (both development and support). I know this is a slippery slope, and can picture the requests/escalations (I just need one more day! Can I do this twice a year? etc.). As it stands, there’s no in-between, and there could be enough “pro-hobbyists” out there to make it worthwhile even if you enable the limited scenario. Over time, you could consider supporting more options (first time is $100, second is $200, etc., so that at some point, it’s cheaper to just buy Pro) if that makes sense. I’ve got money in hand… Thanks for considering! Rich (Finale user since 2014)