Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Clutching at Straws

Simon Knight
I have a catalogue of 89,000 images. I can live with the general speed but on some occasions Capture One displays the beachball and if left to its own devices uses all the system memory and has to be Force Quit.

I have made several support requests but they have yet to come up with any helpful suggestions.

I won't bore you with the various things I have tried but I am now wondering if it is the files in my catalogue that are causing problems. I have noticed that I have a number of Tiffs that Capture One can't open and some images have several side car files created by ON1 and DxO.

I'm wondering that if I remove any suspect or odd files from my image folders if Capture One might start working as it should. So my question is have any of you experienced problems with bad data crashing Capture One?

Simon
0

Comments

7 comments

Date Votes
  • Eric Valk
    [quote="Skids" wrote:
    I have a catalogue of 89,000 images. I can live with the general speed but on some occasions Capture One displays the beachball and if left to its own devices uses all the system memory and has to be Force Quit.

    I have made several support requests but they have yet to come up with any helpful suggestions.

    I won't bore you with the various things I have tried but I am now wondering if it is the files in my catalogue that are causing problems. I have noticed that I have a number of Tiffs that Capture One can't open and some images have several side car files created by ON1 and DxO.

    I'm wondering that if I remove any suspect or odd files from my image folders if Capture One might start working as it should. So my question is have any of you experienced problems with bad data crashing Capture One?

    Simon

    I haven't had bad data crash Capture One since version 9 but I went through a cycle of removing all image files, especially TIFFs, audio and video, that Capture One couldn't open and I believe that did help.

    I don't think the dop sidecar files left by DXO are an issue as I still have them and they don't seem to be a problem. I believe that Capture One only refers to XMP files; if there is an XMP file that doesn't contain anything important I'd get rid of it.
    0
  • Eric Valk
    BTW how much RAM do you have installed?
    0
  • Simon Knight
    Hi,

    I'm using a MacBook Pro, Late 2013 with a quad core i7 processor clocked at 2.3 Ghz with 16Gbytes of RAM and a 500Gbyte SSD. I believe that any bottle necks are going to be in the use of external USB 3 mechanical drives but as I said above I can live with the speed if I can have reliability.

    Since my post I have removed all the video files, tiffs, psd and afphoto files along with some suspect jpegs. Some of the tiffs and jpegs were grey scale only, created by Hamrick Vuescan which Capture One refused to open. At the moment I'm importing images one year at a time into yet another new catalogue. So far the import has run without a hitch and significantly the creation of previews has occurred automatically and completed with the same number as the import count. This is the first time I have seen this happen on the import of a large number of files.

    I forgot all about audio files and will scan the folder tree once the present import finishes, so thanks for reminding me.

    Do you restrict the number of images you store in a single catalogue?

    best wishes
    Simon
    0
  • Eric Valk
    My biggest catalog is 16000 images, I have another 5000 images in sorting that will be added.

    However I have been very busy because my wife has been very ill, so I haven't had time to complete that and a number of other projects.

    I have seen comments from other users that they are successful with up to 120,000 images in a catalog.

    In Capture One 8 and Capture One 9, I went through a very similar process to yours (but smaller scale), first I tried importing my entire Aperture Library and the results were very poor, and often resulted in a hang after Capture One tried to consume upwards of 50GB of RAM.

    Then I broke the Aperture Library into smaller chunks, removed unsupported file types, and imported each chunk, it worked much better.

    In a later test I found that I could import the entire Aperture Library (with unsupported images removed). This could have been due to eitther or both of these factors
    • Capture One 10 instead of Capture One 9

    • Using a late 2015 iMac with 24GB of RAM instead of a late 2009 iMac with 16GB of RAM


    I do observe tthat Capture One is really heavily loaded during a big import, and no application multitasks well in such circumstances. So if I import 1000's of images, I shut down all other apps, and don't disturb C1 until the import part is completed. And once the import starts, I select a user collection that shows none or very few images, so that Capture One doesn't have to continually update the display.

    I still keep an eye on the RAM using activity monitor because I have seen conditions in the past where older Capture One consumes so much RAM (50GB+) that the operating system hangs. Not sure if it would happen for C1 12 and OSX 10.14.

    But if I saw a condition where C1 has grabbed significantly more virtual RAM than the actual RAM installed, e.g. more than 30GB of virtual RAM when I only have 24GB installed, that means that some of the assigned RAM is being swapped to the main drive, then I'd shut down C1 if the trend continues.
    0
  • Simon Knight
    Hi,
    Setting the record straight.
    Earlier I have reported on memory leaks and system hangs that have occurred while using Capture One to catalogue thousands of raw images. It now seems very likely that the problem is not with Capture One but was with the installation of Mac Operating System (OS) on my computer.

    A brief summary of a very long process is that I noticed that Apple Spotlight had stopped searching my hard drive.  This also meant that folder sizes did not update.  After many attempts at solving the problem Apple Support suggested that I reformat my internal drive and conduct a clean install of the OS.  Data and applications were restored from my TimeMachine backup.

    Since the reinstallation of the OS Capture One has imported and build previews of 35,000 raw files without any problems.

    It seems that Mac OS has gone full circle - anyone remember extension conflicts in OS 9 and earlier ?

    best wishes

    Simon
    0
  • Eric Valk
    Thanks for reporting back - another datapoint that might help some users.

    I too have had a freind come over with a very slow MacBook, and after the disk was formatted and the OS was reinstalled the performance was much better.
    0
  • Gerald Werner
    Hello just FYI.
    Last night Capture One 12 started crashing with every catalog I opened.

    Half an hour before I was processing some exports and hit accidentally the process button a second time. I stopped the batch, as the duplicates started, deleted the files from the question, ...
    Long story short. I was working in a different catalog for an hour and suddenly Capture closed. I could not open any catalog anymore. It looked like the program always tried to open the same catalog from an hour earlier.

    After removing the catalogs from their storage location, I was able to create a new one. I moved the catalogs back one after another until I hit the one crashing-
    I was able to open Captutre one with another catalog (not the one which leads to crashes).
    Now I could execute "Verify Catalog or Session" on the crashing catalog. The verification reported an error and offered repair.
    After this action, Capture one seems to be working fine.

    Maybe it helps others. I was for sure in panic for some time.

    Best Regards
    Gerald
    0

Post is closed for comments.