HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3

	Article describe DMXControl DMXControl 3.2.2 Stand: 03.03.2025	HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3
Table of contents A Autoprepare B Bedienoberfläche (GUI) Blackout Bühnenansicht (Stage View) C Chat D Dateien im Projekt (Project Files) DDFs im Projekt aktualisieren (Update Project DDFs) DMX-Schnittstellen (DMX-Interfaces) Device Manager (Add Device Dialog) DDF Library DMX-In DMX-Out-Zuordnung (DMX-In DMX-Out-Mapping) E Effekte und Filter (Effects and Filters) Effektvisualisierung (Effect Visualizer) Einfrieren (Freeze) Eingangszuweisung (Input Assignment) Executor Executor Seite (Executor Page) F Fanning Farbliste (Color List) G Gerät (Device) Gerätegruppe (Device Group) Gerätesteuerung (Device Control) Gobo-Ähnlichkeiten (Gobo Affinity) Goboliste (Gobo List) Group Handling H Hardware Abstraction Layer (HAL) Hauptschalter (Main Switch) Hervorheben (Highlight) HTP-, LTP- und LoTP-Mischung (HTP-, LTP- and LoTP-Mixing) K Kanalübersicht (Channel Overview) Kernel (Server) L Lastmanagement (Electricity) Launcher M Macroboard Master Matrix MIDI-Verwaltung (MIDI Manager) N Netzwerkfunktionalitäten O Ordnungsliste (Item List) P Panel-Konzept Patching Plugin-Verwaltung (Plugin Manager) Positionsliste (Position List) Preset Programm- und Projekteinstellungen (Application und Project Settings) Programmer Programmer Filter Projektverwaltung (Project Administration) Projektexplorer (Project Explorer) Projektaufgaben (Project ToDos) Protokolldateien (Log Files) R Radix Relative und absolute Werte (Absolute and Relative Values) S Softdesk Softdesk Designer Steuerungsfenster (Control Panel) Szenenliste (Cuelist) Szenenlistegruppe (Cuelist Group) Szenenzeitkonfiguration (Cue Timing Editor) T Timecode Player Tracking U Umbra

The HTP, LTP, and LoTP Mixing function determines how multiple Cuelists interact when controlling the dimmer (i.e., the intensity) of the same Device or Device Group.

Overview

The HTP, LTP, and LoTP mixing follows a predefined schema:

• In HTP (Highest Takes Precedence) mixing, the highest value set by any active cuelist is output. HTP mixing defines the lower boundary, meaning "the light is at least this bright." This concept is similar to the preheat function for conventional dimmers.
• In LoTP (Lowest Takes Precedence) mixing, the lowest value among all active cuelists is output—provided that no cuelist with HTP mixing is active. LoTP mixing defines the upper boundary, meaning "the light is at most this bright." LoTP cuelists can act as limiters.
• In LTP (Latest Takes Precedence) mixing, the value from the most recently started cuelist is output—if no cuelist with HTP or LoTP mixing is active.

LoTP-mixed cuelists only become "visible" when another cuelist is running concurrently. If an LoTP-mixed cuelist runs on its own, the base value of the controlled device is factored into the calculation. Since the base value for the dimmer is 0%, a standalone LoTP-mixed cuelist cannot increase the brightness.

Usage

The mixing behavior—HTP, LTP, or LoTP—can be set individually for each cuelist. Along with this setting, the following additional conditions apply:

• Priority takes precedence over mixing, especially with LTP mixing: If several LTP-mixed cuelists have a higher priority (e.g., the value "32"), the cuelist most recently started on that "priority level" will be output—unless terminated by a cuelist group.
• Relative values are excluded from HTP, LTP, and LoTP mixing. Only the priority of the cuelist applies, as explained in the article on Absolute and Relative Values.

Special Case with LoTP

In general, DMXControl 3 always fades in values from "below." If no cuelist is active, the dimmer value defaults to 0%. However, LoTP-mixed cuelists fade in from "above"—meaning from 100%. This behavior prevents sudden jumps in brightness when starting or stopping such a cuelist while other cuelists controlling the dimmer are active.