Creating a session: C1 creates folders/files on source drive

FirstName LastName

• July 02, 2022 12:51

Being new to C1 22 Win, I stumbled across a confusing effect when uploading picture files from a portable HDD to session folders on my computer:

I defined a destination folder on my PC on an internal SSD named E:. This worked as expected; C1 saved all img files on this drive.

The source drive for the uploading process however isn't a memory card, but a portable HDD (F:). Defining the upload source again worked as expected, BUT C1 created subfolders in every source image folder, i.e. on the source drive: <Capture One/Settings153> and <Capture One/Cache>. 

<Capture One/Cache> contains two subfolders - <Proxies> (with one each *.cof and *.cop file for every image) and <Thumbnails> (with one *.cot file for every image).

<Capture One/Settings153> contains settings files for every image file.

Questions:

(1) Shouldn't these files be saved in the session directory, not in the source directory? Is this the result of some kind of mistake I made when uploading the images to a session on my PC ?

(2) Can I delete these files/directories together with the source files on the portable HDD as I would have done when directly uploading from my camera's memory card? 

0

• 

  Permanently deleted user

  • July 02, 2022 19:49

  I'm not sure what you really did but it is normal that a session adds subfolders to the directory containing the session images (for settings/edits and for building up a cache to load image previews faster).

  Did you use the import feature to copy the images to the destination folder structure?

  If you deleted the subfolders on the external drive, you would loose your edits. Deleting the source files might even result in the loss of the images, in case that you did not verify that they are stored somewhere else as well...

  0
• 

  FirstName LastName

  • July 03, 2022 11:36

  I did use the normal importing process, and I verified that my original image files actually also reside in the C1 folder structure on my PC.

  I find it strange that the auxiliary files/folders have been created on the source (ext. HDD), but not on the import destination (C1 folders on my PC). Shouldn't they rather reside in the import target structure?

  0
• 

  OddS.

  • July 03, 2022 12:15

  > Nameless user: I did use the normal importing process

  Capture One session mode creates those (sub)folders in every image folder the session visits. It is not an import thing, they indicate that you likely had a Capture One session "peek" into that folder prior to import. In a normal import, wouldn't you just activate the Import function and navigate to the source folder from there?

  I never use the Capture One session Import, I use some other tool to copy image files from source into the session's Capture folder. Capture One will automagically find and register the files.

  0

Post is closed for comments.