How to delete RAW files to save disk space
Please excuse my ignorance. I'm using C1 Pro for Sony v9.2 on Windows 8.2. I often take lots of pics of children in the family, many of which are simply not worth keeping due to poor focus, funny faces, etc. My usual setting is RAW+JPEG, since I love the C1 software and (now and again) the photos may be worth the editing.
My question is: What is the best way to save disk space by deleting the RAW files, while perhaps saving the .JPGs? Deleting low-rated files in C1 using the trashcan or the delete key does not remove the file from File Explorer. Do I need to review and delete pics in Windows before importing into a C1 catalog?
My question is: What is the best way to save disk space by deleting the RAW files, while perhaps saving the .JPGs? Deleting low-rated files in C1 using the trashcan or the delete key does not remove the file from File Explorer. Do I need to review and delete pics in Windows before importing into a C1 catalog?
0
-
Have you emptied the C1 trash folder?
Ian0 -
The trashcan on the bar at the top of the main window? Yes I have.
This can't be an unusual request: There must be others out there who have no reason to save obviously flawed original files and want to delete them after review in C1.0 -
NN635595615747468081UL wrote:
The trashcan on the bar at the top of the main window? Yes I have.
This can't be an unusual request: There must be others out there who have no reason to save obviously flawed original files and want to delete them after review in C1.
I'm not a regular catalogue user. I use sessions which, in essence, is not dissimilar to working in a catalog with referenced files.
If one uses a session by accessing a folder somewhere in the file system, especially if it is not actually in the nominal "Session Folders", there is an open possibility that file could be part of some other session. Or Catalog.
It may be referenced by an entirely different Editor and RAW file converter. There is no reason to suppose that any programs are able to maintain knowledge about which software applications, other than themselves, is working with the same file(s).
If the original RAW file has been imported to a C1 catalogue and you choose to delete it from the catalogue (not just from some sub-set collection) it would seem reasonable to use the option to get rid of it. If it is a referenced file I would argue that disposing of it is somewhat more risky. However other software designers may take a different view on that so one's experiences may be at variance with C1's approach.
That said there is in the File menu (at least when using Sessions) a "Delete Permanently" option that, if you have the Warnings enabled, will advise that the action will delete the file(s) from the machine.
One assumes this may be what you want to do, although personally I would prefer to move to Trash first and then use the Delete from Machine on the bulk selection from the Trash folder when ready to commit to that action.
Does that help?
Grant0 -
Thanks for your thoughtful reply, Grant.
I usually import to a catalog, and there is a "delete permanently" option under FILE there, as well. Unfortunately it simply removes files from the catalog and not from disk. Similarly, if I import to a session, files only disappear from the session sub file when I "permanently delete" them from there.
In either case there is still a 24 MB file still taking up disk space in the Windows file system.
Ted0 -
Let's step back a little here.
What are you doing within your workflow when you open the files in C1?
I'll be frank and say I rarely delete files unless they are evidently rubbish. Saving space is not a big issue in my opinion compared to the amount of space that will be used anyway, especially if using RAW files. So my breadth of practical experience may be less than many others can offer.
However, using sessions I can import and image, choose to delete it and either go along the Trashcan route or take a "Delete Permanently". Or, of course, as a Windows user use the Windows file system.
The options that will work form within C1 will work with everything known to C1 and managed by C1.
So if I import directly from a memory card C1 will know about the file as it is referenced by a the session into whish I imported it (and possibly other sessions form which I may also be referencing the file - but always from each session individually.)
If I have told C1 to create a backup folder of all the imported images as they are imported that is a separate activity. The result is just a backup folder of images somewhere an nothing then managed directly by C1 or the session. Sensibly it will be a separate disk, probably removable. (Note that I very rarely use the backup that way at the point of import.)
After a few days (or less) of working on a session I will usually back up the entire session to a separate drive. Meanwhile my "backup" is the original memory card.
If I am travelling or undertaking a large multi-day shoot I will copy the files off the memory cards to a travel computer's drive at least daily. Once that process has finished I back up the newly folders to an external drive.
In my case, when travelling, I rarely need to consider doing much processing on the day - a simple "lightweight" viewer and editor suffice for the trip and, usually, C1 only comes into play when back at base.
So I will copy take one of my saved sets - usually from the portable disk drive - and import that to a C1 session. In effect that gives me three sets of copies of the files. (4 if I have not needed to re-use the memory cards.)
However I know that for the travel equipment based copies I can, when the need arises, delete them and re-use the space.
In all cases anything that is not in a C1 session (or imported INTO a Catalogue) will need to be thought of as merely potential external data sources and managed directly - including any culling requirements. This becomes even more the case when multiple back up copies are initially saved AND when, as I would recommend, useful file names are given to imported files thus avoiding the potential for duplicate file names causing confusion within C1 (or another application). Those names may well not be used for any earlier backup sets making identification of "matching" files somewhat more tedious although these days perhaps not unfeasible.
So, after that ramble, If you are "importing" files AND retaining an external backup set of the original out of camera results, only the imports can realistically be managed within C1.
What I tend to do with my sessions is replace entire sessions from time to time as work on then progresses. As long as the original files have been imported to the session folder structure, coping the entire structure means that all adds and deletes will be applied to the new backup and I can, after a successful copy is completed, simply delete the previous one. Crude but effective and deals with the primary backup. My backstop backup (just the files as captured) can eventually be binned as the results of a completed session will end up on 2 external drives as a minimum. At that point the majority of an delete activities will be through the operating system rather then the application(s). Yes it can get more complicated if you use more than one editor application.
Working with a single catch-all catalogue suggests a different approach should be applied. I'll leave it to others to describe what they do in that case.
These things often come down to personal preferences. I suspect all we can do as individuals is distil the information available to us and work out what to do to give us most comfort and satisfaction in the task.
I'm not too concerned about disk space - capacity seems to grow and price reduce at a rate that has my need for storage and hardware updating periods running quite well aligned. On the other hand I'm not invested in bodies that are creating producing large files on a regular basis and I rarely use a TIFF intermediary or output file these days so my disk capacity considerations may be somewhat lower priority than most people will have.
HTH.
Grant0 -
I think CO has a number of issues with deleting image files that need to be resolved to accommodate varying work flow approaches. As a DAM tool it should provide any and all options for deleting images. LR and Aperture do. And this is not complicated stuff.
And it seems to me that the cost of storage is not the issue. Even the best of us get some garbage shots from time to time that have no artistic or documentary value at all. Heck, the other day I bumped the shutter release and took three 24mp images of the ground. There is no reason to keep such images and CO should give us the ability to delete them regardless of where they reside (as long as it can access the source, of course). These should be presented as options with the appropriate warnings if necessary.
Options should include:
Delete from album. Image remains in catalog and its resident source. There should be a specific command/button for this.
Delete from catalog. There should be a specific command for this along with an option to delete the source file at the system level as well (move into system trash) or simply remove it from the catalog into CO trash.
Further, you should be able to do this regardless of where you are working. In other words, if you are viewing and image within a User Collection album, you should have all of these options available. As it stands, within a User Collection you can _only_ remove the image from that album. It remains in the CO Catalog. This is a real nuisance.
I'm not complaining here. I know Capture One is a work in progress as a DAM system. But these capabilities should be on the to-do list.0 -
NN635595615747468081UL wrote:
What is the best way to save disk space by deleting the RAW files
Review/delete using the file system and (in my case), Irfanview - Mac users will have an equivalent image viewer - before exposing the remaining files to a Raw converter.0 -
Now I'm a bit confused. I simply hit the delete button and the file goes into the trash. When I empty the trash - the file is gone. Are we talking about some sort of automated batch delete of multiple raw files, while keeping the jpg? 0 -
Pavel wrote:
Now I'm a bit confused. I simply hit the delete button and the file goes into the trash. When I empty the trash - the file is gone. Are we talking about some sort of automated batch delete of multiple raw files, while keeping the jpg?
You and me both. I have spent the last few weeks going through my 38000 picture catalogue and have successfully deleted 7000 or so files. I select the files I want to delete use one of the many ways of selecting the delete function and a window pops up giving me the choice of removing reference to the picture(s) from the catalogue or deleting completely. One point, deleting completely bypasses the system recycle bin so the file is gone for good. 🤓0 -
I'm desperately searching for a way to delete multiple files at once. Once a group of files is selected, if any of the delete key combinations are invoked, C1 only deletes the first file selected. Selecting with shift-click as indicated in the manual still only deletes one file.
Is there a way to select and delete multiple files at once?
Thanks!
OSX 10.11.6 / C1 10.0.0.1930 -
zeno2358,
viewtopic.php?f=52&t=24013&p=117480#p117480
Regards,
Hans0 -
Worked like a charm.
Thanks!0
Post is closed for comments.
Comments
12 comments