Upgrade from 16.3.8 to 16.5.1 - Old masks are lost
Version 16.5.1 will not work with masks defined under version 16.3.8 - "an adjustment mask is missing for image ...The missing mask has been replaced by an empty mask".
This behaviour makes the new version 16.5.1 unusable for me . A support request has been raised .
-
That masking problem has been coming and going for some time. I agree that it's really annoying, but I don't think it's particularly a version 16.5.1 thing. Are you working in sessions or catalogs?
Ian
0 -
Thanks Ian - I am working with catalogs .
In the meantime I went back to version 16.3.8 . With this version I have the correct access to my pictures with masks .
Paul
0 -
I always had and have this very same problem when importing images from Capture One Mobile using Cloud Transfer from my iPad Pro 12.9 inch screen.
0 -
Quero receber constantemente notificações.
0 -
PEDRO AUGUSTO BENEVIDES MACHADO - notifications of what?
Ian
0 -
Just to let you know about my findings playing a bit around .
Due to the recommendation of C1-Support , I verified my catalog in version 16.3.8 (which didn't have any problems with the masks ) . The catalog was marked as 'damaged' with a subsequent repair action .
Today I installed a test-version of 16.5.2 . This version showed all the (old) masks of version 16.3.8 correctly.
Perhaps this helps with your problems .
Paul
0 -
Thanks for all the help and the comments. Paul Möller, really appreciate your thoughts, thank you. I will try to verify and repair in 16.3.8, though I do not have a backup catalog of that vintage and I think it will not allow me to use a catalog that has been 'upgraded'. I'll await a full version on 16.5.2. Tom - I noted a comment on transferring from iPad version via the cloud - my understanding is that masks at the moment do not transfer, and they certainly didn't when I tried a test. Why on earth that is, I don't know - thanks Capture One! Who would ever have thought anyone would want to do preliminary edits in the field on iPad and then transfer to desktop to finesse them? At this rate I'm beginning to wonder if C1 is really the future for me.
0 -
There was a period where a bug in the app lost layer masks. It never told you it lost them and catalog verify didn't check it. You only found out when you selected that image and that layer with a lost mask. What is even more annoying is that heal and clone layers no longer reflect their proper type - they show up as adjustment layers (the default kind of layer).
At this point you have no idea which images have missing layer masks and how long they've been missing (how far back you'd have to go to get them).
I empathize with you all. I've experienced this and it is frustrating.
0 -
So far I have not been affected, but thinking of writing a script to make the problem apparent more quickly.
What has happened when masks are lost in an upgrade? Does the adjustment layer simply not have a mask (i.e the mask is cleared), or is the layer with the mask missing?
0 -
Upgrades are not causing loss of masks. Bugs in old versions caused loss of masks. New versions have much improved catalog verification that find them. When a layer mask is lost the layer, regardless of its original type, reverts to an empty adjustment layer. I've experienced loss of masks with heal layers and they defaulted to adjustment layers with no mask and no adjustments.
This was a known issue in a few older versions but was supposed to be fixed. The problem is you can have images sitting in your catalog for a long time having already lost a layer mask and you don't know it until you view them.
0 -
To answer your specific question Eric .. the layers do not go away .. when you select them they simply generate a message that their mask is missing.
- Non-adjustment layers that lose their mask change to adjustment layers with no adjustments.
- Adjustment layers that lose their mask retain their adjustments but default to an empty mask.
This has been my experience. Creating a new catalog and importing my main catalog into it every so often seems to keep them clean. I'm told that the bugs that caused this issue in older versions have been fixed.
0 -
I was hoping for a mechanism that would make this bug detectable on a large scale, as I have a lot of images in my catalogs that I haven't worked on for some time.
Copying the mask to another layer doesn't give any error if the source layer has no mask. I think the default is a mask with no points.
Copying the mask, then inverting it and setting the exposure adjustment to zero should give a black image if the starting mask is empty, but I can't get readouts to read back any values.
Enabling each layer (and disabling if previously disabled) might do it, but it might also trigger the one-time user message and not report it.
So far I haven't encountered the issue, probably because I save and update my catalogs before any major new version. But I'd certainly be highly annoyed if it did get me.
0 -
Disappearing masks has happened to me several times over the last few years. Most recently now again on 16.5.3.1. This is so annoying I'm nearly ready to go back to LR. I mean at this point since it loses the masks I don't really lose anything by switching back.
I verified the catalog and it failed. It then repaired but the masks are still gone. And BTW, the catalog backup is supposed to verify the DB when you exit C1. I've never ever been notified of a verify issue during backup. Really getting tired of it because most of my post processing time is spent drawing bloody masks and C1 keeps losing them.1 -
Having had this issue in the past with old versions, and other catalog issues, I once decided to use a C1 session instead. I just don't trust an encapsulated catalog anymore, and with session, issues were seldom, if at all. So I exported all original images from the catalog into a meaningful folder structure, including adjustments (and masks). This was a day or two of work but since then I am happy with this approach.
In order not to loose catalog functionality, mainly the ability to search images and use smart albums, I imported all images into a C1 catalog, inclusive adjustments, and defined smart albums. The point though is that I do all my edits and metadata work in the session, and all classification information goes to metadata and keywords. Almost no static albums in the catalog.
I now can search for images in the catalog, and drag&drop them to the session in order to add variants and/or make adjustments. I then remove these images from the catalog and re-import the folder again. If in doubt (if the images are distributed across several folder), I re-import the top level folder again, adding the missing images which are I removed from the catalog before.
Best practise is to temporarily "remember" the images which I drag&drop to the session in a static album in the catalog, so I can easily find and remove them from the catalog.
Obviously it must be a referenced catalog because the drag&drop action works passing references to the files in the file system, so that the session can use the respective .cos and .comask files from the folder structure.
If the catalog makes any mistakes due to a bug, it will not write it to the session files but only to the catalog file.
At any time I could through away my catalog and simply create a new one, import the images from my image top folder, because all metadata and edits are in that folder hierarchy as simple files. The only thing to recreate manually are the smart albums in the catalog.
Sounds complicated but actually once this workflow is understood and practiced it is quite easy and robust, well worth the additional effort for users having a catalog phobia like me. :-)
Theoretically, one could work like this using a different catalog software, as long as you could drag&drop your search results from the catalog to the open C1 session. Both software, the catalog software and C1 must support passing and accepting the file references according to the drag&drop standard of the specific operating system.
Not all catalog software does, for example I tested darktable on Windows, it doesn't, but digikam did.
C1 supported drag/drop into a C1 session until version 15.2 but in a later version C1 does not support it anymore (and these guys are relunctant to fix this bug). That is on Windows, I don't know if these guys also destroyed drag&drop on Mac.
Cheers,
BeO0
Post is closed for comments.
Comments
14 comments