Cover the need to define particular multiple individual or combinations of fixture's physical attributes which can (also) be dynamically switched between during the operation of the device.
Example of these attributes:
CRI
Luminous Flux / Iluminance (essentially, the unit changes between spot/beam/wash). Here, let me add what frost does to the output, some people might call it Wash mode. It will redefine beam angles (see below) beam flatness (thus illuminance and luminous flux).
BeamAngle(s) (this we potentially cover by using ChannelFunction with different PhysicalFrom/PhysicalTo) and ModeDependency (0.89) part of the issue is, that these behaviours are (sometimes) linked together.
Speed - this can even have dynamic parameter, based on DMX channel value (pan/tilt speed, gobo wheel speed etc...).
perhaps LED relations also apply here
Upon popular request from visualizers, we measure and provide precise speed of rotation of gobo wheels, which is also customizable dynamically via channel.
One idea would be to allow more precise definition of the attributes (as we do for example for Emitters) and allow different definitions to be applied as needed. As if we allowed different Emitter to be used based on say ModeDep. So for example define IES for a particular beam definitions and switch between these via ModeDep.
Currently we have a separation between "logical" and "physical" world. Logical is how to control device, it is a DMX mode section. And physical is more about physical parameters of device, it is in Geometry, PhysicalDescription, Wheels and so one. It is in some places overwrites each other, like geometry axis has from and to xml attributes and pan channel function has also physical from/to. And the rules was, that geometry defines a min and max values and channel function specifies it more precisely. So in your example zoom and intensity can be also specified like this, means that beam geometry has only max zoom and only max intensity and then several zoom channel functions with mode dependencies specifies it more precisely.
Cover the need to define particular multiple individual or combinations of fixture's physical attributes which can (also) be dynamically switched between during the operation of the device.
Example of these attributes:
Upon popular request from visualizers, we measure and provide precise speed of rotation of gobo wheels, which is also customizable dynamically via channel.
One idea would be to allow more precise definition of the attributes (as we do for example for Emitters) and allow different definitions to be applied as needed. As if we allowed different Emitter to be used based on say ModeDep. So for example define IES for a particular beam definitions and switch between these via ModeDep.
Currently we have a separation between "logical" and "physical" world. Logical is how to control device, it is a DMX mode section. And physical is more about physical parameters of device, it is in Geometry, PhysicalDescription, Wheels and so one. It is in some places overwrites each other, like geometry axis has from and to xml attributes and pan channel function has also physical from/to. And the rules was, that geometry defines a min and max values and channel function specifies it more precisely. So in your example zoom and intensity can be also specified like this, means that beam geometry has only max zoom and only max intensity and then several zoom channel functions with mode dependencies specifies it more precisely.