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
-
It's been mentioned before, but this is a user forum with only occasional visits by Phase One staff. If you have issues with Capture One it's always better to log a support call - the more that they see, the more it helps to isolate the issues which undoubtedly exist for many Mac users. 0 -
[quote="atenolol" wrote:
They happily accepted our money.
And you happily spent it - nobody put a gun to your head, and you're free to walk away at any time.0 -
[quote="Keith Reeder" wrote:
[quote="atenolol" wrote:
They happily accepted our money.
And you happily spent it - nobody put a gun to your head, and you're free to walk away at any time.
I'm not sure that's fair.
I think it's reasonable to expect a product – like software, that grows over time... adding features and (presumably) refining code and fixing known problems – to get "better."
As wonderful as Capture One is in many ways I think many would agree that it has room for improvement – certainly in performance but also in features.
If C1 was a car or a toaster I might agree with you more but I think there is a reasonable expectation that issues that I (and many others) are aware of now may be dealt with in future versions.0 -
And I don't think there was a warning about performance issues such as "you cant use this program with more than 5000 images in the catalogue"
Then you could say "well you have had time to trial the product". Nobody will trial the product with full catalogue import or full editing in case of any issue with going back to a previous version. It's like you test drive a car but you don't go to a circuit to test drive it 😉0 -
Bump
CO 10 is really slow. Just want to have this thread at the top of the page.
Better make it sticky.
And they've written in the Release Notes:
"Performance focused re-write for faster viewing experience
Operations all over the app for have been re-written for snappier performance when viewing and working with images: Caching of images, reduction in drawing latency and frame rates for adjustments are all improved".
Oh.0 -
This ongoing issue for me ~32,000 images/catalog is the most frustrating thing. I know I need to edit it and get rid of images that I no longer want or need but it just takes forever for C1 process things that I'm about ready to throw in the towel.
Please C1 developers.... do something about this.0 -
I also bought v10 because of the much touted "performance improvements" claims. So far I see just the opposite compared to v8, v9. The only thing that seems better is the treatment of keywords and some of the search functionality. Switching among images in even a 400 image session (let alone a 20k image catalog) is significantly slower than in previous versions, and I don't notice any improvement in processing adjustments. Lately I'm especially with how miserably slow it is when reopening the program and then trying to display images with several existing adjustments. OpenCL settings don't matter; it's slow no matter what I do in preferences.
I beta tested C1 10 and didn't see quite this slowdown. In fact, it feels like v10's getting slower each time I open a catalog, so I'm going to try and clear caches or reinstalling the app as mentioned earlier.
For the record, my catalog's on SSD and the images are on a 7200rpm hard disk, both connected vial "slow" SATA 2 interfaces.
One thing's for sure: I won't upgrade to v11 as quickly as I did v10. Next time I'll test with a large [duplicate] catalog and run it for the full 30-day trial period before deciding.0 -
[quote="Keith Reeder" wrote:
[quote="atenolol" wrote:
They happily accepted our money.
And you happily spent it - nobody put a gun to your head, and you're free to walk away at any time.
Have been evaluating Phase One (Capture One and Media Pro) the last few days. Was a bit shocked at the choppy performance (spinning beach balls galore, force quit needed regularly) of C1 under "no load" for supposedly "pro" software, and found that Media Pro's UX feels like shareware on a retina iMac. Thankfully I took the time to investigate the user support forums.
With comments like this from existing customers seems like we'll be exercising my right to freely walk away before wasting any more time.0 -
[quote="NNN636248463567163672" wrote:
Have been evaluating Phase One (Capture One and Media Pro) the last few days. Was a bit shocked at the choppy performance (spinning beach balls galore, force quit needed regularly) of C1 under "no load" for supposedly "pro" software, and found that Media Pro's UX feels like shareware on a retina iMac. Thankfully I took the time to investigate the user support forums.
With comments like this from existing customers seems like we'll be exercising my right to freely walk away before wasting any more time.
I think you could have some problems with your computer config. C1 works quite well on my MBP Retina, except when I want to display all images for a query.
I don't know Media Pro, but all what I read is that iy doesn't bring much when compared with C1 catalog.0 -
Wanted to post here to let PhaseOne know that I too am experiencing major performance issues with v10. The lag between selecting thumbnails can be counted in seconds. As a result, editing has become an arduous nightmare. Every other function is fairly smooth and responsive.
There's less lag with .RAF files (Fuji X-T10 ) than with .CR2 files (Canon 1dX MKII and 5d MKIII)...but that may just be due to the slightly smaller file (16MP compared to 20MP). In both cases, poorer performance than v9, but really pronounced with .CR2s.
27" iMac - 3.4Ghz i7, AMD Radeon HD 6970M 2048 MB, OWC 6G SSD startup disk, edit from a Mercury Elite Pro Dual RAID connected via Thunderbolt. Running MacOS Sierra (10.12.3), C1 Pro 10.0.2.
My set up worked great until v10 came along. I hope they get to the bottom of the issue soon.
Thanks.
-Doug0 -
[quote="NN147446UL3" wrote:
Wanted to post here to let PhaseOne know that I too am experiencing major performance issues with v10. The lag between selecting thumbnails can be counted in seconds. As a result, editing has become an arduous nightmare. Every other function is fairly smooth and responsive.
There's less lag with .RAF files (Fuji X-T10 ) than with .CR2 files (Canon 1dX MKII and 5d MKIII)...but that may just be due to the slightly smaller file (16MP compared to 20MP). In both cases, poorer performance than v9, but really pronounced with .CR2s.
27" iMac - 3.4Ghz i7, AMD Radeon HD 6970M 2048 MB, OWC 6G SSD startup disk, edit from a Mercury Elite Pro Dual RAID connected via Thunderbolt. Running MacOS Sierra (10.12.3), C1 Pro 10.0.2.
My set up worked great until v10 came along. I hope they get to the bottom of the issue soon.
Thanks.
-Doug
For what it's worth, I did find that if I make the Browser larger (thus making the Viewer smaller) it speeds that issue up significantly. Still having lots of other issues, but that seems to fix that for me. Good luck!0 -
[quote="NN147446UL3" wrote:
Wanted to post here to let PhaseOne know that I too am experiencing major performance issues with v10. The lag between selecting thumbnails can be counted in seconds. As a result, editing has become an arduous nightmare. Every other function is fairly smooth and responsive.
There's less lag with .RAF files (Fuji X-T10 ) than with .CR2 files (Canon 1dX MKII and 5d MKIII)...but that may just be due to the slightly smaller file (16MP compared to 20MP). In both cases, poorer performance than v9, but really pronounced with .CR2s.
27" iMac - 3.4Ghz i7, AMD Radeon HD 6970M 2048 MB, OWC 6G SSD startup disk, edit from a Mercury Elite Pro Dual RAID connected via Thunderbolt. Running MacOS Sierra (10.12.3), C1 Pro 10.0.2.
My set up worked great until v10 came along. I hope they get to the bottom of the issue soon.
Thanks.
-Doug
Again, the forums are intended for users to interact - if you really want to let PhaseOne know about your issues, log a call with them...0 -
[quote="enkaytee" wrote:
Again, the forums are intended for users to interact - if you really want to let PhaseOne know about your issues, log a call with them...
Yes, the forum IS for the interaction of users, but: PhaseOne is monitoring them. You will see that there are quick replys for certain problems or questions.
They are just not answering here, because they do know that they have a really big issue which they are not able to fix. So they just decided to be quiet and hopefully nobody notices it.
And it is important for new customers to see this kind of threads, so they get an impression of the problems they might see, so they can do better testing beforhand.
Personally I got the feeling that the team for the development of C1 consist of only one or two developers. And they are good in algorithms for retouching, but they do not have any clue in databases or whatever.0 -
[quote="gfingerl" wrote:
[quote="enkaytee" wrote:
Again, the forums are intended for users to interact - if you really want to let PhaseOne know about your issues, log a call with them...
Yes, the forum IS for the interaction of users, but: PhaseOne is monitoring them. You will see that there are quick replys for certain problems or questions.
They are just not answering here, because they do know that they have a really big issue which they are not able to fix. So they just decided to be quiet and hopefully nobody notices it.
And it is important for new customers to see this kind of threads, so they get an impression of the problems they might see, so they can do better testing beforhand.
Personally I got the feeling that the team for the development of C1 consist of only one or two developers. And they are good in algorithms for retouching, but they do not have any clue in databases or whatever.
You may be right about the developers - their database skills seem to be pretty poor. While it's worth making comments here I'd always back them up by a logged call - at least then we can compare PhaseOne's official responses (or lack of them).0 -
I'm on a MacBook Pro 2015, and it's still going fast enough for me. 0 -
[quote="NNN636248463567163672" wrote:
With comments like this from existing customers seems like we'll be exercising my right to freely walk away before wasting any more time.
In other words, taking ownership of and responsibility for your own decisions?
Pity more aren't doing that.0 -
I'm pretty sure that phase one are able to analyse usage of their apps as they report back all the time.
They now everything about who, how much and often we use their application.
I'm waiting for a fix for the inspirational killer of spinning beach ball every time a single thread locks up the program. So they know I don't use the CO.
Yes I paid for it. And yes I'm free to walk away.
And yes I'm doing my work in other application instead because they let me be inspired.
So let's hope that 10.0.3 or 10.1 will fix all these annoying performance and DB crash problems.0 -
(Bump)
Yes, the CO 10.0.2 is still slooow.0 -
I wonder how long it will take to sort these performance problems.
The devs knows about them but it appear that they are having a hard time fixing them otherwise we would have seen a 10.0.3 already.
It would have been better if Support did not close the tickets as soon as they escalate them to another department because our problem is not solved. It just look good according to their SLA when they close them.
We get cut off from any feedback or progress reports.0 -
I'm gonna chime in.
What some of you may not realize is that Phase One isn't that big a company.
I have been using this software for quite a while so I speak with at least a little experience.
It has always been a bit buggy, but people have kinda worked around issues for the longest. Their user base has been less than the "big guys" so these issues haven't been deal breakers.
When Aperture was abandoned, I knew there would be an influx of new users. With the disdain for LR, CC there yet another group of migrants.
You guys were used to a certain standard (in the catalog side of things). C1 wasn't up to that standard. And now you are feeling let down.
When I saw that Aperture was being abandoned, and I knew how much better C1 was better than LR in raw conversion, it was obvious that C1 was going to have a lot of negative feedback.
Personally, I was excited by this.
You see, I knew that C1 had a superior raw conversion and an inferior catalog. When this influx of Aperture and LR folks came in, they had to up their game, and to a great extent, they have.
C1 catalog has issues, no denying that. However, the raw conversion is still phenomenal, at least as far Nikon is concerned. (that's all I have experience in).
Now if anyone thinks i'm a C1 apologist, just look at my past posts. I hold these guy's feet to the fire, as it is an expensive software.
All that being said, make your problems known to the C1 staff. I would think they want these issues to disappear. I would think they want to dominate the market. I firmly believe that they will if the catalog issue is solved.0 -
+1 😄 0 -
As a user of CO since version 8, the problem with 10 is that it is a massive step backwards from version 9 when using a catalogue with more than a few thousand images. eg hangs of 30+ seconds when changing albums and delays of many seconds simply clicking to select several images together in the browser (so much so that it is often unclear if you have even correctly clicked).
This is a regression since v9 and counter to the original marketing claims of vastly improved performance. Moving back to CO9 is also difficult either for catalogue compatibility issues or lack of support for recently released cameras.
I think the Tangent Wave integration, while interesting, was a mistake. It is not something that most users will benefit from and it must presumably have distracted from performance and functional holes (eg more flexibility in the vignetting tool, or anything to simplify colour calibration using passport-checkers etc, or the several seconds of lag I sometimes see when using the brush tool for local adjustments...).
Small companies desperately need razor sharp focus on where they apply their resources.0 -
From reading through this thread, with a few possible exceptions, it seems that the slowness is restricted to the database. Slow in selecting images, groups of images, applying metadata, and so on. I've seen this too, and am surprised at the level of CPU activity shown on my CPU meter when merely selecting an image.
Image adjustments, on the other hand, seem fast enough. There may be a slight lag on the display update as a slider (perhaps exposure) is moved, or when a brush on an adjustment layer is painting, but nothing that has, as of yet, frustrated me the way the catalog does.
And I too have a "solved" support ticket about the catalog slowness that ended with:
"You will still see speed issues but as stated earlier we are working on this. Thank you for your patience and recommendations."
I can't presume to have any idea about how easy the necessary fix is. Maybe its a database performance tweak. Maybe its a flawed database structure that will have to be overhauled from the bottom. Or perhaps its something not related to database operations that has to be done as part of metadata application and image selection.
But we all hope there's a 10.1 soon that gets this problem behind us. As Jimmy has said, once you get out of the database and on to image adjustment, I find that I get to the final image I want faster, and in many cases better, than I could have with Lightroom.0 -
[quote="Mark BCN" wrote:
As a user of CO since version 8, the problem with 10 is that it is a massive step backwards from version 9 when using a catalogue with more than a few thousand images. eg hangs of 30+ seconds when changing albums and delays of many seconds simply clicking to select several images together in the browser (so much so that it is often unclear if you have even correctly clicked).
This is a regression since v9 and counter to the original marketing claims of vastly improved performance. Moving back to CO9 is also difficult either for catalogue compatibility issues or lack of support for recently released cameras.
I think the Tangent Wave integration, while interesting, was a mistake. It is not something that most users will benefit from and it must presumably have distracted from performance and functional holes (eg more flexibility in the vignetting tool, or anything to simplify colour calibration using passport-checkers etc, or the several seconds of lag I sometimes see when using the brush tool for local adjustments...).
Small companies desperately need razor sharp focus on where they apply their resources.
The weird thing is, V10 is actually better on my system. I'm not saying that it is on everybody's, thats sorta obvious.
My system is dated as far as the computer world goes, but other than the lengthy startup, things run smoothly.
If you are interested, I'm running:
2012 Mac Pro,3.33 Ghz 6 core processor
32 gb 1333 DDR3 Ram
A 7950 Video Card.
C1 is referenced catalog, where the original images are on a HDD and the Catalog is on a SSD. (There was no speed improvement putting the referenced images on a SSD)
Wacom Tablet
Tangent KB and MF panels.
Now as far as the Tangent setup goes, well, I like it. It does make editing quicker, easier, and actually fun.
Guess what, it has bugs too. Again, it's not a show stopper, but is aggravating. As soon as I can reproduce the hangs, I'll open a support ticket.
IMO, the vignetting tool is far superior to that of LR. I have found that I have to tweak the tool in LR to get the look I like in C1. Its a waste of time. But to each their own.
It sounds to me that some folks want C1 to be like LR. Well it's not, nor do I want it to be. Would I like the catalog to be like LR, you betcha But that's as far as it goes, If I had the choice of losing all that color control for the sake of a better catalog, I'd just deal with the catalog issues. You could always use another DAM, and edit in C1. LR doesn't even give you that option. For a while, I was using LR as my DAM and editing in C1, saving as a Tiff and importing it back into LR.
But now that things have improved on MY setup, well, I just don't fool with LR.
The only reason I keep the CC subscription is Photoshop, and Affinity is nipping at their heals.
I believe the problem with the catalogs being the slowest to improve is that beta testers aren't so inclined to use their own catalogs as test subjects, I know I'm not. Maybe I should. Maybe i'll take one for the team. Who knows?
I believe it will get worked out, just be patient.0 -
Very interesting. I'm also running a 2012 MP with 32TB of RAM, a Sapphire Radeon 7950 GPU, booting off a PCI SSD, storing the catalog on a different internal SSD, referenced photos on an internal spinning disk. My machine's got the base 4-core CPU, though.
I also run it on a 2012 MBP—top end configuration that's been upgraded to 16GB of RAM and a 1TB SSD.
Both systems are running 10.11.6, although I've also tested the Pro with 10.12.3 and 10.12.4. And on all systems, C1 hammers the drives something crazy (I use iStat Menus to monitor a lot of system usage parameters).
In all cases, opening a catalog, changing among collections that have more than a couple of hundred images, moving among individual images and any other operations having to do with image selection are remarkably slower than in C1 v9. Image adjustments themselves are faster and I prefer the results [just a little bit] over v8 and v9.
I wonder what other differences between your and my environments may be to get such different results. But from my PoV, I'm still trying to figure out C1 10 claims about being a major performance improvement over 9.0 -
[quote="Nature Isme" wrote:
Very interesting. I'm also running a 2012 MP with 32TB of RAM, a Sapphire Radeon 7950 GPU, booting off a PCI SSD, storing the catalog on a different internal SSD, referenced photos on an internal spinning disk. My machine's got the base 4-core CPU, though.
I also run it on a 2012 MBP—top end configuration that's been upgraded to 16GB of RAM and a 1TB SSD.
Both systems are running 10.11.6, although I've also tested the Pro with 10.12.3 and 10.12.4. And on all systems, C1 hammers the drives something crazy (I use iStat Menus to monitor a lot of system usage parameters).
In all cases, opening a catalog, changing among collections that have more than a couple of hundred images, moving among individual images and any other operations having to do with image selection are remarkably slower than in C1 v9. Image adjustments themselves are faster and I prefer the results [just a little bit] over v8 and v9.
I wonder what other differences between your and my environments may be to get such different results. But from my PoV, I'm still trying to figure out C1 10 claims about being a major performance improvement over 9.
That is curious indeed. Your system is identical to mine. Surely the extra two cores aren't making that much of a difference.
All I can figure on the promise of better performance is that must have been the case on a their select machines. Also, I'm wondering whether the Windows users are having the same issues.
Which brings me to the fact that this may be my last Mac now that the trashcan has made its debut. I'm hoping Apple will see the folly of that system and go back to the modular tower.
And not to be a negative Nancy, but Apple's new filesystem is supposed to roll out this fall, so........0 -
Lot of the beach balling I have on my 8 core i7 MacMini is related to the single thread of CO trying to write something super slow to the SSD. It appears as if the performance of whole CO is dependant of this single threaded write sequence.
It's so annoying and effective in killing my creativity that I've stoped using CO. I check out these forums in hope of a 10.0.3 version. It's sad because it have such potential. :/0 -
I too find it slow. Start-up is over two minutes.
If I close it and start it again immeduiatekly, it drops to 45 seconds. Then for a third time it is 33 secs. I should be happy with that probably. But if I have not used C1 for a day it is back to over 2 minutes.
Sierra, iMac 27", SSD with the software and as path for the backup; Spinning Disk for images. Using catalogue.I do have a NAS but I am not referencing it. I use that for Lightroom.
Importing is also very slow: the images do not load from the card quickly. Takes ages. And pressing the 'go' button freezes the machine.
Using a session is the same (that is why I switched to catalogue).
Probably C1 internals switched to an object database. I have seen such things in my ICT past. Great performance on a A4 test setting, not in real life - could be, but the parameters must be totally different.
You know. My Lightroom is so swift, even having 40k images.0 -
Good news !! Thanks Fatih !! 0 -
Just to give an update on my reports from yesterday.
I installed Sierra (I checked and I still has El Capitan); now C1 starts in 90 secs. A huge improvement.
During startup I checked the activity monitor. I saw that there was a process that took all the time: CVM Compiler, it was active for almost 60 secs.
I will look for the beta. I once participated in that amabasador thing.0
Post is closed for comments.
Comments
120 comments