Thought this was a bug with delete, but perhaps a feature.
I am using OS X Yosemite and Capture One 8.3. Here are my questions/issues:
When the photos are embedded in the Catalog, deleting a picture from "Recent Imports" puts the image in the Catalog's "Trash" Collection. If one tries to delete more than one photo, there's popup that the deleted photos will be put into the "Catalog Trash" and if you allow them to be removed from “Recent Imports" they are still in the "Catalog Trash". You can drag them from the “Catalog Trash" to a User Collection, but not back to a "Recent Import".
Concept One's handling of deleted pictures seemed sensible until today, when I created a Folder to put images outside the Catalog because I got nervous that if the Catalog got corrupted that the images might be lost and also liked the idea of having a single Catalog spanning several USB drives. I successfully moved all of the existing images into the new folder and was able to set the default for imports to store the images in this folder rather than the Catalog. (As an aside, I was surprised that moving pictures between folders that are outside the Catalog always copies the files and deletes the originals rather than using OS X's mv command.)
When I delete files in "Recent Imports" which are stored in a Folder rather than the Catalog, the choices are different than if the images were imported into the Catalog. Now the choices are "Cancel", "Keep in Place" and "Move to Trash". If ones selects "Move to Trash", it is the equivalent (if the photos had been stored in the Catalog) of both deleting the picture from "Recent Imports" and Emptying the "Trash", though you can still get the picture back if you use OS X's undelete. Surprisingly, if one selects "Keep in Place" (remember the delete is from "Recent Imports†not a user collection, etc.), Capture One deletes the photo from "Recent Imports" without putting it in the "Catalog Trashâ€. Since there's no "Folder Trash", there seems to be no one-click way to undelete the folder within Capture One without first doing a scan to find the photo that is still on the disk but not in the Catalog. This seems inconsistent with photos stored in the Catalog and a worse workflow.
Why not have a “Folder Trash" Collection for folders outside the Catalog or have the "Trash" Collection work regardless of the whether the images are in the Catalog or an external Folder? The image files would always remain in place when pictures are deleted from "Recent Imports" (just like they currently always stay in the Catalog) and skip the choice between "Keep in Place" and "Move to Trash". When Capture One's “Catalog and Folder Trash" is emptied, the pictures that have been saved in place would get moved to OS X's trash. Then there would no need for a popup when delete a single photo from "Recent Imports", just like is currently the case when the photos are stored in the Catalog.
Am I misunderstanding how the system works?
David
When the photos are embedded in the Catalog, deleting a picture from "Recent Imports" puts the image in the Catalog's "Trash" Collection. If one tries to delete more than one photo, there's popup that the deleted photos will be put into the "Catalog Trash" and if you allow them to be removed from “Recent Imports" they are still in the "Catalog Trash". You can drag them from the “Catalog Trash" to a User Collection, but not back to a "Recent Import".
Concept One's handling of deleted pictures seemed sensible until today, when I created a Folder to put images outside the Catalog because I got nervous that if the Catalog got corrupted that the images might be lost and also liked the idea of having a single Catalog spanning several USB drives. I successfully moved all of the existing images into the new folder and was able to set the default for imports to store the images in this folder rather than the Catalog. (As an aside, I was surprised that moving pictures between folders that are outside the Catalog always copies the files and deletes the originals rather than using OS X's mv command.)
When I delete files in "Recent Imports" which are stored in a Folder rather than the Catalog, the choices are different than if the images were imported into the Catalog. Now the choices are "Cancel", "Keep in Place" and "Move to Trash". If ones selects "Move to Trash", it is the equivalent (if the photos had been stored in the Catalog) of both deleting the picture from "Recent Imports" and Emptying the "Trash", though you can still get the picture back if you use OS X's undelete. Surprisingly, if one selects "Keep in Place" (remember the delete is from "Recent Imports†not a user collection, etc.), Capture One deletes the photo from "Recent Imports" without putting it in the "Catalog Trashâ€. Since there's no "Folder Trash", there seems to be no one-click way to undelete the folder within Capture One without first doing a scan to find the photo that is still on the disk but not in the Catalog. This seems inconsistent with photos stored in the Catalog and a worse workflow.
Why not have a “Folder Trash" Collection for folders outside the Catalog or have the "Trash" Collection work regardless of the whether the images are in the Catalog or an external Folder? The image files would always remain in place when pictures are deleted from "Recent Imports" (just like they currently always stay in the Catalog) and skip the choice between "Keep in Place" and "Move to Trash". When Capture One's “Catalog and Folder Trash" is emptied, the pictures that have been saved in place would get moved to OS X's trash. Then there would no need for a popup when delete a single photo from "Recent Imports", just like is currently the case when the photos are stored in the Catalog.
Am I misunderstanding how the system works?
David
0
-
Hi David,
You might want to move this to the Mac thread. There may be some specific that are different between the two options.
Grant0
Post is closed for comments.
Comments
1 comment