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. ⚠️

Write interval for Catalogs - too slow

ThomasGeist
Whatever Capture One 7.x's write interval for changed parameters in catalogs is, it is too slow. I had my computer crash and once I restarted it and C1 the ten images I edited were back to their unaltered state.

Which means ... C1 hasn't written the changes into the catalog database for a period as long as it took me to work on ten images (and I am not very fast). That is WAY too slow. I would expect for C1 to lose 1 or max. 2 images.

(I had another crash a while ago and the result was similar: a large number of images lost their edits.)
0

Comments

4 comments

Date Votes
  • MidWestTech
    To get a little better appreciation of your problem, would you mind sharing what version of C1Pro7 you are running, what version of OSX you are running, what model Mac, Specs on your Mac (RAM, processor, video card, HD or SSD, etc), What camera's files are you editing?
    0
  • ThomasGeist
    Sure!
    OS X 10.9.2
    Mid 2010 Mac Pro (5,1), 2.8 GHz Quad-Core Intel Xeon, 16 GB 1066 MHz DDR3 ECC, ATI Radeon HD 5770 1024 MB

    Capture One 7.2.1
    D800 and Canon 5D Mark III RAW images
    Catalog and image files are off a Samsung SSD, however I was working on offline images at the time
    0
  • MidWestTech
    If you actually open the catalog up and watch it work (how often new files write) it is actually fairly fast. I have a feeling that something else is hanging up in the background and causing the changes not to be written at all which eventually leads to a subsequent crash.

    Have you dove into the Console and looked at your user diagnostic reports for any indication of what the issue might be?
    0
  • MidWestTech
    If you actually open the catalog up and watch it work (how often new files write) it is actually fairly fast. I have a feeling that something else is hanging up in the background and causing the changes not to be written at all which eventually leads to a subsequent crash.

    Have you dove into the Console and looked at your user diagnostic reports for any indication of what the issue might be?
    0

Post is closed for comments.