Splitting catalogs properly
Even though there has been some improvement with the 10.1 release when working with larger catalogs (20k+ images) there are still tasks which take much longer than in V9. I therefore decided to split and reorganise my catalogs - all images are referenced. However, I have not yet found a proper way of doing this.
So far I have tried
- exporting a subset of images as a catalog. If I select the subset in the Folders Section image export is fine but none of my collections are exported. If I select the subset in the User Collection Section image export is also fine and I get all Albums,..., exported but they are empty.
- duplicating the catalog and removing images I don't want to keep. This keeps my User collection intact but the size of the catalog does not decrease and the new catalog isn't behaving any faster. I tried to backup this new catalog including test for integrity and optimisation as well as regenerate all previews and backuped it again. No change.
Other ideas for splitting a catalog properly?
Best
Frank
So far I have tried
- exporting a subset of images as a catalog. If I select the subset in the Folders Section image export is fine but none of my collections are exported. If I select the subset in the User Collection Section image export is also fine and I get all Albums,..., exported but they are empty.
- duplicating the catalog and removing images I don't want to keep. This keeps my User collection intact but the size of the catalog does not decrease and the new catalog isn't behaving any faster. I tried to backup this new catalog including test for integrity and optimisation as well as regenerate all previews and backuped it again. No change.
Other ideas for splitting a catalog properly?
Best
Frank
0
-
[quote="FL" wrote:
In early July I reported the exported albums being empty as Case 256507. At that time COP could duplicate the problem but didn't understand yet why it was ocurring.
Even though there has been some improvement with the 10.1 release when working with larger catalogs (20k+ images) there are still tasks which take much longer than in V9. I therefore decided to split and reorganise my catalogs - all images are referenced. However, I have not yet found a proper way of doing this.
So far I have tried
- exporting a subset of images as a catalog. If I select the subset in the Folders Section image export is fine but none of my collections are exported. If I select the subset in the User Collection Section image export is also fine and I get all Albums,..., exported but they are empty.
Strangely enough, I have one Album that still contains images when exported. I haven't been able to discover the difference.
In a catalog, the database part is quite small. In my catalog of 15000 images, with a total size of 16.67 GB, the database is only 77MB. The rest is cache - previews and thumbnails. Most of the space is used by the previews folder.
- duplicating the catalog and removing images I don't want to keep. This keeps my User collection intact but the size of the catalog does not decrease and the new catalog isn't behaving any faster. I tried to backup this new catalog including test for integrity and optimisation as well as regenerate all previews and backuped it again. No change.
Other ideas for splitting a catalog properly?
Best
Frank
It is interesting and informative to note that when Capture one backs up a catalog, it only backs up the database, not the cache. That tells me the cache is not essential. (Cache data typically isn't essential)
So - copy the catalog, open the new catalog in COP to delete images, and collections you don't want, backup, save and close. Now use Finder to "show package contents" of the new catalog, open the cache folder and delete the previews folder. You could delete the thumbnails folder too.
Open the new catalog again in COP, open "All Images" in the browser, select every image, and trigger "regenerate preview"0 -
copy the catalog, open the new catalog in COP to delete images, and collections you don't want, backup, save and close. Now use Finder to "show package contents" of the new catalog, open the cache folder and delete the previews folder. You could delete the thumbnails folder too.
Open the new catalog again in COP, open "All Images" in the browser, select every image, and trigger "regenerate preview"
Thanks Eric - it works though I was hoping that there is a more "direct" solution as this involves deleting 100+ albums manually and one by one after deleting the image.
It is interesting that Capture One is not removing previews of deleted images. This keeps a heavily used catalog file growing faster than it needs to.
Frank0 -
[quote="FL" wrote:
copy the catalog, open the new catalog in COP to delete images, and collections you don't want, backup, save and close. Now use Finder to "show package contents" of the new catalog, open the cache folder and delete the previews folder. You could delete the thumbnails folder too.
Open the new catalog again in COP, open "All Images" in the browser, select every image, and trigger "regenerate preview"
Thanks Eric - it works though I was hoping that there is a more "direct" solution as this involves deleting 100+ albums manually and one by one after deleting the image.
It is interesting that Capture One is not removing previews of deleted images. This keeps a heavily used catalog file growing faster than it needs to.
Frank
It's a work around for now.
Once COP fix the export problem, then it's as simple as selecting some albums/projects/groups and clicking on Export as Catalog.
Since this is really bugging you, probably a good idea to raise a ticket. COP support has no way of understanding how many people find this an important problem unless we (the users) tell them so.
As I see it there are three important parts to a ticket- What's the problem
- What's the configuration
- What's the impact on the user
0 -
Already did (case 258035) on July 30th, so far no response.
Best
Frank0 -
@Eric Nepean
This was SOOOO helpful. My catalog shrunk from 1.7 GB down to 112 MB. Just amazing.
Thanks for helping clear that problem up. 😄 😄 😄0 -
So they have no plans to fix this problem ? I have also reported this issue many weeks ago, but nothing happens.. It would be nice to export as a new catalog in a normal way.. 0 -
[quote="NN635469096254966054UL" wrote:
My experience is that once PhaseOne acknowledges a problem, they generally fix it; however It may take a while.
So they have no plans to fix this problem ? I have also reported this issue many weeks ago, but nothing happens.. It would be nice to export as a new catalog in a normal way..
Even making a release with just bug fixes is not trivial, and this is now just after summer vacation and also the time when they are likely updating COP SW to work with the new OSX that Apple will release in a month.
This problem has been acknowledged and I think they will fix it.0 -
[quote="FL" wrote:
Already did (case 258035) on July 30th, so far no response.
Best
Frank
It looks like the problem is not fixed in 10.2
All my open unfixed tickets were closed with no comments, your may have been two.
I raised another ticket 😉 😉0
Post ist für Kommentare geschlossen.
Kommentare
8 Kommentare