Lesson 8 Tut3: Difference between revisions

From English DMXC-Wiki
No edit summary
Line 24: Line 24:




* We go to the'' 'Stage View'''
* We go to the '''Stage View'''
* We select the 'Generic RGB PAR Group "(or choose from all RGB light with one of the other methods)
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* The intensity of the dimmer panel is pulled or press the "Lumos" button
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)


* The intensity of the dimmer panel is pulled or the "Lumos" button pressed
{{Bild_mit_Unterschrift |DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}
* In the Color panel "green" is selected . The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)


{{Bild_mit_Unterschrift |DMXC3L08 firstCue01.JPG|1|Einstellung der Scheinwerfer auf die gewünschte Einstellungen|center|700px}}
* On the left click on "Add new cue"
* It opens a new window called "Programmer filter" which we will explain in Chapter 10. For now press OK.
[[File:DMXC3L08 programmerFilter.JPG]]


* Click on the left, "Add new cue"
* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* It opens a new window "Programmer filter", which we explain in Chapter 10, now first press OK.
* Here we rename the cue in the ''Name'' field to "My First Cue".
* Because we do not have any cue list one will be created now automatically. This is displayed in a new panel.
* Here we rename the cue in the Name field to "My First Cue".


{{Bild_mit_Unterschrift |DMXC3L08 firstCue02.JPG|2|Ansicht des Programmer Fensters|center}}
{{Bild_mit_Unterschrift |DMXC3L08 firstCue02.JPG|2|View of the programmer window|center}}


Each scene needs a "host container"-  that's a scene list. New cuelist can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!"
Each scene (cue) needs a "host container" -  that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".




Line 49: Line 50:
[[File:DMXC3L08_createSceneListnew.JPG|600px]]
[[File:DMXC3L08_createSceneListnew.JPG|600px]]


You can open this new cue list with a '''double click''' on the object in the project explorer or using the context menu item "open" (or double click).  
You can open this new cue list with a '''double click''' on the object in the project explorer or using the context menu item "open" (or double click).  
In the tabular list then the individual parameters of the cue can be adjusted.
In the tabular list you can adjust the individual parameters of the cue.


[[File:DMXC3L08 changeLiveView.JPG]]
[[File:DMXC3L08 changeLiveView.JPG]]
{{BoxHint
{{BoxHint
|Text =The name of the cue should always be changed so that you can remember later quickly, what the cue includes and what is the reason and target of this cue (e.g., "First scene", "Start cue", "ML Red", etc.). Not least, there is even a comment box at the far right in the scene list.
|Text =The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is and wich target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.}}
}}
The life cycle of a Cue is as following:
{{Bild_mit_Unterschrift |DMXC3L08 SlideDMXC3cue.jpg|3|Lifecycle eines Cues in DMXControl 3|center|700px}}
 
 
Cue at first waits for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then comes the delay-time relevant if one is defined. Finally, a fade-in time can be specified where the cue is faded-in (increasing particular the dimmer channel).
 
Alternatively to delay / fade-in you may define  delay down/ fade down. This is common in the theater control, when the value should be reduceded compared to the previous cue.


The life cycle of a cue is as following:
{{Bild_mit_Unterschrift |DMXC3L08 SlideDMXC3cue.jpg|3|Lifecycle of cues in DMXControl 3|center|700px}}


Please note that a cue by itself never "completes", but always with a different cue "overwritten".


Return  to the scene list panel and press the '''Add new cue''' button. At first  the programmer filter tool will appear where you can manually influence  which devices and which attributes should be really taken over into the new scene. Typically you can confirm without modification.
A cue waits at first for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).


[[File:DMXC3L08 programmerFilter.JPG]]
Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduceded compared to the previous cue.




Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.


[[File:DMXC3L08 FirstScene.JPG]]
[[File:DMXC3L08 FirstScene.JPG]]


{{BoxAchtung
{{BoxAttention
|Text = You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
|Text = You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
}}
}}
{{Bild_mit_Unterschrift |Clear_programmer.jpg|4|Löschen des Programmers|center}}
{{Bild_mit_Unterschrift |Clear_programmer.jpg|4|Clearing the programmer|center}}
[[File:Clear_programmer.jpg]]
[[File:Clear_programmer.jpg]]




In following table we explain the meaning of cue attributes (which you can see in the scene list header:
In following table we explain the meaning of cue attributes (which you can see in the scene list header):


{| class="wikitable"
{| class="wikitable"
Line 90: Line 85:
  |-
  |-
  | Progress
  | Progress
  | shows status of scene during execution of scene list (wait time and progress)
  | shows the status of the scene during execution of scene list (wait time and progress)
  | in percent
  | in percent
  |-
  |-
Line 107: Line 102:
  | Fade
  | Fade
  | fade-in value
  | fade-in value
  | in milli seconds
  | in milli seconds [ms]
  |-
  |-
  | Delay
  | Delay
Line 120: Line 115:
  | Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue)
  | Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue)
  | default: active
  | default: active
|-
| Re (ReExecute)
| If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the ''actual'' value to the destination value.
| Example:<br>
Cue 39 Fade 0s: 1 + 2 At Full<br>
Cue 40 Fade 500s: 1 At 0<br>
Cue 41 Fade 10s: 2 At 0<br><br>
Cue 41 should be a blackout<br><br>
Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds.<br>
Now someone on stage forgetts his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left).<br><br>
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in 60s<br><br>
If Re is active for cue 41 the 1 immedately goes down from the ''actual value'' to 0 in 10s together with device 2.
  |-
  |-
  | Comment
  | Comment
Line 128: Line 135:


In the same way you can create some more cues and store it in the scene list.
In the same way you can create some more cues and store it in the scene list.
{{Bild_mit_Unterschrift |DMXC3L08 SecondScene.JPG|5|Cueliste mit mehreren Cues|center}}
{{Bild_mit_Unterschrift |DMXC3L08 SecondScene.JPG|5|Cuelist with some cues|center}}
[[File:DMXC3L08 SecondScene.JPG]]
[[File:DMXC3L08 SecondScene.JPG]]


===Playing Back Cues===
===Playing back cues===
Go, Back, etc.
Go, Back, etc.


However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.
However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.


===Using Advanced Timing (=> Property Based Timing)===
===Using advanced timing (=> Property Based Timing)===
It is possible to set delay and fade times for each property. You can use this feature to build a cue that moves your moving lights to a different position, then changes the color and after that changes the gobo.
It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color and after that change the gobo.


In property grid change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in  milliseconds. Also you can use fanned values here. See [[Lesson 9]].
In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in  milliseconds. Also you can use fanned values here. See [[Lesson 9]].




The  following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.
The  following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.


[[File:Dmxc3 advanced timing value.jpg]]&nbsp;&nbsp;
[[File:Dmxc3 advanced timing value.jpg]]&nbsp;&nbsp;
Line 152: Line 159:
===Editing Property Based Timing===
===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.
Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.


==Excercise==
==Excercise==

Revision as of 18:16, 12 January 2013

Template:Hauptüberschrift

table of content

{{#tree:id=dmxc3|openlevels=1|root=DMXC 3 lessons|

}}


Overview

Scenes (cues) are the most important elements of your show. Here we will explain the powerful scene concept of DMXControl 3. The terms "cue" and "scene" are used as synonym words.


Lecture 8: Scenes (cues) and scene lists

Now the real work begins - we will create our first cue in DMXControl 3! All RGB lights will shine green.


  • We go to the Stage View
  • We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
  • The intensity of the dimmer panel is pulled or press the "Lumos" button
  • In the color panel select "green". The 8 headlights in the Stage View should now respond accordingly (see figure)

Template:Bild mit Unterschrift

  • On the left click on "Add new cue"
  • It opens a new window called "Programmer filter" which we will explain in Chapter 10. For now press OK.

DMXC3L08 programmerFilter.JPG

  • Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
  • Here we rename the cue in the Name field to "My First Cue".

Template:Bild mit Unterschrift

Each scene (cue) needs a "host container" - that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".


DMXC3L08 secondScene.JPG DMXC3L08 SlideDMXC3cue.jpg DMXC3L08 firstCue02.JPG DMXC3L08 firstCue01.JPG

DMXC3L08 createSceneListnew.JPG

You can open this new cue list with a double click on the object in the project explorer or using the context menu item "open" (or double click). In the tabular list you can adjust the individual parameters of the cue.

DMXC3L08 changeLiveView.JPG

 Important Hint The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is and wich target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.


The life cycle of a cue is as following: Template:Bild mit Unterschrift


A cue waits at first for its trigger point, see Lesson 11. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).

Alternatively to delay / fade-in you may define delay down / fade down. This is common in the theater control when the value should be reduceded compared to the previous cue.


Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.

DMXC3L08 FirstScene.JPG


 Attention You have to clean the programmer! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.

Template:Bild mit Unterschrift Clear programmer.jpg


In following table we explain the meaning of cue attributes (which you can see in the scene list header):

Attribute Description Example
Progress shows the status of the scene during execution of scene list (wait time and progress) in percent
Trigger relation to predecessor cue, use "follow" as default see Lesson 11
Trigger Value see Lesson 11
Name free name of scene should explain the content of cue
Fade fade-in value in milli seconds [ms]
Delay fanning for fades see Lesson 9
Ac (active) is this cue active or should it be ignored? default: active
Ap (autoprepare) Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue) default: active
Re (ReExecute) If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the actual value to the destination value. Example:

Cue 39 Fade 0s: 1 + 2 At Full
Cue 40 Fade 500s: 1 At 0
Cue 41 Fade 10s: 2 At 0

Cue 41 should be a blackout

Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds.
Now someone on stage forgetts his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left).

What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in 60s

If Re is active for cue 41 the 1 immedately goes down from the actual value to 0 in 10s together with device 2.

Comment for free use, insert explaining words

In the same way you can create some more cues and store it in the scene list. Template:Bild mit Unterschrift DMXC3L08 SecondScene.JPG

Playing back cues

Go, Back, etc.

However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.

Using advanced timing (=> Property Based Timing)

It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color and after that change the gobo.

In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in milliseconds. Also you can use fanned values here. See Lesson 9.


The following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.

Dmxc3 advanced timing value.jpg   Dmxc3 advanced timing fade.jpg


Dmxc3 advanced timing delay.jpg

Editing Property Based Timing

Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.

Excercise

  • Generate your own cues
  • Try the buttons "STOP", "GO" and "Mode" in the cue list
  • Work with different fade times


Certificate

I have understood the topics of this lecture and want to continue with next course: Lesson 9



table of content

Kategorie:DMXControl 3

Retrieved from "https://wiki-en.dmxcontrol-projects.org/index.php?title=Lesson_8_Tut3&oldid=2042"
Last modified
This page was last edited on 12 January 2013, at 18:16.