メインコンテンツへスキップ

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

Automatic indexing of non-capture one folders

コメント

4件のコメント

  • Paul Steunebrink
    This is not the default behavior of CO6. It is not indexing by the way, but I understand what you refer to.

    My first thought is that either the folders are sub folders of your current session and/or you have listed them as session favorites.
    0
  • NNN634581582418967722
    Steps that I have done:

    - Launch CaptureOne
    - Open new session - with specific location on HDD, one folder, no sub-folders, different place to where I keep any of my photographs (processing_photographs/captureonesession)
    - then navigate to another folder with photographs from Mamiya RZ67 (photography/models/sample)
    (Capture creates it's own sub-folders there, that's fine)
    - in all other folders in the same directory (not sub-folders) in the same root in "photography" folder, new captureone sub-folders start to appear... photography/models/model1 (etc) AND ALSO one folder up, photography/dancing (for example) where I have never navigated in the software - the indexing folder appears.

    Also - all folders in "processing_photographs" that have any type of photographs inside start getting indexed too. These are on the same level as "captureonesession" - for example, processing_photographs/park, processing_photographs/newcastle, etc.

    None of the folders are listed as favorites, I don't open any of the other folders in CaptureOne - it seems, that just the existence of the folders (where one specific folder where I need to work) triggers automatic indexing - how do I switch it off? It's extremely counter-productive in my workflow.

    At the moment, I am deleting the folders manually before I run backup - as it creates thousands of files.

    Thank you for your help.
    0
  • Ario
    Several months back I have opened a Support Case at Phase One on the very same subject (i guess):
    "I use to import files into a CO Session from my Raw File Archive and I noticed that at every import CO create a folder named CaptureOne containing Cache and Setting inside the folder from which I'm importing the raw files and in this way the Raw File Archive is being populated with CO folders which I would prefer to have inside the session only.
    Is there any way to avoid the above?"


    and the following are some of the answers I got from them:

    "Hi Ario,

    No there is no way to avoid this unfortunately.
    .....
    If you would like centralised cache I can add it to the feature request list?
    .....
    Some people have asked for it before. I have added you as a +1 vote."
    0
  • Keith Reeder
    Thats not the same, Ario - what you describe is Capture One's normal behaviour (and no, I don't like it either): the original post describes something different.
    0

投稿コメントは受け付けていません。