Difference between revisions of "Lesson 10 Tut3"
m (Jkuehn moved page Lesson 10 to Lesson 10 Tut3 without leaving a redirect) |
|
(No difference)
| |
Revision as of 23:41, 12 January 2013
{{#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
}}
Overview
Here we explain the "programmer view" - a tool that helps to "debug" your show programming.
Lecture 10: The programmer view
The programmer is a helpful tool during programming your show. It logs all modifications you have made and shows the current content of the "cue buffer".
 |
Remember the "save scene" dialog in DMXControl 2. Here you were requested to determine the channels and values before finally saving the cue. The programmer ist a more extended view of this functionality. |
Let's illustrate this by an example. We make following actions:
- at first we open the moving lights shutters and select the color green
- secondly, the gobos are set for all devices on "Gobo2"
- thirddly, we set the group of front lights to 50% brightness
Template:Bild mit Unterschrift
The result is exactly shown in the programmer. Please be aware the the cue is not saved at this point of time, because further modification could follow.
Template:Bild mit Unterschrift
In case you change your mindset on the current cue, you can press the Clear button in order to remove all settings und refresh the programmer.
Now you have in the programmer close eye on what values would be stored in the cue. Therefore you are also in the "Programmer filter" that appears before saving the cue, select the desired values. The following example shows the generic dimmers are not yet saved (because we decide they perhaps want to be controled in a separate cue).
Template:Bild mit Unterschrift
If your cue is OK, then assign it to a cue list or an executor by "Add new cue" button - a clear the programmer too (to provide "space" for the next cue).
To program more quickly, there is the snapshot function. With it you can cache the latest entries of the programmer and later reload with the drop-down menu in which Load Snapshot is shown. This helps you to program many similar cues with lowest effort.
Besides, you can also create a filter with Set filter or delete filters with Clear Filter. This function is mainly used in output mode. By this tool you can adjust the values of the programmer that are actually spent. If All is active, all the values in the programmer are sent, at Filtered only the values that have been activated in the filter. With blind no values are issued.
Excercise
- Repeat the above scenario
Certificate
I have understood the topics of this lecture and want to continue with next course: Lesson 11
__NOTITLE__
| |||||||||
