New user considering Capture One
Hi!
I've been evaluating Capture one for the past two weeks as a replacement for Aperture. It seems to be a lot faster for me to get my images to look pleasing using Capture One then Lightroom which puts it ahead in my view, however I still have some questions.
I'm a hobbyist photographer, i.e. really not a pro. Currently most of the lenses I have are supported by Capture one, but there is one (Tamron 70-300) that is not, and a bunch of lenses I have considered due to good value (Sigma) that are not (or are only for Canon, not for Nikon). I have been considering replacing the Tamron with a Nikon 70-200, but I would feel bad adding pressure to expensive purchases due to software limitations. 😊 Is Phase One actively adding a lot of new lenses or should I expect that all the main effort will be to add support to pro lenses and anything else is a matter of luck?
My library is a bit under 30000 pictures. I've imported it first from masters, and also tested importing from Aperture library (both imports fine). When the application starts with this big of a catalog it really takes quite a long time for the UI to come up. Does this sound normal? Is it generally a bad idea to have a lot of images in a big catalog vs. splitting it up? Machines should be up for the job (Mac Mini i7 with 16GB ram and 1TB Sandisk Extreme SSD, MBP 15" with i7 and 512GB SSD).
I've been evaluating Capture one for the past two weeks as a replacement for Aperture. It seems to be a lot faster for me to get my images to look pleasing using Capture One then Lightroom which puts it ahead in my view, however I still have some questions.
I'm a hobbyist photographer, i.e. really not a pro. Currently most of the lenses I have are supported by Capture one, but there is one (Tamron 70-300) that is not, and a bunch of lenses I have considered due to good value (Sigma) that are not (or are only for Canon, not for Nikon). I have been considering replacing the Tamron with a Nikon 70-200, but I would feel bad adding pressure to expensive purchases due to software limitations. 😊 Is Phase One actively adding a lot of new lenses or should I expect that all the main effort will be to add support to pro lenses and anything else is a matter of luck?
My library is a bit under 30000 pictures. I've imported it first from masters, and also tested importing from Aperture library (both imports fine). When the application starts with this big of a catalog it really takes quite a long time for the UI to come up. Does this sound normal? Is it generally a bad idea to have a lot of images in a big catalog vs. splitting it up? Machines should be up for the job (Mac Mini i7 with 16GB ram and 1TB Sandisk Extreme SSD, MBP 15" with i7 and 512GB SSD).
0
-
[quote="kamina" wrote:
Hi!
I'm a hobbyist photographer, i.e. really not a pro. Currently most of the lenses I have are supported by Capture one, but there is one (Tamron 70-300) that is not, and a bunch of lenses I have considered due to good value (Sigma) that are not (or are only for Canon, not for Nikon). I have been considering replacing the Tamron with a Nikon 70-200, but I would feel bad adding pressure to expensive purchases due to software limitations. 😊 Is Phase One actively adding a lot of new lenses or should I expect that all the main effort will be to add support to pro lenses and anything else is a matter of luck?
It has been my experience that C1 is not particularly pro-active in adding lenses to its database. I started a thread a bit ago complaining that there were no automated lens adjustments for any Canon 70-300 lenses even though some of these are considered to be pro or semi-pro lenses. The responses that were posted indicated that there probably was no good financial reason for C1 to add those since they were probably not heavily used lenses.
That is probably right but also means that you might not have a good reason to expect C1 to actively pursue adding any of your lenses. One post to my thread suggested that C1 might do the work if someone would send a copy of the lens to them and that is also something that you might want to consider if you can part with your lens for however long it might take to implement a profile for it.0 -
Thanks for the response!
I just noticed the thread where they offer to add a new profile, and while that would be a bit of trouble it is actually a very nice touch (I doubt Adobe would offer the same as Lightroom is also lacking support for one of my rarely used lenses).0 -
[quote="kamina" wrote:
Thanks for the response!
I just noticed the thread where they offer to add a new profile, and while that would be a bit of trouble it is actually a very nice touch (I doubt Adobe would offer the same as Lightroom is also lacking support for one of my rarely used lenses).
And the offer still stands 😊
We actively add lenses to CO, so more and more will come for each release.0 -
[quote="kamina" wrote:
Hi!
My library is a bit under 30000 pictures. I've imported it first from masters, and also tested importing from Aperture library (both imports fine). When the application starts with this big of a catalog it really takes quite a long time for the UI to come up. Does this sound normal? Is it generally a bad idea to have a lot of images in a big catalog vs. splitting it up? Machines should be up for the job (Mac Mini i7 with 16GB ram and 1TB Sandisk Extreme SSD, MBP 15" with i7 and 512GB SSD).
Out of curiosity, how long did it take to build your catalog in C1?0 -
[quote="Jimmy D Uptain" wrote:
[quote="kamina" wrote:
Hi!
My library is a bit under 30000 pictures. I've imported it first from masters, and also tested importing from Aperture library (both imports fine). When the application starts with this big of a catalog it really takes quite a long time for the UI to come up. Does this sound normal? Is it generally a bad idea to have a lot of images in a big catalog vs. splitting it up? Machines should be up for the job (Mac Mini i7 with 16GB ram and 1TB Sandisk Extreme SSD, MBP 15" with i7 and 512GB SSD).
Out of curiosity, how long did it take to build your catalog in C1?
I started my test with Lightroom and set it to create previews for all images during import. It took several hours to finalise, so when I did the import (from master images) in Capture One I just left the computer running over night (so no idea)... It was pretty late at night and I did not feel the length of the import was very meaningful in the comparison.
I did a second import from the Aperture library, it seemed to take longer and the computer was a bit slow once it seemed ready. I guess it was still doing some calculation on the background once the main import GUI was done as it is not slow any more?
Sorry I can't be off much help, the main thing I noticed was high battery usage during the imports, I was not expecting it to be fast. Assuming that C1 actually does process something (previews?) in the background after the import dialogue is done then one big difference was that Lightroom had a pretty clear indicator of what it was doing.
For what it's worth, the library is close to 200GB.0 -
[quote="kamina" wrote:
My library is a bit under 30000 pictures. I've imported it first from masters, and also tested importing from Aperture library (both imports fine). When the application starts with this big of a catalog it really takes quite a long time for the UI to come up. Does this sound normal? Is it generally a bad idea to have a lot of images in a big catalog vs. splitting it up?
I have migrated from Aperture to C1 a few months ago. What I have been experiencing is that C1 runs slower if you reference to a original managed Aperture library compared to referencing to the originals directly and just importing the metadata and everything else from the Aperture database.
My C1 catalog is about 28.000 images (referenced from a SATA drive with the catalog sitting on my SSD boot drive) and while it takes a lot of time to start up, actually working in the application when it is open is not really slower compared to Aperture (which was launching almost instantly). So it's just the launch that is a problem here, maybe some things are happening there which would need to be improved from a coding standpoint.0 -
Thanks.
A couple of point versions back, it was taking me much much longer to build a catalog, on a Mac Pro.
I have noticed this latest version is quicker to open and search.
I may try to build a new catalog.0 -
I imported my Aperture library and C1 created a new referenced catalog. The import went well and there were no problems. However, the performance of accessing that catalog was really slow. I decided to move all the images from the referenced catalog into a managed catalog. Performance jumped significantly! Well worth the simple motion of dragging the images. I made a back up of my original Aperture library and worked off of that. The copy library was destroyed since all the images were moved to the managed C1 catalog. Hence, the back up! 😄
I have an older mid-2011 21.5" iMac and C1 works fine. Sometimes the machine gets a little jerky but only when I try to update the screen too fast or smash the sliders left and right just for giggles. C1 is a power hungry program and my computer will get blazing hot! The fans turn on and the top of the case can almost burn your fingers. I must have the most under powered machine on the forum and C1 still works fine.
The tools are very powerful in C1. It is well worth learning how to use them. Phase One has an excellent YouTube channel with lots of presentations hosted by David Grover. Excellent material! I configured my workspace to look similar to Aperture so the transition to C1 went smoothly. Now I feel I have grown beyond anything Aperture did.0 -
[quote="6BQ5" wrote:
I imported my Aperture library and C1 created a new referenced catalog. The import went well and there were no problems. However, the performance of accessing that catalog was really slow. I decided to move all the images from the referenced catalog into a managed catalog. Performance jumped significantly!
I have not yet gained enough trust in C1's handling of the SQL database to really hand over the full image management to the application. It happens relatively often, that my database gets corrupted and needs to be repaired. Aperture had similar issues from 1.0 to about 2.x, but by the time it hit V3 it was extremely reliable. I will wait until Phase One gets their SQL sh*t together, to be honest. Until then I will stick to referenced. Would love to have all the management done by the application, because I'm lazy as f*ck.[quote="6BQ5" wrote:
he tools are very powerful in C1. It is well worth learning how to use them. Phase One has an excellent YouTube channel with lots of presentations hosted by David Grover. Excellent material! I configured my workspace to look similar to Aperture so the transition to C1 went smoothly. Now I feel I have grown beyond anything Aperture did.
I can second that, my experience has been exactly the same. I miss a few of Apertures neat features, especially the rock solid DAM philosophy behind it, but overall I have a blast with C1.0 -
I can second that, my experience has been exactly the same. I miss a few of Apertures neat features, especially the rock solid DAM philosophy behind it, but overall I have a blast with C1.
i agree with you... this way i cannt compare C1 with Aperture or calling it Alternativ, it seam to bee
that DAM Media Pro from Phase One are not supported moor, since moor then one year i am waiting for a solution.
many users hear in Forum advising to use PHOTO SUPREME to C1 but i will not acept for paying 100 € to my Media Pro that i bay...
Phase One is responsible for fixing this Bug or sending Dicount and i will not bee buying this fixing Bugs in the new coming realese.
thats not means that they do bad Software develop or job .
I wish every one much fun for keep working with C1 its a good decisionto for working RAW files.0
Post is closed for comments.
Comments
10 comments