Is it possible to change my login email? I changed my email and want my effects and history moved with me.

Is there any documentation on how to use the dimming for the COBRA PAR 36 lights?  Is that even released?  I see dimmer for other things but not the COB….. stuff  

I got it to work. Thanks!

Happy to help!   By default, the Spotter Script is configured with the following filter: pinaddress != dmx   In plain English, this translates to: Pin does-not-equal dmx   Which means that any script event that has “dmx” in the Pin column is excluded from the report.   To include DMX events on your Spotter Script, open the report configuration and clear the filter from the “Filter search terms or expression” field near the top of the dialog.

Hi all, I am trying to export a spotter script with DMX events on it. I have looked at editing the spotter script report but in the editing window it shows all the info I am looking for, but when I go to export it, it will only show the pyro.   Any advice on where I should be looking in the settings would be appreciated.

Hello,   We discovered a bug in DMX script export that causes the application to crash if you export a show with a DMX effect at time = 0.  To fix/workaround the bug, just move the DMX effect to time = 1 second or any non-zero time.   The permanent fix will come out in the next beta next week.   Will  

  pyro25612210 wrote: Good afternoon, everyone! Is it possible to combine effect sequences as a group (G) so that they can be replicated at other trigger points? Yes, you may Group (G) events together in your show. Groups are a productivity feature that visually consolidates events together on the timeline and in the script window. Using Groups is permitted because it has no impact on the simulation or real-world production of the show.

Good afternoon, everyone! Is it possible to combine effect sequences as a group (G) so that they can be replicated at other trigger points?

Hey PyroExec, I think you can certainly make it easier than manually counting lines in the Wiring Script report.   As a starting point, it’s helpful to understand the basic capabilities and limitations of the report engine in Finale 3D.   What the report engine essentially does is export data from one of the Finale 3D table windows and format it in a useful way. For example, any report including things like addresses or event/effect times is pulled from the Script window because that data exclusively resides there. Similarly, rack related reports are generated from the Racks window, etc.   The report engine can sort and combine data rows and display any columns that exist in the source window. What it currently cannot do is dynamically generate rows or columns that do not exist in the source window. This means a report cannot have extra rows or columns for counts, subtotals, or anything that doesn’t exist in the source data/window.   Armed with this knowledge, you can customize a report to meet your needs. The Wiring Script is a great starting point because it is already sorted by address and includes the Quantity column. Addresses are key because quick splits / breakout boards aren’t directly represented in the Script window (or anywhere else in Finale 3D). And the Quantity column is key for knowing how many items per QS / BB.   Here are some examples of customizations you can try:   1) By default, the Wiring script report only combines rows when the Rail and Pin and Position and Part Number are a perfect match. This is critical for show setup, but for your needs, you can remove Position and Part Number. This ensures the report shows one line item per Rail and Pin (which is one Address), equating to one QS / BB.   2) By default, the Wiring Script report shows everything that needs to be wired up. But you don’t care about items that don’t require QS / BB. So, you can filter out anything that has one e-match per pin by adding this filter expression: flightcount != 1   To make it fancier, you could create a filter that shows only lines for addresses with 2-4 e-matches per pin. The filter expression would be: flightcount >= 2 + flightcount <= 4   This will give you a report with one line per QS / BB that uses 2 to 4 e-matches. At that point, the only manual work is counting the lines on the report to get your final answer. Alternatively, you can save the report as an XLSX file instead of a PDF and use an Excel function to do the counting.     To learn more about filtering, check out: https://finale3d.com/documentation/search-expressions/   To learn more about Flight Count or any other Script window column, check out: https://finale3d.com/documentation/script-table-columns/

Thank you Tim! Your advice is really apreciated!