Releases: OpenLightingProject/open-fixture-library
Schema version 11.3.0
Incompatible schema changes
None.
Backwards-compatible schema changes
- As an alternative to naming all pixel keys, one can now define pixel groups either with the keyword
allor with an object of XYZ/name constraints. See matrix structure docs and following examples:
"matrix": {
"pixelCount": [12, 1, 1],
"pixelGroups": {
"Master": "all",
"1/3": { "x": ["<=4"] },
"2/3": { "x": [">=5", "<=8"] },
"3/3": { "x": [">=9"] },
"Outer Thirds": ["1", "2", "3", "4", "9", "10", "11", "12"]
}
}"matrix": {
"pixelKeys": [
[
["A1", "B1", "C1", "C2", "B2", "A2"]
]
],
"pixelGroups": {
"A": { "name": ["^A[1-2]$"] },
"B": { "name": ["^B[1-2]$"] },
"C": { "name": ["^C[1-2]$"] }
}
}Bugfixes
None.
Schema version 11.2.0
Incompatible schema changes
None.
Backwards-compatible schema changes
- Physical's
matrixPixelssection now allows for setting only one ofdimensionsandspacing. Before this release, one had to either set both or none of them.
Bugfixes
None.
Schema version 11.1.0
Incompatible schema changes
None.
Backwards-compatible schema changes
ColorIntensitycapabilities can now have two more colors:Warm WhiteandCold White. In all existing plugins, both are mapped to a simpleWhite(which is still also usable). See #759.
Bugfixes
None.
Schema version 11.0.1
Incompatible schema changes
None.
Backwards-compatible schema changes
None.
Bugfixes
- Make speed optional for capability types
IrisEffectandFrostEffect(see #748).
Schema version 11.0.0
With this schema version, fixture wheels (color wheels, gobo wheels, animation wheels, ...) can be specified directly in the fixture like this:
"wheels": {
"Wheel name": {
"slots": [
{
"type": "Open"
},
{
"type": "Color",
"name": "Red",
"colors": ["#ff0000"]
},
{
"type": "Gobo",
"name": "Waves"
}
]
}
}In the capabilities that reference wheels slots, only the slot number has to be specified. No more having to repeat the same color name and hex string for split slots!
{
"dmxRange": [0, 10],
"type": "WheelSlot",
"wheel": "Wheel name",
"slotNumber": 1
},
{
"dmxRange": [11, 20],
"type": "WheelSlot",
"wheel": "Wheel name",
"slotNumberStart": 1,
"slotNumberEnd": 2
},
{
"dmxRange": [21, 30],
"type": "WheelSlot",
"wheel": "Wheel name",
"slotNumber": 2
},If the wheel name is the same as the channel name, the wheel property can be omitted, making the syntax even more concise.
For more information, see PR #659, the updated fixture format docs and capability type list.
Incompatible schema changes
- The capability types
ColorWheelIndex,ColorWheelRotation,GoboIndex,GoboWheelRotation,GoboStencilRotationandGoboShakehave been removed.
Backwards-compatible schema changes
- Wheels can be specified as
wheelsin the fixture object. - The capability types
WheelSlot,WheelShake,WheelSlotRotationandWheelRotationhave been added.
Bugfixes
None.
Schema version 10.0.0
Incompatible schema changes
- All DMX values (default value, highlight value, capability DMX ranges) have to be entered in the same DMX resolution (8bit, 16bit, etc.). The resolution to be used defaults to the maximum resolution, but can be decreased by setting the channel's
dmxValueResolutionproperty (see #594).
Backwards-compatible schema changes
- New
dmxValueResolutionproperty for channels allows specifying default / highlight value in a lower resolution (see the updated fine channel docs). - Default and highlight value can now be entered as a percentage (e.g.
50%), relative to the maximum DMX bounds.
Bugfixes
None.
Schema version 9.2.0
Incompatible schema changes
None.
Backwards-compatible schema changes
Bugfixes
None.
Schema version 9.1.0
Incompatible schema changes
None.
Backwards-compatible schema changes
- New possible
DMXconnectorvalue:5-pin XLR IP65for outdoor XLR cables (#579)
Bugfixes
- Reordered possible
DMXconnectorvalues
Schema version 9.0.0
Fixtures can now contain more links than just one to the manual (see #559):
- "manualURL": "https://www.manufacturer.com/fixture/manual.pdf",
+ "links": {
+ "manual": [
+ "https://www.manufacturer.com/fixture/manual.pdf",
+ "http://www.manufacturer.com/old-version/manual-with-important-information.pdf"
+ ],
+ "productPage": [
+ "https://www.manufacturer.com/products/fixture/"
+ ],
+ "video": [
+ "https://www.youtube.com/watch?v=abcdef123456"
+ ],
+ "other": [
+ "https://someforum.org/fixture-discussion"
+ ]
+ },Incompatible schema changes
manualURLis not allowed anymore. It is replaced by thelinksobject.
Backwards-compatible schema changes
None.
Bugfixes
None.
Schema version 8.0.0
This is the biggest change in the Open Fixture Library's fixture format (so far 😉)! 🎉
The capability syntax is now much more versatile: Every capability defines a type and some type-specific (machine readable) properties. This enables us to write better export plugins, e.g. with information for 3D previews. Please see the updated capability docs and the capability type reference.
This schema version addresses issue #267 and was implemented in pull request #425, which featured a whopping 540 commits!
The export plugins were updated so that the generated output is still valid. The import plugins were updated to read as much new capability information as possible from the (mostly much more limited) input formats.
Incompatible schema changes
- Removed channel properties
type,color,invert,crossfade. - Removed capability properties
name,color,color2,image. - Renamed capability property
rangetodmxRange. - New required capability property
type, along with other required type-dependent capability properties. - Channels must have at least one capability now. If a channel has exactly one capability, the
capabilityproperty must be used (instead ofcapabilitiesarray), wheredmxRangeandswitchChannelsare forbidden.
Backwards-compatible schema changes
- New capability property
commentand a lot of optional type-dependent properties.
Bugfixes
- Channels with only a
NoFunctioncapability (previously channels with typeNothing) must not setfineChannelAliases.