Capture One Pro 10 is so slow that I have to give it up!!!
I am a Capture One Ambassedor myself and I have been having issues with Capture One 10. The most influential one being TOO SLOW. I can hardly browse through the photo in a session. FIX THIS QUICK!!!
0
-
[quote="NN636001528632415944UL" wrote:
I was coming from Aperture, didn't like the subscription plan for Lightroom so bought Capture One 9. Was very happy with the capability and user interface of Capture One. My iMac is mid 2012 so not top-notch and accepted quite slow performance. Now upgrading to version 10.... and this is absolutely not making things better ☹️ After a few times of also freezing totally, I cannot live with such unstability ☹️
Have downloaded trail version of Lightroom and now evaluating. Seems much faster (might be due to " smart preview" option?) Nevertheless I am now very likely going Lightroom way simply because lack of speed and stability. Maybe Capture One is for more pro spec machines - I'm just amateur looking for Aperture replacement.
Why don't you stay with CO9 if you're happier with it?0 -
Hello all, I've been doing a little testing and here's what I've come up with so far. (This is for information of the forum members - I've got case 237934 open with tech support, so don't yell at me, Christian 😄 .)
Configuration - MacBook Pro (Retina, 13-inch, Early 2013), 3 GHz Intel Core i7 with 8 GB RAM and a 500 GB SSD internal drive. This behavior is consistent with the performance I see on my iMac Retina as well.
Version 9.3 catalog with 12859 images @ 25.13GB opens in 26 seconds, closes in 4 seconds.
Version 10 catalog with 12861 images at 25.51 GB after initial conversion took 2 min 55 sec to open, longer than 15 minutes to close, with lots of spinning beachball of death time.
Version 10 catalog after deleting all (5) tif files - opened in 48 sec, closes in 1 min 41 sec, no cpu hanging
after reimporting 3 tifs open time is 43 sec, closing time is 1 min 55 sec.
These times are typical, there seems to be about a 5-10% variance in repeatability. All times were made with Capture One already open.
I also experimented with a different, similar size catalog with 63 tifs and got times consistent with this test, The original import makes a mess of the tiffs, deleting the tifs stops the hanging behavior, improves opening and closing times, but still takes twice as long to open and nearly 30 times as long to close! Reimporting the tifs then seems to work fine. Maybe an issue with the v9 -> v10 update process?
Catalog is referenced, times with external drive disconnected. Times are slightly longer (a couple seconds) with drive mounted. I found when opening the same catalog with a collection of 35 images selected performance was virtually identical between v9.3 and v10 - 12 seconds to open, 1.5 seconds to close, but when you select a larger collection or "all images" version 10 is still much slower.
Note on catalogs: These were all done with essentially the same catalog, but I actually had to rebuild the catalog for version 9 and lost a couple of images (Olympus E-M1 MkII not supported for v9.3) hence the different numbers. Tifs were all flattened and worked fine in v9.3
I use monthly catalogs which are small enough that performance is tolerable now that I've got the tif issue worked out, it may help that I keep the images in catalog until the end of the month when I move the images to an external disc and import the catalog into my annual archive catalog.
That being said, I would be holding off on version 10 except for the fact I have a camera that isn't supported in 9.3. Once the performance issues are resolved I think the new features will be well received.0 -
Phil,
That reads like excellent work.
Still a puzzle as to why V10 is slower even absent the tiffs though.
Do the log files throw up any obvious timing discrepancies? (OK, I know they can be tricky to interpret but sometimes things jump out and smack you between the eyes and they are in chronological order thus relatively easy to work out where the interesting bits to compare might be.
Grant0 -
Grant,
Nothing in the log files, but I have noticed when closing the activity monitor indicates "saving document - step 5 of 10" for an excessive period of time.0 -
John,
I consider this also but honestly, paying for upgrade, with speed mentioned as one of the improvements, I don't feel it's good customer service that solution is that I should go back to previous version. But thanks for suggestion and if I can't get used the thought of subscription payments with Lightroom, might be an option.0 -
[quote="NN636001528632415944UL" wrote:
John,
I consider this also but honestly, paying for upgrade, with speed mentioned as one of the improvements, I don't feel it's good customer service that solution is that I should go back to previous version.
Good point. Since I was offered a free upgrade to 10, I keep forgetting that a lot of people actually paid for it. I don't know what's Phase One policy regarding refunds. Maybe you could ask them.0 -
[quote="NN636001528632415944UL" wrote:
John,
I consider this also but honestly, paying for upgrade, with speed mentioned as one of the improvements, I don't feel it's good customer service that solution is that I should go back to previous version. But thanks for suggestion and if I can't get used the thought of subscription payments with Lightroom, might be an option.
I would think that this is a problem that will be resolved once the source is fully identified. Your step back to V9 would likely be temporary - just as if you had delayed your upgrade in the first place.
Grant0 -
Phil,
same for me. See my other post (also with detailed measurements, support cases are filed) on this.
viewtopic.php?f=68&t=25212
The only difference I have is that I don't see much happening on my disk. They are quite active but load and transfer rates are far from maximum.
Best
Frank0 -
Frank,
I think in the real world disk activity, in terms of read and write speeds, will always be a long way from theoretical maximum as published in technical specifications.
Grant0 -
Grant,
agree in general. My comment was referring to numbers I see when C1P is using the disk extensively and these numbers can be far more than an order of magnitude higher compared to the times when I see the spinning ball. So even random vs sequential would not generate such a difference or in other words the disk is not the limiting factor here.
Frank0 -
Frank,
I thought that might be the context of your observation but decided there was no harm in discussing it for clarity - especially on such an open forum and for such a contentious problem. Other readers arriving later to the discussion might benefit from the further information.
The various comments seem to suggest that whatever the cause the problem is being played out somewhere in memory - although that could cause disk activity too if, relatively, a lot of swapping is in progress.
Grant0 -
[quote="SFA" wrote:
[quote="NN636001528632415944UL" wrote:
John,
I consider this also but honestly, paying for upgrade, with speed mentioned as one of the improvements, I don't feel it's good customer service that solution is that I should go back to previous version. But thanks for suggestion and if I can't get used the thought of subscription payments with Lightroom, might be an option.
I would think that this is a problem that will be resolved once the source is fully identified. Your step back to V9 would likely be temporary - just as if you had delayed your upgrade in the first place.
Grant
I've had the same negative experience with trying the 30-day trail upgrade to Pro 10 - frozen computer, spinning beachballs, and overall a poor impression where I cannot justify paying to upgrade to Pro 10 right now. I am back to my "old reliable" Pro 9.3 However I worry that if and when Phase One finds and fixes the problem with Pro 10, that I may not be able to have access to the $99 upgrade cost and may see a $299 new purchase cost. I won't pay another $299 in that event just to get Pro 10. So I hope Phase One eventually fixes whatever is wrong with Pro 10 and gets the upgrade cost (for Pro 9.3 users) at the same $99 fee.
I should add that I've been in touch with tech support, and, added extra memory to my iMac so that I'm now at 24 GB of memory. But the memory upgrade didn't completely fix the slow running Pro 10.0 -
[quote="Triumph Steve" wrote:
[quote="SFA" wrote:
[quote="NN636001528632415944UL" wrote:
John,
I consider this also but honestly, paying for upgrade, with speed mentioned as one of the improvements, I don't feel it's good customer service that solution is that I should go back to previous version. But thanks for suggestion and if I can't get used the thought of subscription payments with Lightroom, might be an option.
I would think that this is a problem that will be resolved once the source is fully identified. Your step back to V9 would likely be temporary - just as if you had delayed your upgrade in the first place.
Grant
I've had the same negative experience with trying the 30-day trail upgrade to Pro 10 - frozen computer, spinning beachballs, and overall a poor impression where I cannot justify paying to upgrade to Pro 10 right now. I am back to my "old reliable" Pro 9.3 However I worry that if and when Phase One finds and fixes the problem with Pro 10, that I may not be able to have access to the $99 upgrade cost and may see a $299 new purchase cost. I won't pay another $299 in that event just to get Pro 10. So I hope Phase One eventually fixes whatever is wrong with Pro 10 and gets the upgrade cost (for Pro 9.3 users) at the same $99 fee.
I should add that I've been in touch with tech support, and, added extra memory to my iMac so that I'm now at 24 GB of memory. But the memory upgrade didn't completely fix the slow running Pro 10.
Steve,
Historically Phase has offered the discounted upgrade price for anyone upgrading from the previous 2 versions.
Whilst I can't and don't speak for their future policy I would imagine it will hold for a while yet since it seems to common retail practise in the software industry.
Once the entire Industry moves to the subscription model it's a question that will go away ... but for now I would imagine it will continue until we hear otherwise.
Grant0 -
I must admit: after purchasing capture one version-9 in Sept 2016 I was surprised to see version -10 released in December 2016. I attempted to reach out to support to see if I was eligible to upgrade to version-10, but it got turned down.So, I tried version 10 to see if it was worth upgrading, but is quiet slow compared to a bigger catalog I have with the version-9. Now I am thinking the ineligibility to upgrade for free was blessing in disguise. 0 -
I've got a resistance here im Forum after i write my opinion about the Update to V10.
i dont like the policy upgrades history at phase one since c 7.
i saw that Bugs are be fixed with 99 € and slowly.
i dont Accusing here the developers for there great work.
but i believe that Greedy always damages the image,
if they still use the same policy like adobe, they must believe that there are always great alternativ on the market.0 -
It is so disappointing. It seems the C1 catalogue is still not production ready.
I started with version 8 loved the raw processing but handling more than a few images is just a pain in the a** and seems just getting worse. Right now my biggest catalogue contains about 15k images and it takes longer to load than a Lightroom catalogue with 120k images (stored on the same disk of course).
The worst thing is that when I accidentally click on all images, then C1 freezes and even after waiting some minutes nothing happens I have to kill the process. When I do this the catalogue gets corrupted and I get this error message:
"The requested document type is not recognized.
The provided database is of an unknown type."
So I have to get the latest backup of my whole catalogue and every work I did since the last backup is lost. This does not sound like a program worth investing 500€ (over time with updates) since I'm using it. Don't get me wrong I'm a professional and pay for good stuff but right now I can't consider this mess as good stuff.
There are so many things like the TIFF problem (bigger TIF load up to 1min in the thumbnails) crazy long startup time which never got fixed and are so critical for our workflow. It is just a joke that they let us pay for the version 10 sorry.
all the best,
as well switching back to Lightroom until major things are fixed,
Jakob0 -
Same here
to slow many things since V8 still not fixed
so until they get this fixed (if ever they get it) Lightroom
and there are tons of preset that can be applied during import so they have the same default look like in capture one pro0 -
I'm afraid I'm feeling the same way. I willingly upgraded to 10 but the catalog implementation really seems to be getting worse rather than better. I'm seeing similar issues to those mentioned here (long startup times, huge delays in displaying images in the browser), although I've only had a couple of major lock-ups causing database corruption, but I back up regularly just in case. I'm afraid it's no longer feasible for me to work in this way with the constant fear of a crash so I'm also reverting to Lightroom although it doesn't give quite as good results (I'm not a pro photographer so it's not affecting my livelihood!). Good luck to all those who are going to continue with C1P... 0 -
Well the thing is, I'm one of the beta testers with a catalogue of more than 15k NEF files, no Tiff or movies. It is a referenced catalogue and the original files are on a NAS drive.
While I was beta testing I havent experienced any problem, slowleness or anything. But each day my catalogue is getting slower now. I havent changed anything on my workflow, NAS connection or anythign so it is kinda weird.
Cheers,
Fatih0 -
I have posted a case for the Phase One staff about this bad performance. They have asked me to record a sequence of the log when I want to make a query (with filters) in all of my images, i.e. clicking on "All Images" and waiting about 30s (!!) for my 17k pictures to be displayed as previews before filtering.
And I have seen many error warnings in the log, that I can't interpret, as I don't know anything about this matter. But anyway, it seems very suspicious to me. For instance:
[MOVariant(Private) loadAdjustmentLayersFromDatabase:variantRowid:error:] (in Capture One 10) + 503 [0x107a3f68b]
-[SQLite syncReading:error:] (in Capture One 10) + 290 [0x10780e7d9]
Of course I have sent them the log file, and I hope they will read and analyse it when necessary.
Wait and see.....
Robert0 -
I also was a beta tester and saw the kind of performance being discussed here. I filed reports for three beta versions, including sending logs, and was hoping for fixes in the actual release. Unfortunately what I see in the current version is maybe even a little worse than in the betas.
OTOH, I have a colleague who isn't seeing quite the problems I and others on this thread are reporting. While we're both seeing unbelievably slow performance while displaying search results, I see huge lags when typing filter criteria whereas he doesn't. I'm using a fresh catalog created by importing folders of Raw files, and the catalog has about 30k images. I also see this on a catalog of several thousand images created by upgrading an existing C1 v9 catalog.
I'm guessing that the problems we're seeing run pretty deep in the database and that perhaps Phase One isn't devoting sufficient resources toward solving the problem. I just hope they solve it in v10, because from what I'm seeing, I sure won't be upgrading to v11 with hopes like I had for v10.0 -
Faith,
same observation here. In beta test (smaller) catalogs worked mainly fine and I reported several bugs that prevented longer testing periods due to C1P crashing. This had been resolved in the final release.
Beside all the bugs reported I see the speed of catalogs going down the more often I use them. Just tested with a catalog I freshly converted which is much initially then the one I have been using for testing in the past days.
Best
Frank0 -
Reading this makes me cautious. Of course I prefer sessions and this read is more about catalogs. I have a new student that I am mentoring in the world of Fine Art Reproduction, and I cannot recommend C1 at this time except for sessions where there is less problems. I am looking into other library solutions.
I do think everything is moving too quickly. Everything from the OS. Hardware and software even from a monitor calibration standpoint. These new releases should only be made once all the bugs are fixed.0 -
[quote="Nature Isme" wrote:
I also was a beta tester and saw the kind of performance being discussed here. I filed reports for three beta versions, including sending logs, and was hoping for fixes in the actual release. Unfortunately what I see in the current version is maybe even a little worse than in the betas.
OTOH, I have a colleague who isn't seeing quite the problems I and others on this thread are reporting. While we're both seeing unbelievably slow performance while displaying search results, I see huge lags when typing filter criteria whereas he doesn't. I'm using a fresh catalog created by importing folders of Raw files, and the catalog has about 30k images. I also see this on a catalog of several thousand images created by upgrading an existing C1 v9 catalog.
I'm guessing that the problems we're seeing run pretty deep in the database and that perhaps Phase One isn't devoting sufficient resources toward solving the problem. I just hope they solve it in v10, because from what I'm seeing, I sure won't be upgrading to v11 with hopes like I had for v10.
I've found beta testing to be a considerable waste of time. The only benefit is that I get to know which bugs will likely surface in the new version and remain for a point release or two. Feedback falls on deaf ears -- and even if it doesn't, the illusion of such is enough to remove any effort on my part in future. Sad.
Worse yet, this was a major milestone release, or at least it should've been. Version 10 carries a lot of 'weight' and it seems as if this mark was missed and just factored as another release, another upgrade, another batch of features that weren't asked for (or likely to be used by 90% of the customer base -- a $1k set of wheels to adjust colour? I won't even bring that on 9/10 sets I work on). I'd rather GPU issues, Performance issues, Database issues.... I'd rather those get fixed, and maintained, and improved, and cared for.
When it's a running joke in the industry that "Capture One crashed, again!"... Not a great reputation to be constantly living up to.0 -
Without going over what others have already noted I just want to add a +1 to slow performance.
I'm new to Capture One with V10 being my first version of it. I've been learning to use it with a test catalog of currently just 700 images in it. Switching between images has become painfully slow, this seems to have happened since editing my first tiff image within photoshop. I now get the spinning beach ball plus the software crashing.
I hope this issue gets resolved soon. I don't really want to switch back go Lightroom.0 -
I just switched from Lightroom CC to Capture One 10 and find it incredible slow.
I only imported 30 sample images (RAW) and it takes 15 seconds to fully load the catalog. Even switching from one image to the other takes 2 seconds. Never had this problem on Lightroom, selecting images was always instant.
I'm running an 27 inch iMac latest version with 16 GB RAM.
Will this ever be fixed?0 -
I have several catalogs. The one I use regularly has 15,000+ images in it. The only time I notice it gets slow is when generating previews for a large addition to the catalog. I usually just leave it alone for 5-10 minutes and I am fine.
I have only a few hundred tiffs. I work in Canon Raw for most of my stuff.
I just finished converting my main catalog from a managed catalog to a referenced so I can use an SSD for my Capture One catalog file. I have not moved the file to the SSD yet but I am hoping it flies and generating previews goes much faster.
I am running CO on a 2010 Mac Pro base model. I have 32gb RAM and the stock video card with 1gb of RAM.0 -
I have a test catalog with 700 images (all Canon RAW) that has been slowing down since upgrading to C1 10. Over the weekend it became unbearably slow to do something as simple as navigating among images in the same collection.
While the catalog was created with C1 9, the latest 250 images were imported and previews built with v10. On a hunch I just regenerated all previews.
Navigation among images and among collections is now about as fast as it was in C1 9. MUCH faster than before I regenerated the previews.
Hopefully this will also help with editing speed, which also was noticeably slowing down before preview regeneration.0 -
My system is a late 2015 iMac 5K with 4Ghz CPU, 32GB Ram, 512GB SSD. Referenced catalogue, originals are on a NAS. During the initial launching of the program, there is no network activity. All previews are optimized to 5K screen, i.e. their resolutions are 5120 px
So I have tested how fast/slow my system is;
When I open the app with all images selected, it took 30 sec for 13565 pictures.
When I open the app with no images selected, it took 6 sec for 0 pictures.0 -
I'm using a 15'' MBP 2015 (top-notch configuration) with a Dell 5k Display (in 5k mode) and the only real problem I have is switching between the pictures. At the end editing a wedding session I look through the pictures if I didn't miss anything. This takes a little time.
Overall C1 (10) performance is significally faster than in lightroom. Lightroom is only useable when using smart objects, but on a 5k display these smart objects doesn't look good.0
Post is closed for comments.
Comments
120 comments