OpenLightingProject / OpenLightingProject/open-fixture-library

Functional categories

Open
#4,442 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JSON
Stars
258
Forks
100
Avg merge
11h 52m
Merged PRs (30d)
53

Description

A lot of the categories in OFL right now are simple functions of their capabilities, like:

  • Moving Head: has Pan/Tilt channels
  • Color Changer: has ColorIntensity channels or a ColorWheel
  • Haze, Smoke: has those features
  • Matrix: has a pixel matrix

(These are so trivial, we've got automated scripts to check that they're correct!)

What would be more useful is categories which match how lighting is used in the event industry, and which can't be trivially derived from other parts of the file, such as:

  • Wash: A wide spread of light, typically with a beam angle of 25deg or more. The edge of the beam is usually fuzzy.

  • Spot: A narrow beam of light, typically with a beam angle between 5-15deg. The edge of the beam is usually crisp.

  • Beam: Like a spot, but even narrower: 2-5deg.

  • Fresnel: A fixture with a Fresnel lens

  • Cyc: A light intended to light a cyclorama, either from above or below. These are often long and narrow.

  • Photo/video: umbrellas and other large but portable fixtures, often white-only, with control of color temperature, and terrible documentation.

  • PAR: Originally, "Parabolic Aluminized Reflector", but in the age of LEDs, any fixture with similar size and functionality. Often LED variants of classical PAR fixtures, and with "PAR" still in the name.

  • Ellipsoidal/Leko: a spot with an ellipsoidal reflector.

See also #2577.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review related issue #2577 and the existing automated category checks first. Define how the proposed industry categories should be represented and how they differ from capability-derived categories; done means the category model, scope, and validation expectations are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.