Aperture library conversion hung up

Hi. My upgrade/conversion of my photo library to Aperture 3.3.1 has hung up while on Step 8 of 10. It says 0% complete and has been there for about an hour.
I have a huge database. Should it take a while or has it really hung up? Should force quit and restart Aperture?
Any guidance appreciated.
Mark

That's a big Library. If you force-quit, you should then repair your Library, which will take at least a few hours anyway. I'd let it run for six hours, and see if it reports any change. It is (unfortunately) not uncommon for Aperture to give no sign of working, even though it is. OS X's Activity Monitor will often report "Not responding" -- which, presumably, is correct, but doesn't confirm that it is hung. Perhaps someone with more knowledge can tell you whether an actual hang will show in the Console.
As a couple of reference points, upgrading a Library with only 50K Masters (but 1 TB of data) was done overnight. Upgrading a Library with several hundred thousand Masters (but less than 500 GB of data) took over 100 hours. Those numbers are from a MBP 5,5, 2.3 GHz, 8 GB RAM.

Similar Messages

Aperture library conversion to AP3 just Fails - every time

I just upgraded to AP3 from AP2 with the upgrade disc - and it wont allow any library conversion at all - just pops up "update failed" after only 1 sec EVERY time.
tried deleting and reinstalling AP3 same thing
help???

You should get a request to login that is used for the activation on the subscription services.

Aperture 3 Library conversion to LR3

I continue to search the web for a way to do this and still maintain the quality and content of my Aperture library. Has someone come up with a way to programatically convert from A to LR? Thank you

Yes, I can't recall the menu commands and haven't got Aperture on this computer. But if I remember, the export masters command does have an option for preserving project structure.
Also, I think Aperture 3 has a way to let you save metadata back to the files themselves. So you may be able to avoid duplicating your files. In conjunction with this, the batch change command may let you copy the project name to a keyword, or to another IPTC field like job.
Review how your files are held in Aperture. If they are "by reference", then the above save metadata option may be all you need. But if they are "managed", use the "relocate masters" command first - LR can't see inside the vaults.
There are no prizes for rushing things, so I would recommend doing a test with a few pictures and checking that everything has come across properly.
John

Aperture Conversion - My wife is converting from iPhoto to Aperture due to large library ( 33,000 photos, 109GB). Performance-wise, is it better to convert to Aperture library and leave on the 250GB internal drive or convert and store externally?

My wife is converting from iPhoto to Aperture due to large library ( 33,000 photos, 109GB). Performance-wise, is it better to convert to Aperture library and leave on the 250GB internal drive or convert and store externally?

You are welcome.
convert and store externally?
What versions of iPhoto and Aperture is your wife using? With both iPhoto 9.3 or later and Aperture 3.3 or later she simply could open her iPhoto library in Aperture and be done, since these versions are using a unified library format.
Aperture 3.3: Using a unified photo library with iPhoto and Aperture

ITunes doesn't see Aperture Library - iMovie doesn't see Aperture Library

Issues:
Nearly all of my videos in the Aperture/iPhoto library do not show up when I select iPhoto library option in iMovie and iMovie is unable to locate them in any other way. Sometimes the option to select the iPhoto library is completely missing.
iTunes does not recognize my Aperture library, and I get the following message:
"Your Aperture Library could not be found. Open the preferences window in Aperture and enable the preference to share previews with other applications." After reading through forums and multiple Genius Bar appointments here is most of what I have done:
Created multiple new Aperture libraries, selected them in Aperture, rebooted, switched back and forth - Note: iTunes DID recognize the new blank libraries
Booted Aperture with the Command + Option keys and run all three options to repair permssions and even rebuilt the database
Booted Aperture with the Option key and selected the library I was using all along (this worked for someone in a forum)
Opened iPhoto (not Aperture) and selected an option to share photos
Run "Verify Disk Permissions" many times under Disk Utility
Run "Repair Disk Permissions" many times under Disk Utility
Reinstalled OSX
Reinstalled Aperture
Reinstalled iTunes
Reinstalled iMovie
Run a virus and malware scan (no issues)
Verified that Aperture was set to share previews and had a Genius go through all of my options to ensure they were correct in iTunes, Aperture, and iPhoto
Have ran "Reset Home Directory Permissions and ACLs" from the Command + Option + R recovery partition multiple times. Each time it just hangs for hours, the latest attempt ran for over 24 hours before I finally stopped it.
Oh yes, and I found and deleted the file com.apple.iApps.plist
None of these things fixed either of my issues. According the the Genius at my last appointment, now I have to call Apple Care and pay to get support. I must have misunderstood what the Genius Bar was about when I bought my Mac and why I purchased the One to One training. Before I call Apple Care, I was hoping someone might have run across this and can help me.
I asked the Genius if I now need to just create a new Aperture Library and move all of my content to it (that was the last resort for someone in a forum); however, he was concerned that even if this might work that I probably have deeper permission and/or other issues that need to be addressed and that doing so would not fix the root cause.
Thanks for taking the time to read through this issue.

Understood. I thought perhaps the period meant that I was finished and just needed to call Apple Care and fork out the fee.
The formats are primarily .MOV straight from the iPhone. Since going to a Mac, I have pretty much given up on using my Sony Handycam for family videos due to the pains of having to locate, identify, convert, and export AVCHD video to watch on Apple TV. It is just too easy to take video with my iPhone and import it and immediately watch it, although the quality is nothing close to a dedicated video camera, especially indoors and in lower light. All of the video formats in Aperture are supported and most all of my older home videos and Sony Handycam videos are sitting on an external drive (hoping that one day I will have the time to figure out a decent workflow to access them after I work all of the bugs out of iMovie). Great thought though.
All my content is managed. After a handful of One-to-One sessions at the Apple Store, I finally learned that you could not reference videos in iMovie and had to either have them in the iMovie Events directory or in iPhoto (at least that was what she said). Their solution was to import the videos into iPhoto so they could be easily accessed in iMovie. After I had issues mentioned in this post their solution was for me to purchase Aperture that could handle larger libraries. This was supposed to fix the issue and allow iMovie to see my videos. When that didn't work they said that I needed to purchase Final Cut Pro. I'm just a Dad who wants to make a few memorable home movies for his family and I don't think that I should have to purchase a $300 application, especially after paying a premium for my Mac and the iLife software, which I am deeply regretting. But I digress.
I have repaired permissions again and am in the process of repairing the library and will rebuild it again if that doesn't work. It is taking longer so I won't be able to post the results until a later time. Definitely worth a shot to try this again.
If this doesn't work I will take the time to create a new Aperture library. Like I previously mentioned, this was the last resort for another gentlemen who had a similar issue. After doing this it might explain why the "Reset Home Directory Permissions and ACLs" from the Command + Option + R recovery partition is getting hung up and not working. I'll post the results at a later date. If I could save just one person the time, gas, and stress I've experienced it would be worth it.
One additional question? I read a gentlemen's post that passionately argued against ever using iPhoto, Aperture, or iMovie to ever manage video files. He suggested using folders and a file naming system similar to what I used when I was on a PC using Adobe Elements. Do you have any thoughts on that?
For my situation, I have two concerns:
I'm afraid this would not allow me to watch the videos on Apple TV as simply as I can now (although I don't know this to be the case for certain). If the videos aren't in my photo library, I'm not sure how I would be able to access them through Apple TV.
Since I'm a proud Dad I have hundreds of video files spanning many years, so I also don't want to lose the ability to quickly peruse my event library and find content that I want to import into a project in iMovie. At one point I imported some video files to edit that weren't stored in iMovie, and I could only see the file name and date and had to guess if there was content on it that I wanted. When you have hundreds of clips like I do that isn't practical.
He argued that these programs were never meant to manage content and worked much more efficiently using this method. I'd be very interested to hear your thoughts.
Thanks again.

New to Aperture - Library vs Reference files

I'm coming to Aperture from Picasa, which replicated and managed my folder structure as it appeared on my hard-disc, which was nice.
Am I better off importing images into my Aperture Library, or managing the folder structure how I want and just having Aperture work with the reference files?
I'm not a pro-photographer, just a pretty basic user, so will not have loads of large raw image files. What's the benefit of using the Library over using Reference files? I've tried Google-ing but everything I've found just addresses folder/project management within Aperture.
If I use the reference option, can Aperture manage my photos on my hard-drive in the same way Picasa could (ie if I moved a photo from one folder to another in Picasa, it also moved on my drive)
Thanks

Hi TxH,
Welcome to the user-supported Aperture discussion group.
I'm coming to Aperture from Picasa, which replicated and managed my folder structure as it appeared on my hard-disc, which was nice.
If you use Aperture for even a little while, you'll realize that the structure of your photos in your hard drive is not as important as how you organize them in Aperture, especially when you start making albums, which merely contain a pointer to the image in your library. You can have a picture in many albums, but your library (and therefore hard drive) only contains it once.
Am I better off importing images into my Aperture Library, or managing the folder structure how I want and just having Aperture work with the reference files?
That's a matter of opinion. Some people are very opinionated that using referenced files is the only way to go, some are opinionated the other way. Sometimes there really is a better solution for you depending on what you are doing.
What's the benefit of using the Library over using Reference files? I
You will find loads of conversation if you search this discussion group for "managed" and "referenced".
You will always have a library. Your managed pictures will live in the library and you won't have direct access to them through Finder (and you should not want direct access to them for the most part). Your referenced pictures live wherever you tell Aperture to take them from, but the bookkeeping parts of the Aperture library/database are still stored in the Aperture library package.
Benefits of managed include: you don't worry about where the files are; Aperture backs them up if you use its vaults; they are always with you.
Benefits of referenced include: you know exactly where the files are; your Aperture library is significantly smaller than if all your photos were in the library; you can find them with Finder if that's important to you (and a lot of people think it's important to them but then realize they only think that because they're really not using Aperture to its full potential).
If I use the reference option, can Aperture manage my photos on my hard-drive in the same way Picasa could (ie if I moved a photo from one folder to another in Picasa, it also moved on my drive)
Yes. I've never used Picasa, but Aperture allows you to "relocate" your photos in order to manage their external directory structure. You can also choose to "relocate" a managed master to make it referenced.
nathan

Help!- aperture library disappeared after copy

I'm screwed...After a long holiday with my macbook and my aperture (3.0) library (90GB) on an external drive I finally get home and decide to copy the library onto my iMac (pictured folder). I always keep a copy in my external drive as a backup and for macbook use (internal drive too small).
Well, I connect the drive to my iMac, and try replacing the aperture library. Takes very long thinking, so I decide to delete the old aperture library on my iMac and just do a simple copy. Everything seems fine, it starts and says it has 50 minutes to go...so I leave for dinner. An hour later I come back and not only had the aperture library not been copied (only 700 mb or so of it), but the source isn't there either! i.e. it disappeared from my external drive!!
I though it might be a database problem, but mac os x says I have 90 GB more free space on my external drive, so the aperture library seems to have been deleted!
HELP HELP HELP....all of my photography is in there and I cannot believe I have lost everything just by trying to copy it!
thanks for any suggestions!

Alaninnorway wrote:
Yes, I must agree. I have exactly the same problem. Come on Apple - do not invite us to 30 day free trial and give us this hassle for the weekend.
Any help appreciated.
The 30 day free trial cannot convert an Aperture 2 library.
Using the trial you can can only import into a new Aperture 3 library, and should not have any of these conversion issues.
We converted 6 workstations this weekend, specifically did not convert the imaging as that can be done in the future on an as-needed basis.
All of the libraries reside on disks that are no more than 40% full, for performance reasons.
The first library we converted was 500GB and at about 2.5 hours it froze at about 58%. I trashed the partial conversion and started over with a clean copy. This time, in Aperture 2 I did a Library rebuild before I converted. After this the conversion ran perfectly, in about 4 hours.
I ended up with a new file called Aperture Library, and another file called Aperture Library_Original. I found that this is the way the conversion is designed if you have the diskspace for 2 full Libraries. If you do not, it will delete the original after the conversion.
At any rate before converting run a rebuild in Aperture 2, and then make a backup of that library. You will then have a very clean original should anything happen in the conversion.
I am happy to say we followed the rebuild and backup on the other 5 Libraries, ranging in size from 500GB to 1.2 TB, and all the other conversions went smoothly.
The key is have plenty of diskspace available, more than double the size of your library, and Aperture will leave an Aperture Library_Original which can still be opened in A2.
Sincerely,
K.J. Doyle

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.

Aperture library copy vs vault

Hi,
sorry if this is redundant, but I couldn't locate the clear answer to this seemingly basic question:
if using a referenced library, what is the major difference/advantage of creating a vault versus a simple drag & drop copy of the aperture library onto an external HD?
Thanks,
Mike

The Finder is the strongest Mac app. It has been being tested by every Mac user and has had resources allocated to improving its stability since Mac day one. And, all of us use the Finder constantly so we are very conversant with appropriate usage. IMO if one has the discipline to go to the desktop and manually multiple backup using the Finder that is the surest kind of backup.
Personally I prefer manual non-incremental backups. It can be done with forethought after one is comfortable that everything is well with whatever it is that is being backing up.
I keep old iterations of the backup in the event that there is a critical flaw in what is being backed up. E.g. I built a Filemaker images database for an antique store. The db user was given admin control of the db against my recommendation, changed the password at some point, and then left town. Old db copies allowed me to go back to the last backup made before the password change and start over with a new user.
Drag-and-drop is good for Referenced-Masters folks in particular because Masters are not backed up by the Vault process when using a Referenced-Masters Library, so the users need to separately be backing up Masters anyway.
Most important however is to get the backup done however one does it. Other techniques like Vaults, Time Machine, etc. may assist folks who have difficulty maintaining the discipline to properly drag-and-drop.
-Allen Wicks

Can't Import Aperture Library

I am trying to import my Aperture Library into Photos. I open Photos and select the Aperture Library and the conversion starts.
After about 1 hour the conversion stops at 69% and an error message appears. See attachment.
Second question. When I move my Aperture library to Photos is the original Aperture library altered?
Thanks
Derek

I have exactly the same issue. I have a large (535 GB) aperture library stored on an external HD. The HD is correctly formatted and I have rebuilt the aperture library to ensure there are no problems with it. It works fine in aperture.
When I start the conversion it runs for hours (I had to leave it overnight. At some point in the process photos must have begun to repair the library because when I check it it has reached 69% and then I get the same message as you.
When i close the dialogue box photos "cleans up" which takes another few hours. Oddly when I check the contents of the HD before the clean up process there is a file that looks like a photo library and is the same size as my aperture library.
Very frustrating. Any ideas very welcome!

How do i move aperture library to from MBP external drive

Perhaps I am not searching properly,but was unable to bring up a 2011 answer to this question. Does anyone have more current help than 2011?

Thank you, léonie, for your extensive help. I do not wish to impose on you, but have answered the first part of your response below. If you were to continue helping, I would appreciate that greatly. I also hope continuing the conversation within the community this way is ok. If not please advise.
Hansjurg
“What exactly is the mess now? I do not want to contribute to it inadvertently by missing details.”
I meant that, the original library remained on my MBP and the copied library was on my new dedicated external drive. My original problem of only 50 gigs on my MBP meant the beach ball was quite active.
I set the library from within aperture to the file on my new dedicated external drive. Images I looked at appeared and all functioned well but slowly.
Since I had a vault set, had a clone of my original MBP hard drive from before the library copy and a time machine backup to another dedicated hard drive, I sent the original iMovie library to trash and deleted it.
I then reindexed spotlight and the MPB worked much faster, reflecting some 150 gigs available much better than 50 from before.
Is this summary correct?
My external drive was formatted correctly. I did user finder to move my "iPhoto" library from my mac to my external drive.
I did redirect Aperture to the external drive. but I see that the original library remains on my mac. (Which, as I mentioned above, with much care and several types of backup, I trashed the original file, which was on my MBP).
So you could open your library on the external drive? Is it working correctly? Yes
Are you able to open all images? Yes, based on a sampling of images.
Is your library referenced or not? That means, did you import your images into Aperture or photo with the "Import Settings" set to "Store Files: In the Aperture Library"?
I am not sure from where you got the graphic labeled “Aperture Library”. My Aperture version is 3.5.1.
When I go to Aperture preferences and select import, this is what I see:
In advanced this is what I see:
I think the difference is in my version.
Continuing, when I look at iPhoto, it references the new library on my external drive. Here’s that screen shot.
So, the Aperture setting says it is currently set to use iphoto for camera imports and iPhoto is set to use the new external drive’s library. I am not sure how file imports will be affected, but assume it will be the same. Is that correct?
Any comments up to this point?
I will now try the smart album comment.

"Insufficient disk space" to upgrade Aperture library to v.3

I'm getting an "Insufficient disk space" and then an "upgrade failed" error when launching Aperture 3 with my old Aperture 2 library, hoping to upgrade it. My Aperture 2 library is 85.94 GB, and I have 15.31 GB free on my 250 GB disk.
Does anyone know how much space it needs for the upgrade? How can I get this working? Thanks for your help.

presta wrote:
I can't believe that Aperture 3 – with the "update imaging" box unchecked – will increase the size of my database by +over 18%+ and this is just really badly designed.
I do not know but I am wondering if there is some faulty arithmetic going on and it's not looking for say 20% more space, but over 100% more space? In other words, I wonder if people with more free space on their system than their Aperture Library size are seeing this problem. Those with less free space than the size of their library may share your problem. That certainly would be a bug rather than a design flaw I would think, but I don't know what the AP3 format conversion is doing internally in the library before it finishes the process. If you wanted a failsafe method, you could design it in a way that virtually duplicated everything and only did the final step of deleting the AP2 originals when the revisions were successful. Sounds speculative but someone else needs to respond here that only has a modest amount of free space like you yet converted a large library successfully with all the bells and whistles turned on (new RAW, new imaging).
You might be able to call an talk to an Apple technician as I'm sure if there is a bug or design flaw, others will have called already to get the workaround. Unfortunately I won't have the problem that I am suspecting since my free space is greater than my library on this new iMac.
Message was edited by: Rick Lang

Aperture Library Repair fail

Hello,
I have Aperture 3, a 250GB Aperture Library and it faqiled to load this evening, just hung. I reapired permissions, tried to clean up the database and rebuild the database, none of which would run.I can find the library, look inside and see that the files are there in the folders. Aperture wont load it as the repair failed and was interrupted. Tried repair but the program bombs out.
Am scratching my head what to do?
Is there an external repair program that i can run over it? Aperture crashes out.
Bummed
martyn

I too am having difficulty with Aperture permissions. This permission problem has plagued me for the last year. Permissions will not verify using disk utility (Version 13) and disk utility fails to complete the repair after 7 minutes. Now my Aperture drive with all my libraries will not mount. The error message says to copy all files and reformat. How do you do this if disk utility will not mount the drive?
Here is the error log (or part of it).
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Overlapped extent allocation (id = 22557, /New Gourds.aplibrary/Database/apdb/Properties.apdb)
Overlapped extent allocation (id = 22559, /New Gourds.aplibrary/Database/apdb/History.apdb)
Overlapped extent allocation (id = 22561, /New Gourds.aplibrary/Database/apdb/ImageProxies.apdb)
Overlapped extent allocation (id = 97730, /New Gourds.aplibrary/Database/History/Changes/0000000007.plist)
Overlapped extent allocation (id = 205763, /New Glass.aplibrary/Database/History/Changes/0000000015.plist)
Overlapped extent allocation (id = 265087, /Animals.aplibrary/Database/Folders/2cA6IPVGRQWfleHtAEgKTA.apfolder)
Overlapped extent allocation (id = 265091, /Animals.aplibrary/Database/Folders/LibraryFolder.apfolder)
Overlapped extent allocation (id = 265111, /Animals.aplibrary/Database/Keywords.plist)
Overlapped extent allocation (id = 265112, /Animals.aplibrary/Database/KeywordSets.plist)
Overlapped extent allocation (id = 265407, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/+LVQTNHBRaCtWOv 95yR39w/Master.apmaster)
Overlapped extent allocation (id = 265411, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/14HtlPA+T1aImjS 7wtCUNg/Master.apmaster)
Overlapped extent allocation (id = 265415, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/2UWUfVXYSQ+0K+r shNjv3A/Master.apmaster)
Overlapped extent allocation (id = 265419, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/2YKGiQ7mR2GQ5BC +SOm89A/Master.apmaster)
Overlapped extent allocation (id = 265423, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/9UHl3mP5Ri+d2PJ cnTQRmg/Master.apmaster)
Overlapped extent allocation (id = 265427, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/Bhk9e7tsSxu+6l% V4zSD+A/Master.apmaster)
Overlapped extent allocation (id = 265431, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/bWOPURt%TpiCBVb nQhWU8Q/Master.apmaster)
Overlapped extent allocation (id = 265435, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/dm%PJaCIQQqjNyH nnyNM3g/Master.apmaster)
Overlapped extent allocation (id = 265439, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/DyXBQZDmR5+DQEE DOElFcA/Master.apmaster)
Overlapped extent allocation (id = 265443, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/EvzjT7ydSKOC5ST TYZP+uQ/Master.apmaster)
Overlapped extent allocation (id = 265447, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/FVPB8mRwTQGhAnD EkARVJA/Master.apmaster)
Overlapped extent allocation (id = 265451, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/gdcUiUH%TaucwaI DImghGA/Master.apmaster)
Overlapped extent allocation (id = 265455, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/iCkjZj7%TViUZNN XaYX0SA/Master.apmaster)
Overlapped extent allocation (id = 265459, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/iPM6IjyqTYaCCg5 CE7Kkkw/Master.apmaster)
Overlapped extent allocation (id = 265463, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/j3cQYZsGROqrMbd jCw5%9A/Master.apmaster)
Overlapped extent allocation (id = 265467, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/JeuoBg1gQaiV%fx eqPnecQ/Master.apmaster)
Overlapped extent allocation (id = 265471, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/OfZo08RDQ7G385% djcL8hA/Master.apmaster)
Overlapped extent allocation (id = 265475, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/PgGjSNauTIige5g 2xVjeyQ/Master.apmaster)
Overlapped extent allocation (id = 265479, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/QDcWGGqGS+6iLcZ 2O5DdHg/Master.apmaster)
Overlapped extent allocation (id = 265483, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/QfXjLbLPQba+01B 2AgRx0Q/Master.apmaster)
Overlapped extent allocation (id = 265487, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/qhTp5T+uSgGQ1Rt oleVzOQ/Master.apmaster)
Overlapped extent allocation (id = 265491, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/rBOq8LneQf2U%hq LsZnLRg/Master.apmaster)
Overlapped extent allocation (id = 265495, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/swTTA4JESlSqQnY dKNSskg/Master.apmaster)
Overlapped extent allocation (id = 265499, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/UJc5KU4bRE2YHZk pTPR%nw/Master.apmaster)
Overlapped extent allocation (id = 265503, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XA9m7ihER5eCibU glGskRg/Master.apmaster)
Overlapped extent allocation (id = 265507, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/xaM%4EGmQJqZqBn 1kEyL4g/Master.apmaster)
Overlapped extent allocation (id = 265511, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XaS35pzIQZOsDcx wp2GtYw/Master.apmaster)
Overlapped extent allocation (id = 265515, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/xl0svn8rRqGj8OR m3PxzCA/Master.apmaster)
Overlapped extent allocation (id = 265519, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XLqfC6DBT42E78d jsimuWg/Master.apmaster)
Overlapped extent allocation (id = 265523, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XY8Iji95SVmYwHb vEaV5zg/Master.apmaster)
Overlapped extent allocation (id = 265527, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/ZYuDDLvxSuCUQM9 LqdVvXw/Master.apmaster)
Overlapped extent allocation (id = 265532, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/8oVOfqYkTb6C7pD q2oC+hg/Master.apmaster)
Overlapped extent allocation (id = 265536, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/bjiSlJKfTIC1lKn yVfw2fg/Master.apmaster)
Overlapped extent allocation (id = 265540, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/eNFQWAojS5WU2mH 5nCf3ZQ/Master.apmaster)
Overlapped extent allocation (id = 265544, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/HRfBGx5uTIOmCfC rshGvjA/Master.apmaster)
Overlapped extent allocation (id = 265824, /Animals.aplibrary/Info.plist)
Overlapped extent allocation (id = 1017926, /New Gourds.aplibrary/Thumbnails/Segments/Thumb64Segment_1.data)
Overlapped extent allocation (id = 1018813, /New Gourds.aplibrary/Database/Albums/Photostream-286385529.apalbum)
Overlapped extent allocation (id = 1019907, /New Gourds.aplibrary/Database/Versions/2013/05/29/20130529-183722/xyYiYDhwRfmAHoELa wk9wg/Version-1.apversion)
Overlapped extent allocation (id = 1019908, /New Gourds.aplibrary/Database/Versions/2013/05/29/20130529-183722/9NwRiNv5SB+rRA8kS Xq5pQ/Version-1.apversion)
Anyone have any ideas?
Mayte it is time to switch to Lightroom?

Two user accounts sharing aperture library constantly repairing permissions

My girlfriend and I each have a user account on our iMac. We have our Photo Library in a shared folder so we can both access it when using Aperture. However, every time I want to use Aperture, I have to first repair permissions. After doing this, everything runs fine.
Then, when my girlfriend tries to access Aperture, SHE has got to repair permissions first or Aperture gets hung up.
Basically, it appears that when I repair permissions in my user account, it messes up the permissions in her user account and vice versa. Has anyone ever experienced this behavior before and have they found a solution?
Thanks,
Rick

It is not sufficient to have the library in a shared folder. That will not help with the permissions inside the Aperture library package.
The safest way to use an Aperture library from two differnet accounts is to move it to a disk or disk partition that has the "Ignore Ownership on this volume" flag enabled. Then you can take turns using the Aperture library from your accounts.
The procedure is explained in this document for an iPhoto library, but it work also for an Aperture library.
iPhoto: Sharing libraries among multiple users http://support.apple.com/kb/HT1198
Just remember, that any disk you are using for an Aperture library will have to be formatted for Mac:
MacOS Extented (Journaled).
My media drive with the Aperture library looks like this in "File > Get Info":

Does OS influence/affect shared Aperture Library?

Just ran into this problem. I set up my mom's Aperture Library on an external FW800 drive to be shared between a new 24" iMac (2009) and a 17" PowerBook G4, each with a backup vault local to the startup drive. The reason I did this is that she travels frequently, and this way her Aperture library can be identical on both machines at any given time. With iPhoto, it was a tremendous pain to get everything synched.
At the time (early August), both were running the latest versions of Leopard and Aperture. No problems. However, she insisted on upgrading her iMac to Snow Leopard (against my warnings and advice) and now she is having problems. The PowerBook is non-Intel so its OS cannot be upgraded beyond Leopard.
When she recently tried to open Aperture on her PowerBook with the shared Library on the external drive, it worked fine until she tried to quit, then the application hung and she had to force quit. Now Aperture on the PowerBook comes up but all of her photos and vaults are MIA, plus it won't quit without having to force quit. The library on the external drive shows 21+GB in size, so I am hoping that it is not corrupted by this. She hasn't had a chance to try it with her iMac at home since she is currently traveling. Hopefully the backup vault on her iMac is still viable.
Any advice on what to do? Do I need to downgrade her iMac to Leopard to get the shared library issue corrected? Will Aperture need to be reinstalled from scratch on the PowerBook? I am 2000 miles away, so it is hard to tech support this over the phone.

Wow, this is not encouraging. I have a slightly different version of this problem. I had my Aperture library showing up (and updating as I expanded it) in the Media Browser, and all was well until I bought a new Mac and transferred everything over from the old one. For whatever reason, not everything makes it over. Now, on the new Mac, my Media Browser only shows images from Photo Booth--not even iPhoto! I feel your pain and share your ire.
Someone mentioned September (not coming soon enough). Is there speculation that Aperture will be updated (finally!) when Snow Leopard releases?

Aperture library conversion hung up

Similar Messages

Maybe you are looking for