-
Notifications
You must be signed in to change notification settings - Fork 121
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
Is there a "good" way to only update changed pixels? #122
Comments
I’ve done a lot of messing with the timings and haven’t damaged a screen yet. Some displays do support updating a region of the display, but I’m not sure any of ours do. Most of the blinking/flashing is an attempt to erase the previous image from the screen and avoid image retention- you can drastically shorten this period and then run a periodic full update to clean up the screen. If you’ve ever used an e-reader you might notice them doing this. |
Thanks for the clarification! I plan to display the new image as fast as possible and run a full cycle (or clean.py) from times to times. Thanks again for the help! |
is there any similar hack at hand for the UC8159 chip? |
Nope. There is no partial update support, nor even support for custom LUTs. |
Is there a way to speed-up the refresh process by only changing specific pixels instead of going through the whole blinking/flashing cycle?
I use my Inky phat (black) to display a big number at the center, updating every 6 to 20 seconds, it works well so far.
There a couple of solutions around but none that I can figure out how to translate to my inky phat black:
In summary: is the only way to optimize refresh to mess with timings risking damaging the screen or is there a cleaner way if only few pixels change?
The text was updated successfully, but these errors were encountered: