Healing brush create black artifacts
-
Try turning off "Use Hardware acceleration" in the preferences to see if that makes any difference.
If is does we can take things from there. However it would be useful to know about file types and your hardware and software configuration including Windows release version.
0 -
I tried to disabile the hardware acceleration but nothing changed, but creating a new catalag from scratch, everything Is back to normal. Could be the problem related to the fact that the catalog have been created in the previus versioneof capture One?
I'm on Windows 10,
The files are tifThx
0 -
What I have noticed is that when I move from one healing layer to another, a black mark shows briefly on the new layer in the same place as it was on the other layer. I tried deleting all of the cache and getting 20.1 to regenerate it, but that made no difference. The pictures were never edited using 20.1, only 20.0.4
0 -
Tommaso,
Seems very strange.
I'm not sure that Tiff work with the same rules of processing.
It could be a scaling artefact of some sort.
If you are prepared to share the file people could check to see if they get the same results on their systems in the same situation.
Grant
0 -
I had a very similar sounding issue in the beta phase, by just clicking from one layer to another, black blobs or sometimes black and white blobs appeared for a split second. Raw files with existing layers.
Existing healing mask could be edited /modified with the new healing brush, but then the old masked aereas have lost their effect.
They have fixed that issue in another beta version, almost.
Some old images still showed artifacts for a split second when switching thru the layers, but not consistently enough for me to report back. The old masked areas have kept effect, and on export no artifacts were visible.
Opencl on or off made no difference.
New images had no problem whatsoever.
0 -
Ok, so the problem may be somewhat related to files edited on an earlier release since the revised functionality must change a few things under the hood?
I have seen some messages about a need to upgrade the Processing engine it the file has been processed in an earlier version ans is still set to use the earlier engine.. That makes sense.I have not seen a persistent black artefact but the healing layer can sometimes provide a slightly less than ideal lightness matching adjustment in more extreme "fix" situations. Usually lighter rather than darker in my experience.
0 -
That is usually the case when there have been major revisions to the processing engiune. However, in the case of this upgrade no such option is offered.
0 -
I constantly get this problem with scanned images (.tif).
As soon as the healing brush is applied the artifacts start popping up allover the image. (See attached screen shot).
Acceleration on/off does not make a difference. Turning the healing layer(s) off does.
Sometimes the entire image gets a lot brighter, this problem also disappears when the healing layer is turned off.
These two problems combined makes it hard, sometimes impossible, to removed dust etc, artifacts will cover the parts of the image that I want to work on. It's a pretty bad problem.
I'm running Win 8.1 as updated as it can get with the latest drivers and C1 version: 13.1.2.35
PS. The attached image is in "proofing mode", but turning that off does not help. Also, this image was imported into C1 using the latest version, so no old edits involved.
0 -
Michael,
How big, in Megabytes, is your scanned tiff file?
8 bit or 16 bit tiff?
How big are the work files that are created in order to process the tiff?
Is the problem exactly the same with Proofing off?
0 -
1) 46,7MB (A 6x6 medium format negative)
2) 24 bit (16 bit tif files can't be edited in C1 for some reason, all controls are disabled when I try to work on them.)
3) Don't quite understand the question. Do you mean the preview size? In that case I use 2560 px.
4) Yes. Proofing on/off does not make any difference.
Also...this has not been a problem until I updated to version 13, before that everything was hunky dory (except for 16 bit tifs that never worked for me).0 -
Hi! I have the same issue after applying healing, makes it impossible to keep working with the image.
This is a Fuji RAW file, and I've just recently purchased and installed C1, so no previous versions affecting it.
0 -
I'm in the middle of seeking a solution from the C1 help staff. I use v.13.1.4 on W10. Their suggestions are not anything more than what they have told others to do that have not helped, and the response doesn't acknowledge this is a well-known and common problem dating back to the healing brush introduction.
I'm waiting for C1 help to suggest I lay out a bunch of money to move to v.14 - but apparently it still persists in that version too. And for those who might think its a hardware problem, I installed C1 on two different computers including a brand new Surface Pro - and the problem is still there.
I'd be supportive if they came right out and said it was a known bug and they are working on fixing it. Instead, there is no mention they are doing anything about it when so many have reported it.
As an aside...I also noticed the Update window in the program only showed me v14 when I was on 13.1.3 It did not show me 13.1.4.
0
Post is closed for comments.
Comments
12 comments