C! Import Craziness

Eric Nepean

• 29. Juni 2015 05:02

I have imported an Aperture Library of 6474 images into CaptureOnePro. 6470 images arrived in the CaptureOne catalog. After an evening of matching CaptureOne and Aperture screens I located the 4 missing images.

I then then wanted to combine this with another CaptureOne Catalog (9800 images) to create my master catalog.

Not wishing to risk either catalog, I started a new catalog, and imported the catalog of 6470 images into it.

The importer said that it was importing 6454 images (OK, why are there not 6470?)

Then when the import was successfully completed, the new catalog contained 5682 images. It looks to be dropping 10% of the images at random, the ones that are lost are no different than the others.

Do other users experience this incredible behavior, and how do you cope with it?

0

• 

  Paul Steunebrink

  • 29. Juni 2015 13:39

  Are all images referenced, and are they perhaps stored on external disks?

  0
• 

  Eric Nepean

  • 30. Juni 2015 01:09

  Hi Paul
  All images are referenced, and are stored on the hard drive inside the iMac.
  
  There is a folder structure like this on the main hard drive:
  /Users/Eric/Pictures/Photos
  ---- /Scans
  ---- /Before2000
  ---- /2001
  ---- /2002
  ---- /2003Camera1
  ---- /2003Camera2
  ---- /2004Camera2
  ---- /2004Project1
  ... and so forth
  
  The images were referenced by the no longer used Aperture Libraries, and it seemed easy and practical to leave them in place when importing into COP catalogs as a referenced images. In this way they are also firmly referenced to my backups.
  I have chosen "Prefer XMP Sidecar files" so each image file is now accompanied by an XMP file.
  
  Is there another storage arrangement which is more efficient?
  
  I have discovered today that if I sign out all other users and disable all optional SW (antivirus, email, browsers, dropbox, calendar) , then I can import the catalog with 6500 files into another catalog (empty for these tests) - everything works reasonably predictably until the COP message appears that copying is complete, there is only 5 seconds left, then the memory usage grows by the minute until there is 50GB of virtual memory and 20GB of swap memory in use (doing I know not what) and COP is paralyzed, then memory slowly ramps down and after 40 minutes or so it finally stops and CaptureOnePro is responsive once more - and all my file arrive safely. My mistake beforehand was to to not kill the other SW , and not to wait long enough, I guess.
  
  I tried to import the larger catalog with 9300 images into a new catalog, earlier that hung before it started copying. This time it ran until all the images were copied, then the memory required got very large (80GB of virtual memory?) and OSX ran out of application memory.
  
  So it seems one can export a 9300 image catalog, but not import it. I can work with that, but I am wondering if there is any sense in making one master catalog that big.
  
  Any suggestions you can make would be most appreciated.

  0

Post ist für Kommentare geschlossen.