Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Sessions - Capture and Output Subfolders

Kenneth

Hello,

just pulled the plug and purchased c1 21 for raw conv + tethered, after a few trials over the past few years. Would like to get rid of some other software/scripts/manual hacks and ask for your insight.

My existing image organization is as following

<job>/Capture/<Camera name> -> include raw's from different cameras, as well as jpeg

<job>/Selects/ -> any images that goes to Social or Print

<job>/Output/Social -> images that goes to Instagram, Facebook

<job>/Output/Print -> Images for print 

<job>/Trash

I use a similar organization for mp4/mov's clips, mainly due to my backup/cloud setup.

I consider to use C1 catalog for all sessions <job>/Selects, not decided yet.  

Question - Is if possible to view all images in Capture and Output subfolders in Sessions?

I can navigate, using the System Folders, to the Session <job name>, select Capture, select Camera, .. but its super inefficient, and somewhat of a C1 surprise.

Each <job> / projects is less than 1K images, all incl.  

Thanks,

Kenneth

 

 

0

Comments

5 comments

Date Votes
  • Ian Wilson
    Moderator
    Top Commenter

    You can add any folder you like as a session favourite, so then you won't need to navigate to it every time via the System Folders part of the Library tool. Also this has the advantage that images in any folders you include in Session Favourites will appear in the All Images collection for that session.

    Ian 

    1
  • SFA

    As Ian has said.

    However, bear in mind that if you select the "Output" images folder and the contents of the folders match the criteria for them to be editable in Capture One (which in the situation you describe will probably be "true"), the session will create a "CaptureOne" subfolder to the "Output" folder, and prepare subfolder in that folder for edit files, previews and thumbnails.

    You may want to consider whether that is desirable.

    Moreover I one has Output a file for a specific purpose it may not always be useful to view it through an editor. More likely a browser would be more appropriate for on-line postings. For print image files I guess whatever you use to view with should be capable of handling any possible nuance of colour management, etc.

    As an alternative, you can use the Session Library "Output Location" link to go to the session's Output Location folder in the system folders directly. If you have used subfolders in that Location for "Social" and "Print" then those folders will be available at that point and the content can be viewed via non-C1 viwieing options and therefore no edit and cache folder will be introduced.

     

    Note that I refer to "Output Location" link above.

    By default this will point to the Output folder, set up within the Session folder structure when the session is created. However, in the library it is a link since it is possible to select a different folder to be the "Output" folder for the session as and when one's requirements might change. The selected folder can be anywhere.

    Also, if the most common purpose of viewing the Output folders is mainly to make sure they are populating or something similar, it is entirely possible to do that from within the Output definition options during an output process. That too will, by default, jump to the system application preferences for viewing rather than open the folders in C1 and treat them as sources for editable images.

    1
  • Kenneth

    Thanks Ian, and SFA.

    Ian, thanks for the suggestion on using session favorites I think it will do the trick for new jobs and projects.  It will be too manual to use for my existing projects.  

    SFA, thanks for the insight ill try out the output location. I used an export folder with LR some time ago but it was a bit "detached".   I use rsync to move things around (mac-ssd/imac-ssd|raid->nas), its easy to exclude unwanted files e.g. CaptureOne in the outputs folder so perhaps that is the simplest.

    Thanks so much !

    Kenneth

    0
  • SFA

    Kenneth,

    If you are moving sessions around there are a couple of things to consider.

    If you keep all of the images somewhere inside the session folder structure the entire session can be copied as a single entity by copying the top level folder. Any subfolder you add within the default structure will also be copied.

    If you connect a session to folders outside the folder structure you can make them "Favourites" so that their existence and current location are known to the session BUT they will not be copied if you copy the Session folder structure to another location. The session database will still know about them and opening images in those folder should still work providing they are accessible from the new location - but bear in mind that might be across a network and that all versions of the session, wherever they now are found, will be referencing the same files and edits (a least in concept but things may be a little more involved and separated if you have multiple version of C1 on different systems and are referencing shared folders.)

    Note that you can access a folder outside a session folder structure and edit images WITHOUT making the folder a Favourite.  In that event the Session Database will not automatically retain knowledge of that folder's existence and will have no link to it pre-saved for future selection. However, the edits will still exist in sub-folders of the image's folder and can be/will be used if the Image folder is accessed by C1 in session mode at some future point.

    Catalogs require an Import process of some sort before images can be edited. However there is an option to make use of any discovered pre-existing C1 edits (from a session for example) as part of the import process. Another factor that you may wish to bear in mind when defining and refining synchonisation around different locations. 

     

    Personally I try to keep things simple. 

    Edit on a drive within a single device. Back up the originals somewhere. When the session is pretty much done (or has a lot of time invested if it was a large shoot) I copy to a second location, these days usually my NAS.  For operational speed I continue to work on the PC. When I feel that the session is likely complete for most practical purposes, I will again copy the whole session to the NAS and then delete the previous NAS copy and remove the PC copy if I decide to reclaim the disk space. 

    After that I do not expect to undertake a lot of activity on the session so editing speed from the NAS will suffice.

    On rare occasions I may copy everything back from the NAS to the PC if some further bulk editing with speed seems desirable.

    If working with catalogs there are some different considerations to take into account.

    0
  • Kenneth

    Thanks SFA. Im still in early days with C1, raw and tethered mainly. I do have a methodology and try to figure out how C1 fit in and if i can remove some tasks and simplify things while not having to change everything.  Your insight is very good - thank you so much!!

    Kenneth

    0

Post is closed for comments.