I’m experimenting with color space conversions (RGB to HSV) and comparing the VVVV results with other software (Substance Designer, Photoshop).
One thing I noticed is Stride’s “ConvertColor” node outputs unexpected H and S results that aren’t consistent with results from the other software.
So, I decided to try OpenCV’s color space conversion. Going from RGBtoHSV worked as expected, but it seems going back using HSVtoRGB always produces errors in the CvtColor node no matter what. It seems the HSV conversion is causing a hiccup of some sort.
Since I’m working using TextureFX, this patch is a bit convoluted and decidedly less performant, but the RGBtoHSV conversion is more agreeable. Any help is appreciated!
If you transform from LinearToSRgb then you should use SRgbToLinear instead of GammaToLinear, there are subtle differences between them. but maybe there is a simpler solution. how does your setup look at the moment? and with what kind of color data do you work? are they all in sRGB color space?
If you transform from LinearToSRgb then you should use SRgbToLinear instead of GammaToLinear,
That’s what I figured. However, SRGBtoLinear always returns null.
how does your setup look at the moment?
Just using the FileTexture node to load an 8bit rgb image from disk. I see vvvv adding the _srgb suffix after loading. Then, plugging that into a ConvertColor node using the RGBtoHSV type. It appears to need conversions before and after (as well as channel shuffling).