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 ??

Similar Messages

Is anybody else seeing image corruption in Aperture Library?

Folks:
I am new to this forum, but I have encountered a serious issue and I need to know if anybody else is seeing this. If not, then that would point at my platform as the issue rather than the app. What I am seeing is images being trunicated after import from the SD card. The preview is correct (whole image) but part of the image is gone and not recoverable. Additionally, I am seeing corruption of images when I use the Highlights and Shadows function -- it introduces lines into the image. On one case, I saw that using duplicate versions of a single image, attempting to adjust the second version also corrupted the first version. If I export the image, the issues are still there.
Has anybody else seen this issue? I am on V1.5.6 with the ProTools update installed.
Thanks in advance.
Respectfully,
Bill Caid, San Diego

I have a similar problem. I have been shooting on a new EOS 40D, and after 3500 frames the images appear corrupt when I import them into my computer. I have put up examples on my iDisk public folder
idisk.mac.com/ThorvardurGodi-Public
I have tried a new memory card, CF, to no avail. The reason why I am not certain it is the camera, is that corrupt images on my computer, are fine in the camera LCD, even when I zoom into them. Therefore, I have a difficulty explaining if the fault is not in the system or somewhere on the way to the hard disk.
Please if anyone knows this problem, or a solution to it, please respond.
Best
Thor

Access Aperture library from other computer for slideshows?

Hi
I have a macmini connected to my LCD TV. Before when I used to use iPhoto I could share my library on the network, and launch iPhoto on the tv to display slideshows from iPhoto on my macbook pro.
Is there any way that is as easy or similar easy to display slideshows/photos on the TV/macmini with Aperture?

andreas123 wrote:
I have a macmini connected to my LCD TV. Before when I used to use iPhoto I could share my library on the network, and launch iPhoto on the tv to display slideshows from iPhoto
I have this exact setup. Sharing an Aperture Library across a LAN between machines is doable, but problematic. I've corrupted my Aperture Library at least once this way.
My MacPro is in the office and the Mac Mini is on a wired LAN connection (I wouldn't even attempt this over any flavor of WiFi.) I share the Pictures folder on my MacPro and cross-mount it on the Mini, which runs its own copy of Aperture +non-simultaneously with the MacPro+ (that is key - even if you have multiple licensed copies of Aperture on your LAN you +must not+ have multiple instances simultaneously accessing the common Aperture Library.) Then when Aperture starts up on the Mini I have pointed it to the common Aperture Library in the shared folder, cross my fingers and wait...and wait...and wait... until the Mini has loaded the Aperture Library across a 100BaseT ethernet connection.
After 1-2 minutes the Mini will have gotten whatever it needs cached from the MacPro server, and then it runs rather responsively - at least until you switch projects.
But I always get the heeby-jeebies running this way. One classic noob mistake I made was letting the Mini fall asleep after a slideshow +with Aperture still running and attached to the common library+, then starting Aperture back up on my MacPro, which thought it had full ownership of the library. Bad consequences. Not for the faint of heart.
Is there any way that is as easy or similar easy to display slideshows/photos on the TV/macmini with Aperture?
The most obvious safe way to do this would be if iPhoto - which allows read-access to your Aperture Library, if it can find it on your machine or network - would build slideshows from your Aperture images. Unfortunately this is not the case unless you literally import (ie make new copies of) the Aperture images into your iPhoto library, which kind of waters down the notion of "sharing".
A better way, which I've tried with some success, is to use Aperture 3.x's *File->Export->Slideshow as New Library* command. The short version is: build the slideshow you want on your MacBook Pro, then Export it as a self-contained Aperture library across the network to your Mini. Use option-cmd when you open Aperture on your Mini and select that freshly exported library as your Mini's current Aperture Library (or use the new *File->Switch to Library* command and navigate to it.)
This still incurs the overhead of copying files across machines, but it allows you to have full Aperture slideshow functionality on your Mini without actually sharing the library. (That flavor of Export command gives the option of copying over the preview images that will be used for the slideshow or letting your Mini regenerate them - the best choice depends on the speed of your network vs the speed of your Mini, size of preview images, etc.)
A hybrid approach might be to leave the newly exported slideshow library on your MacBook, and +share just that library+ across the network after disconnecting it from your MacBook. It's hard to say whether that might be faster than transferring the whole library and its previews across the network - I haven't tried it.
-Steve

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.

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!

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

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?

Strange permissions in the Aperture Library

I just noticed browsing the Aperture Library with the finder that few pictures files (managed pictures) deleted in the library were still in the library even if not visible in Aperture.
Rebuilding the library the images reappeared, but after deleting same situation.
I found out that these files had "Custom" permissions and cannot be deleted.
Any idea why this happened?
Thank you very much
Max

I forgot: I use version 2.1 But the problem was create with 2.0.1

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.

Error when upgrading Aperture library on an external drive

I have a MacBook Pro and am in the process of upgrading to Aperture 3. When Aperture wants to upgrade the existing Aperture library, it fails saying that there is insufficient memory. (My hard drive is very full). I have copied the Aperture library across to a WD external drive and have held down "Option" key when launching Aperture 3 so that I could select the library on the external drive as the preferred library. That went ok. Then when Aperture 3 was some way through upgrading the library on the external drive, it suddenly stopped and gave me this message.
"There was an error creating a library at the path “/Volumes/External Drive/Aperture Library.aplibrary”. The library could not be created because the file system of the destination volume is unsupported."
The library also seems to have disappeared off the external drive.
Any ideas on what I did wrong?

Hi Paul DT;
In addition to the suggestions that Allen gave you I would also suggest that once you increase the free space on your internal disk drive that you reboot with install DVD and repair the disk using Disk Utility.
When you run the free space down that can greatly increase the chances of corrupting the directory on that disk. If you have any corruption in the directory that cause all kinds of strange problems for you until you repair it.
Allan

Aperture library suddenly won't open

OK, I've been putting off updating to the latest version of Aperture (3.4.3) because I had a sort of premonition about something bad happening to my library. But I finally got around to doing the upgrade, having felt this version had been around long enough to be stable. Big mistake. It worked OK initially, but suddenly today won't open my library, no matter what I do.
When I launch Aperture, it opens a little window with a spinning marker in it and the message "Opening Aperture Library". This is normal prior to the main window opening, but usually I see it for no more than a second or so. Now, it's all I see; the main window never appears.
Oddly, Apertur's menu structure seems to work OK while this 'loading' window is open. I can, for example, open the Activity window. However, it contains no useful information to say what's going on; the entries are just blank in this window. Also, I can quit Aperture normally (whereupon it says 'updating previews' as usual).
I've tried all three of the database-reparing options that Aperture offers if you hold down Option-Command when starting: repair permissions, repair database, rebuild database. In all three cases, it goes through the repair process and then just reverts to showing the little 'opening library' window and nothing has improved.
The upgrade to version 3.4.3 apparently went OK the other day, and I've opened and quit the software a few times since I upgraded it, and I thought everything was fine. The one thing that wasn't quite right (and I wonder if this has somethnig to do with my problem now) was Photo Stream. It didn't seem to be working properly. If I clicked the Photo Stream entry in the list at the left of the window, what I saw was just the 'welcome' message with buttons below it to sign in or turn off the service ("No, thanks" button). I didn't see any actual Photo Stream content. In this window, however, it *did* say that I was signed in with my usual Apple ID, so it wasn't very clear to me whether it was OK or not.
There's a photo I took on my iPhone which I was expecting Aperture 3.4.3 to download from Photo Stream, but it never did. I.e. just one shot that failed to download; all the previous ones had been downloaded by my previous version of Aperture. I couldn't see why the missing picture was failing to download, so I tried turning Photo Stream off and on again from within Aperture. I'm really not sure whether this worked or not; there didn't seem to be any meaningful feedback from the software.
Anyway, after having tried to launch Aperture today (and failed), I checked System Preferences and found that Photo Stream was turned off. So I turned it on again. Unfortunately it makes no difference: Aperture still won't load its library at all now.
I have tried all of following:
1. Rebooting my Mac
2. Verifying the disk contaning my Aperture library (it was fine)
3. All three of Aperture's database-repair options
4. Turning Photo Stream on in System Preferences
...and nothing makes any difference. Aperture simply will not open my library but just sits there, twiddling its spinner.
NB My library still appears to be OK, in that I can access its contents from other software successfully using the media browser.
What I haven't yet attempted is to create a blank new library and import my existing library into it. Failing any better ideas I'll try that next, but it's going to be a big operation that will take a lot of time and disk space, so I'd like to see if there are any better things to try first.
I must say I'm very disappointed that Aperture can apparently break so easily. I haven't lost any actual pictures because I'm paranoid and keep a separate copy of all my shots just in the Finder, external to any management software. But I've lost access to lots of photo books I've created over the years and various other resources, not to mention all the editing work I've done on thousands of shots within Aperture (which I haven't retained separately).
This is supposed to be professional level software. How can it seriously (a) break this easily and (b) not be able to retrieve itself via its database repair options?I'm very disappointed.

Thanks for that very helpful reply. I've followed your instructions and done some further digging too.
To answer your three points, first of all:
1. No, I haven't imported any images since upgrading my Aperture library for version 4.3.4; I did move photos between projects a couple of times, but mostly I just checked that everything appeared OK after the upgrade and tried to work out why PhotoStream didn't seem to be working properly.
2. I've attempted to create a new Aperture library. This didn't work! A library gets created on disk, but attempting to open it produces the same endless spinner as the main library.
3. I switched to a spare user account (a blank one called 'test', just as the system created it) and tried to launch Aperture and create a new library there. Same result: library is created but won't load in.
This is very strange, because I'm not aware of having changed anything substantial on my system recently. No new software that installed anything as a login item, system service or background process etc. that I'm aware of. (I'm actually quite wary of such software, and don't have much of it on my system.) The only substantial thing that I know has changed since I last successfully launched Aperture is the year, to 2013! And I hardly think that's the cause...!
I'm wondering if Aperture itself has become corrupted somehow, and whether I should trash it and reinstall it. But that's rather a pain because I've got the DVD version, not the one from the Mac App Store. Besides, I'm not sure what remnants it leaves on the system (sandbox files etc.).
I've verified my startup disk, on which Aperture resides, and repaired permissions, and no error was reported (nor did many permissions need to be fixed).
Now, the only other possible explanation I can come up with is that startup is being prevented by a misbehaving PhotoStream process, as I've just discovered that I'm having endless crashes from PhotoStreamAgent, as reported in Console. I'm getting the same series of messages popping up every few seconds:
01/01/2013 21:58:51.649 xpcd[4676]: PhotoStreamAgent[5540]: registration request failed: (0x11, 0x0) The file “com.apple.iLifeAssetManagement.agent.plist” couldn’t be saved in the folder “Preferences” because a file with the same name already exists.
01/01/2013 21:58:52.431 com.apple.launchd.peruser.501[473]: (com.apple.photostream-agent[5540]) Job appears to have crashed: Illegal instruction: 4
01/01/2013 21:58:52.431 com.apple.launchd.peruser.501[473]: (com.apple.photostream-agent) Throttling respawn: Will start in 10 seconds
01/01/2013 21:58:52.615 ReportCrash[5531]: Saved crash report for PhotoStreamAgent[5540] version 2.7 (40.34) to /Users/rghallas/Library/Logs/DiagnosticReports/PhotoStreamAgent_2013-01-01-2158 52_Richard-Hallass-Mac-Pro.crash
01/01/2013 21:58:52.620 ReportCrash[5531]: Removing excessive log: file://localhost/Users/rghallas/Library/Logs/DiagnosticReports/PhotoStreamAgent _2013-01-01-215516_Richard-Hallass-Mac-Pro.crash
This is just repeating every 10 seconds, as suggested by the 'Will start in 10 seconds' message. Starts; crashes; loop.
Now, I've searched for a file called "com.apple.iLifeAssetManagement.agent.plist" and have found three instances: one each in the following places:
Aperture:
/Users/rghallas/Library/Containers/com.apple.Aperture/Data/Library/Preferences/c om.apple.iLifeAssetManagement.agent.plist
PhotoStream Agent:
/Users/rghallas/Library/Containers/com.apple.photostream-agent/Data/Library/Pref erences/com.apple.iLifeAssetManagement.agent.plist
iPhoto:
/Users/rghallas/Library/Containers/com.apple.iPhoto/Data/Library/Preferences/com .apple.iLifeAssetManagement.agent.plist
In all three cases, the file appears to be an alias that points to itself (i.e. original path is the same as the alias's path in each case). That seems weird but I hope it's right, given that it applies to all three (and the files alongside these plists in the folders in which they reside).
Anyway, the logs unfortunately don't make it clear exactly *which* Preferences folder is being referred to, and hence which com.apple.iLifeAssetManagement.agent.plist file is causing a problem. I imagine it's the one associated with PhotoStream Agent, since it's the Agent that's producing the ongoing crash reports. But either way I don't know what to do about it. I suppose I could try trashing this particular plist file, but I'm reluctant to do so as I don't want to break anything further.
NB Aperture itself doesn't appear to output any log messages to say what's happening while it's failing to load its library.

Images appear corrupted in Aperture 3

I recently upgraded to Aperture 3.0.3 and I am running Snow Leopard 10.6.3. I am running a Mac6,1 with 3 GB memory. Images in Aperture appear and display corrupted through the normal course of use of Aperture; e.g., when performing an operation such as crop, or even when flipping between images. An example of this is shown in the link below, where the highlighted image in the browser window (e.g., the bottom) appears fine, but when selected the image in the main window is displayed with some corruption.
http://picasaweb.google.ca/agerkis/AppleSupport#5474522443016232530
I have tried regenerating previews, as this was the only suggestion on the forum that seemed remotely close to this problem. I am not sure whether this problem existed under Leopard 10.5.8 or is in any way connected to the upgrade to Snow Leopard.
Help?

Just adding my two cents -- one of my clients is having this issue with her iMac 6,1. She recently upgraded to snow leopard and aperture 3.0.3 (from 2.x). We get the same sort of corruption when browsing between photos -- after the photos load up completely, approximately 75% of the time they become black and corrupted looking.
We tried using another macbook with aperture 3.0.3, and selected the problematic Aperture library to test. Strangely, it works fine on the macbook -- no corruption whatsoever.
Also, we've noticed that opening the images in another application, whether it be photoshop or preview, the photos appear normally. Furthermore, if we press "z" for zoom, the photos appear normal here as well. It's only when browsing in the scaled size, or making adjustments in the adjustments panel that this problem occurs. It all seems very random.
Any ideas?
Message was edited by: Mr Bean

Aperture library on NAS: Aperture keeps asking where it is

Hi all
I have both the library as well as files (separately, referenced) on a NAS (Synology), and that generally works well.
The only thing that keeps bugging me is that most of the times upon starting Aperture, it keeps asking where the library file was. It is even more strange, as the library path displayed in the error window is exactly correct. What I need to do is then to show Aperture the library path, whereafter Aperture starts normally.
Anyone know how to avoid the sysyphus work? Anyone experiencing the same?
Thanks
Simon

For the time, I guess I keep the unsupported solution that works 99% of the time,
You might want to seriously rethink that. Your NAS is essentially a headless computer using (usually) a version of Linux. So you trying to save a complex ecosystem of files created for and by a Mac onto a computer with an entirely different OS and file system structure. And then, doing that over a network share. That article Léonie links to is quite specific:
Storing the Aperture library on a network share can also lead to poor performance, data corruption, or data loss.
So, you're risking not inconvenience, but corruption and data loss. That you've not suffered this up to now is fortunate but it would be unrealistic to expect that good fortune to continue indefinitely.

Strange "corruption" of Aperture Library

Similar Messages

Maybe you are looking for