Library and CaptureOne folder behaviour
Forgive me for this long rant, but his is one aspect of C1 that I don't like. It is what Capture One 6pro (and also 5pro which I have) does by design and I would like to control and tweak or restrict this, but suspect I can't.
Here goes: using Win 7 64 bit.
For my active session folder I always work in 'Capture One library' and import my raw files into this thus finishing up with a sub CaptureOne folder containing Cache (proxies *.cop *.cof) and Settings50 (*.cos) data. So far so good, I can live with this, it is my only (favorite) import location.
With 'Library' you have (on the right, in my configuration) an expanding file structure, like Explorer. Within this are other what I would call 'relevant' folders which I use (but do not import to) e.g. 'Move to' , now renamed 'Select', and 'Trash'. So I can have files moved to these folders by move to or delete and as with 'Capture One Library' these folders have their associated CaptureOne, Cache and Settings50 folders for images that finish up them. No problem with this to here. Now the bit I don't like. As well as 'Move to', Select' etc there is 'Output folder' Click on this and for me fun starts. The 'output folder' is the choice one makes when processing as the destination 'output to' - I named it 'process'. All my images go here as jpegs for sorting final reviewing whatever via an external viewer. (Acdsee). The bad news is if you unfortunately click on 'Output folder' in the library tree Capture one instantly opens up this 'process' folder of jpegs and creates its mandatory sub 'CaptureOne ' folder plus it's Cache, Settings50 etc for these finished jpegs. I can have a lot of images in the process folder and don't need the clutter of unnecessary cache and data files in there too. The *.cop (preview?) files are large. Worse still as far as I can tell if you accidently click on any folder in the directory tree while in the 'Library' you will finish up with a 'CaptureOne' etc folder group for that folder if it contains jpegs - I had a 'CaptureOne' set on my desktop! Unchecking 'edit jpegs and /or tiff' in set up does not stop this behaviour.
It would be good to be able to exclude folders from the library directory tree to prevent this, but i can't see how. For now I shall have to be careful which folders I click on. Unless anybody has solved this in their own way?
Ray
Here goes: using Win 7 64 bit.
For my active session folder I always work in 'Capture One library' and import my raw files into this thus finishing up with a sub CaptureOne folder containing Cache (proxies *.cop *.cof) and Settings50 (*.cos) data. So far so good, I can live with this, it is my only (favorite) import location.
With 'Library' you have (on the right, in my configuration) an expanding file structure, like Explorer. Within this are other what I would call 'relevant' folders which I use (but do not import to) e.g. 'Move to' , now renamed 'Select', and 'Trash'. So I can have files moved to these folders by move to or delete and as with 'Capture One Library' these folders have their associated CaptureOne, Cache and Settings50 folders for images that finish up them. No problem with this to here. Now the bit I don't like. As well as 'Move to', Select' etc there is 'Output folder' Click on this and for me fun starts. The 'output folder' is the choice one makes when processing as the destination 'output to' - I named it 'process'. All my images go here as jpegs for sorting final reviewing whatever via an external viewer. (Acdsee). The bad news is if you unfortunately click on 'Output folder' in the library tree Capture one instantly opens up this 'process' folder of jpegs and creates its mandatory sub 'CaptureOne ' folder plus it's Cache, Settings50 etc for these finished jpegs. I can have a lot of images in the process folder and don't need the clutter of unnecessary cache and data files in there too. The *.cop (preview?) files are large. Worse still as far as I can tell if you accidently click on any folder in the directory tree while in the 'Library' you will finish up with a 'CaptureOne' etc folder group for that folder if it contains jpegs - I had a 'CaptureOne' set on my desktop! Unchecking 'edit jpegs and /or tiff' in set up does not stop this behaviour.
It would be good to be able to exclude folders from the library directory tree to prevent this, but i can't see how. For now I shall have to be careful which folders I click on. Unless anybody has solved this in their own way?
Ray
0
-
I have done this too, but not accidentally, just when checking the default CO folders before I knew what they were, or checking if they changed after an upgrade.
I find it hard to do this accidentally as my RAW files are all kept in a separate directory with separate folders for different batches/shoots. Since I am working from that directory and it's sub-folders they are physically (in the CO folder structure) far from the default CO folders or any other non photos folders on my system.
The rare times I do 'accidentally' go to the wrong folder I find it easy to delete the folders that CO created.0 -
Hello Alex1.
I agree with what you say, and I can take care to choose the right folders in library. What I don't understand is as I see it, is that an output to 'location' for developed images should be just that - the end of the process and kept out of further (C1)processing. These are finished jpeg in my case, maybe tiff for others. Possibly I am seeing this differently as a result of my own workflow, but using the library to browse for images intentionally or otherwise (which happens as you select any part of the tree) might cause lots of CaptureOne subfolders to appear. Ok you can remove them but the whole to me seems odd. Finishing up with a set of cache & proxy files for almost any (jpeg) image containing folder surely is not intended. If it just happened with raw there is some point, (you have to process raw to do something with it) but because C1 can process jpeg and tiff now is why this happens. If deselecting 'edit jpeg and tiff' in preferences could stop cache proxies etc being produced for those file types that would work.
Like some others on the forum I prefer to be able to nominate locations for caches, temp files etc., such as a dedicated second drive. However there is a lot to be positive about with C1 that makes me stick with it over the years.0 -
I use a separate Develop folder for every folder of RAW images. That is legacy from using CO from 3.x days as it always output to a (self created) Develops folder in that associated location. I find it very frustrating actually that CO 4.x+ does not do this any more as I have to manually select an output folder every time I develop an image after browsing to to a new RAW file folder. I often forget and find my Develops in the wrong folder. Needless to say I have found myself moving files around a lot more outside of CO to fix this, very frustrating. 0 -
[quote="Alex1" wrote:
I use a separate Develop folder for every folder of RAW images. That is legacy from using CO from 3.x days as it always output to a (self created) Develops folder in that associated location. I find it very frustrating actually that CO 4.x+ does not do this any more as I have to manually select an output folder every time I develop an image after browsing to to a new RAW file folder.
It has become a feature in CO5 Pro and later.0 -
[quote="Alex1" wrote:
...I have to manually select an output folder...
You can use the Advanced tab in your Process Recipe to set up a default sub folder and root folder for your processed files.0 -
Only if you have Pro. It was a feature removed from the standard edition. But I already had many hundreds of folders that use a sub folder called Develops so I am sticking to that system created by 3.x non-standard. 0 -
Raymond,
Change the Permissions of the "Output" folder to "Read Only".
Although you cannot edit the processed files, you should now be able to browse the location and contents without Capture One writing it's folder of settings.0 -
Thanks Drew, will try this 0
Post ist für Kommentare geschlossen.
Kommentare
8 Kommentare