OpenLightingProject / OpenLightingProject/open-fixture-library

Feedback (gobos) for american-dj/inno-pocket-spot

Open
#5,706 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Gobo 1 is very close to https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/Robe/gobo00025.svg but maybe slightly thicker arcs

Gobo 2 is very close to https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/SGM/gobo00008.svg but the innermost ring is circles

Gobo 3 is similar to https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/Others/gobo00108.svg but with 8 rays of 4 dots each, rather than 9 rays of 4 dots each

Gobo 4 is blocky splotches ... it's hard to describe

Gobo 5 is similar to https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/Others/gobo00008.svg or https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/ClayPaky/gobo00108.svg but with fewer/bigger dots

Gobo 6 is exactly https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/Others/gobo00125.svg

Gobo 7 is exactly https://github.com/mcallegari/qlcplus/blob/master/resources/gobos/Others/gobo00126.svg

I can send photos of any of these projected on my wall, if that helps. I'm not good at turning a photo into an SVG template.

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

Start by comparing the linked QLC+ gobo SVGs with the seven gobo descriptions for american-dj/inno-pocket-spot. Clarify the hard-to-describe fourth gobo, then identify the fixture definition and verify that all seven resulting gobos match the stated shapes, including the exact references.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.