Lesson 8 Tut3: Difference between revisions

From English DMXC-Wiki
No edit summary
 
(14 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}}
}}
}}
{{NavigationTop-Tut3
{{NavigationTop-Tut3
| zurückLink = Lektion_7_Tut3
| LinkBackwards = Lesson_7_Tut3
| zurückText = Lektion 7
| TextBackwards = Lesson 7
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| LinkForwards = Lesson_9_Tut3
| vorLink = Lektion_9_Tut3
| TextForwards = Lesson 9
| vorText = Lektion 9
}}
}}
{{DMXC3_lesson/en}}
==Overview==
==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.
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.


{{BoxHint
|Text =The button for the "Full On" function is labeled "Lumos".  This is a Latin word meaning light.  It was used in the Harry Potter series as a spell to make the magic wand light up.}}


==Lecture 8: Scenes (cues) and scene lists ==
==Lecture 8: Scenes (cues) and scene lists ==
 
Now the real work begins - we will create our first cue in DMXControl 3! We will make all RGB lights shine green.
 
<br><br>
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 go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose 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
* You can control the intensity of the light by dragging the slider or by pressing the "Lumos" button to bring the light to full brightness.
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)
 
{{Picture_with_subtitle|DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}
{{Bild_mit_Unterschrift |DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}


* On the left click on "Add new cue"
* 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.
* It opens a new window called "Programmer filter", which we will explain in Chapter 10. For now press OK.
[[File:DMXC3L08 programmerFilter.JPG]]
{{Picture_with_subtitle|DMXC3L08 programmerFilter.JPG|2|View of the programmer filter|center}}


* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* 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".
* Here we rename the cue in the ''Name'' field to "My First Cue".
 
{{Picture_with_subtitle|DMXC3L08 firstCue02.JPG|3|View of the programmer window|center}}
{{Bild_mit_Unterschrift |DMXC3L08 firstCue02.JPG|2|View of the programmer window|center}}


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!".  
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!".  


 
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).  
[[File:DMXC3L08 secondScene.JPG]]
[[File:DMXC3L08 SlideDMXC3cue.jpg]]
[[File:DMXC3L08 firstCue02.JPG]]
[[File:DMXC3L08 firstCue01.JPG]]
 
[[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).  
In the tabular list you can adjust the individual parameters of the cue.
In the tabular list you can adjust the individual parameters of the cue.
{{Picture_with_subtitle|DMXC3L08_createSceneListnew.JPG|4|Scenelist in the Project Explorer|center}}


[[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, 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.}}
|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 which 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 of cues in DMXControl 3|center|700px}}
 


The life-cycle of a cue is as follows:
{{Picture_with_subtitle |DMXC3L08 SlideDMXC3cue.jpg|5|Life-cycle of cues in DMXControl 3|center|700px}}
<br><br>
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).
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).


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.
Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduced compared to the previous cue.
 
<br><br>
 
Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.
Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.
[[File:DMXC3L08 FirstScene.JPG]]


{{BoxAttention
{{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|Clearing the programmer|center}}
{{Picture_with_subtitle |Clear_programmer.jpg|6|Clearing the programmer|center}}
[[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):
Line 90: Line 68:
  | Trigger
  | Trigger
  | relation to predecessor cue, use "follow" as default
  | relation to predecessor cue, use "follow" as default
  | see [[Lesson 11]]
  | see Lesson 11
  |-
  |-
  | Trigger Value
  | Trigger Value
  |  
  |  
  | see [[Lesson 11]]
  | see Lesson 11
  |-
  |-
  | Name
  | Name
Line 106: Line 84:
  | Delay
  | Delay
  | fanning for fades
  | fanning for fades
  | see [[Lesson 9]]
  | see Lesson 9
  |-
  |-
  | Ac (active)
  | Ac (active)
Line 113: Line 91:
  |-
  |-
  | Ap (autoprepare)
  | Ap (autoprepare)
  | 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 color wheel for next cue)
  | default: active
  | default: active
  |-
  |-
Line 119: Line 97:
  | 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.
  | 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>
  | Example:<br>
Cue 39 Fade 0s: 1 + 2 At Full<br>
Cue 39 Fade 0s: 1 + 2 at full<br>
Cue 40 Fade 500s: 1 At 0<br>
Cue 40 Fade 500s: 1 at 0<br>
Cue 41 Fade 10s: 2 At 0<br><br>
Cue 41 Fade 10s: 2 at 0<br>
Cue 41 should be a blackout<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>
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>
Now someone on stage forgets 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>
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in the residual 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.
If '''Re''' is active for cue 41 the 1 immediately goes down from the ''actual value at this time'' to 0 in 10s together with device 2.
  |-
  |-
  | Comment
  | Comment
Line 135: Line 113:


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|Cuelist with some cues|center}}
{{Picture_with_subtitle |DMXC3L08 SecondScene.JPG|7|Cuelist with some cues|center}}
[[File:DMXC3L08 SecondScene.JPG]]


===Playing back cues===
===Playing back cues===
Line 144: Line 121:


===Using advanced timing (=> Property Based Timing)===
===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.
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]].
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_Tut3|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.
 
{| align="center"
[[File:Dmxc3 advanced timing value.jpg]]&nbsp;&nbsp;
|{{Picture_with_subtitle |Dmxc3 advanced timing value.jpg|8|Value mode|center}}
[[File:Dmxc3 advanced timing fade.jpg]]
|{{Picture_with_subtitle |Dmxc3 advanced timing fade.jpg|9|Fade mode|center}}
 
|-
 
|align="center" colspan="2"|{{Picture_with_subtitle |Dmxc3 advanced timing delay.jpg|10|Delay mode|center}}
[[File:Dmxc3 advanced timing delay.jpg]]
|}
 
<br>
===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.
 
<br>
==Excercise==
==Exercises==
* Generate your own cues
1) Generate your own cues
* Try the buttons "STOP", "GO" and "Mode" in the cue list
<br>
* Work with different fade times
2) Try the buttons "STOP", "GO" and "Mode" in the cue list
 
<br>
 
3) Work with different fade times
 
==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 9]]
 
[[de:Lektion 8]]
[[en:Lesson 8]]
 
__NOTOC__
__NOTITLE__


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

Latest revision as of 11:16, 15 May 2013

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


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

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.


 Important Hint The button for the "Full On" function is labeled "Lumos". This is a Latin word meaning light. It was used in the Harry Potter series as a spell to make the magic wand light up.


Lecture 8: Scenes (cues) and scene lists

Now the real work begins - we will create our first cue in DMXControl 3! We will make all RGB lights 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)
  • You can control the intensity of the light by dragging the slider or by pressing the "Lumos" button to bring the light to full brightness.
  • In the color panel select "green". The 8 headlights in the Stage View should now respond accordingly (see figure)


Picture 1: Setting the floodlights on the desired settings
Picture 1: Setting the floodlights on the desired settings


  • 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.


Picture 2: View of the programmer filter
Picture 2: View of the programmer filter


  • 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".


Picture 3: View of the programmer window
Picture 3: View of the programmer window


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!".

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.


Picture 4: Scenelist in the Project Explorer
Picture 4: Scenelist in the Project Explorer


 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 which 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 follows:


Picture 5: Life-cycle of cues in DMXControl 3
Picture 5: Life-cycle of cues in DMXControl 3



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 reduced compared to the previous cue.

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


 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.


Picture 6: Clearing the programmer
Picture 6: Clearing the programmer


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 color 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 forgets 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 the residual 60s

If Re is active for cue 41 the 1 immediately goes down from the actual value at this time 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.


Picture 7: Cuelist with some cues
Picture 7: Cuelist with some cues


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.


Picture 8: Value mode
Picture 8: Value mode


Picture 9: Fade mode
Picture 9: Fade mode


Picture 10: Delay mode
Picture 10: Delay mode


Editing Property Based Timing

Once you saved a cue with property based timing you can edit the values.

Exercises

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

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