You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: proposal/light-distribution-proposal/proposal.md
+40-40Lines changed: 40 additions & 40 deletions
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Support for Spectral Distribution in MVR and GDTF
1
+
# Support for more Photometric Data in MVR and GDTF
2
2
3
3
## Linked Issue
4
4
@@ -12,20 +12,20 @@ We want to add the option to define the light distribution for fixtures inside t
12
12
13
13
## GDTF
14
14
15
-
### New Attribute LightDistribution
15
+
### New Attribute Photometric
16
16
17
-
We will add attribute `LightDistribution` to the Beam Geometry. This defines the default light distribution for the fixture.
18
-
We will add attribute `LightDistribution` to the Reference Geometry. This overwrites the default light distribution for the linked Beam.
17
+
We will add attribute `Photometric` to the Beam Geometry. This defines the default light distribution for the fixture.
18
+
We will add attribute `Photometric` to the Reference Geometry. This overwrites the default light distribution for the linked Beam.
19
19
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.
20
20
21
-
When the `LightDistribution` 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.
21
+
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.
22
22
23
23
> **Note**
24
-
> We are currently discussing how `LightDistribution` can be defined as child of a `ChannelFunction`
24
+
> We are currently discussing how `Photometric` can be defined as child of a `ChannelFunction`
25
25
26
26
The rules are the following:
27
-
- When a Beam does not have `LightDistribution`, it will not be affected by any `LightDistribution` definition in the file (Allow LED rings to have no spectral data while the main light source have this and you still not need to use the `SubChannelSets`)
28
-
- Only one DMX Channel can have `LightDistribution` links inside their `ChannelFunction` or `SubChannelSet`.
27
+
- 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 spectral data while the main light source have this and you still not need to use the `SubChannelSets`)
28
+
- Only one DMX Channel can have `Photometric` links inside their `ChannelFunction` or `SubChannelSet`.
When a device has multiple beams, that need different Light Distribution 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`.
68
+
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`.
69
69
70
70
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.
71
-
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 `<LightDistribution>` node.
71
+
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 `<Photometric>` node.
72
72
73
73
#### Option A: Use Children of the Channel Set to make multi Beam assign
0 commit comments