projectM-visualizer / projectM-visualizer/projectm
Some way to cap how epileptic presets can be
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.5k
- Forks
- 485
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
Some presets are good. Others will have every color in the spectrum flashing through the screen every frame.
Describe the solution you'd like
Some setting to cap this (Maybe limiting how different from the previous frame every given pixel can be in RGB values, and cut the difference in half until it's within acceptable ranges) would be greatly appreciated and turn this into not a health hazard.
Describe alternatives you've considered
A curated list of presets that cut out the epileptic stuff. Sounds like an undertaking considering the amount of presets shipped, thou. Though it could be done programatically.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by locating the preset rendering path and determine whether the intended scope is an RGB frame-difference cap or curation of shipped presets; done should mean reducing hazardous rapid color changes without breaking normal visualization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100