How to delete images completely?
Hi all,
I'm new to C1 and I'm sorry for this stupid question but I'm not able to delete pictures from both the catalogue (where I've organized them both in groups and albums) and my HD, how can I do that? When I press backspace the selected picture disappear from the C1 browser but if I check my HD it is still there ☹️
I've created my catalogue on my internal HD and I've stored my pictures on an external HD
Thank you so much
I'm new to C1 and I'm sorry for this stupid question but I'm not able to delete pictures from both the catalogue (where I've organized them both in groups and albums) and my HD, how can I do that? When I press backspace the selected picture disappear from the C1 browser but if I check my HD it is still there ☹️
I've created my catalogue on my internal HD and I've stored my pictures on an external HD
Thank you so much
0
-
When you work with sessions, deleting means it is moved to the session trash. Empty the trash and it is really gone.
When you work with catalogs, it depends on whether the image is managed or referenced. When referenced, you get the option to delete it permanently or not. When managed, it is moved to the catalog trash first, as with sessions. Empty the catalog trash.0 -
Is there not also a difference between deleting in an album and deleting directly in the "All Images" view (=Catalog)? I always thought hitting backspace while viewing in an album just deletes the image from the album but not the catalog. 0 -
[quote="EnderWiggins" wrote:
Is there not also a difference between deleting in an album and deleting directly in the "All Images" view (=Catalog)? I always thought hitting backspace while viewing in an album just deletes the image from the album but not the catalog.
In fact I've just realized thai this is exactly my problem: I'm not able to permanently delete an image when I'm in an album, I've to move to "all images" to that ...0 -
This bug seems to have been existing for years according to this post and I'm not sure if PhaseOne actually understands that this is a bug in their "design".
The issue is that when I'm browsing through an album and I want to quickly delete (NOT remove!) images, C1 is incapable of doing so. C1 can only delete an image from a higher level project or a catalog collection like "All Images". Given the fact that projects can't directly hold images but only albums and "All Images" could contain 10s or 100s of thousands of images, I would have to go search for every item to be deleted or mark them in some way that I then can filter them later for deletion. There isn't even a "Reject" rating tag (like in Aperture) available that could be used for that.
Aperture is near perfect in its DAM workflow despite lack of updates in years. The way Aperture does it right is by allowing you to actually drop images into projects and not just albums. That way a shoot can be limited to a project as opposed to an album like in C1. Of course, something similar could be achieved in C1 by only adding one album per project. But then what's the point of even having an album inside that project? - In Aperture there is also the concept of "Rejects", by marking an image with an X, which then just hides it from view but it's physically still part of the project. Yet another way to manage unwanted images directly from within the view.
Coming from Aperture where these functionalities have existed since version 1.0, I can't comprehend how C1 users are still dealing with cumbersome workarounds to quickly trim a collection. I haven't seen a place where I can file bug, so I'll just leave my suggestion here for now and hope one of the mods will file this as a proper bug report. The issue described above could be fixed in two ways;
- with a relatively low LOE: when within an album, allow for an additional action with pressed command-delete or command-option-delete shortcut to DELETE an image from the collection/project. Keep regular delete key action to merely REMOVE an image from an album.
- with a high LOE: implement Aperture's project-level image store, so that projects can become standalone collections.0 -
The workaround - which David admitted in last week's webinar is a bit awkward - is to choose a colour tag for permanent deletes and apply to files in user collections. You can then go to the Folders view, select the reds or whatever and blooter them from there.
In Aperture you rejected them and then later emptied the trash, also a two-stage process, but it did have the advantage that rejection made the things invisible.
Also I'm not sure how this works with multiple variants, but I'm getting there...
David Edge0 -
[quote="dredlew" wrote:
Coming from Aperture where these functionalities have existed since version 1.0, I can't comprehend how C1 users are still dealing with cumbersome workarounds to quickly trim a collection. I haven't seen a place where I can file bug, so I'll just leave my suggestion here for now and hope one of the mods will file this as a proper bug report. The issue described above could be fixed in two ways;
- with a relatively low LOE: when within an album, allow for an additional action with pressed command-delete or command-option-delete shortcut to DELETE an image from the collection/project. Keep regular delete key action to merely REMOVE an image from an album.
- with a high LOE: implement Aperture's project-level image store, so that projects can become standalone collections.
Open a support case. Tell them what you just told us. That way the info gets to the people that need to know. C1 was around LONG before integrated DAM became fashionable. But they are learning. The support case will help them along that path.0 -
[quote="NN635666759823044900UL" wrote:
In Aperture you rejected them and then later emptied the trash, also a two-stage process, but it did have the advantage that rejection made the things invisible.
Rather as in a C1 Session then? Although in a session there is also the possibility to delete directly with no trash can involved. I don't know anything much about catalogues.
One would, presumably, need some sort of warning mechanism in case the original file existed in more than one project/collection/album/catalog/session (assuming that it is referenced rather than managed) and was not also available to other applications or, potentially in some situations, other users.
Grant0 -
[quote="David Edge" wrote:
The workaround - which David admitted in last week's webinar is a bit awkward - is to choose a colour tag for permanent deletes and apply to files in user collections. You can then go to the Folders view, select the reds or whatever and blooter them from there.
In Aperture you rejected them and then later emptied the trash, also a two-stage process, but it did have the advantage that rejection made the things invisible.
Also I'm not sure how this works with multiple variants, but I'm getting there...
David, as I mentioned in my post there are two workarounds to make it happen but they're either silly or not productive. In Aperture you can do these "workarounds" too but they are not needed since you can directly store images into a project and delete from the same. Projects function differently in Aperture than in C1, that's the missing point here.
The concept of Aperture's rejection is simply that you don't want to delete the images permanently, you just want to get them out of sight. Again something that is not possible within C1.
Personally, until this bug is addressed, I'll go with the one-album-per-project workaround and edit with the project (instead of the album) selected, where deletion is possible.0 -
[quote="SteveCase" wrote:
Open a support case. Tell them what you just told us. That way the info gets to the people that need to know. C1 was around LONG before integrated DAM became fashionable. But they are learning. The support case will help them along that path.
Ok thanks, will do.0 -
Done, support case #178580 has been opened. 0 -
[quote="David Edge" wrote:
The workaround - which David admitted in last week's webinar is a bit awkward - is to choose a colour tag for permanent deletes and apply to files in user collections. You can then go to the Folders view, select the reds or whatever and blooter them from there.
The reason the software is designed as such, is because we don't want users to delete their originals by accident, or to delete an image from the catalog by accident. The workaround mentioned above is actually not a bad way to work. Also, right after import, you can just browse through the Recent Import folder and delete all those images you don't want to keep.
However, as this has been an issue for a lot of end-users for some time, I will make a feature request to our R&D team for further consideration on how images can be deleted from a catalog. We always want to improve the experience and workflow for our end-users and your feedback is always appreciated.0 -
Juk, thanks for the reply here so others are kept up-to-date. As I mentioned, the album is fine IF project-level image storage would exist in C1. Since that is lacking, the album should perform further actions. As for accidental deletion, images don't get deleted permanently anyway, they only get moved into the application's trash and can be recovered at any time. No worries there.
Workarounds should not be needed to accomplish simple deletion from the catalog. Not to sound repetitive, but the best way to understand the issue or the correct way it should work is by opening up Aperture and performing the same setup there. Please let me know if this needs further explanation.
Thanks for forwarding this to the right people.0 -
I'm migrating to C1 from "that other now discontinued" package. Spent a few hours trying to figure out how "Trash" works in C1. Found this post and agree that the C1 implementation just doesn't flow. Adding a comment to this post in support of the comments above and to keep it alive for the moderators. Thanks to dredlew for detailing the issue. 0 -
Same here. Just migrated from Aperture to C1 and must admit I'm quite puzzled by the "delete" challenge. To be honest I must read it all carefully again, because in MY projects and even under all pictures the "delete" menu item is still greyed out.
(I considered a hundred things before deciding to switch to C1 - but I never imagined that deleting a picture could turn into a multi-step process...)
Can someone maybe explain how it's really meant to work in C1 - I mean both, technically and some workflow best practices?I guess, since C1 has been around for so long with such excellent reputation, there will likely be something to learn for us Aperture-converts, even if the delete-tango appears awkward at first glance...
Thanks! Chris0 -
The "solution" for me is not to use User Collections at all and to work solely with the folder structure. C1 is a dysfunctional as Lightroom in its limitations on collections. 0 -
I too am a refugee from Aperture but I am finding the editing capabilities of C1 to be so much better that I am persevering, and trying to create a workflow that I can at least remember from one day to the next.
Here is how I deal with deleting images in a way that approaches the intuitive ways of Aperture.
First I store all my images as referenced, just as I did with Aperture, This keeps the catalogue small and means that I can quickly copy it to my laptop for use on the road and as an extra backup.
Then after importing images I search for all images which are not colour coded red.
This makes no difference since I only use red for images which I want to delete.
Now I step through all the newly imported stuff and press the - key for each one I want to delete.
The image disappears because - is a shortcut for red, just like the Aperture reject command.
Finally before closing the program I go to All images and search for images that are red and delete them.
I hope that this helps.0 -
It does take some getting used to, but apparently they are working on it.
The preceding post pretty much sums it up, though I have added a few twists for my own benefit:
- I've mapped the keyboard shortcut Control-9 to the 'set Red tag' command, since that's what I used to use to mark an image as a reject in Aperture.
- All my imports go into a 'to be filed' album, which has a filter set on it to exclude any images with a Red tag. That way, when I hit Control-9, the selected image immediately disappears.
- At the top level of my catalog, I have a Smart Album named 'Rejected' whose filter is set to display /only/ images with a Red tag. That way, I can just click on that folder to locate all the rejected images; this is similar to the Rejected library folder in Aperture.
- Once I've clicked on my 'Rejected' Smart Album, I can do a Select All and hit the Delete key. Since this folder is at the top level of the Catalog, I get the alert dialog that asks me whether I want to move the referenced images (and all my images are referenced) to the Trash. This is equivalent to hitting Command-Delete in Aperture.
Hope that helps a bit.
-Mike0 -
Thanks for the Rejected smart album idea Mike.
That is much nicer than selecting the reds from All images.0
Post ist für Kommentare geschlossen.
Kommentare
18 Kommentare