Difference between revisions of "Lesson 11 Tut3"
| Line 13: | Line 13: | ||
==Lecture 11: Trigger in cue lists == | ==Lecture 11: Trigger in cue lists == | ||
| − | + | In previous lessons we learned how to create cues and scene lists. Now that you are familiar with most of the attributes of the scene list, more explanation about triggers is necessary. A trigger is an event that causes a previously saved scene to start. A trigger might come from things like a button press by the user,or an internal timer. The default trigger is "follow". This means the next cue will be started after the previous one has finished fading in. | |
| − | In previous lessons we | ||
'''Important:''' When you change the trigger type, you need to apply the changes with the enter-key or by clicking in another field. | '''Important:''' When you change the trigger type, you need to apply the changes with the enter-key or by clicking in another field. | ||
| − | + | There are several types of triggers. The following table describes their behaviors. | |
| Line 27: | Line 26: | ||
! Type !! Example format !! Description | ! Type !! Example format !! Description | ||
|- | |- | ||
| − | | manual || (optional) 3 || | + | | manual || (optional) 3 || Use GO to fade in next cue. |
| − | + | Optional: Fade cue in after 3 GO presses. The default is 1. | |
|- | |- | ||
| − | | follow || 5s || | + | | follow || 5s || Wait until the previous cue is faded in, then wait 5 seconds before starting the next cue. |
|- | |- | ||
| − | | wait || 5s || | + | | wait || 5s || Wait time countdown starts when the wait or follow of the previous cue is completed. In other words, the cue will wait 5 seconds after the prior cue has started, rather than waiting for it to finish. |
|- | |- | ||
| − | | timecode || 00:26:05 || | + | | timecode || 00:26:05 || Waits for the DMXControl to be given an external timecode signal equal to 00:26:05. |
|- | |- | ||
| − | | rtc || 13:00:00 || | + | | rtc || 13:00:00 || Real time clock. Fade in a cue at the specified time of 1 pm. |
|- | |- | ||
| − | | beat || (optional) 3 || | + | | beat || (optional) 3 || This requires more settings. See the paragraph below. |
| − | + | Optional: Fade in cue after 3 beats. The default is 1. | |
|} | |} | ||
| − | + | If you type an incorrect format into the '''trigger value''' field, you will get some hints about the expected input syntax. See the example for the "follow" type. | |
{{BoxHint | {{BoxHint | ||
| Line 51: | Line 50: | ||
[[File:DMXC3L11 triggerhelpcontextfollow.JPG]] | [[File:DMXC3L11 triggerhelpcontextfollow.JPG]] | ||
| − | Here is the example for the | + | Here is the example for the real time clock selection. |
[[File:DMXC3L11 triggerhelpcontext.JPG]] | [[File:DMXC3L11 triggerhelpcontext.JPG]] | ||
| Line 59: | Line 58: | ||
===Use of beat trigger=== | ===Use of beat trigger=== | ||
| − | If you want to have your scenes beat | + | A '''Beat Trigger''' is a trigger based on the main rhythm of the music. It may be manually set, or automatically generated by DMXControl as it analyzes an audio signal and looks for peak transients. |
| + | |||
| + | If you want to have your scenes beat controlled, you need to select the source for the trigger '''beat''' . | ||
{{BoxHint|Text=In the '''Trigger''' field you can specify after how many beat signals the next cue is called | {{BoxHint|Text=In the '''Trigger''' field you can specify after how many beat signals the next cue is called | ||
}} | }} | ||
| Line 72: | Line 73: | ||
==Summary== | ==Summary== | ||
| − | The following figure shows the | + | The following figure shows the dependencies and capabilities of mixing several trigger types: |
[[File:DMXC3L11 SlideDMXC3Trigger.jpg|600px]] | [[File:DMXC3L11 SlideDMXC3Trigger.jpg|600px]] | ||
| Line 82: | Line 83: | ||
| − | == | + | ==Exercises== |
* Test a mix of "follow" and "wait" triggers in one scene list | * Test a mix of "follow" and "wait" triggers in one scene list | ||
| − | * Use a tool providing timecodes (DE MediaCenter) and test a scenelist that is completely based on | + | * Use a tool providing timecodes (DE MediaCenter) and test a scenelist that is completely based on time codes |
| − | |||
| − | |||
| − | |||
| − | |||
[[de:Lektion_11_Tut3]] | [[de:Lektion_11_Tut3]] | ||
Revision as of 00:53, 16 March 2013
| [[File:{{{Logo}}}|48px|link=]] | {{{Pagetitle}}} |
Overview
Cue lists are the best tool to control the flow of your show. In this lesson we explain how to define the sequence and the change of scenes by triggers.
Lecture 11: Trigger in cue lists
In previous lessons we learned how to create cues and scene lists. Now that you are familiar with most of the attributes of the scene list, more explanation about triggers is necessary. A trigger is an event that causes a previously saved scene to start. A trigger might come from things like a button press by the user,or an internal timer. The default trigger is "follow". This means the next cue will be started after the previous one has finished fading in.
Important: When you change the trigger type, you need to apply the changes with the enter-key or by clicking in another field.
There are several types of triggers. The following table describes their behaviors.
| Type | Example format | Description |
|---|---|---|
| manual | (optional) 3 | Use GO to fade in next cue.
Optional: Fade cue in after 3 GO presses. The default is 1. |
| follow | 5s | Wait until the previous cue is faded in, then wait 5 seconds before starting the next cue. |
| wait | 5s | Wait time countdown starts when the wait or follow of the previous cue is completed. In other words, the cue will wait 5 seconds after the prior cue has started, rather than waiting for it to finish. |
| timecode | 00:26:05 | Waits for the DMXControl to be given an external timecode signal equal to 00:26:05. |
| rtc | 13:00:00 | Real time clock. Fade in a cue at the specified time of 1 pm. |
| beat | (optional) 3 | This requires more settings. See the paragraph below.
Optional: Fade in cue after 3 beats. The default is 1. |
If you type an incorrect format into the trigger value field, you will get some hints about the expected input syntax. See the example for the "follow" type.
 |
Type in combined time information without "blank" characters, e.g. 1m20s |
Here is the example for the real time clock selection.
Currently only the time code from Digital Enlightenment Mediacenter [1] is supported. Support of other time codes will follow.
Use of beat trigger
A Beat Trigger is a trigger based on the main rhythm of the music. It may be manually set, or automatically generated by DMXControl as it analyzes an audio signal and looks for peak transients.
If you want to have your scenes beat controlled, you need to select the source for the trigger beat .
| |
In the Trigger field you can specify after how many beat signals the next cue is called |
|
| Picture 4: Example for beattrigger |
Now you have to inform the Cue List which source of the beat signal should be used (manual beat/audioanalyzer....)
Therefore you have to assign an input in the Input Assignment via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).
|
| Picture 5: Input Assignment |
Summary
The following figure shows the dependencies and capabilities of mixing several trigger types:
- Each cue has its delay-time (before the fade-in start) - delay1 to delay3
- Cue2 has a follow-trigger of 1s. It starts 1s after the fade-in of the previous cue is completed
- Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the follow of the previous scene has expired
- Cue4 also has a wait-trigger (1s). So it will wait for 1s after the wait (0s) of the previous scene has expired.
Exercises
- Test a mix of "follow" and "wait" triggers in one scene list
- Use a tool providing timecodes (DE MediaCenter) and test a scenelist that is completely based on time codes
__NOTITLE__
| |||||||||||||
