happy-kat wrote:Patience was the same of the game.
With a mask set walk away do something else then go back and it will be done.
But
The mask was ignored and the entire image was wiped.
I could repeat this, the mask is always ignored on wipe.
The mask is still there just ignored the whole image is effectively wiped.
The same happens in version 1.3.5.289 as it does in 1.4.332
Wipe is also putting the image background way too close to the black point and effectively clipping the image when using wipe colour and brightness option.
I am going to try process again to see if the clipping is coming about from the Contrast module I used directly after wipe.
Hmmmm.... I've been trying to replicate this, but to no avail. I'm wondering if there might be a misunderstanding as to what Wipe is doing with the Mask?
Masking out in Wipe does not mean the area will be unaffected in the end-result. It just means that the area is not used as input for modeling gradients.
The fewer pixels you give Wipe to work with, the harder it has to work to create a model for the complete image; the pixels you mask out still need values calculated for them to subtract. They will still be corrected; all pixels in the image will be corrected.
You should use a mask for Wipe in two cases;
- You have dark anomalies (e.g. darker-than-real-background pixels) in your image that could confuse Wipe.
- You have a large area of contiguous nebulosity (without background poking through) in your image which Wipe may start mistaking for a gradient at higher Aggressiveness settings; Wipe may start removing the nebulosity a little in a larger-scale context.
To see whether you even need a mask, see what Wipe produces with- and without a mask. You may find there is virtually no difference at the default Aggressiveness settings.
Does this help?
