You are here

8 posts / 0 new
Last post
Aperture 2.1.4 crashed/pics gone forever? #1
monotypemaker's picture
by monotypemaker
February 18, 2013 - 7:09am

Hi All–
I'm a newbie at on-line questions, so forgive if I'm not following protocol in some way. I'm still using Aperture 2.1.4 (I know: DINOSAUR!) Used to love it, but had to move to newer computers (a 2009 Macpro desktop, and soon a 2010 Macbook pro laptop) Still have Snow Leopard osx. Anyway. All seemed fine til an out-of-the-blue full crash of Aperture2.1.4 in early January. Somehow it came back by itself! I think this magically stable computer was able to restore it all (took several days). Since then I've continued tentatively, w.o. any trouble, knowing I need to upgrade to Aperture 3+. Last night, again, it crashed. Either won't open at all,or suddenly will after looooong delay, but a glancing at a project freezes then closes the software down. Photos all gray etc.
My question: Could there be a virus out there that might be lurking in my MAC that is doing this? Or (I hope!) will advancing to Aperture 3+(latest update) solve the issue? If I didn't still have the same library (minus 2-3 recent projects) on an older desktop, I'd be freaking out about the seeming loss of all. (Now I'm concerned, and fearful, but resigned to my fleeting existence on the earth.)
Will probably need help upgrading, especially since I'm not sure it will talk to anything —as it won't even open. My new(used) 2010 laptop will arrive this week, which is when I will be attempting an upgrade.

monotypemaker

monotypemaker's picture
by monotypemaker
February 24, 2013 - 2:30am

Again, Walter, thanks for your responses, thus far. I am now reassessing all dangers. Need to copy my old Aperture 2.1.4 library from my old G5 (preIntel 2006) desktop to my new/used MacPro (end 2009 2 TB hd, solid state drive for applications). Now have latest ML and Aperture 3.4 installed on it.
Remember, Aperture 2.1.4. using Snow Leopard had crashed on this new MacPro and in the end, the library itself must have fully corrupted. The new OS & Aperture could not access it. Then, when I tried a “Library Repair,” I watched my 292 gig library drop to 9 mb.
Yes. GONE. And vault wouldn’t open either. Finally, deep breath. Gotta make a clean start. Deleted every scrap related to these from MacPro, knowing I still have 99% of my pix on my G5, almost identical Aperture Library.
Since I’m currently spooked, what is SAFEST way to get these pictures into the new system? My instincts now say: Export one project at a time (225 altogether) on 4-8 gig flash drives if need be, so as not to freak out Aperture 3.4. Have experimented by moving 1 or 2 exported projects. Can’t find “Import project” anywhere on Aperture 3.4, so have been dragging and dropping the individual projects into various libraries. Seems to work, upgrades them etc.
Sidebar: In the process, I noticed it isn’t easy to rename a library once created. Finally succeeded, by doing so outside Aperture, but it confused Aperture, which then said that library had to be rebuilt. Also, how does one move a project to a different library if accidentally dragged into wrong one?
I KNOW my process is convoluted, but it feels safe. Soon, I will absolutely set up an external hd system for backups, but want to get going on transferring my work into the new environment for safe-keeping.
To avoid future heart attacks if nothing else.

monotypemaker

Walter Rowe's picture
by Walter Rowe
February 18, 2013 - 11:41pm

If you don’t have fresh backups, make them ASAP. Sounds like you need to do a Library Repair. I would also encourage you to upgrade to the latest OS X and Aperture. Both are more stable and faster. You can repair your Library by holding down Command-Option when starting Aperture. It will pop open a screen that lets you repair the Library.

monotypemaker's picture
by monotypemaker
February 19, 2013 - 2:07am

Thanks so much, Walter. Is a “library repair” same as a “library restore”? Also, when you say “fresh backups” do you mean I need to do a new copy of the library to a vault? Last night it seemed to be staying open long enough to start that process, but over night at one point it quit. Do you know if saving to a vault when the library is screwed up will save it all screwy? Forgive my weak grasp of tech lingo.

monotypemaker

Walter Rowe's picture
by Walter Rowe
February 19, 2013 - 6:38am

Library repair is different from restore from vault, and a fresh backup would be a separate copy of your library to a separate hard drive than your vault backup. If this is a managed library, you can drag-n-drop the library to a new drive. Just make sure that Aperture isn’t running.

monotypemaker's picture
by monotypemaker
February 20, 2013 - 4:05am

Really appreciate your help. Glad to know the repair library trick–I followed your directions. Was surprised and encouraged the program even stayed open on my screen long enough to seem to be accomplishing the task. Saw the progressing bar for quite a while, saying, “rebuilding projects,” etc. But alas, suddenly it crashed again (now about 25-30 failed attempts).
Do have a copy of my library from last month, only missing a few recent projects I can live w.o., so am calmer than I would be. Today a new/used laptop arrives. Could you offer me the main steps for making this big upgrade? If all seems fine in the copied library, should I still do a “repair” (or can it be detrimental?) For starters, know I’ll need to up my osx to the latest. Don’t live near an Apple store, unfortunately. Would prefer to have a non-virtual disc in hand rather than a download. Will I be able to get the latest version of Aperture 3 or will I need to download it in stages (since I’m still way back in Aperture 2.1.4) before adding on all the upgrades I’ve read about?

By the way, would have done this before, but my motto is “when ain’t broke don’t fix it.” Old Aperture 2 was just slow and “pinwheely”, but had NEVER crashed. Nor had any of my Macs, so I guess I was lucky and naive. Not now, sigh. So much so, I wonder if LightRoom might be a more stable set up. But am not thrilled to need to learn a new interface.Whatever I decide, I never want to experience this complete crash again… BACKUP! will be my new motto.

monotypemaker

Walter Rowe's picture
by Walter Rowe
February 20, 2013 - 9:19pm

If your current and new/used laptop both have a FireWire port, I would boot the current laptop in “target” mode (shut down, hold the “t” key, press power button). Then connect the current laptop to the new one with a FireWire cable. You will see your current laptop disk is now “connected” to the new laptop.

After connecting the old laptop to the new one, you can use the Migration Assistant tool in Applications > Utilities to migrate all your applications, users, settings, etc, to the new system. If you prefer to start fresh, you can simply use Finder to navigate into the old laptop disk and drag-n-drop the contents of your old laptop home folder into your new laptop home folder. This might be the cleanest method to insure you don’t bring over any cruft from your old OS.

Will the new laptop have Mountain Lion and Aperture 3 on it? I would run Software Update on the new laptop to make sure it is completely updated. Then migrate all of your items from your old laptop to the new laptop.

Aperture 3 should recognize that your current Aperture library(s) are older version and will ask you to let it “upgrade” them. Do that on the new copy of your library so that the old copy remains as a safety net should something not go right.

Walter Rowe's picture
by Walter Rowe
February 25, 2013 - 10:30am

When you export an old library project to a new library, import that library as a project on the target library (File > Import > Library). It should import into the target library as a new project. If you imported it into the wrong library, delete the project, switch to the correct library, and File > Import > Library again.

It sounds like the process you are using is reliable. May be better to stick with it. Maybe try doing more than one project at a time to see if you can make the move in fewer export/import operations.

You may login with either your assigned username or your e-mail address.
Passwords are case-sensitive - Forgot your password?
randomness