Lesson 10 Tut3: Difference between revisions

From English DMXC-Wiki
m (Jkuehn moved page Lesson 10 to Lesson 10 Tut3 without leaving a redirect)
No edit summary
 
(12 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Hauptüberschrift
{{Maintitle
| logo = Im-aim.png
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
| maintitle = First Steps: {{PAGENAME}}
}}
}}
{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
{{NavigationTop-Tut3
| zurückLink = Lektion_9_Tut3
| LinkBackwards = Lesson_9_Tut3
| zurückText = Lektion 9
| TextBackwards = Lesson 9
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| LinkForwards = Lesson_11_Tut3
| vorLink = Lektion_11_Tut3
| TextForwards = Lesson 11
| vorText = Lektion 11
}}
}}
==Overview==
==Overview==
Here we explain the "programmer view" - a tool that helps to "debug" your show programming.
Here we explain the "'''Programmer'''" view - a tool that helps in programming and "debugging" your show.


==Lecture 10: The programmer view ==
==Lecture 10: The programmer view ==
 
The '''Programmer''' tool logs all modifications you made and shows the current content of the "cue buffer".  
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".  


{{BoxHint
{{BoxHint
| Text= 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.
| Text= Remember the "save scene" dialog in DMXControl 2? There you were asked to define the channels and values before finally saving the cue. The '''Programmer''' is an extended view of this functionality.
}}
}}


Let's illustrate this by an example. We make following actions:
Let's illustrate this by an example. Perform the following steps:


* at first we open the moving lights shutters and select the color green
* First, open the moving lights shutters and select the color green
* Second, set the gobos of all devices on "Gobo2"
* Third, set the group of front lights to 50% brightness


* secondly, the gobos are set for all devices on "Gobo2"
{{Picture_with_subtitle |DMXC3L10 liveviewProgrammer.JPG|1|Stage View|center}}
* thirddly, we set the group of front lights to 50% brightness


The results are now shown in the programmer. Please be aware that the cue is not saved at this point in time, because further modification might follow.


[[File:DMXC3L10 liveviewProgrammer.JPG|center]]
{{Picture_with_subtitle |DMXC3L10 Programmer.JPG|2|All changes of the device settings are shown in the programmer|center|800px}}
{{Bild_mit_Unterschrift |DMXC3L10 liveviewProgrammer.JPG|1|Ansicht des Stage View|center}}


If you change your mind on the current cue, you can press the '''Clear Programmer''' button to remove all settings and refresh the programmer.


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.  
Now you can see in the '''Programmer''' which values would be stored in the cue. When you save the cue, you are able to select the desired items in the '''Programmer Filter''' that appeared before. In the following example, we do not save the "Generic Dimmer" (by deselecting them) because we probably want to save them in another cue list.


[[File:DMXC3L10 Programmer.JPG|center|600px]]
{{Picture_with_subtitle |DMXC3L10 ProgrammerFilter.JPG|3|View of the Programmer Filter|center}}
{{Bild_mit_Unterschrift |DMXC3L10 Programmer.JPG|2|Alle Änderungen der Gerätewerte werden im Programmer angezeigt|center|800px}}


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.
If your cue is OK, then assign it to a cue list or an executor by pressing the "'''Add new Cue'''" button and then clear the programmer (to provide "space" for the next cue).


In order to program quicker, there is the snapshot function. With the button '''Write Snapshot''' you can save the current selections in the programmer and reload them later by using the drop-down menu ('''Load Snapshots'''). This helps you to program many similar cues with little effort.


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).
In addition to the above, you can also create a filter with '''Set Filter''' or delete filters with '''Clear Filter'''. Filters are mainly used in '''Output Mode'''. With filters you can adjust the values ​​in the programmer that are actually sent out. If '''All''' is active, all the values ​​in the programmer are sent. With '''Filtered''' only the values ​​that have been activated in the filter are sent. And with '''Blind''' no values are sent out.
 
{{Bild_mit_Unterschrift |DMXC3L10 ProgrammerFilter.JPG|3|Ansicht des Programmer Filters|center}}
 
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.
 
[[File:DMXC3L10 Programmer.JPG|600px]]
 
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.
 
[[File:DMXC3L10 ProgrammerFilter.JPG]]
 
 
==Excercise==
* Repeat the above scenario
 
==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 11]]
 
[[de:Lektion 10]]
[[en:Lesson 10]]
 
 
__NOTOC__
__NOTITLE__


==Exercise==
1) Repeat the above scenario


{{NavigationTop-Tut3
{{NavigationTop-Tut3
| zurückLink = Lektion_9_Tut3
| LinkBackwards = Lesson_9_Tut3
| zurückText = Lektion 9
| TextBackwards = Lesson 9
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| LinkForwards = Lesson_11_Tut3
| vorLink = Lektion_11_Tut3
| TextForwards = Lesson 11
| vorText = Lektion 11
}}
}}
 
[[de:Lektion_10_Tut3]]
[[Kategorie:DMXControl 3]]
[[Category: Tutorials DMXControl 3]]

Latest revision as of 22:23, 15 May 2013

[[File:{{{Logo}}}|48px|link=]] {{{Pagetitle}}}


Arrow back.png Lesson 9
Lesson 11 Arrow forw.png
table of content

Overview

Here we explain the "Programmer" view - a tool that helps in programming and "debugging" your show.

Lecture 10: The programmer view

The Programmer tool logs all modifications you made and shows the current content of the "cue buffer".


 Important Hint Remember the "save scene" dialog in DMXControl 2? There you were asked to define the channels and values before finally saving the cue. The Programmer is an extended view of this functionality.


Let's illustrate this by an example. Perform the following steps:

  • First, open the moving lights shutters and select the color green
  • Second, set the gobos of all devices on "Gobo2"
  • Third, set the group of front lights to 50% brightness


Picture 1: Stage View
Picture 1: Stage View


The results are now shown in the programmer. Please be aware that the cue is not saved at this point in time, because further modification might follow.


Picture 2: All changes of the device settings are shown in the programmer
Picture 2: All changes of the device settings are shown in the programmer


If you change your mind on the current cue, you can press the Clear Programmer button to remove all settings and refresh the programmer.

Now you can see in the Programmer which values would be stored in the cue. When you save the cue, you are able to select the desired items in the Programmer Filter that appeared before. In the following example, we do not save the "Generic Dimmer" (by deselecting them) because we probably want to save them in another cue list.


Picture 3: View of the Programmer Filter
Picture 3: View of the Programmer Filter


If your cue is OK, then assign it to a cue list or an executor by pressing the "Add new Cue" button and then clear the programmer (to provide "space" for the next cue).

In order to program quicker, there is the snapshot function. With the button Write Snapshot you can save the current selections in the programmer and reload them later by using the drop-down menu (Load Snapshots). This helps you to program many similar cues with little effort.

In addition to the above, you can also create a filter with Set Filter or delete filters with Clear Filter. Filters are mainly used in Output Mode. With filters you can adjust the values ​​in the programmer that are actually sent out. If All is active, all the values ​​in the programmer are sent. With Filtered only the values ​​that have been activated in the filter are sent. And with Blind no values are sent out.

Exercise

1) Repeat the above scenario

Arrow back.png Lesson 9
Lesson 11 Arrow forw.png
table of content
Retrieved from "https://wiki-en.dmxcontrol-projects.org/index.php?title=Lesson_10_Tut3&oldid=2475"