Created by Florian and Felix Edelmann.
The developer documentation can be found at the GitHub repository. It contains an explanation of the JSON fixture format we use internally, and from which fixture definitions in other formats can be exported by plugins.
We were used to programming lighting shows with the e:cue software and – because at some point we found it being limited in functionality – wanted to try out other programs. I built a DMX interface with Open Lighting Architecture to be able to try QLC+ and we kept on using that combination since then.
The problem we noticed during our testing phase was that all the fixture definitions we created for e:cue could not be easily converted for use with other software. The idea for a converter was born (fixture-converter on GitHub, September 2016 – January 2017).
Since we wanted our work to be as useful for other people as possible, we decided to build a website that would store the fixtures in a wiki-like way (everybody can help improve it) and allow auto-generated fixture files in various formats to be downloaded. Creating new fixtures should be made as simple as possible with an online Fixture Editor that could also import from existing fixture definitions. For roughly a year (February 2017 – March 2018), the site kept getting better and better at open-fixture-library.herokuapp.com.
In March 2018, we decided it was time to get our own server and domain – and at the same time were invited to the Open Lighting Project (see issue #453 on GitHub), so here we are "under the new flag" at open-fixture-library.org! Of course there is still more to be improved, so feel free to contribute!
See the project page on GitHub to see how you can help.
We respect users' privacy and thus collect as few data as possible. No personal data about our visitors is stored on our server or sent to other sites without users' consent. The communication between users' browsers and our server is encrypted via HTTPS. Videos are embetted with embetty, so no information is sent from users' browsers to the video hosting platform (e.g. YouTube) until the video is played. The fixture editor only uses the entered data to open a pull request in our public GitHub repository; this means that the chosen author name and GitHub username – the only personal data – will be made public. Unfinished fixtures and the last submitted author name / GitHub username are saved locally in users' browsers.