Error Loading Adjustment Mask

Comments

50 comments

  • SFA

    New mask or mask from a previous edit in an earlier version?

    Catalog or session?

    What sort of mask (assuming you are able to work out what it might be ...)

    0
    Comment actions Permalink
  • Michael

    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.

    0
    Comment actions Permalink
  • Michael

    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.

    0
    Comment actions Permalink
  • SFA

    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?

     

     

    0
    Comment actions Permalink
  • Michael

    Yes I am moving images only within C1.

    I am seeing some errors in the IC log at the time I got the warnings in the event viewer so I'll open a ticket with support.

    Thanks again for your continued support in this forum SFA,

    Michael

     

    0
    Comment actions Permalink
  • Thomas Kyhn

    I get this too regularly, with the description in the event log saying "An adjustment mask for an image is missing. The missing mask has been replaced by an empty mask."

    1
    Comment actions Permalink
  • Thomas Kyhn

    Has anyone been able to solve this issue? I've been holding off doing any further work in Capture One, waiting for a solution.

    0
    Comment actions Permalink
  • Michael

    I have reported this to support and they are investigating. I'll report back when I hear back from them.

    1
    Comment actions Permalink
  • Thomas Kyhn

    I've reported the issue too, and haven't heard anything other than requests for more information.

    0
    Comment actions Permalink
  • Ryan Ball

    I'm having the same issue since updating to capture one 20, all my masks get lost, it's almost unusable to edit in at the moment as I spend ages making the masks and then they get lost. 

    1
    Comment actions Permalink
  • Thomas Kyhn

    Same situation here. Did you contact support?

    0
    Comment actions Permalink
  • Michael

    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.

     

    0
    Comment actions Permalink
  • Andrzej Artymowicz

    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)

    0
    Comment actions Permalink
  • Will Cravens

    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. :(

    0
    Comment actions Permalink
  • Andrzej Artymowicz

    I feel your pain... Now I'm retouching the images using Affinity Photo, way faster and safe... We need to wait for the bug fixes

    0
    Comment actions Permalink
  • Thomas Kyhn

    Same thing here. Keeps happening.

    0
    Comment actions Permalink
  • Ryan Ball

    Three months since this was reported and still no word from CO as to when this will be fixed. It seems to be happening when a previous saved session is opened, it then can’t read the layers correctly.

    2
    Comment actions Permalink
  • Will Cravens

    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). 

    1
    Comment actions Permalink
  • BeO

    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.

    1
    Comment actions Permalink
  • Ryan Ball

    Unfortunately for me the same occurs on EIP files.

    0
    Comment actions Permalink
  • Will Cravens

    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. 

    0
    Comment actions Permalink
  • Ryan Ball

    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?

     

    1
    Comment actions Permalink
  • Marco Hyman

    The release notes state

    • Fixed an issue where masks could fail to load after using Heal and Clone

    Are the release notes incorrect?  Or perhaps there is more than one issue.

    0
    Comment actions Permalink
  • Thomas Kyhn

    "Are the release notes incorrect?  Or perhaps there is more than one issue."

    Failing to load sounds like the mask is still there, which isn't the case.

    0
    Comment actions Permalink
  • Ryan Ball

    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.

    0
    Comment actions Permalink
  • Thomas Kyhn

    They've confirmed that this issue is supposed to be fixed in the latest update.

    0
    Comment actions Permalink
  • Chris Barker

    I started getting the message a few days ago; I've just updated the application and it happened again.

    0
    Comment actions Permalink
  • Thomas Kyhn

    @Chris Barker – Were the adjustments that were lost made in the new or the previous version of Capture One?

    0
    Comment actions Permalink
  • Chris Barker

    I had just updated it, as I wrote.  

    It's on v.13.1.2.37 and the message arrived on the first try after the update.  But I've just had another try with no error message.

    0
    Comment actions Permalink
  • Thomas Kyhn

    Yes, but you didn't specify whether the adjustments that were lost were made in the new or the previous version. If they were made in the previous version, the issue could have been caused by that version too, even if the error message showed up in the new version.

    0
    Comment actions Permalink

Please sign in to leave a comment.