13.1.1 unuseably slow. Downgrade catalog?
I recently upgraded to 13.1.1
I have a client project, and the catalog upgraded
When I launched C1, it was extremely slow. CPU usage was going crazy, and I figured that it was some background process that had to complete with the catalog upgrade.
I waited maybe 2-3 hours, came back, and found the catalog was usable. I spent 4-5 hours working in the catalog.
Now I'm back, and relaunched C1. I am having the SAME issue. CPU usage is maxed out by Capture One. I've waited 10 minutes for one image to load at full resolution.
I guess I'll leave it running overnight and see if it's usable in the morning. But in the long run, I can't spend several hours everytime I launch C1 with this catalog.
Any troubleshooting?
Any way to downgrade the catalog so I can just use it with 20.0.4?
for what it's worth I have a maxed out 16" MBPRO.
Kicking myself for forgetting that you have to gave Capture One a good 6-8 months on a new release before the bugs are worked out. <big sigh>
-
Hi Jacob,
It's rather common that CPU usage is far above 100% with Capture One, it was already the case even with previous versions. What is NOT normal is that it takes hours to open your catalogue or images. What is the weight of your images ? Did you reimport your catalogue, or is it the same ?
Anyway, I would suggest to submit a ticket to the support. By the way, what is your MacOS ?
I am not sure you can downgrade the catalogue to 20.0.4. If you want to, the best way is to find your last catalogue backup (before you installed 13.1) and to start from it, maybe after removing the .backup extension.
0 -
Thank you for the response!
I have indeed opened a ticket with Capture One. Based on how long it took for them to respond to a previous (unrelated) ticket, I was not counting on hearing back from them in a timely manner, so thought there might be some good advice here.
By "weight" of images do you mean size? They are all 61.8MB raw files (Canon a7RIV from a two day advertising shoot)
The session (to be clear it's a session, not a database, I may have been confusing in my initial post) was upgraded automatically when I upgraded Capture One.
OS is 10.15.5
Yes, using the catalogue backup seems like a valid approach. I just hate to loose 4-5 hours of work.
However, From what I can tell, because I'm using a session, the image adjustments will be reflected when I open the old catalog. And perhaps if I change "auto sync sidecar XMP" to "full sync" I can even get my tags/ratings to appear in the old catalog?
The most satisfying solution would certainly be to find out what is going on, and to be confident that I can move forward using 13.1.1 for future shoots. However, perhaps the above is my best bet.
0 -
Jacob,
Can you please clarify whether you are using a Catalog or a Session basis in Capture One. They are different in several ways.
Forget the "database" aspect of anything for the moment.
Also whether your "session", if that is what you are using, is a session specifically for the shoot you have undertaken or something shared with other shoots and in other, earlier times.
If you are using a Session basis than the "Catalog backup" is not relevant - if you are referring to the Catalog Backup function.
Assuming further that all of thins activity you mention between catalog and session is within Capture One (i.e. if you DO have a C1 Catalog from an earlier version ...rather then, say, a Lightroom catalog) then the XMP sidecar sync points are not relevant.
It's difficult and perhaps unhelpful or even dangerous to try to provide any suggestion without a better and clearer understanding of what we are advising about.
As for the "weight" of images question I think Robert would be wondering about the Size of the entire set of files. How many Gigabytes most probably and perhaps the number of files.
0 -
Thanks for the feedback.
To answer your question, I'm using a session.
It is a session specifically for a single (two day) shoot.
Total size of session including raw files: 762 Gigs.
The backup I was reffering to is the file ending cosessiondb.backup that was created when upgrading.
0 -
You might look into creating a new catalog...and try to import your original session into it and see if you can salvage things that way?
HTH,
cayenne
0
投稿コメントは受け付けていません。
コメント
5件のコメント