Releases: Timendus/thumby-grayscale
v4.0.3
v4.0.2 (hemlock)
Support for 2023+ Thumby displays (OLED2) with auto-loading calibrator.
Newer Thumbys after around the start of 2024 came with an OLED
component from a new manufacturer that needs calibration and
improvements to the process and parameters around grayscale
effect to achieve a stable grayscale image.
Big thanks to @dan5sch for the collaboration on these changes.
- Brightness starts at 1 to match changes in thumbyAPI for new OLED.
- User friendly calibration process:
- Auto-loads as needed (not when HWID < 2).
- Saves configuration parameters to thumbyGS.cfg.
- Selects between OLED presets, and then allows fine tuning.
- Calibrator is automatically loaded on first import, when HWID >= 2.
- Much faster and stable switching between grayscale and B/W.
- Brightness reliability improvements.
- More stable thread initialisation.
- Fast reset.
Contributors
Assets 2
v3.0.0-alpha
The previous major release got the image stable, this one gets the thread to run stable 😄 We should have no more annoying crashes, even when reading from and writing to the flash memory on the main thread. This miracle of engineering was brought to you by @fuglaro's thorough testing and debugging and @doogle's work to make the grayscale thread run completely from RAM. Any bugs or instabilities you still run into are 100% my (@Timendus) fault in combining those two worlds 😂
This version brings the grayscale library even more in line with the rest of the Thumby APIs. We hope this library will at some point be integrated in the standard library, so we adopted some of TinyCircuits' naming conventions.
Finally, this version of the library will allow you to test, run and debug your grayscale programs in the emulator at code.thumby.us. @fuglaro submitted some changes to the emulator to TinyCircuits to make this possible, making our lives as grayscale developers much easier! 🎉
Please note that this is an alpha version. If you run into any issues, please report them. We can use all of your testing and feedback!
The public API (so basically: things described in the README) will probably be quite stable, going forward. So we expect to be on major version 3 for a while. But please don't rely on any internal variable names to stay the same or things like that, as we will probably have to refactor some of the internals to solve the last couple of outstanding issues before we release the "official" 3.0.0 version.
