CaptureOne folder created at output location

MK

• February 28, 2021 04:27

I am using Capture One with sessions. Since updating to the latest version I have noticed that whenever a file is processed/exported, a "CaptureOne" folder is created in the output directory which contains a cache folder and a settings folder. Reading through the forums this seems like an issue that has come up repeatedly with no solution.

I do not view processed JPEGs with Capture One, but I can kind of understand the logic of this folder being required to generate the previews for the "Output Folder" under "Session Folders", however it is creating a ton of cruft across my file system. This is particularly egregious for a "general" session I use, from which I export to various locations as required (local disk, cloud storage, external drives, etc.). Each of these now gets a "CaptureOne" folder.

Has anybody found an elegant workflow that avoids this issue? Are catalogues the solution? Any tips for someone switching from session to catalogues?

---

Note: I have tried a variety of ways to export/process the images as well as the two solutions in the linked post below (global filters, "File" tab of "Process Recipe" panel). Nothing seems to make any difference

• https://support.captureone.com/hc/en-us/community/posts/360012180057-CaptureOne-Folder-Inside-Processed-Location?input_string=CaptureOne%20folder%20created%20at%20output%20location

 

1

• 

  SFA

  • February 28, 2021 04:38

  Where is your output folder in relation to the rest of the folders known to the session?

  0
• 

  MK

  • February 28, 2021 17:37

  There is the standard output folder within the session directory, but I also process to other output locations such as other local folders (e.g., desktop), folders within cloud locations (e.g., OneDrive), or even external storage (e.g., NAS or USB drive).

  In the past Capture One did not create the "CaptureOne" folder in locations outside of the session directory. It now seems to be creating this folder at each output location.

  0
• 

  SFA

  • March 01, 2021 20:41

  C1 will create a Capture One folder for any image-containing folder that it accesses when editing is active. 

  So if you choose to open an "Output" folder with the browser the contents will be considered to be possible editable material and the relevant step will be taken to create thumbnails, Previews, and basically formatted edit instruction files.

  Is it possible that that is what has happened?

  If not there may be some sort of issue in the combination of C1 version, Mac OS version, and, possibly, Mac hardware version.

  I don't recall reading about such problems with Windows systems - but that may be mean that there are no problems be discovered.

  0
• 

  MK

  • March 01, 2021 20:55

  I only open the output folders with Finder.

  I have tested with outputs to a new location:

  • Import file to Capture folder
  • Move to selects via the context menu
  • Edit
  • Go to Output tab > select recipe
  • Output Location > Destination > Choose Folder...
  • Click Process
  • Open Finder and navigate to folder specified with "Choose Folder..."

  Even when I select a completely new folder and go directly from output to finder (no viewing in Capture One), a "CaptureOne" folder is created in the output directory

  I started using a MBP 16 in December 2019 and this is definitely a new issue, but I don't know if it's caused by a Mac OS update or a Capture One update.

  0

Post is closed for comments.