XnViewMP, Topaz Adjust AI) behave in a predictable manner, too. Other colour-managed applications that I have installed (e.g. When I open your swapped channels test file in Lightroom, using the HSL, White Balance or Tone Curve modules doesn’t cause the channels issue. Both behaved similarly but it seems they apply a different image processing pipeline for rendered RGB files than some other applications. In my previous testing I compared how DxO PhotoLab2 and Affinity Photo worked with your test file. OK, I re-tested this with other applications and it’s an interesting issue. Apple Photos, has no issue with that example. Cyans are Magentas, Magentas are Yellows and Yellows are Cyans for this file. If you want to affect the Yellows in your swapped channels photo (the grass and the foliage are seen by PhotoLab as Yellows rather than Greens), choose the Magentas swatch and rotate the hue. So all your editing will be shifted accordingly and works as the embedded profile tells PhotoLab to work. When you pick the Red swatch you affect the Green channel, etc. When you select the Green swatch and shift the hue, you’re not manipulating the Green channel as expected when using a regular RGB file, but the Blue channel because that’s what the ICC profile tells the program to do. It’s best to see this in the HSL tool (point E above). It’s manipulated in such a way that what’s called the Red channel is in fact Green, Green channel is Blue and Blue channel is Red. I can see that the swapped channels profile embedded in the file was created in Displa圜al. The moral of the story is: while they are good for testing purposes, don’t use swapped-channel ICC profiles for your editing (as a working colour profile).Īlthough the RGB channels in your test file look correct in a colour-managed program, when you start shifting the hues in a tool which operates on channels (Tone Curve, HSL, most filters in simple Style-Toning), the changes will affect a different channel than expected. If anybody can explain what happens here I’d be very happy. In P元, even if I export with the original color space, the colors are wrong, e. Also the MacOS preview shows no issues applying a Sepia tonung to the picture with the special color space and even save it back to the same color space. So I start to wonder if my reasoning is flawed.Īpple’s Photos App, though, works as expected. To be fair I tested the exact same thing in Pixelmator 3.9 classic and found the same. embedded in RGB) -> color transformation -> working color space of P元 -> tools (HSL, tone curve, etc.) -> color transformation -> output color space (display, export file).īut given these results it seems like P元 works in the input color space and assumes that green is green, regardless of what the embedded profile of the RGB picture says. My mental model is: Input color space (e.g. But generally spoken I’d have expected the color management in RGB to work so that there are predictable outcomes, regardless of the color space of the source material. I think in reality this is no big deal, at least not for me, since I use P元 to develop RAW files, not RGB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |