-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Description
Is your feature request related to a problem? Please describe.
I recently had an issue with my pixel string doing a weird flashing when running effects. When a solid colour was "played", it worked just fine. I went down a rabbit hole of possible voltage issues, current draw spikes being too much for my buck converter, bad grounding, everything. However, it turned out the actual issue was the way I set up my segments, in that I had multiple segments that were landing on the exact same LED.
I noticed this when creating my segments, but I assumed that turning off/unselecting a segment meant it was taken out of consideration for data updates, but that's not actually what happens. As it turns out, I was sending both an effect/colour and an off to each LED, which resulted in weird flashing that looked like power issues.
Describe the solution you'd like
It would be great to have a little
This wouldn't be a matter of identifying overlapping segments, because there's a perfect valid use case for that, provided the spacing is such that an overlapping segment actually doesn't hit on the same LED's within its range
Describe alternatives you've considered
The only other thing I've thought about is creating a browser extension that would be able to read the values set in WLED, but that would only be useful for people using a browser on desktop to interact with WLED.
Additional context
I may be naive in thinking there's no reason for segments to be able to overlap and also target the exact same LED's within those segments
Thank you for your ideas for making WLED better!