Switched from Sessions to using a Catalog, and Capture One 21.1.1 crashes regularly
I have been working with Sessions for the last 4 years and never had unexpected crashes. After switching to a Catalog workflow, I'm getting numerous regular crashes when doing operations with the catalog, selecting or filtering images, navigating, etc.
I always press the key to send the reports both to Apple and Capture One, but a friend who has a much larger catalog doesn't report the same issues.
What could it be? I've removed it per the instructions online, reinstalled it, removed old conflicting extensions from my system that were creating conflicts with a different application, have 64Gb of RAM, and cannot figure out what is going on.
I have build 14.1.1.63
Thanks for any insights!
René
-
I did not experience as many crashes with any previous versions
either… and I only work in session — similar machine and version.0 -
I've been working with catalogs since C1 8 and never encountered problems like this. Perhaps your catalog is corrupt. Have you tried having C1 Verify the catalog (far down in the File menu)?
Another possibility is that one or more of your files is corrupt. I had that happen once: a couple of .mov files were screwy (I still don't know what was wrong with them), and every time C1 encountered them, including parsing a selection that included them, it would spontaneously crash. I eventually ran a tool (can't remember if it was TechTool Pro, Drive Genius, or another one), found the corrupted files and removed them, and the catalog's behaved fine since.
0 -
My catalog is brand new, and I only have NEF files. Never had a problem with Sessions but they started as soon as I created my catalog. I have <23K images, so not a huge catalog by any means.
How do I get in touch with Technical Support to see if they can troubleshoot what is going on?
0 -
Here is the information page about the process. It contains the link you require.
Once you know how it is intended to work it is worth knowing, for future reference, that the link can also be found on the top line of the Forum pages and in the bottom part of Knowledge Base documents.
0 -
Meanwhile,
New Catalog or not, try the verification process to see what it reports. Something may have gone awry during creation.
Also, perhaps, check for any unsupported file types or files with mis-named types, files that do not meet the size or colour space requirements and the log files for the creation of the OpenCL GPU drivers (if any).
It is likely to be an internal system problem but that alone does not necessarily help you since there are so many variables in play.
Having one time many versions ago had a similar sounding problem with a session running under Windows 7 I have a lot of sympathy for your sitaution.
In my case, I found the problem by chance halfway through an edit of about 3000 images.
A file that I would have arrived at almost at the end of my editing activity for the session presented with a corrupt thumbnail. I tried refreshing the Preview and thumbnail but it looked just the same.
Attempts to edit the image failed.
I deleted it and then re-imported the original and all was well thereafter.
During my investigation, I noticed that the internal Windows reference to one of the file fragments making up the image looked quite unusual in that it ended with a long string of zeros. I suspect that the fragment ID was incomplete for some reason and the result was that it would be picked up as an incorrect reference for a file fragment to be attached to other images - about every 10th image iirc. If the data the fragment contained was the wrong type of data for the field the application thought it was processing it would likely crash the system without being trapped since it was a system-level problem at the point of introduction and the Application has to assume that file fragment data managed by the system is being correctly gathered and presented. It's not realistic to build in error checking at the file fragment level within an Application.
I am not suggesting that your problem is the same as mine was back in V7.
However, something creating a similar effect may be possible. My problem with that session started pretty much as soon as it was created as far as I recall.
0 -
Thanks for all the guidance and suggestions. I'll run the verification process, but I run both the optimize and verify options every time I close the catalog. Sill, I'll run the one from the menu and see what it says.
I'll check to see if there is anything weird with my images that I can find.
René
0 -
Verification showed everything is OK.
0 -
That suggests that either the problem lies not with the catalog but with system or image related data OR it is the catalog but something obscure and not considered by the Verification process.
You could check the log files.
I would also be sure to create a Support Case using the "Submit a request" option.
The automatic crash reports, as I understand things, are mainly used for generic statistics and problem trend analysis rather than offering personalised support.
A Support Case should provide a Case reference number and initial e-mail contact once C1 staff have looked at the log files that are requested as part of the Case creation process.
Does this problem exist on a single catalog?
Have you tried creating a new catalog and, if so do you get the same results?
Is the catalog small enough to consider a test that involves exporting it to a session to see if the session produces the same problems?
Information in the log files that reports what is happening right up to the point immediately before the crash may well be useful when trying to find things to consider and investigate as possible sources of the problem.
0 -
Where is your catalog located? On an internal drive? External drive? Network drive?
I ask because I recall reading several complaints of issues when people were using a network drive. I do not know if those issues were resolved.
0 -
My catalog is on the internal SSD, and the library is on a Thunderbolt RAID.
I sent an e-mail and attached the file that is created for support, hopefully that will help and someone will get back to me. Not sure I'm knowledgeable enough to make more sense from any other logs, but will see what I can figure out.
The idea to create a session from the catalog is interesting; I still have many sessions I haven't converted, so perhaps I'll work on those and see if I get the crashes.
René
0
La publicación no admite más comentarios.
Comentarios
10 comentarios