Capture One creating files everywhere...
Hi,
First let me tell you I love Capture One for many reasons, but the output it generates is what keeps me going back to it. That being said, there is for me one major annoying thing that Capture One does, it creates CaptureOne and files everywhere...
In each folder where I have RAW files, Capture One add a folder and fills it with preview or whatever... It is not compatible with my workflow and I kinda hate that.
My question is : Is there any way to tell Capture One to store all these files at the same place instead? I want my RAW folder structure the remain as clean as possible and contain "only" RAW files.
Thank you.
C
First let me tell you I love Capture One for many reasons, but the output it generates is what keeps me going back to it. That being said, there is for me one major annoying thing that Capture One does, it creates CaptureOne and files everywhere...
In each folder where I have RAW files, Capture One add a folder and fills it with preview or whatever... It is not compatible with my workflow and I kinda hate that.
My question is : Is there any way to tell Capture One to store all these files at the same place instead? I want my RAW folder structure the remain as clean as possible and contain "only" RAW files.
Thank you.
C
0
-
Hi,
The scenario you describe is kind of unavoidable with sessions. The solution in this case is to use the catalog - with referenced files. Settings and cache will then be made in the catalog rather than local to each folder of RAWS.0 -
Catalogs?!
I've read about it on the feature page but never tried it, my version of Capture One doesn't support them it seems... Maybe time to update.
I'll get the trial.
Thx.0 -
But C1 is also creating folders inside the output-folders. Why? 0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare