Capture One unresponsive when searching/filtering – ?
Do other users see Capture One becoming unresponsive when searching/filtering? I assume this mostly happens when using larger catalogues. I've had this issue since I started using Capture One a few years ago, so in my experience it's not specific to M1 Macs or to any particular versions of Capture One, but most likely has to do with limitations to the database.
-
I see the same. I believe it's both the way they built the database and the way they conduct searches. I'm sure you've noticed that Capture One tries to find items that satisfy the requests as each letter is typed. I'm a really fast typist and can rarely get 3-4 letters entered before C1 starts searching. So apparently the search restarts as each letter is entered. Once I have enough letters typed in to specify what I want (and thus stop typing) results are returned fairly quickly.
Another slowdown happens when you want to enter multiple criteria. Again, search restarts as each letter of subsequent criteria is entered.
They really need to do a lot of work on the database, as has been pointed out for years both here and in direct feedback (I know: I've given my feedback to them and I've read of others who've done the same). Unfortunately it seems that they're not very interested in fixing this very important part of the program.
0 -
Thanks for your reply.
To avoid what you describe, I usually write the search term elsewhere so I can copy it and then paste it into the search field in Capture One.
It seems to be common knowledge that Capture One is bad at handling larger catalogues, and you should think it would be about time they did something about it.
The reason I ask is that I have an open support request about this specific issue. It's been two months since I submitted the request, and they're still working on reproducing the issue, they claim. Considering that it appears to be a common problem, it does not sound entirely credible that they should have trouble reproducing it.
0 -
Yes; I do that as well. Frankly, from the numerous posts I've seen here, on FM Forums, and DPReview, this is a big issue that C1 obviously doesn't deem sufficiently important to fix. Oh well...
0 -
I asked about this in the Windows section of the forum too (here). One confirmation so far.
0
Post is closed for comments.
Comments
4 comments