# Input needed: pixel value functions

**URL:** <https://forum.electromage.com/t/input-needed-pixel-value-functions/1272>\
**Category:** Feature Ideas + Requests\
**Created:** [June 2, 2021, 4:55am UTC](https://forum.electromage.com/t/input-needed-pixel-value-functions/1272 "2021-06-02T04:55:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![wizard](https://forum.electromage.com/user_avatar/forum.electromage.com/wizard/32/4_2.png) [@wizard](https://forum.electromage.com/u/wizard)\
**Post date:** [June 2, 2021, 6:50pm UTC](https://forum.electromage.com/t/input-needed-pixel-value-functions/1272/3 "2021-06-02T18:50:28Z")

</div>

This topic is mainly about getting access to the current pixel’s RGB value after it has been set by `hsv()` or `rgb()`.

There is not necessarily a backing buffer in Pixelblaze, which is a design goal from the start. I do intend to keep going in the direction of high level APIs.

Having an optional pixel buffer could be pretty handy though, and could make it easier to generate patterns that lend themselves to that approach. It’s not uncommon to make a buffer, draw into it, and fade them out a bit each frame. This would be a single pixel array, not a global array. Perhaps accessible via `mapPixels()` as well ([see this post](https://forum.electromage.com/t/input-needed-functions-wishlist/806/10)).

---

_[View the full topic](https://forum.electromage.com/t/input-needed-pixel-value-functions/1272)._