CaptureOne Folder Inside Processed Location

Philip14

• 2014年01月22日 20:49

Since version 7 came out it makes a "CaptureOne" folder in whatever you set your processed folder to be. Why?

Aren't the settings for the files already kept in the "CaptureOne" folder inside the Captures folder? Or in the EIP itself? Why do we need this cluttering up the processed folder? I don't see any use for it at all.
If I clear the Processed History then next time Capture One will make the folder again and all those little files inside of it again.

We back up to tape since we do such high volume of images here and the backup software (Retrospect) will show me those new files all the time.

Is there a way to disable it?

0

• 

  Drew Altdo

  • 2014年01月23日 14:13

  The Output Folder is part of the Session.
  As the folder is part of the session it is actively accessed by Capture One.
  
  All supported files, in folders actively accessed by the Capture One Session will preemptively create a "CaptureOne" folder.
  
  If you do not want Capture One to browse the files and create preemptive proxy files, then ensure the files are not supported by Capture One. If you are processing TIFFs or JPEGs please turn on the Global Filter to hide these types of files. Capture One will ignore them and then ignore the files so no Proxy file is created.
  If you want to avoid the default "CaptureOne" folder all together then process to a specific folder set in the "File" menu of the Process Recipe. The folder not being associated with the session (favorites or Output/Selects shortcut) will then never be associated with the session and no folder will be created.

  0
• 

  Philip14

  • 2014年01月23日 16:08

  Thanks Drew, I have tried what you told me (the "File" tab under the processing menu) but our workflow is a bit different. We shoot in the studio, backup, etc and then the retouchers will grab the individual capture folders of the session pertaining to the specific thing we need to work on and then process to a "Processed Files" folder on a fast RAID. So we are not bring over complete sessions because a lot of the times we do not need them.
  
  I don't under stand why does the "Processed Files" folder then needs to have proxies from processed files created in there. Especially since there are a lot of proxies in there that are very old. I have cleared the History cache and tossed that whole folder and then it just makes it all again. Not sure why, I think it is a bug.

  0
• 

  Drew Altdo

  • 2014年01月24日 08:42

  [quote="Philip14" wrote:
  I don't under stand why does the "Processed Files" folder then needs to have proxies from processed files created in there. Especially since there are a lot of proxies in there that are very old... Not sure why, I think it is a bug.

  
  
  Sorry if I didn't explain the why clearly. Since the Output Folder is part of the session, it is mapped to the workflow and the folder is actively browsed. The folder being actively browsed see's files that it can read and builds Proxy images in anticipation that they may be viewed by the user in Capture One. It's a preemptive step, not a bug.

  0

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