That would solve my issue in most circumstantiates   I believe. The only thing I could think of as another situation, is often we shoot product in a “3-inch Pairs”(Example) position because we have limited equipment on or around the 4th, so every cue counts. I could add a note of where it should go in bulk (A Field) , and then just click the product to drop on the timeline.   We are often dealing with seasonal shooters so we try and make it as simple and logical sense as possible.   This is just a broad Example.   Just a thought.

I am looking for the properties for the rack layout window.  If possible I would like to change the settings for grid size, snap to(if it exist), and try to find the setting for selection of rack clusters.  My office mate has something turned on when he selects a rack cluster a nice big colored box shows up that show some information on the racks selected.

Hey Drew!   1&2 I understand (been using Cobra for 10 years now) and I get how this would be difficult on your end, had to ask.   I’ve used the mass update before and it will get the job done.  I have some ideas in my head on how it might be doable programmatically but need to think them thru a bit more and ponder if it’s even worth the work if it only benefits a single firing system.  You may see an email from me.   Thanks Again!  

Hi NEC, I completely understand the usefulness of having your reports and labels indicate where you plan to use each COBRA module type. The reason the bank letters for 36M and 72M aren’t represented in addresses in Finale 3D is twofold:   1) Because the highest pin (i.e., cue) number is 18, not 36 or 72. A 36M or 72M is essential 2 modules or 4 modules packaged together. By contrast, the Mongoose system has an option for 2 slats of 24 pins because the pins on the actual physical module are 1 through 48.   2) Because the COBRA script format doesn’t use three-part addresses that include letters. A three-part address would be something like 01-A-12 which would represent module 1, bank A, pin 12. Instead, all COBRA addresses are two-part (just module and cue). By contrast, the fireTEK script format uses three-part addresses that include module, slat, and pin.   For these reasons, it’s really not possible for Finale 3D to represent the bank letters for the 36M or 72M in addresses. As a future improvement, we might be able to represent the modules another way. In the meantime, using one of the notes columns or another custom column in the script window is your best bet. In terms of the manual work required, I think it might be less than you think. Did you know that you can mass update script rows by selecting them, right clicking, and selecting ‘Edit properties’? This means you can just filter your script to module numbers or positions that will use 36Ms, press Ctrl+A to select all, right click, select Edit properties, and add a note to all the rows simultaneously. Then, just repeat the process for the 72Ms.

Hi Pyro_67840000, you reported the same issue about 7 months ago in October. How did you fix the problem at that time?

Thank you Drew!

The original post on this topic was from 2022, and the answer is a little different now: the industry’s hardware support for DMX ramp features has changed, and we’ve begun a project to support exactly what you are asking for.   The majority of the DMX capable firing systems already have or soon will have support for ramping functions.  Thus the majority of users scripting DMX lights in Finale will have the capability in their hardware to support fades and color changing fades as continuous transitions without requiring a large number of events to simulate a continuous transition with short stair step changes.  This is great news.   In light of this change in hardware support, we began a project at the end of 2023 to rewrite our DMX exporter so it could support continuous transitions and fades, as well as other improvements like “latest takes precedence” semantics for overlapping effects.   The first phase of this project, which was tested in our implementation of the new DMX-capable Showven firing system, proved out our technical design and removed most of the technical risks behind our approach.  This phase completed 2024 Q1 (middle of March).   At that time we had to pause our DMX work to switch our attention to a set of rack layout improvements, which we’ve been working on since then.  The rack layout project is likely to continue into Q3 of 2024.  At that point our plan is to resume work on the DMX project.  Our goal is to support fades and color changing fades as continuous transitions by the end of the year, hopefully before, on all major hardware.   Will      

Hi TN Pyro, thanks for posting, here are some tips:   To view the distance between positions Click the Top camera preset on the right side of the design window to view the positions from above. Then, hold Shift on your keyboard and left click on two or more positions. Rulers will automatically be drawn showing the distance between the selected positions.   To change ruler units from meters to feet Go to ‘File > User settings > Show ruler distances in feet instead of meters’.       The Hobbyist and Pro versions of Finale 3D have a selection of features for laying out positions. These features aren’t available in Lite. Here’s a screenshot from the feature comparison.  

Hi Will coming back on this topic : it’s “pretty” easy to fade in  / fade out using multiple dimmer events with 10% increment, back to back. But what about color transition from one to another ? No “ramp” feature so far ? This is way more complicated, and require to create a sh*tload of DMX effects for every transition 🙁

Hi, I am not able to find a way to easily tell the distance between the various positions, how do I easily see that? And is there a way in Lite to easily set the distance between positions in bulk or do I have to click and drag each one?   Thanks.