-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flicker #2
Comments
You can reduce the refresh rate with fastled itself and you should be able to update the leds in the loop as often as you like (unless you need more fps within other parts of the program). Fastled 3.1 should fix this automatic to keep the update rate low enough. You should probably supply a bit more information about what leds you use and when you run into problems. |
Hi Nico, |
I was actually doing what antonmeyer suggested a while back by performing a show only when changes occur, but I vaguely recall a conversation with Daniel Garcia where he said to run the show continuously. I'll play around with that again. Haven't seen any flicker myself though, and I'm using WS2812's and APA102's. I used to get flicker on pin 13, but they patched that issue and I now use pins 11 and 12 on the Nano. |
Ok, I will double check. May be I should just add a resistor and/or capacitor. |
if you move the show call into EVERY_N call
output get much more smooth.
I guess that the high refresh rate of leds causes the flicker.
And as long you do not change the LEDs there is no need for a show call.
results in:
void loop () {
EVERY_N_MILLISECONDS(thisdelay) { // FastLED based non-blocking delay to update/display the sequence.
ripple();
show_at_max_brightness_for_power();
}
} // loop()
The text was updated successfully, but these errors were encountered: