Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Layers not Applying next day ...

Comments

48 comments

  • Scott Lendon

    Yes it is.. I can have 4 images in the shoot session all the same just diff exposures. when I re launch Capture one sometimes the layers are only missing from one or two of the shots. Just to note only the mask is missing the exposure and settings that were applied to the mask are still there

    0
  • Patrick Infante

    My situation has been clone layers not getting applied and hence whatever was cloned is gone.

    0
  • Scott Lendon

    Probably the same thing ... I don't use the clone, but, Radial, Filled, Empty and Linear all go missing.

    0
  • Ahmad Sazali Mohamad Noh

    Wow!.. I'm not alone. Some of the layers show a black line. Error & force quit almost every time. What is going on? Does anybody know?

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    "What is going on? Does anybody know?"

    The replies I've received from support contains no indication that they have any clue why this is happening. Though it's possible they're just keeping it to themselves.

    0
  • Jason Patel

    I seem to get this fairly frequently.  

    Thursday: Heal masks don’t render correctly after closing and reopening C1. Open a Ticket and am told to disable OpenCL. Doesn’t fix it..

    Sunday: Create an edit, creat a duplicate then export failed. Closed C1 to fix this. Re-open and export works but the heal layer has stopped working and on closer inspection layer masks are gone but layers still around in the list.

    I feel that the support has got a lot worse with the change of the forum and ticketing system. Did C1 also change staffing? I can’t imagine how full time pros can use the software unless they simply avoid layers all together. 

    0
  • SFA

    Jason,

    Are you using Sessions or Catalog?

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    "Did C1 also change staffing?"

    They appear to have taken on more support staff, at least I've received replies from people whose names I hadn't seen before.

    0
  • Jason Patel

    I use sessions exclusively, windows platform.

    As I understand the layers are all kept in a specific file in the CaptureOne subfolder in the session - Can only assume theirs some corruption.

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    "Are you using Sessions or Catalog?"

    Is there any reason to assume it would make a difference? Aren't masks saved in the same way in both?

    0
  • SFA

    Thomas,

     

    No, probably not. But that was not the reason for the question.

    As Jason is using sessions and knows that the files can be found in a folder I can advise where they are to be found.

    For a catalog things may be similar but I have never looked so would be less inclined to suggest anything.

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    OK, I understand.

    0
  • Jason Patel

    Having a look at the mask files *1679.cs3.comask has a number of bck, files guess those are backups not sure what’s going on.

    https://ibb.co/dMfZ4tJ

    0
  • SFA

    Jason,

    For sessions in the source image folder you should be able to find a folder named "CaptureOne" and within that a folder named "Settingsxxx" where xxx indicates a build/release level. For example Settings131 for the 13.1 build.

    In the Settings folder you will typically find .cos files (Capture One Settings) that contain the Edit and metadata information for an Image and all of its variant edits. If the File also had Mask layers you should also see some .comask files.

    The .cos files will typically be quite small - a few kb. The .comask files somewhat larger.

    This would give you the opportunity to identify that an image with an  apparently missing Mask has of does not have a .comask file associated with it, at least so far a data content file is concerned.

     

    A "Cannot load..." message sounds more like something one might expect if the file was found but could not be used for some reason. Access Privileges, file corruption, etc.

    But then, it is only a message and the accuracy of the information it delivers is somewhat dependent on what sort of problems the developer foresaw when designing and writing the software. There is always the possibility of some other issue making use of the same message.

    0
  • SFA

    Hi Jason,

    I was distracted earlier and just re-discovered and posted my response only to find you already know the location. (I thought you probably would but  just in case ...)

    bck suggestion a backup file might mean that a write activity failed for some reason. The bck might be a temporary creation prior to writing a modified version of the mask from memory?

    I would be tempted to make another copy and then rename the bck file for an image followed by checking to see if the masks magically return presumably in pre-last edit state?

     

    One other thought occurs to me. There were some changes of course to masking when the Luma range was introduced and also the Heal and clone developments. In this case the bck file might relate to that. However if the problem can arise, as has been reported, "overnight" using the same software version (or at least I assume using the same software version for the purpose of this thought exercise) the creation of the bck files may be entirely for other reasons.

     

    That there are a number of versions of what seems to be the same file all with the same time and date is "interesting". Also that there is one very large comask file for the same image name. If file extension display is turned off does a .bck extension count as an exception?

    0
  • SFA

    Thinking some more about the previous suggestions - it might also be  useful to see if renaming the latest  non-bck file to a bck file produces a different message. Or at least  does something differently.

    0
  • Permanently deleted user

    I am experiencing the same issue.

    0
  • Andreas Wüste

    Me too.

    0

Post is closed for comments.