Error Loading Adjustment Mask
I am constantly getting error messages stating that an adjustment mask cannot be loaded. The layer is there but the adjustments are gone. I have run Verify and no issues came up. Could someone suggest why this may be occurring and how to fix it?
Thanks.
-
When you say version, I assume you are referring to CO version. This has been occurring across several versions of CO including the newest so, old masks. The first version I use was the first release of v20 or the last version of v12. I am not certain.
I use catalogs.
The masks are color related, almost certainly the Color Editor / Advanced.
These images were not imported from LR. It was a folder import and I started editing the original RAW file.
Thanks.
-
I am resubmitting this response in hopes that it bypasses the Pending Approval process.
-----------------
When you say version, I assume you are referring to CO version. This has been occurring across several versions of CO including the newest so, old masks. The first version I use was the first release of v20 or the last version of v12. I am not certain.
I use catalogs.
The masks are color related, almost certainly the Color Editor / Advanced.
These images were not imported from LR. It was a folder import and I started editing the original RAW file.
Thanks.
-
Michael,
This may be complex one.
The log files produced by C1 may help to identify which mask(s) are problematic. That could provide a basis for some specific investigations. Verify may not help with this. I think it is mainly involved with check the integrity of the Session or Catalogue database in terms of entries in those being found to be valid. How far it would check into the related edits - other than checking the basic files for Thumbnails, Previews and edit data exist I don't know. Probably not at all in some cases since the check for complete function would require a load of everything in the system and that may not be deemed to be acceptable for the purpose of verifying the Catalogue or Session database entries.
I could be wrong.
This sort of problem has been reported before over the years. I don't recall reading of a fix that would seem to be universal. Nor does it seem to be a regular large problem
I would suggest you "Submit a request" ASAP - no harm in doing so even if someone here suggest something that turns out to solve the problem.
I'm assuming here that if you have been moving images around the movements have all been undertaken within C1?
-
Yes, support is investigating but it is worth opening a ticket to let them know.
I have not had that problem in a while. The only thing I can attribute that to is renaming or deleting the .plist file (com.captureone.captureone13.plist) per this post to resolve the problem with undo not working...https://support.captureone.com/hc/en-us/community/posts/360009532798-Undo-Not-Functioning.
I am not certain that resolved the missing mask issue but it other than causing Capture One to think it is being opened for the first time, it does not do any harm. And as I said, I have not had that problem since deleting that file.
-
I have the same issue. After doing a lot of heal layer correction CO stops responding properly. Even previews of the pictures are loaded with low resolution. No problem with session verification. After quitting and reloading CO I get error loading adjustment mask. The adjustment mask is MISSING! Hours of work has vanished... (the latest CO version, MacOS Catalina)
-
Same issue here. I spend a couple hours editing an image, removing hairs and blemishes and using masks for coloring and then they were just all gone. I would haven't wanted to throw my laptop out the window if I had just been able to process a JPG first. I guess I'll need to regularly export along the way since this keeps happening. :(
-
I was working in a new 2020 catalog (not upgraded or migrated or any of that) and it happened WHILE I was editing. It all of a sudden stopped applying new adjustments and then wouldn't let me Process/export the JPG out because it couldn't read the adjustment layers. I'm pretty sure it was a new Cloning layer that was to blame for the hiccup. I had no issues until I was trying to define a source point for a clone mask. Undo didn't help. I closed out CO knowing I had synced Metadata pretty often and hoped that would help me recover everything, but it obviously didn't because it sounds like that adjustment information is saved to another type of sidecar file. (I'll have to figure out how to create these sidecar files for the Catalog images).
-
Will,
it is probably the .comask file. However the unique ids in this file and the layers in the db must match and I'd recommend to save a complete and consistent intermediate state of the image with all its adjustments and layers, once in a while, which is probably best achieved by exporting the image as an EIP package.
I once had a layer failure back in v11, several variants with multiple layer each, and though it did not happen again since then, I do this as a precaution for images which I invest hours of work. Only for those.
-
BeO, thanks for that! I was digging around for how to export the adjustments and this helps a ton! This is what I assumed "sync settings" was doing, but think I was mistaken, so I'm glad I know how to manually do it for important images. I'll incorporate this into my workflow to export the EIP as soon as I "finish" editing an image (and maybe along the way if sync settings isn't doing its job for some reason). It would be ideal if CO frequently updated this EIP (or if it was easier to figure out how to actually attach cos and comask files next to my CR2s as I was lead to believe would happen). There is no way I'm going to make an EIP for every photo I make an adjustment layer for, so I may have to accept that these changes may be lost over time.
-
Unfortunately the latest release 13.1.2.37 of capture one has not fixed this issue. Very odd this bug has not been fixed in the latest release, considering it's such a fundament problem, which many are experiencing. Could someone from Capture one respond with some insight into the issue?
-
I read the release notes and was very hopeful that it would resolve the issue. Unfortunately as soon as I open an existing session it lost the mask info and the error message popped up as per usual.
I’m only hopeful that any new session created may not inherit the issue with the latest update, but I can’t see why it would make a difference.
Please sign in to leave a comment.
Comments
70 comments