On May 1, 2014, at 3:29 PM, Darrin Cardani <dcardani@apple.com> wrote:
On May 1, 2014, at 3:18 PM, Paul Miller <paul@fxtech.com> wrote:
On 5/1/2014 4:56 PM, Darrin Cardani wrote:
It’s converting them between color spaces. I believe that the values you send to -addColorParameter: are in sRGB because that’s the color space that the user interface operates in. But your filter will process them in either linear or gamma-corrected RGB (depending on your -properties) with Rec. 709 primaries rather than sRGB primaries.
But if I say I work in rec709 shouldn't it assume my default colors are also in rec709 and not convert them for me? It seems wrong to munge my default colors and give me different ones.
Can you give me an implementation of the reverse of your function so I can pre-reverse-munge my defaults (when I define the parameter) so I get back what I gave you initially?
Yeah, I agree that it’s weird for setting some parameter values. I think the assumption is that you’ll pick a default via the color picker. Like, you’ll make a version of the plug-in with the color picker, and you’ll either play with it, or give it to a designer or beta tester, and they’ll pick some value from it that they think should be the default. In that case, you’d want to be able to just enter the numbers from the UI into your code without converting from sRGB to Rec. 709.
But that’s obviously not always the case. I’ll see if I can find a conversion routine.
OK, here’s the conversion routine: color = pow(color, 1.956); if (color <= 0.0031308) { color = 12.92 * color; } else { color = 1.055 * pow(color, 1.0 / 2.4) - 0.055; } Let me know if that helps. Darrin _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com