Lesson 11 Tut3

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

{{{Pagetitle}}}

Lesson 10 Lesson 12 table of content Lesson 1: Installation and configuration Lesson 2: The Panel concept of DMXControl 3 GUI Lesson 3: The Project Explorer Lesson 4: The Stage view Lesson 5: Device properties and its control Lesson 6: Configuration of output plugins Lesson 7: Summary and some more details of setup Lesson 8: Cues and cue lists Lesson 9: Fanning, Chasers and other effects Lesson 10: The Programmer view Lesson 11: Triggers in cue lists Lesson 12: Edit of cues and cue lists Lesson 13: Presets Lesson 14: Summary and details - Programming Lesson 15: Executors and use of cue lists Lesson 16: Softdesk Lesson 17: Audio analyser Lesson 18: Multimedia Support Lesson 19: Other DMX Clients Lesson 20: Create new device definitions Lesson 21: Summary and details for Execution Lesson 22: Input Assignment Lesson 23: Create a RGB Matrix Lesson 24: Transfer DMX values via ArtNet to DMXControl 2 Appendix 1: Commands and Shortcuts Appendix 2: Tips for Testing and behaviot in error case

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: Triggers 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.

Picture 1: Accepted triggers

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.

Type in combined time information without "blank" characters, e.g. 1m20s

If you type an incorrect format into the trigger value field, you will get some hints about the expected input syntax. See the example below for the "follow" type.

Picture 2: View of Trigger Value help context

Below is the example for the real time clock selection.

Picture 3: View of Trigger Value help context

Currently only the time code from Digital Enlightenment Mediacenter [1] is supported. Support for other time codes will be created in the future.

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:

Picture 6: Overview of possible trigger functions

• Each cue has its own delay-time (before the fade-in start) - delay1 to delay3
• Cue2 has a follow-trigger of 1s. It starts 1 second after the fade-in of the previous cue is completed
• Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the previous scene is finished.
• Cue4 also has a wait-trigger (1s). So it will wait for 1s after the wait (0s) of the previous scene is finished.

Exercises

• Test a mix of "follow" and "wait" triggers in one scene list

• Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes

Lesson 10 Lesson 12 table of content Lesson 1: Installation and configuration Lesson 2: The Panel concept of DMXControl 3 GUI Lesson 3: The Project Explorer Lesson 4: The Stage view Lesson 5: Device properties and its control Lesson 6: Configuration of output plugins Lesson 7: Summary and some more details of setup Lesson 8: Cues and cue lists Lesson 9: Fanning, Chasers and other effects Lesson 10: The Programmer view Lesson 11: Triggers in cue lists Lesson 12: Edit of cues and cue lists Lesson 13: Presets Lesson 14: Summary and details - Programming Lesson 15: Executors and use of cue lists Lesson 16: Softdesk Lesson 17: Audio analyser Lesson 18: Multimedia Support Lesson 19: Other DMX Clients Lesson 20: Create new device definitions Lesson 21: Summary and details for Execution Lesson 22: Input Assignment Lesson 23: Create a RGB Matrix Lesson 24: Transfer DMX values via ArtNet to DMXControl 2 Appendix 1: Commands and Shortcuts Appendix 2: Tips for Testing and behaviot in error case