Zum Hauptinhalt gehen

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

Session Capture - Subfolders and Favourites

Kommentare

4 Kommentare

  • SFA
    The sessions folders are not discrete physical folders - they are pointers to the folder that are the current targets for the function. Of course by default when creating a session a folder called Capture is actually created as are the other three liseted as Session folders - but the conceptual "folder" can be pointed elsewhere as required. This they always point to a single folder.

    For your second question - when you open a folder in C1 it will automatically seek out any files it can process and create some sub-folders that will, amongst other things, establish basic edit files ready for use, thumbnails for the browser and preview files. The preview files may well involve some significant processing depending on the size of the RAW/DNG/TIFF/Etc. files found and the size of the Preview you have set for the default.

    The location of these files - for example on an external drive - may also influence the processing speed and the system's capacity to allow parallel activities. The same it true of the Import process. In effect the processing in progress is likely to be much the same.

    On my system, using what was an reasonably fast workbook i7 processor from about 3 years ago, an internal SSD (or now 3 of them) and a sensible amount of memory opening folders or importing are relatively fast activities for the files from my cameras (nothing gigantic) and I can start to review files whilst the initial processing continues in the background. However being wary of potential glitches (from Windows rather than C1) I tend to wait until the activity is complete since, as you mention, it takes a few seconds - maybe a minute or two - and working in the images at the same time will tend to slow things down anyway so there is not enough to be gained to make the chance of confusing Windows worth risking.

    HTH.


    Grant
    0
  • Westdale
    Helpful, Grant, thanks,... but....
    If one points the capture folder somewhere outside the session folder, it breaks the idea of being able to move the session folder as a physical unit containing all Raw and Edits?
    I am gradually exporting all my catalogues [which are recommended for newcomers to C1] to sessions for exactly this reason...that some day, I shall need to move these files to a new computer - and possibly a different drive letter etc.
    I am very uncomfortable with the idea of having structure in one place and data in another as one has to mentally manage such a move ( I really wish that CaptureOne worked with sidecar files .. but that is another story! ). The session folder is I think as near as I can get to a coherent unit.
    0
  • SFA
    You have control over where the folders related to the session should be ...

    There are, in effect, 2 concepts of sessions (informally).

    One is where you shoot a "project" - a studio session, event, holiday, etc. - and as part of the related import activity (or capture in tethered shooting parlance) group everything together in a Master folder.

    Since V8 (iirc) C1 has consolidated what were 2 session concepts - The Tethered session and the Other Type session, which had different default folders setups - into a single concept default session structure. The Capture folder now appears in both.

    What I learned after a while of use was that if the session was one I wanted to manage as a session (I shoot quite a few events so a discrete session or the event makes sense.) the sensible thing to do was to create subfolders under the Capture folder in the session folder structure and then everything would be in one place.

    However for more random activities or, to put that another way, when I want to process images that are not really related to a special project of any kind, I just have a generic session and browser to the folder in question as and when required.

    In that situation it would not be so easy to manage the session as a single "thing" should I want to move it. But then in effect I had already made the decision that I would be unlikely to want to manage it in that way so that's fine.

    It could certainly get more complicated than that - there is for example no obvious reason why a folder could not be associated with more than one session. In which case folder and file management does indeed become a fun challenge (unless one duplicates image folders - along with their sub folders - of course.)

    So just avoid splitting the structure and all should work well with minimal effort.

    If you feel forced to split the structure then you may indeed run the risk of the folders becoming orphaned but there should not be too much effort involved with identifying and enacting a process to overcome that "breakage" efficiently should it occur at some future point. Carefully considered naming of folders (and indeed files) should make them easily re-discoverable and once found re-connection to the session information database ought to be easy enough.


    HTH.


    Grant
    0
  • Westdale
    Yes - that sounds familiar .. I now have moved my big catalogue to be 'italy2015', 'london' and others as "sessions-in-one-place" and was going to have one 'misc' catalogue to deal with the odds and ends - but that may now be a session as you describe ... thanks - I shall think on it!
    0

Post ist für Kommentare geschlossen.