diff --git a/gdtf-spec.md b/gdtf-spec.md index 8ac543f..e39b281 100644 --- a/gdtf-spec.md +++ b/gdtf-spec.md @@ -165,6 +165,8 @@ all firmware revisions of the device. ./models/svg_side/yoke.svg ./models/svg_front/base.svg ./models/svg_front/yoke.svg +./photometric/lamp1.ies +./photometric/lamp1.ldt ``` @@ -1386,6 +1388,7 @@ the Beam are specified in [table 41](#user-content-table-41 ). | BeamType | [Enum](#user-content-attrtype-enum ) | Beam Type; Specified values: "Wash", "Spot", "None", "Rectangle", "PC", "Fresnel", "Glow". Default value "Wash" | ColorRenderingIndex | [Uint](#user-content-attrtype-uint ) | The CRI according to TM-30 is a quantitative measure of the ability of the light source showing the object color naturally as it does as daylight reference. Size 1 byte. Default value 100. | | EmitterSpectrum | [Node](#user-content-attrtype-node ) | Optional link to emitter in the physical description; use this to define the white light source of a subtractive color mixing system or the color for the beam when no color mixing is defined. Starting point: Emitter Collect; Default spectrum is a Black-Body with the defined ColorTemperature. | +| Photometric | [Resource](#user-content-attrtype-resource ) | Optional. File name without extension and without subfolder containing description of the IES or EULUMDAT file in the subfolder `./photometric/`. | @@ -1582,6 +1585,7 @@ for these geometries. | Position | [Matrix](#user-content-attrtype-matrix ) | Relative position of geometry; Default value: Identity Matrix | | Geometry | [Name](#user-content-attrtype-name ) | Name of the referenced geometry. Only top level geometries are allowed to be referenced. | | Model | [Name](#user-content-attrtype-name ) | Optional. Link to the corresponding model. The model only replaces the model of the parent of the referenced geometry. The models of the children of the referenced geometry are not affected. The starting point is Models Collect. If model is not set, the model is taken from the referenced geometry. | +| Photometric | [Resource](#user-content-attrtype-resource ) | Optional. File name without extension and without subfolder containing description of the IES or EULUMDAT file in the subfolder `./photometric/`. The Photometric only replaces the Photometric of the parent of the referenced geometry. The Photometric of the children of the referenced geometry are not affected. The starting point is Models Collect. If Photometric is not set, the Photometric is taken from the referenced geometry. | @@ -1940,6 +1944,8 @@ currently defined XML attributes of channel function are specified in | Min | [Float](#user-content-attrtype-float ) | Minimum Physical Value that will be used for the DMX Profile. Default: Value from PhysicalFrom | | Max | [Float](#user-content-attrtype-float ) | Maximum Physical Value that will be used for the DMX Profile. Default: Value from PhysicalTo | | CustomName | [String](#user-content-attrtype-string ) | Custom Name that can he used do adress this channel function with other command based protocols like OSC. Default: Node Name of the Channel function Example: Head_Dimmer.Dimmer.Dimmer | +| PhotometricFrom | [Resource](#user-content-attrtype-resource ) | Optional. IES or LDT file name without extension containing the spectral data for the start for the Active Channel Function for all Beams of the fixture. | +| PhotometricTo | [Resource](#user-content-attrtype-resource ) | Optional. IES or LDT file name without extension containing the spectral data for the end for the Active Channel Function for all Beams of the fixture. | @@ -2008,6 +2014,29 @@ are specified in [table 62](#user-content-table-62 ). The subchannel set does not have any children. +###### PhotometricSet + +This section defines the PhotometricSets of the channel function (XML node +). The currently defined XML attributes of the PhotometricSet +are specified in [table 62](#user-content-table-62 ). + +
+ +#### Table 62. *PhotometricSet Attributes* + +| XML Attribute Name | Value Type | Description | +|----|----|----| +| Beam | [Name](#user-content-attrtype-name ) | Optional link to the Beam Geometry this is for | +| DMXFrom | [DMXValue](#user-content-attrtype-dmxvalue ) | Start DMX value; The end DMX value is calculated as a DMXFrom of the next PhotometricSet – 1 or the maximum value of the current channel function; Default value: 0/1 | +| PhotometricFrom | [Node](#user-content-attrtype-node) | Photometric start value to start interpolating to. function. | +| PhotometricTo | [Node](#user-content-attrtype-node) | Photometric end value. function. | + + +
+ +The PhotometricSet does not have any children. + + #### Relation Collect ##### General diff --git a/proposal/light-distribution-proposal/proposal.md b/proposal/light-distribution-proposal/proposal.md new file mode 100644 index 0000000..f207a5c --- /dev/null +++ b/proposal/light-distribution-proposal/proposal.md @@ -0,0 +1,220 @@ +# Support for more Photometric Data in MVR and GDTF + +## Linked Issue + + +# Problem + +We want to add the option to define the light distribution for fixtures inside the beam of the fixture. In simple works, this file define how even the light inside a beam is distributed. + +# Proposal + + +## GDTF + +### New Attribute Photometric + +We will add attribute `Photometric` to the Beam Geometry. This defines the default light distribution for the fixture. +We will add attribute `Photometric` to the Reference Geometry. This overwrites the default light distribution for the linked Beam. +Inside the `ChannelFunction` and the `SubChannelSet` we also will add this this attribute, so that the fixture can change the behavior depending on the current status of the fixture. This will also define a range. + +When the `Photometric` is an attribute of the `ChannelFunction` it applies to all Beams, while when it is in a child node you can specify the beam it is for. + +> **Note** +> We are currently discussing how `Photometric` can be defined as child of a `ChannelFunction` + +The rules are the following: +- When a Beam does not have `Photometric`, it will not be affected by any `Photometric` definition in the file (Allow LED rings to have no photometric while the main light source have this and you still not need to use the `SubChannelSets`) +- Only one DMX Channel can have `Photometric` links inside their `ChannelFunction` or `SubChannelSet`. + + +Example Simple Fixture: + +``` xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` +## Multi Beam defining + +When a device has multiple beams, that need different Photometric files, we need to assign the files per Beam. This could be done either as a child of the `ChannelFunction`, or as a child of the `ChannelSet`. + +When using the `ChannelSet`, we can use the DMX ranges from the `ChannelSet`. But we are also forced to use existing structure of `ChannelSet` or even create `ChannelSet` just for this propose. +When using the `ChannelFunction`, we need to also define a DMX range here. The requirements for the DMX range for channel set also applies for the `` node. + +#### Option A: Use Children of the Channel Set to make multi Beam assign + +Example Two Beam Fixture: + +``` xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +#### Option B: Use Children of the Channel Function to make multi Beam assign + + +``` xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +#### Challenges +- How do we handle multiple beam in one fixture + - Multi LED Strip Light (Challenge is how you measure device) + - Multi LED Wash Light (You want to measure all at once, but represent the beam as one) + - LED Ring and normal beam (You only need the beam as IES file) + - Multi head fixtures (You need for each an individual beam, and it also needs to change) + +- Only one IES file (or and interpolation between two IES files) can be active. This is challenging when multiple Attributes have effects on the light output. + +- Do we need to add measurement instruction to the GDTF spec or only reference the IES spec. + - You measure devices in such a distance that the actual shape of the device has no influence on the measurement. For strip lights, this means a big distance. Not all can measure strip lights at such distance. The distance that IES recommends is 7x the beam diameter. + + +## MVR + +Currently there will be no impact on the MVR. + +