CO20 Losing Adjustment Masks
I keep getting the following error on different images: "An adjustment mask for an image is missing. The missing mask has been replaced by an empty mask."
It seems to happen with healing brush masks, which usually have a significant number of edits (fixing up defects/dust etc in film scans, where the scan is either a 20MP or 80MP hires Olympus macro image). The result is that all the work patching up the image is completely lost.
Is anyone else seeing this? Can anyone suggest a work-around?
Thanks,
-- Mark
-
There are a number of threads on the forum with similar observations in the past few months.
A search should find them quickly listed and give you an opportunity to review the information available so far.
It seems to be more of a Mac problem than Windows and presumably not affecting everyone using Mac.
1 -
The only thread that I could find was quite old and implied that the mask bugs had been fixed in 13.2.1.37. The suggested work around was to upgrade.
However, I have only started seeing this problem since I updated, and it is occurring with newly imported and edited images.
I think that I will raise a support case, although I do not have a guaranteed way to provoke the problem (other than to spend hours editing a mask to maximise the frustration).
0 -
Here's one previous thread about the issue.
As mentioned there, since creating a new catalogue (in version 13.1.2.37) and importing my old catalogue into this new catalogue, I haven't seen the issue again.
0 -
Thanks! I will try that. The problem is driving me crazy at the moment, and what is odd is that it only started with the most recent update.
0 -
Unfortunately, creating a new catalogue didn't solve the problem. It just happened again here.
0 -
After 4 months with this issue you should think it was about time they came up with a solution.
0 -
The issue has been going on for a lot longer than 4 months. On a previous version it used to happen to me a lot but on the current version it has only happened once, or perhaps twice, so something has changed, although clearly they have not yet got to the bottom of it.
Ian
0 -
Ian,
Any possibility that some local setting or "orphaned" work file is involved?
The majority of observation seems to be Mac related.
However I have seen the error message once or twice on my Windows system and possibly going back to V12 or maybe even V11. But it has been very rare and very random and so not something one could realistically try to diagnose.
Although I have seen the message I don't recall ever discovering a missing mask. But then It maybe that I simply did not feel it necessary to follow up on the message for the (very few) images involved.
The obvious issue here is that IF it IS something that happens locally in certain situations then expecting a "fix" may be unrealistic. Or perhaps the "fix" that may be possible has so many things to check to catch all eventualities that it will simply take some time to design, develop and refine for performance needs.
How many people are seeing the problem? Clearly some are not, despite using layers. Why not? What, if anything, is different about their usage or their systems?
0 -
Support says they've found the cause of the issue.
0 -
Excellent.
Hopefully the fix is not too complicated.
Is there something required beyond the Mask related fix listed in the Release notes for 20/13.1.2?
0 -
I don't know anything about the details.
As I understand, the 13.1.2 update was supposed to fix the issue, which it didn't. Hopefully, the next update will.
0
Post ist für Kommentare geschlossen.
Kommentare
11 Kommentare