Skip to content

Conversation

@FloEdelmann
Copy link
Member

  • Add fixture chroma-q/beam

Fixture warnings / errors

  • chroma-q/beam
    • ❌ Capability 'Strobe speed 0…250Hz' (10…250) in channel 'Strobe 2': StrobeSpeed can't be used in the same channel as ShutterStrobe. Should this rather be a ShutterStrobe capability with shutterEffect "Strobe"?
    • ⚠️ Unused channel(s): strobe
    • ⚠️ Category 'Color Changer' suggested since there are ColorPreset or ColorIntensity capabilities or Color wheel slots.
    • ⚠️ Category 'Moving Head' suggested since there are pan and tilt channels.
    • ⚠️ Category 'Scanner' suggested since there are pan and tilt channels.
    • ⚠️ Category 'Barrel Scanner' suggested since there are pan and tilt channels.

Thank you abdurrahman!

@FloEdelmann FloEdelmann added new-fixture Request or implementation to add a new fixture definition. via-editor Opened via the editor on the open-fixture-library.org website. labels Nov 23, 2025
@github-actions
Copy link

Export files validity

(Output of test script tests/github/exports-valid.js.)

Test the exported files of selected fixtures against the plugins' export tests.
You can run a plugin's export tests by executing:
$ node cli/run-export-test.js -p <plugin name> <fixtures>

✔️ chroma-q / beam: d-light / attributes-correctness
  • ✔️ chroma-q/beam-beam360.xml
chroma-q / beam: dmxcontrol3 / channel-numbers
  • ❌ chroma-q-beam-beam360.xmlChannel 14 "Color Macros" is missing capabilities. Used ranges: 11…255
✔️ chroma-q / beam: dragonframe / json-schema-conformity
  • ✔️ chroma-q/beam.json
  • ✔️ manufacturers.json
chroma-q / beam: millumin / json-schema-conformity
  • ❌ chroma-q/beam.jsonfixture/availableChannels/Strobe (type: Nothing) must NOT have more than 1 properties
    fixture/availableChannels/Strobe (type: Nothing) must have required property 'name'
    fixture/availableChannels/Strobe (type: Nothing) must match exactly one schema in oneOf
chroma-q / beam: qlcplus_4.12.2 / fixture-tool-validation
  • ❌ fixtures/Chroma-Q-beam.qxfNamespace(map=False, convert=None, validate=['.']) Starting validation ./manufacturer/fixture.qxf: Invalid physical dimensions detected 1 definitions processed. 1 errors detected
chroma-q / beam: qlcplus_4.12.2 / xsd-schema-conformity
  • ❌ fixtures/Chroma-Q-beam.qxfElement '{http://www.qlcplus.org/FixtureDefinition}Dimensions', attribute 'Weight': [facet 'minExclusive'] The value '0' must be greater than '0'.
    Element '{http://www.qlcplus.org/FixtureDefinition}Dimensions', attribute 'Width': '0' is not a valid value of the atomic type 'xs:positiveInteger'.
    Element '{http://www.qlcplus.org/FixtureDefinition}Dimensions', attribute 'Height': '0' is not a valid value of the atomic type 'xs:positiveInteger'.
    Element '{http://www.qlcplus.org/FixtureDefinition}Dimensions', attribute 'Depth': '0' is not a valid value of the atomic type 'xs:positiveInteger'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-fixture Request or implementation to add a new fixture definition. via-editor Opened via the editor on the open-fixture-library.org website.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants