Total found:3032
Another nice to have: When opening a show and getting the notification that there are Updates to blueprints as well as missing blueprints, it’s an all or nothing option. I’d like to have the ability to only get the updated blueprints and not the “missing” as I’ve created a lot of custom versions and purposely removed all of the ones I do not want (ex: I only use 3 Avery labels so having all of the other options are just a distraction). <edit> If easier, have a column that tags a blueprint as “Default” or “Custom” for quick filtering
Thanks Drew I did know about the 44100Hz project sample rate but have been running the Audio box MP3 at 192 kbps on export will try using the 320.
CLC wrote: Hello PyroExec I have come across this as well using Audacity for creating my mixes and exporting a MP3 file at 256 KBPS, if I dropped it down to 192 KBPS the clipping was gone. Just keep in mind, if you’re formatting your soundtrack as an MP3 because your using the COBRA Audio Box, then it’s critical that the bitrate of your MP3 file is 320 kbps. Reference: https://help.cobrafiringsystems.com/hc/en-us/articles/5643587743643-Creating-and-Formatting-the-MP3-Soundtrack
Given how prevalent slices are becoming, it would be nice to have a parttype of slice for filtering purposes. As it stands, slices are parttype cake with a LOT of subtypes making filters for reports/labels pretty tedious to construct
Hello PyroExec I have come across this as well using Audacity for creating my mixes and exporting a MP3 file at 256 KBPS, if I dropped it down to 192 KBPS the clipping was gone.
Question regarding default pathnames. I organize shows in a directory structure as follows, with items in <> changing as needed: Parent Directory — <Drive Letter>Shows<year><showname> Do I need to manually create all of the possible sub-directories that may get used for default-pathnames to function properly for this feature work correctly or will they get created if not already existing?
Having a “Preview” option when creating/customizing reports and diagrams would be really nice, having the ability to customize everything is very helpful, but having to export a report, review PDF, go back and make adjustment(s) and repeating this cycle can get tedious and sometimes frustrating.
Hello all a bit new to the hobby but as I’m sure with must of you once I’m hooked I go ALL in. I can’t wait to see what Finale 3D has in store to improve my shows. Thanks Jesse
I’m wondering what the best ways are to manage tracks? A few of the challenges that I’ve come up against, and somewhat overcome, but wondering what others do? I don’t have the luxury nor trust in my product to script an entire show so generally fire the show as many small sequences. I’m assuming I’m not the only one? So far, my approach is to use the minute marks as the starting point for each sequence to assist with logical grouping (eg 1m xx sec is for Track 1, 2m xx sec is for Track 2 and so on). My longest sequences are usually around 40 seconds and this has worked relatively well transitioning from my script in a spreadsheet to placing it on the Finale3D timeline, which then exports nicely to FireOne. I’m not sure yet whether it is more efficient than going straight from the spreadsheet to FireOne yet but thats a different matter, however the visualiser is kind of nice and did allow me to pick up on a couple of minor glitches in my ideas. What do you do however once you get to the point of having a show scripted and then decide you want to insert another track/event somewhere in the middle? In FireOne UF there is an event manager so quickly creating a new event at the end, and then bumping it up to where it needs to go is a trivial task but it seems like there is no similar functionality in Finale3D at least not that I can find, nor any real reference in the documentation. In a Lighting Console world, you would insert a ‘dot’ Cue – If you have Cues 1 and 2, inserting Cue 1.1 will place it sequentially between. Most Lighting Consoles then let you to perform some type of resequencing resulting in all Cues having a major number. Finale certainly accepts a decimal in the Track field, but doesn’t do anything to process it. I’m certainly not expecting anyone to answer before New Year. Enjoy the festivities! Also (maybe I should ask separately – so feel free to tell me to get lost) – but is there a way to sort columns in numerical order rather than alphabetical/string order? Currently the Track Column sorts 1,10,11,12,2,21,22 etc which is inconvenient to get events in a row.
Site layout and rack layout diagrams contain an optional information panel on the right of the page that displays a variety of information tailored to the purpose of the diagram, such as whether the diagram is for a client, or the authority having jurisdiction, or the display operator’s crew, or the personnel who assemble single-shot racks in advance to bring to the shoot site. You choose what information to display by configuring the diagram template (blueprint), which is accessed from the blue gear menu in the upper right corner of the rack layout window. The diagram template contains eight configurable text boxes, and the text boxes can contain variables that refer to information from the diagram or the show. The site layout’s “Diagram side panel text”, which you set from the “Show > Set side panel text” menu or from the button in the top left of the rack layout view for site layout, also supports text box variables. The table below shows the list of variables available to you and their meaning. Table 1 – Variable meanings in site layout diagrams and rack layout diagrams Variables Meaning in site layout diagrams Meaning in rack layout diagrams {annotation} <undefined> The union of annotations of racks in rack clusters that are associated with racks that are included in the diagram page’s “consists-of” specification and filter. Rack diagrams often have a single annotation per rack cluster, describing the entire cluster of racks, but the annotation itself in the user interface is associated with a specific rack. This definition of the {annotation} variable ensures that if the rack layout diagram displays any of the racks in a rack cluster, the {annotation} will include the annotation describing the cluster. {diagram_page_number}, {number_of_diagram_pages} <undefined> Rack layout diagrams contain a collection of diagram pages, such as one diagram page per position, or module, or rack. Each diagram page typically consists of a diagram and a table of information. If the table is short, it may fit on the same page as the diagram, in which case the diagram page requires just a single page of paper, but if the table doesn’t fit on the same page as the diagram, the diagram page may require multiple pages of paper for the overflow. Whereas the page number in the upper right of the page counts the pages of paper, the {diagram_page_number} counts the diagram pages. {diagram_title} The title of the diagram, from the diagram template. Same as for site layout. {effect_angles_table} A table of angle counts for effects in racks in all positions passing the site layout’s position name filter. A table of angle counts for effects in racks in the diagram page’s position, which may include racks not in the diagram page itself for diagram configurations like per-rack-cluster which create diagram pages for subsets of the racks in a position. {effect_angles_table_per_diagram_page} <undefined> A table of angle counts for effects in racks included in the diagram page itself. {module}, {rail}, {rack_number}, {rack_cluster}, {rack_name}, {rack_manufacturer}, {rack_notes} <undefined> The union of module numbers, rail numbers, etc. of events included in the diagram page’s “consists-of” specification, and if the specification is “PER MODULE” then also the diagram page’s position’s pre-assigned rails (or modules thereof) that match the diagram page’s module, and if the specification is “PER POSITION” then also all the diagram page’s position’s pre-assigned rails (or modules thereof). {number_of_modules}, {number_of_rails}, {number_of_ematches}, {number_of_pins_used}, {number_of_pins_total}, {number_of_devices}, {number_of_universes} The count of modules, rails, etc. of all events in all positions passing the site layout’s position name filter. The number of modules is based on used and pre-assigned rails. Total pins includes pins from pre-assigned rails. The count of modules, rails, etc. of all events in the diagram page’s position, whether included in the shown racks or not. The number of modules is based on used and pre-assigned modules. Total pins includes pins from pre-assigned rails. {number_of_multi_loaded_holders} The count of individual single-shot holders that contain multiple effects, considering racks in all positions passing the site layout’s position name filter. The count of individual single-shot holders that contain multiple effects, considering all racks in the diagram page’s position, which may include racks not in the diagram page itself for diagram configurations like per-rack-cluster which create diagram pages for subsets of the racks in a position. Certain types of single-shot racks, such as those with the rack structure “Single-shot rack, 1-axis tiltable holders for up to 4 tubes,” support multiple effects in the same holder if the sizes are sufficiently small. For such racks, if a holder contains zero or one effect, the holder does not contribute to this variable’s count; if it contains two or more effects, it does contribute. In the physical world, racks of this structure may need a plug in the bottom of their holders if and only if the holders contain more than one effect. The purpose of this variable is to tell you how many plugs are required. {number_of_multi_loaded_holders_per_diagram_page} <undefined> The count individual of single-shot holders that contain multiple effects, considering all racks included in the diagram page itself. Certain types of single-shot racks, such as those with the rack structure “Single-shot rack, 1-axis tiltable holders for up to 4 tubes,” support multiple effects in the same holder if the sizes are sufficiently small. For such racks, if a holder contains zero or one effect, the holder does not contribute to this variable’s count; if it contains two or more effects, it does contribute. In the physical world, racks of this structure may need a plug in the bottom of their holders if and only if the holders contain more than one effect. The purpose of this variable is to tell you how many plugs are required. {position} <undefined> The name of the position containing the information shown in the diagram page. {rack_counts_table}, {rack_totals_table} A table of counts of racks in all positions passing the site layout’s position name filter. The totals table includes one line per rack name and size. The counts table includes one line for each angle of each rack and size. A table of counts of all racks in the diagram page’s position, which may include racks not in the diagram page itself for diagram configurations like per-rack-cluster which create diagram pages for subsets of the racks in a position. The totals table includes one line per rack name and size. The counts table includes one line for each angle of each rack and size. {rack_counts_table_per_diagram_page}, {rack_totals_table_per_diagram_page} <undefined> A table of counts of all racks included in the diagram page itself. The totals table includes one line per rack name and size. The counts table includes one line for each angle of each rack and size. {rack_weight_total} Total weight of racks in all positions passing the site layout’s position name filter. Total weight of all racks in the diagram page’s position, which may include racks not in the diagram page itself for diagram configurations like per-rack-cluster which create diagram pages for subsets of the racks in a position. {rack_weight_total_per_diagram_page} <undefined> Total weight of all racks included in the diagram page itself. {universes}, {sections} The union of universes or sections of all events in all positions passing the site layout’s position name filter. The union of universes or sections of all events in the diagram page’s position, whether included in the shown racks or not.