You are here

2 posts / 0 new
Last post
NewB trying to get started with mid-size library import #1
ApertureLabRat's picture
by ApertureLabRat
February 7, 2014 - 11:36am

Hi all.

My platform is an older MacBook Pro, so I’m kinda stuck at Snow Leopard and have purchased Aperture 3.  My photo library is already organised into a folder hierarchy by years and dates, on the household NAS, and I’m trying to import it as Referenced rather than eat up space on my internal drive.  I have read a little about importing and am trying the “import folders as projects” route so that I can ingest a whole hierarchy in one operation.  I have checked the “leave in their current locations” option.

So… I have maybe 80,000 images of moderate size (not very high res).  On first attempt, the import ran for 18 hours and used up all the memory on my MacBook (even with other large apps shut down):  by the next morning it was clearly in terminal swap frenzy with 10M memory free and the “rainbow lollipop” busy cursor, not responding.  I sent the Aperture process a HUP and did some online reading to see if I could find a better way to do the import.

I tried setting the app to start in 32 bit mode (this was recommended in some venues as a cure for very slow imports).  I then tried opt-cmd-click on the Ap Library icon to force a library rebuild.  I did not get the expected Repair Library dialogue.  Instead, Ap went back to “Processing”.  I cancelled that task via the task listbox, and tried “Delete Folder” in the hope of starting over.  No dice:  Ap went off the rails again, busied out and would not respond to any further input (no confirm dialogue for the delete ever came up).

So far I have to admit I’m a little frustrated.  Must I really import the library in smaller chunks, manually?  How many days or weeks may I expect this to take?  How long *should* it take to import 80K files (only 39GB of image data!)?  What should I do now, to start over with a better prospect of success? 

I would rather use Ap than LR because I’m more into organising, albums, book production etc than into heavy post processing, and I like the “referenced” option which suits my workflow.  But so far it appears rather painful and frustrating to try to get Ap to recognise the existing photo library.  Previously I was a Picasa user, and that was fine until I moved photos to the NAS :-)  Picasa does not respond well (understatement)  to having any part of its library come and go with network interruptions.  I was hoping Aperture would solve that problem.  I still hope it can.

Can anyone help me with a “best practise” for getting Ap 3 (fully updated for Snow Leopard) to import a large number of smallish images w/o running right out of RAM and going catatonic?


de (feeling like I’m trapped in Aperture Labs)

-- Cortes Island BC

ApertureLabRat's picture
by ApertureLabRat
February 8, 2014 - 10:36am

No advice?  uh-oh.

I started over from scratch (destroyed my Ap Library and relaunched) in 32 bit mode and watched OSX closely while importing a small chunk of the photo library (7200 images approx).  Also watched Ap’s process window.  It took over 3 hours to ingest the 7200 images, and sure nuff, as I have read elsewhere, Ap slowly ate all the system memory.   With each folder processed, a bit more free mem disappeared.  After 2.5 hours we were down to only 10M free, with a couple of gig of inswap history, not a good sign.

My current thinking is that 4GB is not enough memory to run Ap3:  it seems to be a hog even in 32 bit mode.  I’ve ordered DIMMs for upgrading to 8GB (this is going to be an expensive photo organiser tool before I’m done).  Would others concur with this conclusion?

I’m hoping not to be told that Ap4 is the solution, ‘cos that would force me to upgrade past 10.6.8 and from what I read, that’s not such a good idea for my laptop.

-- Cortes Island BC

You may login with either your assigned username or your e-mail address.
Passwords are case-sensitive - Forgot your password?
© 2019 All rights reserved.