Evaluating mask AI, I find serious bugs that need addressing:
Parts of areas in red get in the masked image. Red should be an absolute “remove” order, under no circumstances pixels in red should be kept: this produces inconsistencies.
After the “Pan” hand tool is selected, nothing else works until it is deselected again. The tool should automatically deselect when the user selects another tool, like a brush or a bucket, to keep workflow smooth.
I am interested in this program, but it is obviously not ready for prime time yet.
Mask Ai leaves a white artifact around every bit of the masking. Using v1.0.2
Seems to mask well until you place a fill behind the cutout. Then it’s Obvious!
Also, it does no better than PS masking on areas that aren’t extremely contrasty or easy to mask. Trees seem to be Ai’s forte. Amazing that the background gets transparent, however, there is still the white outline artifact.
Wanted to buy; it looked on the surface to be fantastic.
The Pan tool issue is a known problem but for the rest I am having a hard time reconciling what you have said as here is an example after 30 seconds of brushing and then Compute AI:
Know this picture very well as it’s mine. Your mask is a little misleading, put a dark/black background behind that cutout and you will see quite an unsuitable result. The only way I could get a good mask out of this was using Remask 5 and refinement tools.
