Schema version 12.5.0

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

• Add RJ45 DMX connector (see #3831)

Bugfixes

None.

Commits since last release

Schema version 12.4.1

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

None.

Bugfixes

• Narrow down RDM manufacturer ID range (see #3621, thanks @kengruven!)
  • previously allowed: 0…65536 (0x0000…0xffff)
  • now restricted to: 1…32767 (0x0001…0x7fff)

Commits since last release

Schema version 12.4.0

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

• Add new powerConnectors object to physical (see #3350, thanks to @CGBassPlayer!):
  Specify input only / output only / input and output for each of the following connectors:
  • IEC C13
  • IEC C19
  • powerCON
  • powerCON TRUE1
  • powerCON TRUE1 TOP
  • powerCON 32 A
  • Hardwired
  • Proprietary

Bugfixes

None.

Commits since last release

Schema version 12.3.0

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

• Add Burst as new shutter effect (see #2094, thanks to @JonahKr!)

Bugfixes

None.

Commits since last release

Schema version 12.2.2

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

None.

Bugfixes

See #1998:

• Define $schema property in regular properties rather than in patternProperties
• Simplify plugin schema with default instead of an enum + allowed free text
• Simplify wheel-slot and capability schemas with discriminator and oneOf
• Fix required and additional properties
• Define type and pattern in the same object
• Simplify oneOf
• Replace some $comments with descriptions → will be shown in VS Code

Commits since last release

Schema version 12.2.1

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

None.

Bugfixes

• In Effect, EffectParameter and Maintenance capabilities, the parameter property value can now be a negative integer. Previously, only non-negative integers were allowed, besides the keywords.

Commits since last release

Schema version 12.2.0

View schemas

We finally added support for gobo images! 🎉 ⭐
Have a look at the Showtec Phantom 50 fixture page to see how much this helps distinguishing different gobos and gobo capabilities (and how nice it looks 😉)!

Incompatible schema changes

None.

Backwards-compatible schema changes

• Wheel slots of type Gobo can now reference a gobo resource, which are stored in the resources/gobo directory. For more information, see #1185 and the updated fixture format docs.

Bugfixes

• The name, comment and website properties in the manufacturer schema now use the nonEmptyString, nonEmptyMultilineString and urlString definitions, respectively.

Commits since last release

Schema version 12.1.0

View schemas

We're adding a completely new capability type to make especially Laser fixtures more accurate! 🎉

Incompatible schema changes

None.

Backwards-compatible schema changes

• New capability type BeamPosition ↔️ ↕️ . Compared to Pan/Tilt, this moves only the beam (often a laser) and not a visible physical part of the fixture. See the GLP impression Laser which has both Pan/Tilt for moving base/yoke and BeamPosition for moving the laser beam.

Bugfixes

• Capability type order: BeamAngle has been moved, together with BeamPosition, after SoundSensitivity and before Focus.

Commits since last release

Schema version 12.0.0

View schemas

Incompatible schema changes

• The physical property focus (with properties type, panMax and tiltMax) has been removed, as all the information can be inferred from categories and channels (at least with the new Barrel Scanner category).

Backwards-compatible schema changes

• New category Barrel Scanner. Use this instead of Scanner if the mirror is cylindrical shaped.

Bugfixes

None.

Commits since last release

Schema version 11.3.1

View schemas

Incompatible schema changes

None.

Backwards-compatible schema changes

None.

Bugfixes

• We now make more use of JSON Schema formats: Dates now have format date, URLs have format uri and matrix name constraints have format regex. This is possibly a little more restrictive (e.g. invalid dates like 2019-13-32 are no longer possible).

Commits since last release