Lesson 11 Tut3 - Revision history

Jnoetzel at 18:56, 2 March 2025

2025-03-02T18:56:33Z

← Older revision		Revision as of 20:56, 2 March 2025
Line 37:		Line 37:
	\|}		\|}

	{{~~BoxHint~~		{{Manual Box \| en \| Hint \| Type in combined time information without "blank" characters, e.g. 1m20s
	\|~~Text=~~ Type in combined time information without "blank" characters, e.g. 1m20s
	}}		}}

Line 54:		Line 53:
	If you want to have your scenes beat controlled, you need to select the source for the trigger '''beat''' .		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		{{Manual Box \| en \| Hint \| In the '''Trigger''' field you can specify after how many beat signals the next cue is called
	}}		}}
	{{Picture_with_subtitle \|Beattrigger.PNG\|4\|Example for beattrigger\|center}}		{{Picture_with_subtitle \|Beattrigger.PNG\|4\|Example for beattrigger\|center}}

Skistner at 10:59, 2 March 2025

2025-03-02T10:59:45Z

← Older revision		Revision as of 12:59, 2 March 2025
Line 1:		Line 1:
	{{Manual Header		{{Manual Header
	\| Type = DMXC3 Tutorials		\| Type = DMXC3 Tutorials
	\| Version = 3.0		\| Version = 3.0.0
	\| LinkBackwards = Lesson_10_Tut3		\| LinkBackwards = Lesson_10_Tut3
	\| TextBackwards = Lesson 10		\| TextBackwards = Lesson 10
Line 76:		Line 76:
	* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes		* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes

	~~{{NavigationTop-Tut3~~
	~~\| LinkBackwards = Lesson_10_Tut3~~
	~~\| TextBackwards = Lesson 10~~
	~~\| LinkForwards = Lesson_12_Tut3~~
	~~\| TextForwards = Lesson 12~~
	}}
	[[de:Lektion_11_Tut3]]		[[de:Lektion_11_Tut3]]
	[[Category: Tutorials DMXControl 3]]		[[Category: Tutorials DMXControl 3]]

Jnoetzel at 10:46, 2 March 2025

2025-03-02T10:46:57Z

← Older revision		Revision as of 12:46, 2 March 2025
Line 1:		Line 1:
	{{~~Maintitle~~		{{Manual Header
	\| ~~logo~~ = ~~Im-aim.png~~		\| Type = DMXC3 Tutorials
	\| ~~maintitle~~ = ~~First Steps: {{PAGENAME}}~~		\| Version = 3.0
	}}
	~~{{NavigationTop-Tut3~~
	\| LinkBackwards = Lesson_10_Tut3		\| LinkBackwards = Lesson_10_Tut3
	\| TextBackwards = Lesson 10		\| TextBackwards = Lesson 10

JayJay at 21:41, 15 May 2013

2013-05-15T21:41:33Z

← Older revision		Revision as of 23:41, 15 May 2013
Line 18:		Line 18:

	There are several types of triggers. The following table describes their behaviors.		There are several types of triggers. The following table describes their behaviors.
			{{Picture_with_subtitle\|DMXC3L11 trigger.jpg\|1\|Accepted triggers\|center}}
	~~[[File:~~DMXC3L11 trigger.jpg]]

	{\| class="wikitable"		{\| class="wikitable"
Line 45:		Line 44:

	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.		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_with_subtitle\|DMXC3L11 triggerhelpcontextfollow.JPG\|2\|View of Trigger Value help context\|center}}
	~~[[File:~~DMXC3L11 triggerhelpcontextfollow.JPG]]

	Below is the example for the real time clock selection.		Below is the example for the real time clock selection.
			{{Picture_with_subtitle\|DMXC3L11 triggerhelpcontext.JPG\|3\|View of Trigger Value help context\|center}}
	~~[[File:~~DMXC3L11 triggerhelpcontext.JPG]]

	Currently only the time code from Digital Enlightenment Mediacenter [http://www.digital-enlightenment.de/mediacenter.htm] is supported. Support for other time codes will be created in the future.		Currently only the time code from Digital Enlightenment Mediacenter [http://www.digital-enlightenment.de/mediacenter.htm] is supported. Support for other time codes will be created in the future.
Line 61:		Line 58:
	{{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
	}}		}}

	{{Picture_with_subtitle \|Beattrigger.PNG\|4\|Example for beattrigger\|center}}		{{Picture_with_subtitle \|Beattrigger.PNG\|4\|Example for beattrigger\|center}}

	Now you have to inform the '''Cue List''' which source of the beat signal should be used (manual beat/audioanalyzer....)		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 [[Lesson_22_Tut3\|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).		Therefore you have to assign an input in the [[Lesson_22_Tut3\|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).

	{{Picture_with_subtitle \|DMXC3_L11_InputassignmentBeat.png\|5\|Input Assignment\|center}}		{{Picture_with_subtitle \|DMXC3_L11_InputassignmentBeat.png\|5\|Input Assignment\|center}}

	==Summary==		==Summary==
	The following figure shows the dependencies and capabilities of mixing several trigger types:		The following figure shows the dependencies and capabilities of mixing several trigger types:
			{{Picture_with_subtitle\|DMXC3L11 SlideDMXC3Trigger.jpg\|6\|Overview of possible trigger functions\|center\|600px}}
	~~[[File:~~DMXC3L11 SlideDMXC3Trigger.jpg\|600px]]

	* Each cue has its own delay-time (before the fade-in start) - delay1 to delay3		* Each cue has its own delay-time (before the fade-in start) - delay1 to delay3

JayJay at 13:52, 14 May 2013

2013-05-14T13:52:05Z

← Older revision		Revision as of 15:52, 14 May 2013
Line 18:		Line 18:

	There are several types of triggers. The following table describes their behaviors.		There are several types of triggers. The following table describes their behaviors.


	[[File:DMXC3L11 trigger.jpg]]		[[File:DMXC3L11 trigger.jpg]]
Line 40:		Line 39:
	Optional: Fade in cue after 3 beats. The default is 1.		Optional: Fade in cue after 3 beats. The default is 1.
	\|}		\|}


	{{BoxHint		{{BoxHint
Line 57:		Line 55:

	===Use of beat trigger===		===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.		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.

Line 73:		Line 70:

	==Summary==		==Summary==

	The following figure shows the dependencies and capabilities of mixing several trigger types:		The following figure shows the dependencies and capabilities of mixing several trigger types:

Line 82:		Line 78:
	* Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the previous scene is finished.		* 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.		* Cue4 also has a wait-trigger (1s). So it will wait for 1s after the wait (0s) of the previous scene is finished.


	==Exercises==		==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
			<br>
	* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes		* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes

	~~__NOTOC__~~
	~~__NOTITLE__~~


	{{NavigationTop-Tut3		{{NavigationTop-Tut3
Line 98:		Line 90:
	\| TextForwards = Lesson 12		\| TextForwards = Lesson 12
	}}		}}

	~~[[category:DMXControl 3]]~~


	[[de:Lektion_11_Tut3]]		[[de:Lektion_11_Tut3]]
			[[Category: Tutorials DMXControl 3]]

Jmintenbeck at 13:36, 17 April 2013

2013-04-17T13:36:33Z

← Older revision		Revision as of 15:36, 17 April 2013
Line 87:		Line 87:
	* 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 time codes, such as MediaCenter, and test a scene list that is completely based on time codes		* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes


	~~[[de:Lektion_11_Tut3]]~~
	~~[[en:Lesson_11_Tut3]]~~

	__NOTOC__		__NOTOC__
Line 104:		Line 100:

	[[category:DMXControl 3]]		[[category:DMXControl 3]]


			[[de:Lektion_11_Tut3]]

Mminini at 23:03, 15 March 2013

2013-03-15T23:03:45Z

← Older revision		Revision as of 01:03, 16 March 2013
Line 12:		Line 12:
	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.		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 ==		==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.		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.

Line 41:		Line 41:
	\|}		\|}


	~~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
	\|Text= Type in combined time information without "blank" characters, e.g. 1m20s		\|Text= 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.

	[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]		[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

	~~Here~~ is the example for the real time clock selection.		Below is the example for the real time clock selection.

	[[File:DMXC3L11 triggerhelpcontext.JPG]]		[[File:DMXC3L11 triggerhelpcontext.JPG]]

	Currently only the time code from Digital Enlightenment Mediacenter [http://www.digital-enlightenment.de/mediacenter.htm] is supported. Support of other time codes will ~~follow~~.		Currently only the time code from Digital Enlightenment Mediacenter [http://www.digital-enlightenment.de/mediacenter.htm] is supported. Support for other time codes will be created in the future.

	===Use of beat trigger===		===Use of beat trigger===
Line 61:		Line 61:

	If you want to have your scenes beat controlled, you need to select the source for the trigger '''beat''' .		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 77:		Line 78:
	[[File:DMXC3L11 SlideDMXC3Trigger.jpg\|600px]]		[[File:DMXC3L11 SlideDMXC3Trigger.jpg\|600px]]

	* Each cue has its delay-time (before the fade-in start) - delay1 to delay3		* Each cue has its own 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		* 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 follow of~~ the previous scene ~~has expired~~		* 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 ~~has expired~~.		* Cue4 also has a wait-trigger (1s). So it will wait for 1s after the wait (0s) of the previous scene is finished.


	==Exercises==		==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 time codes		* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes

Mminini at 22:53, 15 March 2013

2013-03-15T22:53:51Z

← Older revision		Revision as of 00:53, 16 March 2013
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 ~~learnt~~ how to create cues and scene lists. Now we are ~~familar~~ with most of the attributes of the scene list ~~but some~~ more explanation about ~~the~~ trigger is ~~nessecary~~. The default trigger is "follow". ~~That~~ means the next cue will be started after the previous one ~~is faded~~ in.

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

	~~Besides of '''follow''' there~~ are ~~some other~~ types of triggers. The following table ~~informs you about~~ their ~~behaviours~~.		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 \|\| ~~use~~ GO to fade in next cue		\| manual \|\| (optional) 3 \|\| Use GO to fade in next cue.
	~~optional~~: ~~fade~~ in ~~cue~~ after 3 GO presses, default is 1		Optional: Fade cue in after 3 GO presses. The default is 1.
	\|-		\|-
	\| follow \|\| 5s \|\| ~~wait~~ until the previous cue is faded in, then the ~~countdown is started~~		\| 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 wait or follow of previous cue is completed		\| 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 \|\| ~~expects~~ external timecode ~~information~~		\| 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 a specified time		\| rtc \|\| 13:00:00 \|\| Real time clock. Fade in a cue at the specified time of 1 pm.
	\|-		\|-
	\| beat \|\| (optional) 3 \|\| ~~you have to do some~~ more settings~~, see next~~ paragraph below!		\| beat \|\| (optional) 3 \|\| This requires more settings. See the paragraph below.
	~~optional~~: ~~fade~~ in cue after 3 beats, default is 1		Optional: Fade in cue after 3 beats. The default is 1.
	\|}		\|}


	~~In case~~ you type ~~a wrong~~ format into the '''trigger value''' field you will get some hints about the expected input syntax. See the example for the "follow" type.		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 ~~realtimecode~~ selection.		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 ~~controled~~, you need to select the trigger '''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 ~~dependencys~~ and ~~capabilitys~~ of mixing several trigger types:		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:


	==~~Excercise~~==		==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 ~~timecodes~~		* Use a tool providing timecodes (DE MediaCenter) and test a scenelist that is completely based on time codes


	~~==Certificate==~~
	~~I have understood the topics of this lecture and want to continue with next course:~~
	~~Lesson 12~~

	[[de:Lektion_11_Tut3]]		[[de:Lektion_11_Tut3]]

Steiny at 20:06, 22 January 2013

2013-01-22T20:06:46Z

← Older revision		Revision as of 22:06, 22 January 2013
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

Vrystyle: /* Use of beat trigger */ minor fixes

2013-01-22T11:17:27Z

Use of beat trigger: minor fixes

← Older revision		Revision as of 13:17, 22 January 2013
Line 63:		Line 63:
	}}		}}

	{{~~Bild_mit_Unterschrift~~ \|Beattrigger.PNG\|4\|Example for beattrigger\|center}}		{{Picture_with_subtitle \|Beattrigger.PNG\|4\|Example for beattrigger\|center}}

	Now you have to inform the '''Cue List''' which source of the beat signal should be used (manual beat/audioanalyzer....)		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 [[Lesson_22_Tut3\|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).		Therefore you have to assign an input in the [[Lesson_22_Tut3\|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).

	{{~~Bild_mit_Unterschrift~~ \|DMXC3_L11_InputassignmentBeat.png\|5\|Input Assignment\|center}}		{{Picture_with_subtitle \|DMXC3_L11_InputassignmentBeat.png\|5\|Input Assignment\|center}}

	==Summary==		==Summary==