06-17-2021, 07:28 AM
There could be a bug(*). But in practice, Gimp 2.10 doesn't work with integer values for color channels, all the processing is done in floating point, and your [0..255] colors are converted to floating point after applying a gamma correction, which for some values can put them close to a tipping point for a round-off. The integer values are accepted in scripts for compatibility.
IMHO unless you are using a rare built-in Gimp filter there are more efficient ways to do you image processing. There are image processing libraries around (pillow, the Python binding for ImageMagick....). Also, the image processing core of Gimp is called GEGL and can be used independently of Gimp.
(*) feel free to report it here.
PS: gimpcolor.RGB(int(rgb[0]), int(rgb[1]), int(rgb[2])) ? gimpcolor.RGB(*map(int,rgb))!
IMHO unless you are using a rare built-in Gimp filter there are more efficient ways to do you image processing. There are image processing libraries around (pillow, the Python binding for ImageMagick....). Also, the image processing core of Gimp is called GEGL and can be used independently of Gimp.
(*) feel free to report it here.
PS: gimpcolor.RGB(int(rgb[0]), int(rgb[1]), int(rgb[2])) ? gimpcolor.RGB(*map(int,rgb))!