Heal Tone Mapping Weirdness
Has anyone else seen the tone mapping on the Heal tool change after you edit the image?
A couple of times I've seen images with obvious issues with Heal areas after I deliver the images to a customer. Had it happen with the image below just today. There are three heal areas in this image where the tone mapping os obviously off (left cheek, forehead between eyes, just below lower right lip).
When I opened this image in C21, the tone mapping issues were visible, but what's strange is when I deleted any one of the heal brushes, the tone mapping for the other 2 would be corrected. Each brush had its own sample area, so they shouldn't be linked. Look at the screen recording.
What's most concerning here is that I can't imagine I saw the tone mapping issues while working on the image. The customer pointed it out to me after he reviewed the processed images I sent him, so I have to believe C21 did something either during the Processing of the images or some other time after I finished working with the image. Just really concerning that this could change after I finish working with the image...
Screen Recording: https://youtu.be/lBH647HejvU
-
I have experiences similar behavior....seldom, but it has happened. In my experience it seems to occur more often when correcting very similar tonal areas with individual sampling points. It's almost as if my iMac Pro is "catching up" with the corrections, and it seems the more correction points there are the more likely it is to occur. Sometimes C1 "self corrects" and other times I need to delete a correction point or two. Oddly, there have been times when the healing correction looks great in C1 but when I send it to Photoshop the tone corrected areas are darker. As an example...healing a stray hair on a gray background will look great in C1 but when I process the image to Photoshop there will be a much darker gray point/line where the correction was applied.
Sorry no answers...just more questions!
0 -
On output the entire image is calculated from the start. So if, for some reason, there is a glitch in part of that process you may see things in the output file that did not exist in the screen version since it is an entirely fresh rendering.
That you can then see the problems afterwards when re-editing is interesting. I think the "delete one, the others will be fixed" observation is probably because a final stage of the rendering process, missed when producing output (and presumably when then rendering the same image on screen to see what has gone wrong), will then be re-run and fixes whatever heal points that are still present.
As ever, if you are using Hardware Acceleration (most people are as it is set to on by default) it would be interesting to turn it off to see if that produces a consistent result.
There are some other ideas around in posts in the forum so searching may turn up some further suggestions for an immediate solution. However I would recommend that you use the "Submit a request" option and create a Support Case that offers some personal support from the C1 team. Being able to analyze your log files may be helpful to discovery the problem source and developing a consistent solution.
0
Post is closed for comments.
Comments
2 comments