Open topic as PDF Version 1.6

Recipe Presets

Recipes can be a very useful tool for touring shows or when the show changes a lot.

Recipes can be stored in cue parts and presets. A cue part or preset can contain multiple recipe lines describing what should happen based on a set of information. The recipe can be used to "cook" values into the cue part, preset, or programmer. This cooked data is marked by a small pot icon and the cooked data can easily be removed again if needed.

A recipe line can contain information about a group, preset, MAtricks, individual fade, delay, speed, and phase values.

Values from recipes can be combined with conventionally stored values.

The rest of this topic explores using recipes in presets.

The flexibility in the recipe system allows for a variety of uses. The recipes could be used to:

• Create recipe presets for groups with references to other presets for a flexible fixture setup.
• Create "template" presets with ranged values that can be applied to a flexible selection of fixtures.

Adding Recipe Lines

Recipe lines are added to presets using the Edit Preset Object pop-up. This can be accessed using the Swipey on a preset pool object.

The middle part of this pop-up is about the recipes.

The line with On/Off toggle buttons near the top of the editor is used to hide or show different element columns for the recipes.

• References:
  These are the columns for defining a Group, Preset, and MAtricks.
• Layers:
  These are the timing layers. X, Y, or Z also needs to be active for any of the layer columns to be shown.
• MAtricks:
  These are the MAtricks columns. X, Y, or Z also needs to be active for any of the layer columns to be shown.
• Invert:
  These are the Invert columns. X, Y, and Z have invert columns as well and might need to be active to show the desired columns.
• X, Y, and Z:
  Each of the grid axes has columns. If the recipe only uses one or two axes, then the columns can be limited to only show the relevant columns.

Create a Recipe

Tap Insert New Recipe to create a new recipe line.

It is almost always relevant to at least add a preset reference value. To do this tap and hold the field in the recipe row in the preset column.

This opens a Preset Pool selection pop-up. Here it is possible to navigate through the existing presets and select the desired preset. It does not have to be in the same feature group and the recipe preset.

Add the desired values in the other columns.

If the recipe contains a group, then the preset is automatically cooked when the edit pop-up is closed.

Example

We want a preset that can be used to take the current selection of fixtures to a new position in two wings and with a ranged time.

Requirement:

Have a show with some moving heads patched and placed in a row. The show also needs a position preset and dimmer preset where the fixtures are at full. This example uses the Demoshow.

Follow these steps to create the recipe preset:

1. Tap an empty position preset pool object and swipe the finger outside the preset to open the Swipey menu.
2. Select Edit Setting in the Swipey menu.
3. Tap Insert New Recipe to get a recipe line.
4. Tap and hold the first field in the preset column.
5. Tap Dimmer and then the preset where the intensity is at full (Open).
6. Tap and hold New Recipe to create a second line.
7. Press Assign.
8. Tap the position preset (Roof Floor) in the position preset pool.
9. Tap the empty recipe line to assign the preset to the line.
10. Select both recipe lines in the XWings column (if the column is not visible then make sure both "X" and "MAtricks" are active in the row with toggle buttons).
11. Edit this value so it says "2" in the XWings.
12. Select both rows in the "Fade From X" column and set the value to "1".
13. Select both rows in the "Fade To X" column and set the value to "3".

It should look like this:

14. Close the editor.
15. Select some fixtures (for instance, group 1).
16. Tap the new recipe preset and see the fixture move while they turn on.

If the move and fade should start from the center then open the edit preset object pop-up again and set the InvertStyle to All and the InvertX to Yes for both recipe lines.

Working with Recipe Presets

There are three suggested workflows with presets using recipes:

1. Preset containing values and recipe.
2. Preset containing no values and recipe with group values.
3. Preset containing no values and recipe without group values.

Preset Containing Values and Recipe

The values of the Preset take precedence and the recipe line will not be loaded in the programmer (Programmer Parts window).

The intention is that the workflow is assuming that recipes are used to cook values into the presets, therefore it is not desired that the recipes are in the programmer so that it is NOT stored into a cue. Only the values of the preset go to the cue.

Preset Containing No Values and Recipe With Group Values

Since the preset has no values, of course, no values will be directly loaded in the programmer. The recipe will be loaded into the programmer (Programmer Parts window) and therefore the values are cooked into the programmer. The cue can then be stored, which will store the cooked values and recipe to the destination cue part.

This workflow does NOT follow the current selection. A group is assigned to the recipe, so the cooking within the programmer will always refer to the group, not the current selection.

Think of these as recipe templates that allow to quickly build recipes into cues. It is the intention to use recipes within the cues to re-cook cues from venue to venue in a touring show.

Preset Containing No Values and Recipe Without Group Values

As there are no values and no group, this recipe works with the current selection of fixtures. The recipe is not loaded into the programmer. Instead, the recipe preset link and MAtricks are used with the current selection of fixtures to cook values directly to the programmer.

This is a great way to have a bunch of template objects in the preset pools that allow to quickly call complex looks based on MAtricks ranges.

Additional Cue Recipe Workflow

Recipes from the Programmer Parts window will store to the destination cue and will respect the parts.

Example 1:

1. In the Programmer Parts window build some recipes in Part 1, 5 and 7.
2. Store Cue 10.
3. These Recipes will go to CueParts 1, 5, and 7 inside Cue 10.

Example 2:

1. In the Programmer Parts window build some Recipes in Part 1, 5 and 7.
2. Select Part 5.
3. Store Cue 11 Part 23.
4. Only the Recipes of selected ProgrammerPart 5 will go to CuePart 23 of Cue 11.

Select different version- latest - 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2.0

  previous next

Open topic as PDF