Basic rules (DDF-Syntax) DMXC3: Difference between revisions

From English DMXC-Wiki
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Chaptertitle |Version=DMXControl 3.2.0}}
{{Chaptertitle|Version=DMXControl 3.2.0}}


{{DMXC3 Manual-Navigation DDF
{{DMXC3 Manual-Navigation DDF
|backLink = Function elements (DDF-Syntax) DMXC3
|backLink = Function elements (DDF-Syntax) DMXC3
|backText = Function Elements
|backText = Function elements
|forwardLink = Intensity (DDF-Syntax) DMXC3
|forwardLink = Intensity (DDF-Syntax) DMXC3
|forwardText = Intensity
|forwardText = Intensity
}}
}}


= Basic Rules for Creating a DDF =
 
== General Rules ==
= Basic rules for creating a DDF =
== General rules ==
The following basic rules should be observed when creating DDFs:
The following basic rules should be observed when creating DDFs:
* DMX channels are always counted starting from 0 in the DDFs. Therefore, for an LED PAR with 5 DMX channels in the DDF, the DMX channels are also listed as 0 to 4, while the functions in the DMX channel are labeled from 1 to 5 in the user manual.
* DMX channels are always counted starting from {{Manual Value | DMX channel | 0}} in the DDFs. Therefore, for an LED PAR with {{Manual Value || 5}} DMX channels in the DDF, the DMX channels are also listed as {{Manual Value | DMX channel | 0}} to {{Manual Value | DMX channel | 4}}, while the functions in the DMX channel are labeled from {{Manual Value | DMX channel | 1}} to {{Manual Value | DMX channel | 5}} in the user manual.
* The designation of the devices is limited only to the designation itself, as it appears on the cover of the manual. Additional information such as the DMX mode/channel assignment or any other comments should not be included there.
* The designation of the devices is limited only to the designation itself, as it appears on the cover of the manual. Additional information such as the DMX mode / channel assignment or any other comments should not be included there.
* Values for strobe frequency, pan and tilt pan ranges, gobo rotation speed, etc. should be entered without units. The usual units for these values are listed in the table below.
* Values for strobe frequency, pan and tilt pan ranges, gobo rotation speed, etc. should be entered without units. The usual units for these values are listed in the table below.
* The associated DMX values, for example for gobo rotation speed, should be entered so that the speeds increase clockwise and counterclockwise from the gobo rotation stop point.
* The associated DMX values, for example for gobo rotation speed, should be entered so that the speeds increase clockwise and counterclockwise from the gobo rotation stop point.
Line 18: Line 19:
* DDFs are usually written in English to remain universally applicable and usable for all language versions of DMXControl 3. In addition, the default language of DMXControl 3 is English.
* DDFs are usually written in English to remain universally applicable and usable for all language versions of DMXControl 3. In addition, the default language of DMXControl 3 is English.


== Expected Units for Values ==
== Expected units for values ==
The following table provides a general overview of the units in which the HAL expects values for the listed functions. These are the values for the <code>minval</code> and <code>maxval</code> attributes when a <code>range</code> element is used in a function (gobo wheel, strobe, zoom, etc.) to describe the value range of the function on the specified subset of the DMX channel. The permissible values for the <code>minval</code> and <code>maxval</code> attributes can be found in the description of each function.
The following table provides a general overview of the units in which the HAL expects values for the listed functions. These are the values for the <code>minval</code> and <code>maxval</code> attributes when a <code>range</code> element is used in a function (gobo wheel, strobe, zoom, etc.) to describe the value range of the function on the specified subset of the DMX channel. The permissible values for the <code>minval</code> and <code>maxval</code> attributes can be found in the description of each function.
{| class="wikitable toptextcells"
{| class="wikitable toptextcells"
Line 50: Line 51:
|}
|}


=Troubleshooting=
= Troubleshooting =
These are common errors that prevent a DDF from being added to a project:
These are common errors that prevent a DDF from being added to a project:
* No pan range specified in the <code>range</code> attribute for pan and tilt.
* No pan range specified in the <code>range</code> attribute for pan and tilt.
* No value specified for <code>minval</code> and <code>maxval</code> for strobe.
* No value specified for <code>minval</code> and <code>maxval</code> for strobe.
* The <code>model</code> tag is still misspelled.
* The <code>model</code> tag is still misspelled.
{{Manual Box | en | Important | If an older project in particular cannot be loaded, this can always be traced back to DDFs. Each time a project is loaded, DDFs are automatically checked for any logic errors. If this is not completed successfully, the loading of the project is aborted. It can help here to load the DDFs from this project once separately in an empty project and correct them if necessary.}}


[[de:Grundregeln (DDF-Syntax) DMXC3]]
[[Category: DDF DMXControl 3]]
[[Category: DDF DMXControl 3]]

Latest revision as of 13:40, 10 February 2024

Books.png Basic rules (DDF-Syntax) DMXC3 Article describes
DMXControl 3.2.0
Arrow back.png Function elements
Intensity Arrow forw.png
Table of Contents
Part 1: Basics
Part 2: Functions
Part 3: Procedures
Part 4: Examples


Basic rules for creating a DDF

General rules

The following basic rules should be observed when creating DDFs:

  • DMX channels are always counted starting from 0 in the DDFs. Therefore, for an LED PAR with 5 DMX channels in the DDF, the DMX channels are also listed as 0 to 4, while the functions in the DMX channel are labeled from 1 to 5 in the user manual.
  • The designation of the devices is limited only to the designation itself, as it appears on the cover of the manual. Additional information such as the DMX mode / channel assignment or any other comments should not be included there.
  • Values for strobe frequency, pan and tilt pan ranges, gobo rotation speed, etc. should be entered without units. The usual units for these values are listed in the table below.
  • The associated DMX values, for example for gobo rotation speed, should be entered so that the speeds increase clockwise and counterclockwise from the gobo rotation stop point.
  • Images for the device icon as well as for the gobos should be stored in a resolution of 128 x 128 pixels and as *.png files in the DDF.
  • DDFs are usually written in English to remain universally applicable and usable for all language versions of DMXControl 3. In addition, the default language of DMXControl 3 is English.

Expected units for values

The following table provides a general overview of the units in which the HAL expects values for the listed functions. These are the values for the minval and maxval attributes when a range element is used in a function (gobo wheel, strobe, zoom, etc.) to describe the value range of the function on the specified subset of the DMX channel. The permissible values for the minval and maxval attributes can be found in the description of each function.

Value Unit Usage
Speed 1/s

(Revolutions per second)

Gobo rotation, prism rotation, continuous rotation of the color wheel, continuous rotation of the gobo wheel
Color temperature K

(Kelvin)

Color temperature
Frequency Hz

(Hertz)

Strobe frequency, gobo shake speed
Angle °

(Degrees)

Pan and tilt pan range, gobo indexing, prism indexing, zoom
Dimensionless %

(Percent)

Dimmer, Iris

Troubleshooting

These are common errors that prevent a DDF from being added to a project:

  • No pan range specified in the range attribute for pan and tilt.
  • No value specified for minval and maxval for strobe.
  • The model tag is still misspelled.
Important hint If an older project in particular cannot be loaded, this can always be traced back to DDFs. Each time a project is loaded, DDFs are automatically checked for any logic errors. If this is not completed successfully, the loading of the project is aborted. It can help here to load the DDFs from this project once separately in an empty project and correct them if necessary.