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
-
I'm finding C1 v10 extremely slow too - much, much slower than v9. I'm not sure what the claims of increased speed an efficiency are based on. It can take 3-4 secs to select an image; up to 5 secs to apply an adjustment once I've moved a slider; constant pixelation of images when moving between them - it's like walking through mud.
I've tried suggestions I've seen on this forum such as turning off hardware acceleration, but nothing seems to help.
I'm running: OS Sierra 10.12.1; MacBook Pro (Retina, 13-inch, Mid 2014); 3 GHz Intel Core i7; 16 GB 1600 MHz DDR3; Intel Iris 1536 MB.
I'm not giving C1 up, but it is very frustrating when updates, which hype up increased speed and efficiency, are actually slower than their predecessor on the same spec machine.
P.S. I work in sessions0 -
I tested the demo with my session catalog
For 2 dayes and found also no speed
I ask my self way should i change my
My better workend v9 .0 -
I have been using C1 since version 7 with not too many issues on each upgrade. However 10 is awful, it crawls... especially just going from picture to picture. I wish I hadn't bothered to upgrade ! I mainly did it for auto masking for Fuji and the speal of it being faster !!
Mac Mini quad core, 950 SSD, 16GB, Sierra, EIZO monitor. Work in catalogues.
Hope there is a firmware upgrade very very soon. Its putting me off using it and I spend many hours gladly just editing my pics until now.0 -
Fully agree.
+
C1P10 is the most unstable and least performing release since I started with C1P8. Even worse it is advertised as "Capture One 10 is a major release with several new features and large scale performance and stability improvements to the Capture One experience" in the release notes and besides some (minor) additional feature I was expecting to pay mostly for performance and stability increase and this is certainly not the case.
Best
FL
PS: I wonder if ever 5% of all customers will use Tangent Systems. I tried the App a couple of times and have then uninstalled it as I cannot see any benefit of using it (and having an insane price). The hardware might be better due to haptic feedback but is even worse with respect to pricing.0 -
🤓 🤓
i am just wondering what you guys are running it on...
I am an ambassador myself. I beta tested and I can tell you that with the exception of a couple of bugs the software is stable and fast.
It slows to a crawl if you use tiffs, that it does. any adjustments you make on a tiff file takes forever but on raw files it flies
care to tell us your sys config?0 -
Selecting and deselecting of thumbnails is awfully slow. Sometimes the beachball is running. All in all not very promising. This is definitely not an upgrade dealing with speed improvments. 0 -
iMAC 27 i7 3.4 GHz, 24 GB RAM, 680 MX 2GB, images either on NAS with catalog on SSD (400 MB/s) or all on SSD, latest Sierra with all updates. During beta test I used catalogs with few hundred images and that was fine. Once I get into a couple of thousand (all referenced) the problem start. If they are on a NAS (currently not recommended) it gets even worse.
Try a catalog with 10 or more thousand images and click on the all images collection.0 -
[quote="FL" wrote:
Try a catalog with 10 or more thousand images and click on the all images collection.
Yes. I have a catalog of 17,000 + images, and when I click on "All Images", it takes about 30 s to display all the images, while it was 5s with v9. I submitted a case #236310, and the last answer I got was : Merry Christmas 😭 and the case was reported as solved !!0 -
Sorry guys, but You will have to be much more specific in your statements.
What is slow?
What kind of files are you working with ?
What are you doing when it is slow ?
We currently know of an issue with Tiff handling, which will be solved.
Contacting our Support will get You further than this user forum, as we 1) got a fighting chance to sit down and help You one on one, and 2) can register your issues for further tracking and prioritization.0 -
Hi Christian,
Thank you for reading us. I have given the support team all the details in my case #236310, but I am ready to give them one more:
The catalog has been improved significantly with the v10, specifically by the new functionality of renaming, moving files within Capture One, with immediate effect on the files and folders storing device.
An other function of the catalog, very important to me, is to find, for instance, the pictures taken in Paris with my Summicron 90mm in May 2015. For that, I have to go to "All Images", display all the pictures in the browser, and then apply the filters. Displaying my 17,000 + pictures takes about 30s after clicking on "All Images", while it took only 5s with v9.
In Lightroom (that I quit because of its poor capacities of development), it is immediate.
All the other operations are very fast on my computer (MacBook Pro early 2014, SSD 512 GB, RAM 16 GB, referenced catalog on an external HDD 1TB 7200 rpm).
Cheers,
Robert0 -
[quote="tenmangu81" wrote:
[quote="FL" wrote:
and the case was reported as solved !!
The solved-status is seen as a Support status. They have done their job of reporting your issue to R&D.0 -
[quote="Christian Gruner" wrote:
[quote="tenmangu81" wrote:
[quote="FL" wrote:
and the case was reported as solved !!
The solved-status is seen as a Support status. They have done their job of reporting your issue to R&D.
We mentioned that previously, but let me say it once more : this "Solved" statement is very confusing to a lot of users. Makes them think that the issue was indeed solved or that Phase One doesn't give a damn. Could you consider changing it to something more meaningful to the end-user, such as "Reported" ? Thx.0 -
[quote="John Doe" wrote:
Could you consider changing it to something more meaningful to the end-user, such as "Reported" ? Thx.
You have to take that up with the Support Team directly.0 -
Christian,
"Sorry guys, but You will have to be much more specific in your statements. "
I have several support cases submitted on this and also described some of the issues in more detail here in the forum
viewtopic.php?f=68&t=25212
Even though I have had extensive discussion with support and they see the issue the last response was "this should not be the case" as well as that 15s of spinning wheel when selecting a collection with just 4000 images "seems ok". Neither does help nor gives me the feedback that the issues are going to be solved and they make working with V10 basically impossible.
Version 9 was/is much much faster on the same catalogs and also more stable as the big memory bug had finally been resolved in V9 is now back.
Best
Frank0 -
[quote="Christian Gruner" wrote:
[quote="John Doe" wrote:
Could you consider changing it to something more meaningful to the end-user, such as "Reported" ? Thx.
You have to take that up with the Support Team directly.
Done, thx. 😊0 -
[quote="Christian Gruner" wrote:
[quote="tenmangu81" wrote:
[quote="FL" wrote:
and the case was reported as solved !!
The solved-status is seen as a Support status. They have done their job of reporting your issue to R&D.
Thanks Cristian !! I was confused with the terminology. Seems to be solved 😂 as John reported to the development team. Thanks John.0 -
I had this very same discussion about "solved" with support roughly a year ago and asked them to change their reporting as once it is reported to R&D you have to re-open a new case to start the discussion again if nothing happens or the solution is not working.
So far support did not change the reporting but I keep my fingers crossed that it will happen eventually ...0 -
[quote="FL" wrote:
I had this very same discussion about "solved" with support roughly a year ago and asked them to change their reporting as once it is reported to R&D you have to re-open a new case to start the discussion again if nothing happens or the solution is not working.
So far support did not change the reporting but I keep my fingers crossed that it will happen eventually ...
That may be a limitation of the the software system deployed.
If so, and if it is not an entirely flexible system, making a change may be a major undertaking.
When I worked as part of a team developing Service Management systems (a long time ago) we got around that annoyance (for both parties as it turned out) by creating a "follow-up" record should one become necessary.
However creating the record and linking to the original (or previous record if a chain of reports came into existence) was the easy bit. Dealing with all of the different customers with different views about how the management control and reporting should be dealt with took some time to specify and develop into a system that people were happy about.
It's amazing how many different status descriptions can be "absolutely necessary" (and utterly confusing) if you make a system really flexible!
Grant0 -
Dear Christian,
It is not that we are not trying to be specific. I think you guys should be aware that this is not a "minority report". While a lot of people are reporting the same issue, and a lot of them are experienced users of CO, I assume that Phase One will look into it quickly and tell us, "Yea, we realise that, we are fixing it."
As an ambassador, I have been telling people to use it and my students keep coming back to me and ask about it. So do you think if I should tell all of them to report in a case very specifically?
Ok, so you want me to go specific, I will try.
2013 Retina Macbook Pro
2.6GHz i7
16G 1600 Ram
GeForce GT750M 2048Mb
Run on internal SSD and also Lacie external thunderbolt SSD 500G sometimes
Browsing through images are obviously slower than CO9. Both images by IQ3 100mp and also Canon, nikon and sony images. Adjustment is also reacting slowly. as least not as "real time" as before.0 -
[quote="Christian Gruner" wrote:
We currently know of an issue with Tiff handling, which will be solved.
You do realise the TIFF problem has been around since version 9.0.0 ?
With the number of problems pertaining to performance with v10 that users have cited in this forum, it makes me wonder what is Phase One's performance testing methodology ?0 -
[quote="col_du_aspin" wrote:
[quote="Christian Gruner" wrote:
We currently know of an issue with Tiff handling, which will be solved.
You do realise the TIFF problem has been around since version 9.0.0 ?
With the number of problems pertaining to performance with v10 that users have cited in this forum, it makes me wonder what is Phase One's performance testing methodology ?
We have found a regression bug (from 9.3.0) in the tiff handling, that will be fixed in an upcoming service release.0 -
[quote="Christian Gruner" wrote:
We have found a regression bug (from 9.3.0) in the tiff handling, that will be fixed in an upcoming service release.
Who says the Phase One team is not responsive ? Even on Sundays 😄0 -
[quote="Christian Gruner" wrote:
We have found a regression bug (from 9.3.0) in the tiff handling, that will be fixed in an upcoming service release.
Hey Christian, thanks for responding to this even on a Sunday. 😊
I'm a little confused as to why this bug regressed from 9.3.0 when TIFF performance was just as bad in 9.1.2 ? Could it be that you and I are talking about two different bugs ?
I will keep my fingers crossed with the hope that your service release is coming soon and that all TIFF issues are resolved and doesn't cause problems on Windows. Reverting to Windows is my solution if the TIFF is still poor under Mac OS.0 -
[quote="col_du_aspin" wrote:
[quote="Christian Gruner" wrote:
We have found a regression bug (from 9.3.0) in the tiff handling, that will be fixed in an upcoming service release.
Hey Christian, thanks for responding to this even on a Sunday. 😊
I'm a little confused as to why this bug regressed from 9.3.0 when TIFF performance was just as bad in 9.1.2 ? Could it be that you and I are talking about two different bugs ?
I will keep my fingers crossed with the hope that your service release is coming soon and that all TIFF issues are resolved and doesn't cause problems on Windows. Reverting to Windows is my solution if the TIFF is still poor under Mac OS.
We are very likely talking about different things, yes. We will of course continue to improve every aspect of CO, but Rome wasn't built in a day, as they say.0 -
My very slow response is working with RAW only and just browsing from one picture to another. I have to give C10 a while to catch up before going to the next picture using arrow key. If I use the trackpad to scroll down the thumbnails its even slower !
I will submit a ticket.
I didn't see get this beach ball whilst viewing on Beta test. Its not that zippy as 9.3 when editing also !
System:
Mac OS Sierra 10.12.2
2.3 i7 Quad Mac Mini
16 GB Ram
1TB SSD (which has hundreds of GB free)
Intel HD 000 1536MB
Working in catalogues.
I have turned off CL but making no difference at all. This is the only version since 7 that I have experienced crawl like performance.0 -
[quote="Minigill" wrote:
I didn't see get this beach ball whilst viewing on Beta test. Its not that zippy as 9.3 when editing also !
Out of interest, did you run the final beta that was available just before release?
If so was that OK at the time?
I would surmise that whatever is different between how your system was set up for the test and how is is set up for live use now may be where clues about what is happening can be identified.
Could it be something as basic as a different size of catalogue?
Grant0 -
[quote="SFA" wrote:
Could it be something as basic as a different size of catalogue?
Grant
Ha ha !! Yes, it could be that, as most of the betatesters test with small and provisory catalogs, in order not to corrupt their real one(s).0 -
Hi Grant
Yes, I don't use the full catalogue when beta testing, a much smaller one. Was using the latest beta version. Its the same computer also. I used a smaller catalogue when Beta testing V9 (can't remember which version I started testing) and there was no difference between testing and the final production until now.
Compared to V9.3 its like night and day, not sure which you class as the slow one, but the speed difference is very noticeable ! Current catalogue is about 5,000 pics so no where near as large as some people run.
Hope there is a fix in the next update. I am not sure about doing a clean install, bit nervous of loosing everything, or making a mess of things, although I back up when closing after doing any edits every time (in Capture) and its fully backed up to TM & Crash plan oh and NAS !
I am just an enthusiast with editing, nothing hugely technical !
I have everything else shut down when using Capture, like internet etc. Not seeing a huge draw, about 3-4GB (in the terminal). V9 in the early days was 10GB and quicker.
All the pictures are on the SSD.
Edit: I will create a new catalogue at the weekend with less images and see if this helps highlights an issue.0 -
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.0 -
I fully understand why people use a small catalogue when testing. It makes a lot of sense and may be necessary anyway unless available hardware has a lot of storage capacity.
The problem is that IF IT IS an issue related to a combination of catalogue size AND specific configuration then performance issues will likely not be discovered.
In a development test lab set up one may think the most bases of configuration challenges have been covered - but still some can be missed.
If one has nothing else running on the system in terms of applications other than "system stuff" there is at least (and in theory) a limited amount of diagnostic work to do. Testing RAID arrays, NAS handling, any real time backup software and so on would be good first time investigations. Sync via XMP files too if people are using that.
The other useful comparison would be to compare the configuration of two machines where one is apparently slow and the other not. Check out the differences and eliminate possible causes. But I guess that would require someone who has that situation and I suspect that most people with 2 machines are running very similar configurations for them in terms of software, NAS and so on. Thus there might not be anything easy to compare.
All rather puzzling if results are not consistent across a large selection of installations.
Grant0
Post is closed for comments.
Comments
120 comments