Line 26: | Line 26: | ||
===Recording Presets=== | ===Recording Presets=== | ||
To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See section (TODO: Add link here) how to use the programmer filter. After you pressed OK in the programmer filter, a new preset will be recorded. You can now use F2 to rename it. | To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See section (TODO: Add link here) how to use the programmer filter. After you pressed OK in the programmer filter, a new preset will be recorded. You can now use F2 to rename it. | ||
===Modifying Presets=== | ===Modifying Presets=== | ||
Line 33: | Line 35: | ||
====Replace==== | ====Replace==== | ||
Replace will remove all existing entries from the preset and save everything that is in the programmer to the preset. | Replace will remove all existing entries from the preset and save everything that is in the programmer to the preset. | ||
====Merge==== | ====Merge==== | ||
Entries that are not in the programmer but in the preset, are not touched. Existing entries will be updated and missing ones will be added | Entries that are not in the programmer but in the preset, are not touched. Existing entries will be updated and missing ones will be added | ||
====Append==== | ====Append==== | ||
Entries that are in the programmer but not in the preset will be appended to the preset. Entries that are in the programmer and in the preset, will stay untouched in the preset and the entries in the programmer will be removed. | Entries that are in the programmer but not in the preset will be appended to the preset. Entries that are in the programmer and in the preset, will stay untouched in the preset and the entries in the programmer will be removed. | ||
====Substract==== | ====Substract==== | ||
Entries that are in the programmer and also exist in the preset will be removed from the preset. However keep in mind, not the new value is substracted from the old, but the whole property will be removed from the preset. | Entries that are in the programmer and also exist in the preset will be removed from the preset. However keep in mind, not the new value is substracted from the old, but the whole property will be removed from the preset. | ||
====Update==== | ====Update==== | ||
don't ask me... no clue | don't ask me... no clue | ||
===Deleteing Presets=== | ===Deleteing Presets=== | ||
You can delete existing presets by selecting the preset you want to delete and then press Delete or in the presets window use Edit -> Delete Preset | You can delete existing presets by selecting the preset you want to delete and then press Delete or in the presets window use Edit -> Delete Preset | ||
===Applying Presets=== | ===Applying Presets=== | ||
Line 78: | Line 73: | ||
TODO: i guess this should work, too. | TODO: i guess this should work, too. | ||
===TODO=== | ===TODO=== |
Revision as of 21:06, 23 May 2011
DMXControl 3 lessons
Overview
In this lesson we explain how to apply presets. By re-using presets you are more efficiently when programming your show.
Lecture 13: Presets
Presets are very similar to cues. You can create them in the same way, see lesson 8. Similar the the button "Create cue" here you find the button "Create preset". You can use presets to store different values for the parameters of your fixtures. You can store:
- moving light positions
- colors of RGB Pars
- combination of gobo, shutter on and color
- generic chasers (where you later only replace/modify the color)
- or simply intensities of your conventional fixtures
- etc.
The big advantage of using presets is, that it's referenced data. That means, whenever you record a cue using presets, not the actual values, but a link to the preset is stored. So keep in mind, if you change your preset, all cues that use this preset will use the new values. A simple example where presets can rapidly speed up programming would be: You've recorded a color of your cyc wash as a preset and used this preset in five cues. If you later decide to modify the cyc wash a bit, you just need to update one preset instead of five cues. However if you just want to change the color in one cue you can do that by overwriting the reference with manual data. (i hope!)
Recording Presets
To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See section (TODO: Add link here) how to use the programmer filter. After you pressed OK in the programmer filter, a new preset will be recorded. You can now use F2 to rename it.
Modifying Presets
If you want to modify an existing preset, select the preset you want to modify and click on the arrow right of the "Store Preset" Button. A menu will pop up, where you can choose how to modify the preset. Options are explained in the following
Replace
Replace will remove all existing entries from the preset and save everything that is in the programmer to the preset.
Merge
Entries that are not in the programmer but in the preset, are not touched. Existing entries will be updated and missing ones will be added
Append
Entries that are in the programmer but not in the preset will be appended to the preset. Entries that are in the programmer and in the preset, will stay untouched in the preset and the entries in the programmer will be removed.
Substract
Entries that are in the programmer and also exist in the preset will be removed from the preset. However keep in mind, not the new value is substracted from the old, but the whole property will be removed from the preset.
Update
don't ask me... no clue
Deleteing Presets
You can delete existing presets by selecting the preset you want to delete and then press Delete or in the presets window use Edit -> Delete Preset
Applying Presets
You can "drag&drop" a preset into your scene list. A copy of your "preset cue" will be inserted. All values from the preset are taken over into the new cue.
Applying Presets for Selected Fixtures Only
TODO: uhm should work, ha?
Applying Selected Parameters of Presets
It is also possible to take not the whole preset, but only a selected attribute from the preset for your current cue. For this case you drag&drop the preset to your dedicated attribute, e.g. the dimmer. Please have a view to the programmer: You can see that in our case the dimmer value was taken from the preset.
Applying Selected Parameters of Presets for Selected Fixtures Only
TODO: i guess this should work, too.
TODO
- TODO: some paragraphs sound odd, going to change that later ...
- TODO: add some better explanation what presets are.
Excercise
- Create some presets and use it in your scene list
Additional links and references
Certificate
I have understood the topics of this lecture and want to continue with next course: Lecture14: XXXX
{{#tree:id=dmxc3|openlevels=1|root=DMXC 3 lessons|
- preamble
- lesson 1: Installation and configuration
- lesson 2: The GUI panel concept
- lesson 3: Creating and patching fixtures
- lesson 4: The live view panel
- lesson 5: Setting properties with property panels
- lesson 6: Output plugins
- lesson 7: Summery and details - Setting
- lesson 8: Scenes (cues) and scene lists
- lesson 9: Fanning, chasers and other effects
- lesson 10: The programmer view
- lesson 11: Trigger concepts
- lesson 12: Editing scenes and scenelists
- lesson 13: Presets
- lesson 14: Summary and details - Programming
- lesson 15: Working with parallel scene lists
- lesson 16: Softpult
- lesson 17: Artnet
- lesson 18: Multi-media: Beamer tool, Matrix etc.
- lesson 19: Other clients and plugins (Android, iOS, ...
- lesson 20: Create new device definitions
- lesson 21: free topic
- lesson 22: Hints for testers and test reporting
- appendix1: Summary of commands ans shortcuts
- appendix2: Kernel menu tree
}}
Language: |