Import: Subfolder as Project Name?
Hi there. Switched Aperture user here, trying to wrap my head around the differences in importing from camera cards with Capture One. I maintain separate libraries/catalogs by year, using referenced masters, and I also keep all the master files in folders by year with subfolders for each event/project.
Anyway, I'd plug in the card, then in Aperture I'd have it import directly into a new project that I'd name manually right there in the import panel (such as "06-27-15 Hyde Park Blast Criterium"). I'd only have to pick the right parent folder to store the files in (like "2015 Sports") and Aperture would create the subfolder name the same as the project, and then all the photos go into that project. Thus the file structure in my "2015 Sports" folder on my hard drive directly mirrors my "2015 Sports" Aperture Library with each project corresponding to a particular folder, and they're all named the same.
In Capture One, I can't import directly into a project, since it's not a "container" per se, so I have to remember to first create the project, and an album inside (I usually call it "All Photos") and make sure that album is selected before I click on the import button. That's clumsy, but at least workable. Once the import panel is open, I can choose the same "2015 Sports" or whatever folder to store the files in, but none of the subfolder tokens seem to have the ability to pick up on the project name. So I have to manually reenter the name of the project into the subfolder field. Again it's workable, but it's a bunch of extra steps, and there's a chance the folder could be named different than the project, which maybe isn't a problem, but it makes me nervous.
Is there a better way to streamline this, or a different approach I should be taking? It just feels too "manual" and fraught with potential mistakes for comfort.
Anyway, I'd plug in the card, then in Aperture I'd have it import directly into a new project that I'd name manually right there in the import panel (such as "06-27-15 Hyde Park Blast Criterium"). I'd only have to pick the right parent folder to store the files in (like "2015 Sports") and Aperture would create the subfolder name the same as the project, and then all the photos go into that project. Thus the file structure in my "2015 Sports" folder on my hard drive directly mirrors my "2015 Sports" Aperture Library with each project corresponding to a particular folder, and they're all named the same.
In Capture One, I can't import directly into a project, since it's not a "container" per se, so I have to remember to first create the project, and an album inside (I usually call it "All Photos") and make sure that album is selected before I click on the import button. That's clumsy, but at least workable. Once the import panel is open, I can choose the same "2015 Sports" or whatever folder to store the files in, but none of the subfolder tokens seem to have the ability to pick up on the project name. So I have to manually reenter the name of the project into the subfolder field. Again it's workable, but it's a bunch of extra steps, and there's a chance the folder could be named different than the project, which maybe isn't a problem, but it makes me nervous.
Is there a better way to streamline this, or a different approach I should be taking? It just feels too "manual" and fraught with potential mistakes for comfort.
0
-
What I do is I have a group and a project called Incoming, and inside Incoming Project one or albums, one of which is called Incoming, and others called Sort_A, Sort_B and so forth. When I upload from the camera, depending on the contents (single topic, multi topic) the images first end up in one of these albums.
Then I sort images into topics, bursts, brackets and so forth, delete unusable images, add keywords, and then finally move them to the final destination, which I may do by dragging the images or by dragging the album.0 -
You might like to look into the potential of using a Session as your first point of import.
Do the work of selecting and processing in the session until you are satisfied with what you have, then take it into the Catalog if you feel the need to do so.
I use sessions not Catalogs for my events. When I started using C1 it did not have Catalogs. My other favoured RAW converter/editor also does not have catalog functionality so the two can easily co-exist, unlike the experience I had in the early days of LightRoom. (I can't comment on Aperture).
If you usually work on Projects as you have described I would suggest that the Session concept is probably almost perfect for your needs to get the shoot processed. Then adding the results to the catalog gives you the advantages of a catalog it you need it without the overhead of performing edits in an ever growing database and collection of images.
There are some videos and tutorials around that can help to set the scene for you.
HTH.
Grant0 -
I'm not sure about sessions, but I honestly haven't read up a lot about them. Since I've never shot tethered I don't have the familiarity with that sort of a workflow to try to apply it to a non-tethered situation. Nevertheless, it looks like what might save a few steps at import could hamper usability during the editing phase. The main reason is because while I may be working in just one specific project at a time, I'll routinely have photo orders come in which I'll have to pull from multiple projects, and I usually reference older projects to copy things like album names in and such. While I understand that multiple sessions can be opened at a time, it doesn't appear to be as robust as the catalog where everything is available always. 0
Post is closed for comments.
Comments
3 comments