Aperture Library corrupted

I have my 2007-08 Aperture Library on a external drive (2nd gen DROBO) with essentially all of my pictures as referenced files. A couple of days ago, I got a warning that said there was an inconsistency in the library and that I should do a consistency check. I did that, and after about 2 hours of VACUUM everything seemed to come back and was working fine. Yesterday, after exporting 600 images in three file formats to the Drobo, I got another inconsistency warning. I have started aperture with the command-option key down again and it still running VACUUM. Using Activity Monitor, Aperture seems to be doing something with Mach Messages Out, Mach System Calls, and Context Switches changing..going up.
QUESTION: Is Aperture hung and not really do anything or is it still working away at a very nasty database corruption?
If I get my database back, I will move it off the Drobo as I suspect (no proof) that there is something strange going on between their RAID structure and the continual updating of Aperture Library.

OK...this is a remarkable story and I post it in case anyone else does a search on VACUUM, the software that seems to run when one does a consistency check.
So I let the consistency check run overnight (CPU time was 13 hrs in Activity Monitor, but total elapsed time was about 24 hours. It was still running this morning so I decided to do a forced quit. Opened the Library on the Drobo drive and much to my amazement, it opened without difficulty and all the pictures were visible and it seemed fine.
Having been spooked about what was happening to the AP Library (size 60 GB) on the Drobo when I exported files, under the Finder did a drag and drop of the Library over to my internal drive. Opened the Library on my internal drive and it successfully found all of my referenced pictures on the Drobo and seemed to function fine. Checked several of the projects and the few seemed ok.
Have now done a SuperDuper backup of my internal drive to an external FW drive (part of the routine)
Don't know whether the next time I do a large export to the Drobo whether I will have problems again with the Library, but I will provide an update to these notes in the future.

Similar Messages

Aperture library corruption

Hello, I am a bit rattled by the fact that my Aperture Library with 60k photos taken over 15 years is corrupt. I'm missing the last 2.5 years of photos, and all the projects that do have photos have been either duplicated or renamed with either a date or a longer string of numbers. I've pulled an older version of the library from a time machine backup and the same renaming, duplication is happenning, only in that case, any remaining photos are corrupt. Customer support has me on a series of wild goose chases that take 8-12 hours to complete (exporting, rebuilding, etc.), so I don't know if its possible that they will be able to recover my photos.
1. Can someone reassure me that Apple's sloppy file architecture will not cost me 15 years of photos? Wll I ever see them again?
2. Does anyone know a service that I can upload a 200 GB library and they can fix this? I've lost two days of work on this, and I'm afraid to back up my computer and spread this corrupt file to my backups.
Any help or reassurance is appreciated.

No vaults. I never understood how that worked. I only have time machine backups.
The description "sloppy architecture" was in reference to the fact that you lose your library with one corrupt file. There should be some redundancy. I'll take that back if its possible to extract the files with another computer. Are there instructions somewhere that explain how to extract the RAW files?
The last applecare person said I should export the current library. Its been doing this for 6 hours. I'm wondering if this was the right appraoch?

Aperture library corrupted - have photos on iPad; how to get them back on my Mac?

My Aperture library became corrupted after a Time Machine restore. For some reason, half the photos are missing and videos are all scrambled.
I still have my complete Aperture library on my new iPad (in iPhoto for iOS). Does anyone know if there is a way to get the photos off my iPad and back onto my Mac so I can restore my complete library? I will never rely on a Time Capsule for Aperture backups again, learned my lesson!

deepey,
have you tried the usual trouble shooting after restoring your Aperture Library from Time Machine? If you invested a lot of work into your Aperture library I would try first to fix this, before giving up on it.
If your Aperture Library is referenced you probably need to reconnect the missing masters (select the images with missing masters and select File->locate referenced file).
If your Library is managed, the "Aperture Library First Aid Tools "(repairing permissions and repairing/rebuilding the library) may help, see Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805
Transfer from the iPad (sorry, I do not have an iPad available right now to try it, only an iPod): Do you have Photo Stream enabled? You can transfer via PhotoStream or use the sync cable - Aperture can see the iPad as a camera and import like from a camera, see: Re: Importing photos on iPad to Aperture
Regards
Léonie

My aperture library lives on an external hard drive that is corrupt and I can not locate the library. I do have it backed up with TM. How do I safely restore the library from TM to my laptop? I am using the newest version of aperture on my macbook pr

My aperture library lives on an external hard drive that is corrupt and I can not locate the library. I do have it backed up with TM. How do I safely restore the library from TM to my laptop? I am using the newest version of aperture on my macbook pro.

Hello Sandra,
The article linked below details how to go about restoring items from Time Machine in Snow Leopard.
Mac OS X 10.6: Recovering items using Time Machine and Spotlight
http://support.apple.com/kb/PH6379
Sincerely,
Allen

Corrupted Aperture Library - Any way to recover original RAW files?

Hi all - as a user since the initial release of Aperture, I'm afraid I've run into my first show-stopper of a problem with Aperture 2.01. At some point (and I can't seem to see where) about 15 projects in my library have become corrupted, where I have only blank grey thumbnails for each image. Clicking on any image gives me a lighter grey image in the viewer window.
Even worse - if I select an image and try the view Master command (M), I get a lovely "Invalid Image Format" in red. I understood that the RAW files were stored inside of the aperture library file and was fairly confident that even in the worst-case I would just lose my meta data and edits.
I've exported out the projects that were still intact into seperate project files which I'll re-import after a fresh install of aperture (once I get past my emergency status)
Seems I was wrong. Restoring from my last few Vault backups (up to a month ago) has not resolved anything (or the corruption occurred far earlier).
Any assistance in recovery strategies is greatly appreciated. Otherwise I'll end up walking away from a good set of 10,000+ shots. (my current library is around 55k images)
Is there someone I can contact at Apple Support directly for assistance?!?
Thanks in advance,
Ted

Thank you kindly for the suggestions - the Show Packages option did not show any of the affected projects (in fact even the folders were missing).
Sadly also my vault copies where also missing. It would seem that somewhere along the line the files themselves were deleted from the drive without updating the Aperture library.
It looks like I'll have to suck it up this time - as I haven't been able to identify any recoverable archives - all my vaults see to be empty or suffering the same missing images syndrome. I've found a few very old copies of a portion of past shoots, but the bulk are gone. Needless to say I'm not very happy atm.
Me thinks I'll have to be more diligent about burning and DVD of each shoot immediately after I import them into Aperture going forward.
My next question is how can I guarantee a fresh re-install of Aperture? Is simply deleting icon from my Applications folder sufficient?
Thanks again for your suggestions!

Strange "corruption" of Aperture Library

I say "corruption" in quotes because I'm not sure that's what it was, but anyway....
On my rMBP Aperture (3.3.3) starts more or less instantaneously - the 'Loading Aperture Library' message appeared for about a second (27GB library).
Then, out of the blue, it slowed dramtically - the 'Loading' message appearing for ~10 seconds.
This coincided with me inadvertently importing ~160 Canon CR2 raw files into the Library as Managed. When I realized my mistake I converted them to Referenced using File->Relocate Masters. Whether this was just coincidental I don' t know, but tonight I ran 'Rebuild Database' (holding Command-Option while starting Aperture). It took about 3 hours, but now Aperture is back to it's lightning fast startup.
OK, so it's fixed, but I'm curious (and a little concerned) about what happened, in case it happens again. Moving Manged photos to Referenced (and vice versa) is a normal operation so was it just coincidence?
Can anyone shed any light on this?

Hello I have a similar problem : I have to pass a cluster parameter containing numeric values in C DLL (that configure serial channels on a Serial Board) as a Struct so defined :
struct ChannelInfoEx
ViInt16 interfaceType;
ViInt32 baudRate;
ViInt16 numBits;
ViInt16 stopBits;
ViInt16 parity;
ViUInt16 flowControl;
This parameter is passed to a VI as a AdaptToType with a format Handles by Value
All the fields of the struct (except interfacetype the first one) have a shifted values (stopbits has the value for parity numbits for stopbits and so on).
This problem is raised when I have deleted from the first filed of the struct (ViInt16 channelName) and I have tried to define all the fields as ViInt32 and the parameters are passed correctly.
Someone could help me and explain this strange behaviour ?? It's a Labview bug ??
There is a way to avoid to redefine all the fields as ViInt32 in the DLL ??

Aperture 3.0 Library corrupt?! What to do

I have a serious problem! Aperture 3.0 crashes whenever i try to open my Library; but also when i try one of the 3 repair options! A fresh library works without any problems.
Before installing A3 today, I was exporting all the projects.
Installed A3, created a fresh library.
Imported the exported libraries.
So far everything was working optimal, so i pumped the A2 projects and libraries. (go regain the space)
Then I started importing the iPhoto 09 library. that took some time, but also finished.
This is where the things started to get problematic. It started "processing" something.
The Mac got slower, and hotter. Activity window showed like "rebuilding face thumbnails".
Queued was one more thing to process all the imported photos.
When the face stuff was almost done, i went for something to drink, when i came back the mac screen was black, and did not wake up any more. So i waited but no HDD activity, but even while getting cooler it still did not make a sound, did not wake up, screen stayed black, …
so after some more waiting i decided to restart the mac by pressing the power button 5sec and then turn it on again.
That's where i realized my mac was hit hard. Spotlight was reindexing the HDD from 0.
I tried to open Aperture, it opens (quite fast by the way) but then crashes even faster.
I tried repairing the Library -> aperture crashes
I tried rebuilding the Library -> aperture crashes
I tried repairing the Library permissions -> completes, and then aperture crashes
Main problem is that there is no backup for the aperture 2 data
Does anyone has an idea how to fix that?

Personally i recovered from that, but it was not really painless.
Created a copy of the aperture bundle. and then removed i think the Database/folders folder, and after that it was able to rebuild the database.
The recovered photos where all there, but the folder/project structure was lost, … no surprise, and not a huge problem, .. using smart folders i got things sorted quickly.
since i learned my lesson i exported the aperture data after i had it sorted into a fresh library to restart from there.
first thing there was to add a vault which i now update after each import …(i'm using a local vault on the same disk for now, and will add vault on a dedicated USB drive when i get back to my place where i have the spare drives)
for me it got a bit better, even if it is still regularly crashing on huge load.
so what i did is to put a button into the toolbar to display the activity window.
and each time after some import when it starts the processing i pause for example thumbnail creation until processing is done (i let run only one CPU intense task)
aperture crashed also this time after importing the iphoto library, but fortunately the aperture library is still working and i just had to restart and finishing processing.
ps: since it seems to depend on CPU intense tasks and not in disk i/o i tried to lower apertures priority with "renice" terminal command, surprisingly that made it crash within about 5 seconds during image processing. this is the opposite of what i expected and so my guess is that it might be a problem with OpenCL and my integrated Intel graphic card (that makes the mac freeze)
That would be logical since less CPU power would lead to heavier outsourcing to GPU, and kill it faster.
That all leads to the question: Is it really using OpenCL, and iff so, is OpenCL supported for integrated graphic processors at all?
Maybe you can tell what system configuration you have?

Corrupted Aperture Library: need Help!

I am running Aperture 3.1.3 and mylibrary seems to be stuck in version 3.1.2 and won't open.
When I try to open Aperture I get the error:
"Warning:
There was an error opening the databasefor the library “[my library]”."
It goes straight to this warning when I open my Aperture library no matter what I do. I have tried theCommand-Option thing when I open it with no effect.
I followed some advice I found on a photography forum where I rename/move my Aperture Library. I was able to open Aperture when a new library was created, and then I use File-"Switch to library" to open my old library, holding down the Option-Command keys while opening it. ALL I get is a progress box that says “Upgrading Library: scanning library”. Its got the moving barber-pole thing going on and it seems to stay static like this indefinitely, I left it on overnight last night with no apparant progress being made. I just checked and the same thing happens if I do not hold down Option-Command while opening.
I tried almost everything on this page and none of it has worked. The only thing I did not try is restoring Aperture from a disk, I will be trying that shortly. My disk drive won't seem to accept any DVD's (working on that now), so I will try restoring Aperture once I get that problem worked out. I will also try fiddling with the Tech Tools that came on my AppleCare DVD.
Can anyone tell me what I should do now?

I am aware how Export Versions works, even if I choose "JPEG - Original Size" It would still limit it to an image that was 1200 pixels tall, even when drawing from a 12 MP RAW file. Something is wrong ith the export presets.
Now when I try to open Aperture with the original Application Support/Aperture folder back in my library. So I put the dummy/replacement library back and then held the option key down while opening Aperture and got my library to load again.
I have just a few dozen older photos that are not managed files within my Aperture Library and none of them are the ones that ended up in the Application Support folder. I'm not convinced these images that are in my Applications Support/Aperture folder belong in my library. It seems they may be duplicates or images that I had "trashed".
But I am not sure if it is safe to just go in there and clean house. Should I remove all the image files from the Application Support folder, or should I put the new/dummy Application Support/Aperture folder back in my library, and copy over what look like valuable files from the old one (which is now on my desktop) into the new one?

Is it possible to share an aperture library with different users using osx server.

is it possible to share an aperture library with different users using osx server.

Not really. You should not be sharing an Aperture library over a network. It's not designed for that and you'll likely corrupt your library at some point.

Can I put an aperture library on a network drive and edit from multiple computers?

I have an Imac desktop and a macbook pro. I want to be able to edit pictures from multiple computers. If I simply put the aperture library on a network server drive in my home, can I edit the same aperture library from both the Imac and the macbook? Rather than always having to sit in my office making changes to files I would love to also be able to do this with my laptop sitting ont the couch or in the kitchen. Any advice is greatly appreciated.

Get yourself a small portable external drive for your Aperture library.
An Aperture library needs to be on directly connected drive formatted MacOS Extended (Journaled). network access is not supported and can lead to data loss and library corruption.
See Apple's support document: Use locally mounted Mac OS X Extended volumes for your Aperture library
http://support.apple.com/kb/TS3252

What is the best way to move an aperture library from one full drive to an external drive?

Just want to make sure I move my existing Aperture library on my internal drive (which is full) correctly to an external drive that has plenty of space.
Thanks for the help!

As I use a MBP with limited internal drive space, my approach is to have the image files on an external drive, while leaving the library itself on my internal drive. The library takes up about 80GB while the images are closer to 1TB.
The library always contains 'Thumbnails' of the images which it shows in place of the disconnected image files.
This means I can still open the library even when the external drive is not attached, and I can still do keywording and rating and organising and so on.
I also maintain 'Previews' for my best images. Previews are like thumbnails but larger in size and can be shared with other apps, so I can still use and share these copies of the images, again even while the external drive is not attached.
I don't like the idea of having the actual library on an external drive connected to a laptop (although I have done so from time to time without issue). There's always a chance it can become accidentially disconnected (kids, pets, etc) and if this happens while using Aperture it can corrupt your library. A corrupted library can be repaired with Apertures first aid tools, but it's better to avoid it in the frist place when you can.

Can't sync Aperture library with multiple user accounts

I have created the aperture library on my main computer account and have synced photos to my iPhone with no problem. I created an account for my wife on the computer and she has admin rights. When I try to sync photos from Aperture onto her iPad I get the error message: You do not have enough rights for this operation. I checked the permissions on the Aperture library and she has Read+Write rights. Is there a solution so that we both can use Aperture for the management of our photo library but still have separate accounts?

yes, as best as I could tell.
This is a library I use for my desktop wallpaper (rotating 5 seconds apiece, random pics) so the images are kept in a folder separate from the library, which is one of the few that I permit to copy images and manage their location.
So I deleted those four images from the library, deleted their album, and reimported them from the main folder, and recreated their album, and all was well.
I presume one of them got corrupted, but the odd thing was that iTunes complained the phone couldn't be synced, and in no way indicated a fault with a file being synced.

Can I use aperture library on more than one machine

My situation is thus:
I have a Macbook Pro on which my Aperture Library resides, in wherever Aperture decided to put it when I bought the software.
I now have a iMac, which obviously will be better than the Macbook for photo editing.
But I want to be able to take my Aperture Library with me when I take the Macbook out and about, and if necesary still edit on the Macbook.
Is there any way to share the Aperture Library, so that I can edit on the iMac, but leave the library on the Macbook, and then edit on the Macbook if I wish.
I am the only user, and will only be using Aperture on one machine at any one time.
I have searched archives but not managed to find the answer.

Is it possible to simply share the directory that contains the necessary file(s).
If your Library is in the location that aperture picks by default, then it will be in your "Pictures" folder - look for a file with a name like "Aperture Library. aplibrary".
What you will need to share depends on your import strategy for the master images. If you use managed masters, and all your master images reside inside the Aperture library, then you simply need to make this library file accessible or copy it to an external disk.
If on the other hand your masters are referenced, then I would recommend to consolidate them into the library before you share the library and then share the consolidated library.
If you will share your library over the network or just by moving it to an external device is really up to you, but you might consider the following pros and cons:
- If you want to profit from the faster CPU on your iMac, then you should keep the library on the fastes volume that is available, and a network volume might be much slower than a directly connected volume.
- if the network fails during a critical operation your library might get corrupted, if it resides on a network volume - there have been quite a few problems reported in this forum.
That is why I suggested to use your Macbook as directly mounted external volume, that leaves the library in its place on the Macbook Pro - no need to copy - and you have a very quick and stable connection, but the decision is yours to make. You will have to be comfortable with the workflow you choose.
HTH
Léonie

Aperture Library/Database hacks

After one week playing around with aperture, i want to share my current insights with 'customizing' (my) aperture's way of dealing with my picture files.
Warning:
The following thoughts and arrangements are working for me, they're
undoubtly NOT supported by apple and the programmers of the aperture
application!
Reading a lot of articles in the forum when aperture hit the masses, i've been disappointed about how aperture will fit with me.
Over the years my growing picture collection moved over from one computer to the other, deploying more storage, and will continue to do so in the future. So the technical equipment has to be independent from the treasure's of my data, to follow state of the art hard- and software development.
For me, aperture approved to be of such a kind.
Despite aperture stores away all my digital masters into it's own Library, thus duplicating data during imports, it just brings in some kind of more detailed
directory hierarchies to my way of organizing my picture library. How does it do?
How do i store my Library?
Sorry to be that longish, but to explain my concepts i have to.
Modern operating systems distinguish private/personal and public/common data for their file storage locations. Hopefully they follow the 'FHS' (Filesystem-Hierarchical-Standard) brought up by linux, to name the diverse locations for classified data.
I do run mixed os'es within my networks, as no computer should be isolated from a networked environment anymore. But to be honest it's more a single-user situation in reality, then the multi-user aspects i always keep in mind when designing my infrastructure environment for a network.
My picture library/online-archive is classified 'common' data, so it stores outside my home-directory, and every user allowed to, has access to it. I do not support locales within my filenaming-conventions, users and me are german-spoken, so the 'common' data for my systems is always called
'/Bibliothek'.
Furthermore we're dealing with pictures (Bild), movies (Film), music (Musik) and documents (Dokumente) in all common used operting systems (os x, windows), storing private data to the home-directory within appropiate directories and public/common data to the equivalent directories at a common storage.
/Bibliothek
/Bibliothek/Bildarchiv
/Bibliothek/Filmarchiv
/Bibliothek/Musikarchiv
BTW, i customized windows to reflect this filetree within explorer windows, so users click to 'Eigene Bilder' (my pictures) and 'Bildarchiv' (common pictures) there, to change between directories, making it very convenient to work with.
Especially the 'common' picture files are strongly organized by date, which is reflected at the directory-structure, for example:
'/Bibliothek/Bildarchiv/2004/2004-04-17, make a good description/'
'/Bibliothek/Bildarchiv/2005/2005-12-00, a bunch for the whole period/'
A descriptive directory name is highly portable between operating systems, applications and last but not least, users!
For now, aperture seems to be pretty much a single-user solution.
But it's library can be 'distributed' to accomodate my needs.
I started to import my data by drag'n'drop, which works best for me. I didn't like the import assistent, which seemed to result in a different structure of my data in aperture's 'all projects' list. By creating a folder in aperture for the year, then drag'n'drop the multi-selected directories from the finder, i got within aperture:
All Projects + * (<-Aperture)
<div class="jive-quote">Library (smart-albums, collapsed)
2005 (folder)
2005-11-00 (folder, nested)
2005-11-17, sample bla (project, from directory)
Images from 2005-11-17, sample bla (album, inherited)
2005-12-08, take a better name (project)
Images from 2005-12-08, take a better name
Using aperture's preferences to switch between libraries i did import to different aperture libraries for the years, resulting in a bunch of directories, each holding an 'Aperture Library.aplibrary' paket there.
/Bibliothek/Bildarchiv/2004/2004.aplibrary
/Bibliothek/Bildarchiv/2005/2005.aplibrary
Yes, the pakets can be renamed, to better reflect whats in there. Aperture has to be restarted to change from one library to another!
The total amount of imported data, yet: 130 GB, ~33164 pics.
I am working with a 15" powerbook, 1,5gb ram, 80 gb hdd on the road and a 200gb external drive at home/office.
to make me feel comfortable with aperture, i switched to (terminal hacking!):
~me/Pictures/Aperture Library.aplibrary/
~me/Pictures/Aperture Library.aplibrary/2004/ ->
/Bibliothek/Bildarchiv/2004/2004.aplibrary
~me/Pictures/Aperture Library.aplibrary/2005/ ->
/Bibliothek/Bildarchiv/2005/2005.aplibrary
~me/Pictures/Aperture Library.aplibrary/Texturen/ ->
/Bibliothek/Bildarchiv/Texturen/Texturen.aplibrary
~me/Pictures/Aperture Library.aplibrary/...
/Bibliothek/Bildarchiv/2004/2004.aplibrary
/Bibliothek/Bildarchiv/2005/2005.aplibrary
/Bibliothek/Bildarchiv/Texturen/Texturen.aplibrary ->
/Volumes/HD39.1/Bibliothek/Bildarchiv/Texturen/Texturen Library.aplibrary
Linking folders to where i believe they are right placed in my systems.
Now aperture's settings don't have to be changed each time to switch between libraries. Not connecting the external hdd gives me grayedout
folders within aperture, for data stored on the external drive. Having a folder located on my inetrnal hdd and 'linked' to aperture:
~me/Pictures/Aperture Library.aplibrary/local ->
/Bibliothek/Bildarchiv/working.local.aplibrary
i can work with aperture normally, even if the external drive is not available.
the grayedout folders/subfolders/projects are browsable, but all thumbnails are just gray rectangles with its 'version name' underneath. same with smart-albums. available pics have colored thumbnails, unavailable pics are gray, naturally.
And aperture's database? well, i am very happy with it, really. Compared to my pre-aperture structure all the above mentioned tweaking gave me:
~me/Pictures/Aperture Library.aplibrary/Aperture.aplib/Library.apdb
This file is actually the sqlite3 database file. it's size is 111 MB now.
~me/Pictures/Aperture Library.aplibrary/Local ->
/Bibliothek/Bildarchiv/Working.local.aplibrary
I can store pictures there into folders and projects when i am on the road, filling up my local harddisk. Inspecting the paket shows up how aperture differenciated my pre-aperture filestructure:
/Bibliothek/Bildarchiv/Working.local.aplibrary/2005-12-08, take a better name.approject/2005-12-08 @ 01/49/06 PM - 1.apimportgroup/DSC0168/dsc0168.nef
All nicely packed into a single unit from the finder, easily browsable from aperture, and searchable by sql queries. Every Master enclosed in its own folder box, hm. Every import of files seperated to one folder, which makes clearly apparent that we will import redundant(duplicate) files for ever.
Adding two/three levels to my previous filestructure, strange namings all inclusive. As i sort my files with aperture into projects, the files accordingly move around at the filesystem-level. I'll let them go. They are there if i need access to them in case of failure.
T H E G L I T C H E S
within my setup the most current sql database is stored at:
~me/Pictures/Aperture Library.aplibrary/Aperture.aplib/Library.apdb
importing the way i did results in a sqlite3-database file for each library i switched to before linking them together. Right after linking one of those aplibrary pakets as a new folder, aperture will rebuild the current database at startup, which can indepently be invoked with 'option command aperture' anytime the program is started.
Changes to the metadata of a picture are written to the current database aperture is running on, but can be transfered to any other database file
when rebuilding the library at startup (which can be a time-consuming thing!)
Even if the external hd is reconnected before startup, some thumbnails are not properly generated all the time. At the current state i don't have any glue what's the cause for this. All Versions are properly accessable anyway.
Once again,
DO THIS AT YOUR OWN RISK,
if you try some of the suggestions i've made. Better you know how to handle a terminal before you even think about what i told here. Don't bother me, if something does not work for you - it works for me.
I can do this because it's my data, i am the only one affected by failure and i still do have my data on my windows system as a backup, for now.
Do the same before you trash your treasures.
Why i did made this post? Aperture really lacks support for team-working now. I cannot see how aperture can be really employed to its potential for an environment with more than a single user?. The sqlite3 database is said to handle concurrent users, i read on its homepage. So i still hope, there will be a group-worked aperture someday.

my reports, just for the logs.
drwxr-xr-x 2 fo03c fo03c 68 Dec 19 20:15 ArchiveInfo
-rw-r--r-- 1 fo03c fo03c 362 Dec 19 20:17 DataModelVersion.plist
-rw-r--r-- 1 fo03c fo03c 173107200 Dec 20 00:26 Library.apdb
comparing the timestamps, the time needed to recreate 'my' library, is:
4h 11 min.
The sql database contains 972 projects with 57952 picture items, as the startup overlay tells me. not that bad, i think. depends on the situation, and how much zen you learned, if you can wait for the 'recreate'.
but i didn't stop to mature aperture!
i switched to one of my 'old' libraries (choosing from preferences panel) and set some new
a) ratings
b) keywords
c) deleted a master from that 'old' library.
after changing back to the 'linked' aperture database file (within my home-directory, as described previously), and restart aperture -
yes, it crashed! oops.
yet another try - crash. i realized, i deleted the first pic from the 'current view' aperture tries to load after relaunch. ?! =:-(
if the database is corrupted again, i would have to reinvest ~4 hours to recreate the database? but how about the preferences?
apple this is a bug! when i made the preferences file
~me/Library/Preferences/com.apple.Aperture.plist
UNAVAILABLE (delete or rename as you like), aperture starts with the import assistent, as at its first time.
Since then i can start aperture and navigate to the project i deleted the file from (very unpolitly). The corresponding thumbnail shows up with a new 'icon' to lower right corner of the thumbnail. It clearly means: this file is UNAVAILABLE.
YES =:-) i deleted it!
the rating and keywording on the 'old' database is gone -
thus making the precedence of the database against the sidecars obvious, doensn't it?
selecting the 'orphaned' thumbnail, now leaves aperture with the message 'loading', but it does not crash. Changes in ratings or keywording to the current library (the 'recreated' new one) on different files are persitent across restarts of aperture. btw, aperture restarts with the focus on the orphaned first thumbnail, now marked with the icon 'i am NOT available', but it does not crash anymore, when starting.
my conclusion:
someone in the forums pointed towards the difficulties maintaining a database of pictures and the separation of their storage, as users will delete or move files seperated from that database, breaking everything.
NO, aperture does widely tolerate such doing.
But why should we do so? =:-)f
For me: its fun, i will not complain about failure, when i do mature an application like this.

Restoring Aperture Library from Vault

Hi all,
I hope someone can help. I recently had my 'Drobo' die on me as two discs failed at the same time. I also have a copy of my Aperture Library backed up in a Vault. I have carried out a 'Restore from Vault' and my new external HD shows 1.5TB of data (same as my original library). When I open Aperture, I can see all my folders and projects, but each project has no photos in it. I have tried repairing the database and rebuilding the database using the option key on start up, but I repeatedly get to approx 83-89% complete and my system hangs and I get a message that I have run out of applications memory. I then get the Spinning wheel and eventually have to reboot the iMac.
1. How can I recover my data?
2. Is there anything else I can/should do? Am I doing anything wrong?
3. Is there anyway of recvering the files seperately of the external hard drive with other data recovery software?
I am running Aperture the most uptodate version of Aperture 3.4.x, on OS X Mavericks, on a 3.4GHz i7 iMac with 12GB ram.
One point I may need to add, I was backing up to Vault when my 'Drobo' unit failed, although based on the size of the vault, I think it had finished backing up, although can not be certain.
Any help/assistance or advice would be greatfully received as I have lost my library, its parity due to two failed drives simultaneously and possibly a corrupt vault(?).
Thank you in advance for your help.
Paul W

Will rebuilding the library place the images into their correct projects/folders?
Will rebuilding return the images to their edited version state?
This library is the restored library from your vault, correct?
What seems to be missing are all of the 'version' images processed in Aperture.
In what way "missing"? Are all your projects empty or are you seeing broken thumbnails of the missing images in the projects?
I am afraid, rebuilding will not be able to reconnect the "recovered" originals to the versions. The images are in the "Recovered" project, because Aperture does not know the link to the version.
If your missing versions are still showing thumbnails, however correpted, you could use the lift&stamp tool to transfer the adjustments from the unusuable versions to the recovered versions.
But that would be a bit daunting for 14000 recovered originals.
I'd try something different - quick and dirty emergency measure: Try to open your vault directly on the drive where it is now without restoring it.
Keep the restored library you are now having save and don't delete it.
Change the filename extension of your vault to ".aplibrary", this will turn the vault into an Aperture library and try to open it directly in Aperture by double clicking it. This needs to be done in-place, on the Drobo-attached drive where you originally created the vault. Do not move it.
Aperture will now try to open the vault as the current Aperture library and upgrade it. There is a slim chance, that the links between originals and versions will remain intact, if the vault is not restored to a different volume but repaired in-place on the original volume.
Frank, what do you think? Should Snurge first try to repair the permissions on the drive?
-- Léonie

Aperture Library corrupted

Similar Messages

Maybe you are looking for