Where does Capture One 10 store preview files?
I am running with a referenced catalog. I moved my Capture One catalog files to an SSD and have my original files on a standard hard drive.
I opened the catalog from the SSD and regenerated all the previews. It took hours but I let it go. After I was hoping to see a big improvement in program opening time and when clicking on "All Files". My main catalog has just under 15,000 files.
During the "regenerate previews" operation I could hear the hard drive working hard. I thought I read that previews are stored inside the catalog file. It appears they are on the Hard Drive. Inside each of the folders where my originals are is a folder called proxies with a .cop file.
Maybe I need to change a setting to take advantage of the catalog being on the SSD while the original files reside on a different drive.?
I opened the catalog from the SSD and regenerated all the previews. It took hours but I let it go. After I was hoping to see a big improvement in program opening time and when clicking on "All Files". My main catalog has just under 15,000 files.
During the "regenerate previews" operation I could hear the hard drive working hard. I thought I read that previews are stored inside the catalog file. It appears they are on the Hard Drive. Inside each of the folders where my originals are is a folder called proxies with a .cop file.
Maybe I need to change a setting to take advantage of the catalog being on the SSD while the original files reside on a different drive.?
0
-
they should be (on my system) in the ".cacatalog/Cache".
the Previews in CaptureOne are not that smart. I think it's not good to generate the preview of every pictures when clicking on "All Images". It never worked here.
I would like CaptureOne do add "advanced" preview management. Like being able to deploy the cache on ANOTHER location (other disk, etc...), limit the previews size (eldest preview would be deleted), and allow to NOT generate preiew all the time.
Regards0 -
Hi,
Once the previews have been generated, it's once for all. You don't need to regenerate them each time, even when clicking on "All Images" : they are already there (in the Cache you mentioned). Previews and thumbnails are two different things, of course !!
The previews need to have a quick access as they are used as smart previews, when your RAW storage disk is off line, for instance. It's then better to have them on your main internal disk, together with the software.
And you can change the size of the previews in the preferences if you think they are too long to generate after a shot session, or if they take too much room on your disk.0 -
[quote="Edgephoto" wrote:
I opened the catalog from the SSD and regenerated all the previews. It took hours but I let it go. After I was hoping to see a big improvement in program opening time and when clicking on "All Files". My main catalog has just under 15,000 files.
Did you move the catalogue folder or just the catalogue database file?
Grant0 -
[quote="SFA" wrote:
[quote="Edgephoto" wrote:
I opened the catalog from the SSD and regenerated all the previews. It took hours but I let it go. After I was hoping to see a big improvement in program opening time and when clicking on "All Files". My main catalog has just under 15,000 files.
Did you move the catalogue folder or just the catalogue database file?
Grant
I moved the file with the extension .cocatalog. If I "Show Package Contents" there are many files inside this. The catalog file is 17.5GB and contains references to about 15,000 photos.0 -
Was everything on the external drive to start with?
If so all of the Catalogue files for adjustments, previews and so on, will have been on that drive in the file structure under the .cocatalogue "file" - as I understand things. I'm on windows and while as far as I know the principles of operation are the same the on screen presentation seems to be a little different. There is a folder not a .cocatalog file for example.
I would guess, if you moved the file from the external drive to the SSD C1 will either have copied everything from the external drive and created the necessary links back to the original images OR may have gone through a process of copying the adjustment files but then regenerating the thinks that are in "cache" since they can be recreated anyway. I.E. they are, potentially, disposable although for best performance that might not be a great idea.
Either way - copy or regenerate - I would think the original files would be left on the external drive as well since that would be a safer assumption to make given the potential for disk sharing between computers, etc.
So in effect you would have two sets of previews, thumbnails, etc. Is that what you see?
Grant0 -
[quote="Edgephoto" wrote:
I am running with a referenced catalog. I moved my Capture One catalog files to an SSD and have my original files on a standard hard drive.
I opened the catalog from the SSD and regenerated all the previews. It took hours but I let it go. After I was hoping to see a big improvement in program opening time and when clicking on "All Files". My main catalog has just under 15,000 files.
During the "regenerate previews" operation I could hear the hard drive working hard. I thought I read that previews are stored inside the catalog file. It appears they are on the Hard Drive. Inside each of the folders where my originals are is a folder called proxies with a .cop file.
Maybe I need to change a setting to take advantage of the catalog being on the SSD while the original files reside on a different drive.?
Consider this. COP is running from your catalog file on the SSD. It needs to generate the preview of an image. Where does it get the information to create the preview image?
Answer: It gets the adjustments (from your catalog file) and the original image, which is on the (magnetic) hard drive.
So, the fact that hard drive was being repeatedly acceess during the regenerate previews activity is perfectly normal.
However, I don't see this as a reason to move the images to the SSD. Generation of previews for a very large number of images is something that should occur rarely. The generation of previews for a small number of images is more normal, and for this is the access time of the hard drive does not matter. The image on the hard drive is also accessed when editting, and here again, it does not matter.0 -
[quote="Eric Nepean" wrote:
[quote="Edgephoto" wrote:
I am running with a referenced catalog. I moved my Capture One catalog files to an SSD and have my original files on a standard hard drive.
I opened the catalog from the SSD and regenerated all the previews. It took hours but I let it go. After I was hoping to see a big improvement in program opening time and when clicking on "All Files". My main catalog has just under 15,000 files.
During the "regenerate previews" operation I could hear the hard drive working hard. I thought I read that previews are stored inside the catalog file. It appears they are on the Hard Drive. Inside each of the folders where my originals are is a folder called proxies with a .cop file.
Maybe I need to change a setting to take advantage of the catalog being on the SSD while the original files reside on a different drive.?
Consider this. COP is running from your catalog file on the SSD. It needs to generate the preview of an image. Where does it get the information to create the preview image?
Answer: It gets the adjustments (from your catalog file) and the original image, which is on the (magnetic) hard drive.
So, the fact that hard drive was being repeatedly acceess during the regenerate previews activity is perfectly normal.
However, I don't see this as a reason to move the images to the SSD. Generation of previews for a very large number of images is something that should occur rarely. The generation of previews for a small number of images is more normal, and for this is the access time of the hard drive does not matter. The image on the hard drive is also accessed when editting, and here again, it does not matter.
You have misunderstood what I was explaining. I know the hard drive will be accessed during regeneration of previews. I regenerated all previews hoping that this would speed things up after I moved my catalog file to the SSD.
Even after all previews have been regenerated and I closed the program I still have a very long time until the program becomes responsive. During the startup of the program it is really working the hard drive where the originals are stored. You can hear it being accessed. Once the program is responsive it seems to be much more snappy than when the catalog file was on the hard drive.
I don't do much post processing to my photos. I am from the film days and do my best to get it right in the camera. I usually just tweak white balance, exposure and maybe a few subtle contrast, color adjustments but that is rare.
I love CO but it is no where near as speedy as Aperture. With Aperture I had a single large catalog. I have split my catalog up into 3 with CO to try and make it less laggy. it is not really slow but has a slight lag. Although with the SSD that seems better too.
I just wish I could find a catalog program that reads CO 10 edits. I tried Media Pro with CO9 and was underwhelmed but I have since changed from a managed catalog to a referenced so I will revisit if they provide a patch to read CO10 files.0 -
The slow response of larger catalogs has been lamented on this forum by many, and although the why is not known, the previews, when available, may not be the cause.
One thing that may slow down the startup is the fact that C1 has to scan the picture folders so it can indicate whether images are offline or not. Some people claim that the startup is faster when their image disk is disconnected (I haven't noticed much difference, but I keep my catalogs small).
The fact that your image disk has "proxies" folders with .cop files in it suggests that you have been visiting those folders via a session. (although, those proxies folders are normally stored inside a "cache" folder in a "CaptureOne" folder.) In a catalog, there are no "proxies" folders; the previews are stored inside the catalog folder (in Cache > Previews).
I believe that those proxies folders can be safely deleted (unless you stil use a session). You could try by moving one such folder out of its containing image folder and check whether it has any consequences on your catalog (move it before you start C1). And also check whether C1 recreated that folder; it shouldn't.
I also believe that those proxies folder are not the cause of the slow startup, unfortunately.
HTH,
Peter.0 -
[quote="peter.f" wrote:
The slow response of larger catalogs has been lamented on this forum by many, and although the why is not known, the previews, when available, may not be the cause.
One thing that may slow down the startup is the fact that C1 has to scan the picture folders so it can indicate whether images are offline or not. Some people claim that the startup is faster when their image disk is disconnected (I haven't noticed much difference, but I keep my catalogs small).
The fact that your image disk has "proxies" folders with .cop files in it suggests that you have been visiting those folders via a session. (although, those proxies folders are normally stored inside a "cache" folder in a "CaptureOne" folder.) In a catalog, there are no "proxies" folders; the previews are stored inside the catalog folder (in Cache > Previews).
I believe that those proxies folders can be safely deleted (unless you stil use a session). You could try by moving one such folder out of its containing image folder and check whether it has any consequences on your catalog (move it before you start C1). And also check whether C1 recreated that folder; it shouldn't.
I also believe that those proxies folder are not the cause of the slow startup, unfortunately.
HTH,
Peter.
I was thinking about deleting one of those folders to see what happens. These folders were not there before I regenerated all previews. The date stamp indicates the date that I regenerated the previews.I might create a smaller catalog for testing purposes instead of possibly corrupting my main catalog and having to copy from a backup.
I have never used sessions.
With the catalog on the SSD and All Files is selected it takes 2-3 minutes to become responsive. Once it is responsive it works fine.0 -
[quote="Edgephoto" wrote:
I just wish I could find a catalog program that reads CO 10 edits. I tried Media Pro with CO9 and was underwhelmed but I have since changed from a managed catalog to a referenced so I will revisit if they provide a patch to read CO10 files.
Photo Supreme is somewhat able to read CO edits.
I got it a while back when looking for alternatives to Media Pro. MP did a better job of reading the edits, but would oversaturate pics sent in an email. If Phase One would fix that, I would use MP0
Post is closed for comments.
Comments
10 comments