Add fixture nanlite/forza-60cr

[FloEdelmann]

• Update manufacturers.json
• Add fixture nanlite/forza-60cr

Fixture warnings / errors

• nanlite/forza-60cr
  • ❌ Channel key 'DIMMER' is already defined (maybe in another letter case).
  • ❌ Fine channel alias 'DIMMER fine' in channel 'DIMMER' is already defined (maybe in another letter case).
  • ❌ Channel key 'CROSSFADE' is already defined (maybe in another letter case).
  • ⚠️ Unused channel(s): cct, green/magenta, hue, sat

Thank you nanlite!

[github-actions]

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>

✔️ nanlite / forza-60cr: d-light / attributes-correctness

• ✔️ nanlite/forza-60cr-CCT & HSI 16bit.xml

✔️ nanlite / forza-60cr: dmxcontrol3 / channel-numbers

• ✔️ nanlite-forza-60cr-CCT-&-HSI-16bit.xml

✔️ nanlite / forza-60cr: dragonframe / json-schema-conformity

• ✔️ nanlite/forza-60cr.json
• ✔️ manufacturers.json

✔️ nanlite / forza-60cr: millumin / json-schema-conformity

• ✔️ nanlite/forza-60cr.json

❌ nanlite / forza-60cr: qlcplus_4.12.2 / fixture-tool-validation

• ❌ fixtures/Nanlite-Forza-60cr.qxf

  Namespace(map=False, convert=None, validate=['.'], report=None) Starting validation ./manufacturer/fixture.qxf:CCT & HSI 16bit: No physical data found 1 definitions processed. 1 errors detected

✔️ nanlite / forza-60cr: qlcplus_4.12.2 / xsd-schema-conformity

• ✔️ fixtures/Nanlite-Forza-60cr.qxf

[kengruven]

Is this the same DMX map as the Forza 60C (#3816)? These fixtures have the same product webpage, and both of the personalities in the two OFL submissions are identical across the two, but they do have separate manuals, and there are a lot of modes.