C1 Catalog performance
Much appreciate some advise and guidance.
Some background:
Have been using LR for many years - both in a personal and a professional basis.
Shooting with Sony A99, A7r2 and of late the A99ii
Have noticed a rather red colour cast in our calibration - esp with the A7r2
We have dome Xrite colour profiling on three occasions for each camera and lens combination to try fix the problems.
As we prefer tethering with C1, we are now looking into the prospect of taking a big step and switch to C1 in place of LR.
The red cast is just getting to us, as is the slow editing - esp with spot correction and brush work.
Last week we did a quick edit and comparison of the same portrait and were very impressed with the colour of C1.
Out studio PC system is new and current.
Editing in LR is now unpleasant. Guess the 42MB RAW files don't help either
So, I'm testing and playing at home and in the studio with whatever spare time I have.
Recently purchased David Grover's Creative-Live course so we it right...from the horses mouth so to speak.
Up to session 18 tonight.
Where I am right now
My home LR catalog operates fine - no issues. Currently have 176k pics in it. Cat plus preview take up 70GB
I have been importing the same files into C1 - catalog - and have hit 59K and my system is dying.
Drive C is 500GB SSD and my drive monitor is almost always at 100%...for the past 4 days! Current Disk space for the C1 catalog is 37GB
I can see its building previews, but can't see why it is taking so long.
During this time C1 is almost impossible to use.
Wonder if this is normal?
Appreciate advice or suggestions...
I am almost at the point of considering pulling the plug, but this can't be right!
Thanks in advance
Some background:
Have been using LR for many years - both in a personal and a professional basis.
Shooting with Sony A99, A7r2 and of late the A99ii
Have noticed a rather red colour cast in our calibration - esp with the A7r2
We have dome Xrite colour profiling on three occasions for each camera and lens combination to try fix the problems.
As we prefer tethering with C1, we are now looking into the prospect of taking a big step and switch to C1 in place of LR.
The red cast is just getting to us, as is the slow editing - esp with spot correction and brush work.
Last week we did a quick edit and comparison of the same portrait and were very impressed with the colour of C1.
Out studio PC system is new and current.
Editing in LR is now unpleasant. Guess the 42MB RAW files don't help either
So, I'm testing and playing at home and in the studio with whatever spare time I have.
Recently purchased David Grover's Creative-Live course so we it right...from the horses mouth so to speak.
Up to session 18 tonight.
Where I am right now
My home LR catalog operates fine - no issues. Currently have 176k pics in it. Cat plus preview take up 70GB
I have been importing the same files into C1 - catalog - and have hit 59K and my system is dying.
Drive C is 500GB SSD and my drive monitor is almost always at 100%...for the past 4 days! Current Disk space for the C1 catalog is 37GB
I can see its building previews, but can't see why it is taking so long.
During this time C1 is almost impossible to use.
Wonder if this is normal?
Appreciate advice or suggestions...
I am almost at the point of considering pulling the plug, but this can't be right!
Thanks in advance
0
-
I would strongly suggest that you create a Support Case to get official Capture One Support Team input for this.
Meanwhile, do you have any XMP syncing going on?
Also the mass upload of files from another catalogue system can be a challenging task as it will not be a straight copy of data but a partial copy and a lot of calculations and internal file generation of previews, thumbnails and so on. It is possible that the sheer volume with some large files in play has found a way to swamp the system's memory management. (For example).
Make a Support Case to get direct technical input started while you wait for a response here from a Windows user who may have experienced similar problems and resolved them.
Sorry I can't offer more than this. I use windows but not LR nor catalogues.
Grant0 -
Thanks Grant. Will do 0 -
One thing I forgot to mention ....
If the source of the original catalogue - LR in this case - has any form of maintenance tool to keep it in good shape internally I would strongly suggest using it before attempting a conversion.
In addition many here have found that the entire process will run more consistently it broken up into small er segments - say 10k images at a time.
That's not unusual. Any Database will have a "performance curve" especially if there is some processing going on - not just a reload and re-index. Typically desktop systems that I have worked with testing such things (but not with such large records as digital images) will show a good speed for the first 40k records and then progressively slow down after that to some extent.
So with a large pressure on memory around 10k files seems to make sense since it appears to work for most people.
HTH.
Grant.0 -
Grant
I am not converting a LR catalog and have no special maint tools for LR catalogs
I am doing fresh imports into one newly created C1 catalog.( ie slowly adding to it)
I have also noticed that when I invoke C1, there is about a 20-30sec delay before any images or thumbs appears, or I am able to click/select any item. Rather strange.
I have lodged a support ticket but in the meantime will add no more images and see if it settles down.
Thanks
John0 -
[quote="JnJ" wrote:
Grant
I am not converting a LR catalog and have no special maint tools for LR catalogs
I am doing fresh imports into one newly created C1 catalog.( ie slowly adding to it)
I have also noticed that when I invoke C1, there is about a 20-30sec delay before any images or thumbs appears, or I am able to click/select any item. Rather strange.
I have lodged a support ticket but in the meantime will add no more images and see if it settles down.
Thanks
John
OK, in that case I think you have just hit some typical data load performance drop off points that are part of a compromise decision that has do be balanced out for expected usage of a database. In general, and not just for image processing, the designers need to handle the data choosing either speed of access (small data amount handling, large number of records to select from) or data volume (but slower access). That's the simplified view.
Photo storage and processing demands both. Hitting a balance can be tricky. I would suggest the very high volume loads, as, usually, one-off activities are lower on the performance tuning map the designers would work to. Breaking up the load into smaller chunks - 10 to 20k records perhaps, would make sense especially as there is other processing required on import to generate thumbnails and previews and the base "adjustments" that enable them.
Your start up delay is likely to be C1 going through its initiation process. Details will be in the log files. Remember you are asking it to work with a 37Gb catalogue amongst other things. Unless you have a lot of spare memory available that alone will take some time to read and load even off a (relatively) fast SSD
Grant0 -
I refer you to my post here: viewtopic.php?f=69&t=26212 which may shed some light. 0
投稿コメントは受け付けていません。
コメント
6件のコメント