ssamm |
When using the color controller, if the Hue is set to, say 170, and you change the Saturation setting to 0, then the Hue seems to get reset to 0. (You can see this immediately as it effects the image, but you don't see this in the color controller until you press "okay" and then re-open it.) However, if the Saturation is set to 1, then the Hue seems to remain where it was set.
I'll attach a filter for an example. It has a color controller where in the first preset it's hue is set at 170. If you then adjust the color's Saturation to 0, the result will also reset the Hue to 0/red. (It's sort of an unwanted feature on a personal filter I made -- but still, it's not a big problem, since I can avoid it by simply not setting the saturation to 0. ![]() Color Controller anomaly.ffxml |
|
Posted: January 5, 2008 3:34 pm | ||
Sphinx.
![]() |
When you set saturation to zero in a HS-x colorspace, hue will be undefined - thats how these formulas work (try guessing the hue of a gray object..). Since you only use the hue from that color input, setting the saturation to zero will make the hue undefined. That the value zero is returned is simply because some value must be returned by the internal functions..
|
|
Posted: January 6, 2008 7:57 am | ||
ssamm |
Sphinx,
Thanks, yeah I was sort of guessing that. What I was expecting was that the hue value returned by the internal functions would be the same value it was before saturation was set to 0. (Or the value the Hue slider is adjusted to.) How it is now, I can't use a single color controller to output saturation=0 and Hue=170 -- where I wished that it could, but saturation=1 is close enough for me... |
|
Posted: January 6, 2008 11:16 pm |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,533 Posts
+31 new in 30 days!
15,348 Topics
+73 new in year!
28 unregistered users.