пн, 6 нояб. 2023 г., 00:00 Andrew Randrianasulu <[email protected]>:
вс, 5 нояб. 2023 г., 23:16 Phyllis Smith via Cin < [email protected]>:
Maybe Andrew knows how to detect this -- if it is just a matter of looking at each plugin to see if it looks like the word "float" is in effect for the majority of variables, that is something I could do. Or if Andrew has another way?
may be look for lines like
case BC_RGB_FLOAT case BC_RGBA_FLOAT
with grep -r in plugins directory?
it looks like they all support at least input in float colorspace but histogram for example calculates curves with 8/16 bit precision, may be this is that gives clamping at the end? Does it exist if you output to native tiff? also, you can look for grep "CLAMP" -r plugins/ clamp macro itself, but you need some code reading for understand what exactly it clamps ... for example all display output still 8bit, so there is no sense yet to keep full range of channel values for in-plugin drawing ... sorry for absence of easy answer ...
On Sun, Nov 5, 2023 at 12:10 PM Andrea paz via Cin < [email protected]> wrote:
From the source code we can tell if a plugin works in 32 bit float or 8/10 bit integer? I don't know, maybe by searching for the string "float" in the code or something like that? Or the normalized range (0-1.0) instead of the range (0-255), etc. It would be important to put this information in the manual because, for example, I know that Histogram works with integers and this can lead to clipping (with loss of information) in highlights or deep blacks. In contrast, Blue Banana works in floats. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin