The illustrations may differ in some details from the original. Subject to change without prior notice.
Copyright
©
2016,2017 by Dynamic Projection Institute GmbH. All Rights Reserved. http://www.dynamicprojection.com - MDC_QSG - Version 1.0.8- Page 23
Copyright
©
2016,2017 by Dynamic Projection Institute GmbH. All Rights Reserved. http://www.dynamicprojection.com - MDC_QSG - Version 1.0.8 - Page PB
9. Automatisation programming
The MDC automatisation backend is one of the most powerful ways to control a MDC show. Basically it works like a
sequencer that sends commands to the MDC program, telling it what to do next. Before you start with automatisation
we strongly recommend that you get familiar with the MDC concept of Presets. To do so please watch one of our
tutorials. Below you will find a short explaination what Presets are.
•
A preset is a container storing the values of different states (timeline).
•
Every value has transition/change times (map, audio, dmx,media)
Every Preset in the MDC program has four fade times:
•
Map Fade Time
•
Media change offset time
•
Audio Fade Time
•
DMX Fade Time
The illustration below when the timing starts and when the preset is finished with loading.
When calling presets one after the other or in parallel you have to consider that a value can only change to one
specific target value over time. So calling two presets which overlap in a value at the same time will cause unecpected
behaviour - ofcourse two presets can change the DMX values but not the same channels!
In the case above the calling sequence of the Presets would be:
1.
Call Preset#1
2.
Wait 2 seconds
3.
Call Preset#6
4.
Wait 7 seconds
5.
Call Preset#2
6.
Wait 4 seconds
7.
Return to the beginning
