wilecoyote2015 / lex-lutor

WIP application for 3D Lookup Table Manipulation. This is a technical prototype with fixed layout and no undo. The code is a mess (and so the commit log), as, currently, this project is just for curiosity. If it is useful and I have time and motivation, it will be rewritten from scratch with a (hopefully) better architecture and proper packaging. However, contributions are always welcome ;)
GNU General Public License v3.0
0 stars 0 forks source link

Node Transformation should always refer to base color #2

Open wilecoyote2015 opened 2 years ago

wilecoyote2015 commented 2 years ago

Current Behavior: After a transormation, the resulting RGB coordinates are written to the nodes as current position. When a new transformation starts, for example along saturation, the current RGB is converted to the transform color space and new coordinate in transform space is calculated by shift by weighted distance. This has the drawback that transformations are not reversible. In particular, information regarding source color is lost. Consider saturation transform: First transform saturation to 0. Then, the resulting RGB coordinates are all equal. Hence, Hue is lost. Doing a saturation transform by the negative distance of the transform that resulted in zero saturation afterwards will then not recover the source color.

Better: Somehow store / reconstruct / track transformation path of all previous transformations. use that as start. In the end, each series of transformation operation should be invertible