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. ⚠️

Clicking on a folder in Library creates a C1 subfolder. Why?

Denis Mortell
If I click on any folder in the Library hierarchy, C1 8.0.2 creates a C1 subfolder containing, in turn, Cache and Settings80 subfolders.

Why does it do this? Is this normal?

Thanks.

D.
0

Comments

10 comments

Date Votes
  • Drew Altdo
    This is normal as it is the basic operation of a Session.
    Capture One, in a session workflow, will automatically look for files in the folder you choose and begin to display them in the software, in doing so it must create a preview for the image and a settings file to save any adjustments.
    0
  • Denis Mortell
    Drew,

    Thanks again.

    The thing is, I don't have a Session going for these folders that I'm aware of...

    Yes, at the top of the Library, a Session is listed in the drop down menu (the only one, in fact), but I thought that this would only relate to the (small) folder of images which it was created from?

    So, are you saying that, with this Session selected in the drop-down menu, any other folder I click on in my Images databank becomes part of that Session too?

    If so, if I was to create a new Session for any one of those folders, would this override what is happening now?

    Thanks again.

    D
    0
  • Drew Altdo
    [quote="Dinarius" wrote:
    The thing is, I don't have a Session going for these folders that I'm aware of...

    A Session does not have to be folder specific, that is the beauty of a Session.
    By clicking on a folder to browse it, you are effectively opening that folder with that session. Temporarily or, by saving as a favorite, permanently.
    As such, once a folder is accessed, the session associates with it and begins the action of prepping the contents for editing. There is no way around this in a Session workflow.

    [quote="Dinarius" wrote:
    if I was to create a new Session for any one of those folders, would this override what is happening now?


    Not at all. Again, a Session is quite simple as it references images you access and reads the sidecar files in that directory. So multiple sessions accessing the same folder of files, all read the same "database" of sidecar file adjustments. One Session does not interfere with the other.
    0
  • Denis Mortell
    Drew,

    That sounds great...so, one last question.

    If I create a Session called, for example, Images 2014 (which is what I call the master folder on my HD that contains all my Client Folders/Job Sub-folders), I don't really have to create another Session then, do I?

    However, this begs a question that relates to one of my other questions on the board, namely, applying edit presets to Imported images.

    If I want to apply the edit presets, I will still have to Import each folder, correct? Simply clicking on a folder of images and activating the Session sidecar files on it, won't do this, right?

    Apologies for all the questions, but C1 offers so many choices versus LR, at the Import stage, that getting one's head around them is a bit intimidating. 😲

    Thanks again.

    D.
    0
  • Drew Altdo
    [quote="Dinarius" wrote:
    I don't really have to create another Session then, do I?

    You don't have to but it is recommended. A Session file that is small, that references only what you need, is quick and nimble. A session file that is bloated, that references EVERY folder on your system is slow. Sessions are designed to be a 1 Shoot = 1 Session workflow as appose to a 1 Computer = 1 Session for everything.
    So, the more often you create a new session the better you'll be in terms of performance as again they're designed for on-set studio work where one product or a one day shoot uses 1 session.

    [quote="Dinarius" wrote:
    Simply clicking on a folder of images and activating the Session sidecar files on it, won't do this, right?

    Incorrect. Importing is only necessary in a Catalog workflow, to associate the Files to the Catalog. If the files already reside on your system and you are using a Session, importing is not necessary at all. There is an "import" feature but that is to help facilitate transfer from external to local, ex. a CF card to your computer.
    0
  • Denis Mortell
    Drew,

    Understood.

    In that case, the Catalog route is the way to go.

    That way, I am obliged to Import, and I can simply restrict those imports to Job Sub-Folders that I want to edit.

    Also, I won't be looking at a mountain of folders (everything on my HD, in fact) in the Library hierarchy, as I currently am via a Session. Much neater, I think.

    Basically, all I'll be seeing is what I've imported - a bit more LR-like, which is what I want.

    Make sense? I hope so!

    Thanks again.

    D.
    0
  • Drew Altdo
    [quote="Dinarius" wrote:
    Make sense? I hope so!

    Yup, sounds like you've got it.

    Just different workflow options for different requirements.
    0
  • 2eyesee
    [quote="Dinarius" wrote:
    Drew,

    Understood.

    In that case, the Catalog route is the way to go.

    That way, I am obliged to Import, and I can simply restrict those imports to Job Sub-Folders that I want to edit.

    Also, I won't be looking at a mountain of folders (everything on my HD, in fact) in the Library hierarchy, as I currently am via a Session. Much neater, I think.

    Basically, all I'll be seeing is what I've imported - a bit more LR-like, which is what I want.


    I've reached the same conclusion as you, Drew.

    The idea of importing to a Catalog didn't appeal to me, so I tried to make Sessions work. But with a Session when I browsed to a folder that had 15GB of images, Capture One spent 25 minutes building 2.5GB of previews on my hard drive. That's over the top when I only want to edit a handful of files, so I'm back to a Catalog where I just import the the files I want to edit.
    0
  • Drew Altdo
    [quote="2eyesee" wrote:
    when I browsed to a folder that had 15GB of images, Capture One spent 25 minutes building 2.5GB of previews on my hard drive


    Exactly. That workflow would be beyond the design of a session, hence the implementation of a Catalog workflow to maintain some semblance of performance.
    0
  • SFA
    [quote="Drew" wrote:
    [quote="2eyesee" wrote:
    when I browsed to a folder that had 15GB of images, Capture One spent 25 minutes building 2.5GB of previews on my hard drive


    Exactly. That workflow would be beyond the design of a session, hence the implementation of a Catalog workflow to maintain some semblance of performance.


    Maybe Drew, but I frequently work with sessions (NOT Tethered) with multiple folders each with up to 16Gb of images - sometimes more if it makes sense from an organisational point of view. No problems as far as I am concerned.

    So it may not be ideal but it's not a problem and I really don't see any evident performance difference between small and large sessions other than for Batch Prep time when I undertake a large Process run.

    So I would suggest people should try whatever they want to try to see if it works on their system. If it does, great. If not, go smaller.

    HTH.



    Grant
    0

Post is closed for comments.