MadMapper 3.5 comes with a big new feature that really changes the way we program a show with it: Scenes & Cues. This new feature completely replace Presets, it offers a much more flexible way to store / restore the status of surfaces, fixtures, medias or any parameters.
Principles: Surfaces & medias are objects with a set of parameters and each of those can be store in cues with the granularity you need and with editing facilities. For instance you might want to store the complete application status (surfaces, fixtures, medias & master settings), like with Presets before (but the new facilities to edit scenes & cues will improve the workflow.)
You might also want to control independently different projectors, or have different cues for video outputs and for lights/leds etc. So you would create cues on row 1 for the stage projector, on row 2 cues for side projectors, row 3 for LEDs.
Or you might want to have control on the medias and colors separately, having a set of cues on row 1 to change medias and another set of cues on row 2 with surfaces colors.
Cues can store everything that can be controlled with MadMapper “Controls” (MIDI/OSC/DMX etc.) and some more parameters (complete geometry etc.)
Also cues allow transitioning smoothly from a state to another, fading all parameters with specified transition (including media fading, geometry etc.)
To make things easy for the most common case, Scenes are a replacement for presets. Scenes are located on the first row of the cue bank grid. When you create a Scene, it stores everything (surfaces, fixtures & medias) and starting it will hide any surface you added after creating the Scene. To clarify:
A Scene is like a Cue but with limited edition: you cannot remove entries from a Scene, and you cannot store only part of an object in a Scene
A Scene will hide any surface/fixture that is not stored in it (because they were created after the Scene was created)
The idea is that when you start a Scene, you will see the exact same thing than when you stored it (on all video outputs and DMX output).
Scenes are made to handle in an easy way the most common cases, while Cues allow finer control of you show. Using one or the other, or combining both, depends on your scenario.
MadMapper also offers an easy way to automate **scenes/**cues (ie “loop through my cues each 1 minute”), and the Cue Scheduler module can be instantiated for more precise Automation / Scheduling (ie “start this cue on January 1st at 0am”, “start this cue each Thursday at 9am”, “loop through cues on row 1 on Monday, on row 2 on Tuesday”…)be moved into the Trash folder and automatically deleted after 7 days of inactivity.
A new “Cue Bank” view is available under the previews for cues and a menu “Cues” has been added.
The cue bank view consists of a top toolbar and a grid of cells. By default the grid size is 16x8 cells, it will automatically grow when you store anything in the last column/row. On top of the cell grid, there are column buttons indicating the number of the column and allowing to trigger the scene or all the cues in this column (if there is no scene) in a single click (or using MIDI, OSC, DMX etc.)
In the cue bank toolbar, from left to right, you’ll find:
Press the “+” button in a cell of the Scene row (first grid row), the + button appears when mouse is over the cell.
There are different options to create a cue:
To rename a scene/cue, just double click on its name.
To change the fade time, double click the “Fade: xxx” label in the cue cell.
To change transition type, color/image or comment, click the cell setup button:
You can inspect & modify a scene or cue by pressing the “Inspector” button:
Parameters values can be changed from the inspector.
By default all parameters use the cue transition settings. But you can specify “local transition settings” for each parameters individually. For instance you want to fade the opacity but not the RGB levels.
You can also select multiple cues to edit their content (remove parameters, change value, change transition settings etc).
For instance if I have 10 cues containing Quad 1 and I want to update “Output Geometry” from all of them, I can select all 10 cues, choose the “Surfaces / Quad 1 / Output Geometry” entry and press “Update from current values”.
If I want to stop fading on color levels of Quad 1, I can select all 10 cues, select Red, Green and Blue in the editor, and in the inspector I choose “No Transition”:
When cueing a visual, some parameters are not stored by default, but can be added manually. Generally you don’t want the current position in a movie to be stored in a cue, while that might be useful in some cases. Same for visual “Restart”, you can choose wether starting a cue will or will not restart the visuals.
To add those settings, enter Edit mode (see below), and click the “restart” button (rewind icon for movies) or the movie playback position widget.
To duplicate a cue, just drag&drop it to another grid slot with Alt key pressed. You can also do Cmd+C / Ctrl+C, select another cell and press Cmd+V / Ctrl+V.
You can move one or a multi-selection of cues by drag&drop. To insert/delete a column/row, use right-click popup menu “Layout” submenu:
For Scenes: in the popup menu, “Update Scene” will update the scene from the current project state.
For Cues: in the popup menu, “Update Values” entry will update all parameters already stored in this cue with their current value (not adding any parameter).
If you press the “Edit” button (or Cmd+Shift+C), MadMapper will show a red overlay on all cuable parameters:
Parameters that are stored in at least one of the cue selection (multiple ones may be selected) also have a red or orange outline. Orange outline means that this parameter value is different than the one stored in the cue(s), or is not present in all selected cue(s).
Surfaces and medias also have a red outline when at least one of their parameters in stored in the cue selection.
For instance in this screenshot, the cue being selected, “Cue-1”, contains the parameters Opacity, Red, Green & Blue of surface “Quad 1”, but not the other parameters. The opacity is orange, which means that its value in the cue is different than current parameter value.
Pressing one of the widget will add, remove or update this parameter in selected cues.
In Edit Cues mode:
Scenes & Cues can be start by clicking the “play” button on it, or by clicking a cue grid column button. You can also use the “Next Column” button to trigger all cues in the next column, or the “Auto Play” mode for automation. The last option is to use the “Cue Scheduler” module that will be presenter later.
There are also a lot of “Controls” to trigger cues. When entering “Edit MIDI Controls” mode (or Keyboard, DMX, OSC etc.) you can assign a MIDI channel to trigger a cue cell (ie column 1, row 1):
In Edit Controls mode, new buttons appear below the cues toolbar. By default “Map to Cell Position” is activated, which means that the assignment will be on a grid cell position (ie “/cues/bank_1/cues/by_cell/col_1/row_1”). If you activate “Map To Cue”, the control will be assignment to the target Cue (ie “/cues/bank_1/cues/by_name/INTRO 1”), so if you move the cue in the grid, the assignment will still trigger this cue.
You can also assign a control to trigger a column (by clicking a column button over the grid), it will start all cues in this column (from bottom to up).
For more options you can check in the “Controls List” dialog, by pressing the + button on the left.
When a Cue is started it will send all parameter values stored in the cue to the document, if a fade time is set, it will start a transition for this parameter (from its current value to the value stored in the cue). If any other cue had a running transition for this parameter it will be discarded. When a transition is ongoing, you can see the transition progression on the cue that generated this transition. If a cue contains various transition settings for the different parameters, the progress indication will reflect the longest transition that was generated by this cue. If you use a “damper” transition, the progress will not show anything relevant, except that a transition generated by this cue is ongoing.
When starting a Scene, the same happens, but any surface/fixture not stored in the Scene will be hidden using cue transition duration setting (ie if you create a scene and create new surfaces after)
The Cue Scheduler is a module that can be created from the new Modules tab, next to Outputs tab. You can create multiple instances. Let’s have a look at its parameters:
The Schedule part is used to define a date/time at which we would start a cue/column.
The Automate part is used to make an automation (ie start a cue/column each N seconds / beats, or start when a movie finished playing).
The last part (Target settings) defines what to trigger, either by specifying a column number or cue cell, or specifying a range (ie columns from 1-16 or cues from row 2-2, columns 1-16). If you selected a range you can choose a “Mode” to play the selected range in loop, or just once, or choose a random cue/column in this range each time something is to be started.
Which this set of parameters, many things become possible. Here are a few examples:
Let go in details now. The Schedule option will have a different behavior depending on the Automate setting.
The settings in schedule will define when a cue/column will be started. You can enter a specific date/time, ie to start a new year eve count down:
Year=2018, Month=12, Day=31, Hour=23, Minute=59, Second=0
For all Schedule settings except Seconds you can choose “Each”. If you want to start a cue each Monday at 9am:
Year=Each, Month=Each, Day=Monday, Hour=9, Minute=0, Second=0
Internally, the module will check each second if the current clock matches Schedule settings. If it matches, it will execute the action defined in Target settings (start a specified column/cue, or start a column/cue in a specified range with a specified mode).
If automate is activated, the Schedule effect is to activate or deactivate the automation. When automate is on, new parameters appear in Schedule: From Hour/Minute & To Hour Minute.
If the computer clock matches Schedule parameters, the automation will be active.
Automation settings let you choose to execute the desired event