Unwanted Cache and other folders created by C1
I am testing Capture One (C1) 5.2.1.
When I point C1 at my photo database folders, it creates many unwanted new folders (cache and others). I cannot find a way to stop this behavior.
I have my folders organized the way I want them and do not want C1 or any other software adding new folders to my arrangement.
I have photo cache and other similar files on a separate fast hard drive. I store my image database on a larger slower hard drive but that is where C1 is placing the cache and other unwanted folders.
Is there a solution to this issue? I searched the forum posts and see that this problem has been raised many times in the past but I did not see any news of a solution.
Thanks
Bill Wood
When I point C1 at my photo database folders, it creates many unwanted new folders (cache and others). I cannot find a way to stop this behavior.
I have my folders organized the way I want them and do not want C1 or any other software adding new folders to my arrangement.
I have photo cache and other similar files on a separate fast hard drive. I store my image database on a larger slower hard drive but that is where C1 is placing the cache and other unwanted folders.
Is there a solution to this issue? I searched the forum posts and see that this problem has been raised many times in the past but I did not see any news of a solution.
Thanks
Bill Wood
0
-
For short, this is the way Capture One 5 works, and you can't change that behavior.
In each folder with images, CO5 creates a Capture One folder with subfolder for the settings (adjustments) you like to make and for the preview (cache/proxies). This way CO5 can present the raw file and your adjustments to you without writing to the raw file, which is another aspect of CO5.
This might scare you off initially, but you might (or might not) get accustomed with it. Success testing CO5.0 -
[quote="NNN634248497449153575" wrote:
Is there a solution to this issue? I searched the forum posts and see that this problem has been raised many times in the past but I did not see any news of a solution.
There's no "solution" because it's not a fault - although I admit that I'm not a fan of this implementation either.0 -
Thanks for the responses. I understand that the cache files are necessary. My objection is that C1 will not let me put the folders where I want them, namely on a separate faster hard drive in folders of my choosing. So the implementation certainly is a "fault". And its a serious fault for me since I am not going to buy the program because of it.
Regards
Bill Wood0 -
[quote="NNN634248497449153575" wrote:
My objection is that C1 will not let me put the folders where I want them, namely on a separate faster hard drive in folders of my choosing. So the implementation certainly is a "fault".
No, it's not a fault, Bill - but it is (arguably) a flawed design decision.
I wouldn't let it stop me using Cap One though - just do what many of us do, which is to delete the cache folders when they're no longer needed.0 -
up to the introduction of Version 4, COne allowed you to put the image cache anywhere you wanted. That user flexibility came at a price....almost all user issues AFA support came from issues with this system. Forcing the program closed would loose information, archiving image files with their adjustments was misunderstood, even though quite well implemented.....and even though preview files could be automatically (or manually) removed, there was a build-up of adjustment files in the cache over time that was...a problem. And, if the selected drive was offline for any reason, the default was returned, and that was another issue.
..in short, I've come to the slow realization that the present implementation is probably better overall for most users...and gives me much more flexibilty in moving and backing up raw files with the contained adjustments. At a minmum, the files are coherent so I can do with them what I want...unlike a competing program that seems to assume moving files across a network is never done...<g>...0 -
Have you looked into using EIP?
http://www.phaseone.com/en/search/artic ... nguageid=10 -
I for one am very thankful for the way C1 v5 is setup. All of my clients are put on my server and we work from 3 workstations. Having a CaptureOne cache folder inside of my clients’ folder is a big plus. It is so nice to have all of the work we have done on one work station, saved automatically, rather than saving to archive and having to restore on a different work station. This is one reason why I don't use Lightroom. Lightroom does not work on a server environment. With use it's all about workflow and efficiency and that's another reason why CaptureOne is the best RAW file converter, and dominates in my opinion. 0 -
I think this behavior is one of those that can make that program so fast.
The best way is to keep an individual HDD for "Work files" and put final files to your usual directory.
Béla0
Post is closed for comments.
Comments
8 comments