Copying an Aperture Library

I have an Aperture library that I have developed to manage a lot of old family photos. One batch is from my side of the family and the other, from my wife's. I would like to be able to share the entire library, already organized into projects, albums, etc., so that she can have the same thing on her MB Air. My photos are referenced and held on an external drive.
Can I give her the same library and structure, already constructed, by copying apertureLibrary.aplibrary and putting it on her MB air? If she needs the full images, could I just attach the external HD which contains the referencd images?
Or are there other suggestions?
Thanks!

Can I give her the same library and structure, already constructed, by copying apertureLibrary.aplibrary and putting it on her MB air? If she needs the full images, could I just attach the external HD which contains the referencd images?
It will work, if you are using the same version of Aperture and MacOS X on both your macs. Or, at least, her Aperture version needs to be the newer one. What versions ar you using on your Macs?
Set the "Ignore ownership on this volume" flag on the external drive with the original image files - the procedure is described here:   iPhoto: Sharing libraries among multiple users
And she will need to repair permissions on the copied library, before she can access it.
To repair permissions on a photo librara see this manual page on repairing and rebuilding:  
Repairing and Rebuilding Your Aperture Library: Aperture 3 User Manual

Similar Messages

  • I am changing to a larger hard drive on my Mac. Can I copy the Aperture library from my backup disk running Time Machine without loosing anything?

    I am installing a larger harddrive on my Mac. Can I copy the Aperture library from my backup disk running Time Machine without loosing anything? I am getting help migrating everything else on to the new harddrive, but since copying the 350Gb Aperture library takes a lot of time, I am planning to do that part myself.

    I found the following information on Time Machine help about restoring Aperture library from TM
    Restoring Your Aperture System
    If you buy a new computer or use another system at a different location and want access to the Aperture library, you can install Aperture and then transfer the library from your vault (on your backup disk) to the other computer. If you experience equipment failure or other unexpected events, such as fire or weather-related damage to your equipment, you can easily restore the entire library to your new computer from a backup disk.
    HideTo restore the entire library from an external backup disk
    Restoring Your Aperture System
    If you buy a new computer or use another system at a different location and want access to the Aperture library, you can install Aperture and then transfer the library from your vault (on your backup disk) to the other computer. If you experience equipment failure or other unexpected events, such as fire or weather-related damage to your equipment, you can easily restore the entire library to your new computer from a backup disk.
    HideTo restore the entire library from an external backup disk
    If you buy a new computer or use another system at a different location and want access to the Aperture library, you can install Aperture and then transfer the library from your vault (on your backup disk) to the other computer. If you experience equipment failure or other unexpected events, such as fire or weather-related damage to your equipment, you can easily restore the entire library to your new computer from a backup disk.
    HideTo restore the entire library from an external backup disk
    Connect the hard disk drive that contains the most up-to-date vault to your computer and open Aperture.
    Choose File > Vault > Restore Library.The Restore Library dialog appears.
    Choose the vault you want to use to restore your library from the Source Vault pop-up menu.If the vault doesn’t appear in the Source Vault pop-up menu, choose Select Source Vault from the Source Vault pop-up menu, navigate to the vaults location in the Select Source Vault dialog, then click Select.
    Click Restore, then click Restore again.

  • Can I copy an aperture library on my imac and transfer it to my laptop?

    Can I copy an aperture library from my imac to an external drive and then place and open it on a new macbook pro ??

    Click here and follow the instructions.
    (122590)

  • Can I copy certain aperture library files from the finder?

    Hello,
    I have an older library, that I updated to the current Aperture, and recently froze from bad media.  I think it was a bunch of videos in one of the events.  Anyways, I want to copy some of the photos from a event in the old library to a new working library.  Can I do this from finder?  I tried exporting and it froze, leaving the photo export in some limbo state...

    Do you also have iPhoto 9.5.1? If you open your Aperture library in iPhoto you can use "File > Reveal in FInder > Original File" to show you the original image file inside the library. Then you can copy it easily to a new location.
    If you do not have iPhoto, you can reveal the original photos by ctrl-clicking the Aperture library and using the command "Show Package Contents".  Your images are in the Masters folder, organized by the year, month, day of importing them.
    But be careful, when browsing these folders. Only copy, don't move.

  • About Vault and a simple copy of  Aperture Library

    I have a Vault in an external HD and my Aperture Library in another external HD. I have observed when I open Aperture and forgot to turn the external HD on that I have first to turn it on and re-write the route in Preferences.
    My question is: If I have a copy of my Library instead a Vault and in case of losing the information that I have in the main HD I simply changed the route selecting the second HD. Is it the same?
    Regards.
    Guillermo

    I just bought a new MBP and I'm looking for some clarification about the library/vault when using more than one Mac with aperture. I don't always want to be stuck carrying an external HD around with my laptop. Will the following thought process work....I backup my library on my mac pro to a vault on an external HD then transfer that vault to my new MBP. If I'm on the road and make changes to the library on the MBP I would need to sync with the vault on the external HD and then sync the external HD with the library on my Mac Pro desktop to maintain identical libraries, correct? I was thinking that I would need to do this to maintain multiple copies of my library but also to be able to do final editing with my desktop and cinema display. I guess I could also just connect my cinema display to my MBP and use the 17" & cinema displays for final editing.
    Thanks for any comments/suggestions.
    MBP 17"   Mac OS X (10.4.10)  

  • Copying my Aperture Library to Keyword on Vacation?

    On upcoming vacation I would like to work on keywording my (large for me) Aperture libary.
    Library is 66 Gig (referenced library) plus all the actual images (465 Gig).
    Is the following the best strategy?
    1) Copy the entire referenced libray PLUS all the images from my Desktop onto a portable drive for vacation.
    2) Do keywording on the portable.
    3) When I return, merge the portable copy with the new keywording onto the permanent MacPro?
    Seems to me that Aperture wouldn't let me merge two libraries a few months ago because one was a clone of the other with only keyword changes.
    I wish I could just bring a copy of the referenced library without the actual 465gig of images but Aperture won't let you keyword those.
    Thanks.
    Jim

    Hi Jim.  The answer is "Yes".
    Here's more.  Your Library is a database.  The core record in the database is the Image.  Attached to the Image are all the info-pieces Aperture knows about the Image.  One of the pieces of Information is where that Image's Master is located.  (If it is located inside the Library, the Image has a Managed Master; if it is located outside the Library, that Image has a Referenced Master.)  The Library is a stand-alone unit -- you can put it on any up-to-snuff Mac that has Aperture (the program) installed, and open it and use it.  If, when open, Aperture can access your Masters, then they are "on-line" and you have access to all of Aperture's features.  If Aperture cannot access a Master, then that Image's Master is "off-line" and you cannot make adjustments to, or export full versions of, or print (a form of export) that Image.  Even if the Master is off-line, you can work with all Image metedata: ratings, keywords, Albums, etc.
    So: copy your Library to your laptop.  You now have another backup.  Take your laptop on vacation.  Add to your Library (probably using Managed Masters), do whatever keywording and other metadata administration you want on any of your Images.  Return home.  As a precaution, make a backup of your changed-on-vacation Library.  Then delete the Library on your desktop (this copy is now out-of-date), empty your system trash, and copy your up-to-date Library from your laptop to your desktop.  STOP USING the laptop version.  Use the desktop version.
    While on vacation, your not-added-while-on-vacation Masters will be off-line.  Once you copy your laptop Library back to your desktop and open it, it should find and reconnect to all your old Masters -- it will make them "on-line".
    You can filter for Images with Managed Masters (the ones you imported while vacationing), and use "File→Relocate Masters" to convert them from Managed to Referenced and join them with your pre-vacation Masters.
    It is possible to take only a subset of your Library with you.  That is a little more complicated.  In that case, you will want to select the Images you want to have available on vacation, and export them as a Library.  Take that Library with you, work with those Images (with the same limitations vis-a-vis whether they have Managed or Referenced Masters), and then merge that Library into your desktop Library.
    Have a good trip. 
    Message was edited by: Kirby Krieger

  • Copying Aperture Library takes forever

    I 'm creating an off site backup for the first time as it's something I've been meaning to do for ages. Its not a fancy affair, just dragging and dropping the folders I want. I have numerous on site backups that are all in sync etc so this method should be fine.
    Any way, when it came to copying my aperture library, which has almost 26000 reference images and is almost 32GB, things didn't go well. It was telling me that it was going to take 26 hours, and the time was rising, for it to copy. I have seen something similar with iPhoto but not nearly on the same scale.
    What's causing this and how can I fix it? I could put a vault on the drive via aperture which doesn't take to long, but I'd really prefer to have the original library on the backup. I am currently trying to compress the folder, and although the size won't really change, it may(?) speed up as its copying an archive rather than the library.
    Any ideas?
    Regards

    how old is the library? I experienced the same thing when copying my AP3 library to an external..it's a 48GB library with 70,000+ referenced files...estimated time did not move up to 6 hours like yours, but it did go up to 2, which is too long to copy 48GB via firewire 800...
    I let it run, and total copy time ran about 30-40 minutes. There were patches where things got really slow, then other patches where they sped up again.
    I would take a look at this thread
    http://discussions.apple.com/thread.jspa?threadID=2343039&tstart=0
    specifically reply #10..as my question about long copy times and disk fragmentation was addressed there.

  • I was getting messages that my Aperture Library was full, so I updated to Aperture 5.3.1. When I open it, I'm asked to update my library. When I select that option, I'm told that my library is full. Now I can't access my library at all. What should I do t

    Hi all,
    I was getting messages that my Aperture Library was full, so made an appointment at my closest Mac store, but have to wait 2 days. They advise you to update saoftware before coming in, so I updated to Aperture 5.3.1. When I open it, I'm asked to update my library. When I select that option, I'm told that my library is full. Now I can't access my library at all. What should I do to access my library? Do I have to uninstall 5.3.1 and reinstall an older version?
    Another problem I have recently encountered ... all the up and down scrollers on various screens have disappeared. They reappear fleetingly when I use my up and down arrowa, but I can't always catch them. How do I get my scrollers back?

    Thank you so much for your patient guidance and screen captures.
    You are welcome.
    My external hard drive is properly formatted for Aperture, so I am currently copying my Aperture library to it. That will take hours since it is copying 101 GB.
    o.k.
    I understand that I need to clean some space on my internal hard drive and reformat the Aperture library to get back in operation.
    You need to upgrade the Aperture library to be used with Aperture 3.5.1.  That will happen automatically, when you first double click the copied lirary to open it in Aperture.
    I'll also need to back up my external drive with a new external drive if I make space on my internal drive by removing some photos from there and store them on my current external drive.
    What do you use for backup? If you are using TimeMachine it is better to have only the Time Machine backup on the Time Machine drive . In that case would I put the Aperture library and other data on a new drive and keep the old drive for backup.

  • Moving a lot of masters from an external drive to Aperture library

    I have just treated myself to an iMac, 3.06 GHz with 1 TB Hard drive. I have some 2,000 pictures that I have done a lot of work on already on an external Firewire drive. I have copied the Aperture library to the hard drive on the new iMac - but, they are referencing them from the external drive. I would like to import all the 45 project containing all the photos masters into my Aperture library so that I have them all together.
    What is the best way to do this? Do I have to do it with individual pictures - which will take forever! I cannot seem to get the option of Relocate Master. When I tried to import - from the external hard drive - I was not able to see any pictures to import. Was this because they were already in the library and I had checked 'Do not import duplicates"
    Do I need to make a new Aperture Library?
    Any advice would be most welcome!

    Hi William These are the two reports that seem to relate to Aperture. It is all "Gobbledygook" to me!
    May 24 12:13:19 MacBook-Pro Aperture[1001]: * NSRunLoop ignoring exception 'Exception in Aperture: [<BKiPhotoFolderItem 0x28841d90> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key itemiPhotoEventDisplayName.\nBacktrace:\n0x00071fea (in Aperture)\n0x91e8beb7: +[NSException exceptionWithName:reason:userInfo:] (in CoreFoundation)\n0x90c25510: -[NSObject(NSKeyValueCoding) setValue:forUndefinedKey:] (in Foundation)\n0x90b1b028: _NSSetUsingKeyValueSetter (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x26a5bfe6: -[BKiPhotoEventsFolder loadFolderSubfolders] (in iLife)\n0x26a5274d: -[BKiLifeFolderItem itemsFoldersOnly] (in iLife)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x010078ea (in BrowserKit)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x01003016 (in BrowserKit)\n0x0100341c (in BrowserKit)\n0x90b1c7a7: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x90b4a39a: -[NSObject(NSKeyValueCoding) valueForKeyPath:] (in Foundation)\n0x93992e48: -[NSBinder _valueForKeyPath:ofObject:mode:raisesForNotApplicableKeys:] (in AppKit)\n0x93992a50: -[NSBinder valueForBinding:resolveMarkersToPlaceholders:] (in AppKit)\n0x9399253c: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01003c94 (in BrowserKit)\n0x01002447 (in BrowserKit)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01013b9f (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x00ff2ee4 (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x00ff39a8 (in BrowserKit)\n0x90b2e02d: __NSFireDelayedPerform (in Foundation)\n0x91e12b5e: CFRunLoopRunSpecific (in CoreFoundation)\n0x91e12d18: CFRunLoopRunInMode (in CoreFoundation)\n0x969da6a0: RunCurrentEventLoopInMode (in HIToolbox)\n0x969da4b9: ReceiveNextEventCommon (in HIToolbox)\n0x969da32d: BlockUntilNextEventMatchingListInMode (in HIToolbox)\n0x937cd7d9: _DPSNextEvent (in AppKit)\n0x937cd08e: -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)\n0x00369f54 (in Aperture)\n0x937c60c5: -[NSApplication run] (in AppKit)\n0x00979e5a (in ProKit)\n0x00003252 (in Aperture)\n' that raised during posting of delayed perform with target 0x2694c080 and selector '_setOutputSourceProviders:'
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Con trast.monitorPanel/Contents/MacOS/Contrast and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions.
    May 25 17:55:41 MacBook-Pro Aperture[1018]: * NSRunLoop ignoring exception 'Exception in Aperture: [<BKiPhotoFolderItem 0x2375da50> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key itemiPhotoEventDisplayName.\nBacktrace:\n0x00071fea (in Aperture)\n0x91e8beb7: +[NSException exceptionWithName:reason:userInfo:] (in CoreFoundation)\n0x90c25510: -[NSObject(NSKeyValueCoding) setValue:forUndefinedKey:] (in Foundation)\n0x90b1b028: _NSSetUsingKeyValueSetter (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x2c9a6fe6: -[BKiPhotoEventsFolder loadFolderSubfolders] (in iLife)\n0x2c99d74d: -[BKiLifeFolderItem itemsFoldersOnly] (in iLife)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x010078ea (in BrowserKit)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x01003016 (in BrowserKit)\n0x0100341c (in BrowserKit)\n0x90b1c7a7: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x90b4a39a: -[NSObject(NSKeyValueCoding) valueForKeyPath:] (in Foundation)\n0x93992e48: -[NSBinder _valueForKeyPath:ofObject:mode:raisesForNotApplicableKeys:] (in AppKit)\n0x93992a50: -[NSBinder valueForBinding:resolveMarkersToPlaceholders:] (in AppKit)\n0x9399253c: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01003c94 (in BrowserKit)\n0x01002447 (in BrowserKit)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01013b9f (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x00ff2ee4 (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x00ff39a8 (in BrowserKit)\n0x90b2e02d: __NSFireDelayedPerform (in Foundation)\n0x91e12b5e: CFRunLoopRunSpecific (in CoreFoundation)\n0x91e12d18: CFRunLoopRunInMode (in CoreFoundation)\n0x969da6a0: RunCurrentEventLoopInMode (in HIToolbox)\n0x969da4b9: ReceiveNextEventCommon (in HIToolbox)\n0x969da32d: BlockUntilNextEventMatchingListInMode (in HIToolbox)\n0x937cd7d9: _DPSNextEvent (in AppKit)\n0x937cd08e: -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)\n0x00369f54 (in Aperture)\n0x937c60c5: -[NSApplication run] (in AppKit)\n0x00979e5a (in ProKit)\n0x00003252 (in Aperture)\n' that raised during posting of delayed perform with target 0x2373bbd0 and selector '_setOutputSourceProviders:'
    May 25 17:55:09 MacBook-Pro [0x0-0x79079].com.apple.Aperture[1018]: CoreImage failed to create context: CGLCreateContext return: 10002

  • Transfering  aperture library via vault to new comp

    I apologize in advance if my question already have been answered in another thread. But I couldn't find any threads matching my problems.
    I recently bought the new iMac after my old 24" could not handle the pressure anymore. I wanted to move my aperture library from the old to the new. And ofcourse I wanted all info (adjustment changes and so on) to come with in the move. After reading a few threads on the subject I created a "Vault" that I later opened up in the new comp. At a fist glance everything looks great in aperture but when opening up a picture to make adjustments it says "image offline".
    On my old comp I can see (where my pics are stored) two aperture files:
    Aperture Library
    Aperture Library_original
    …so far so good.
    But then that are tons (well, many) folders named like my projects in aperture. And not folders within the aperture library file but stand alone…if that makes any sense.
    What am I doing wrong? I get all the pics over to my new comp with the help of Vault but can't edit any of my pics from a few months back (when for some reason aperture started to create folders outside the library file)
    On my new iMac i have 2 files
    Aperture Library
    Aperture Library_old
    ...so no folders got transfered
    /Jonatan, sweden

    It looks like your Aperture library were a referenced library. When you imported your image files you did not import the originals into the Aperture library, but stored them in folders outside the library. That are folders named like your projects that you are seeing. When Aperture needs to access the originals to render edited versions, it will reference the image files in those folders, see this section in the Aperture 3 User Manual: Aperture 3 User Manual: Working with Referenced Images
    When you create a vault, Aperture will only include images that you imported into the library, not the originals you stored outside. You need to copy the folders with projects as well to your new mac and reconnect them to the image versions, otherwise you will not be able to edit your images.
    But it looks like you did create these folders outside accidentally and did not intend to use referenced original files. If that is so, I'd suggest to repair this, by consolidating your library.
    Select the "Photos" view in the source list of your Aperture Library and select all your images at once.
    Then use the command "File > Consolidate Originals" from the main menu bar. This will move (or copy) all referenced images from the folders outside into your Aperture library.
    When you now create a vault, it will contain all images. Use this new vault to recreate your Aperture library on your new mac.  You can also simply copy your Aperture library itself to your new mac. You do not need the detour using a vault.
    BTW: Where Aperture will store the originals image files depends on the settings in the "Import" panel. Make sure the "Store Files" option is set to "In the Aperture Library".
    Regards
    Léonie

  • 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 location...

    Help needed, please - I have Aperture and library running on my hard drive and a lot of images are now in place. I have also bought a 500gb external drive.
    What I want to ask is:
    Is it possible to move Aperture to my 500gb?
    Is it advisable to do that, will it free up a lot of space on the Mac HD?
    If it will free up a lot of space how do I move it, step-by-step?
    All help & advice appreciated.

    John
    Is it possible to move Aperture to my 500gb?
    Yes.
    Is it advisable to do that, will it free up a lot of space on the Mac HD?
    Advisable? It's certainly not a problem. It will free up as much space as the Library takes up.
    If it will free up a lot of space how do I move it, step-by-step?
    Are you using Managed or Referenced Masters? Assuming you are using Managed:
    1. Quit Aperture
    2. Copy the Aperture Library from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching Aperture. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    Regards
    TD

  • How do you export aperture library to external harddrive?

    Any assistance would be greatly appreciated. Im trying to save my entire Aperture library to an external harddrive. What are my options other than using Time Machine? Thanks

    Managed or Referenced Library?
    Assuming it's a Managed library:
    Make sure the drive is formatted Mac OS Extended (Journaled)
    1. Quit Aperture
    2. Copy the Aperture Library from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching Aperture. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    If you're using a Referenced Library then you'll need to relocate the Masters first.
    Regards
    TD

  • Need Step-by-Step Instructions for Moving Aperture Library to New iMac

    I've been using Aperture on an old MacBook Pro and am totally out of memory on it (I have less than 4GB free out of 465 GB).  I'm needing to move my Aperture library over to a newly purchased iMac.
    I have already installed Aperture on the new iMac and have updated the version to 3.5.1.  Aperture on my old MacBook Pro is version 3.4.5.  Will this difference in versions be a problem as I move the library over?
    On the MacBook Pro, I use a referenced library, housing all of my masters on an external drive.  I had to do this because of insufficient memory/storage capacity. 
    I do not have any vaults. 
    While I had been backing up to an old TimeMachine, I ran into problems with it a few months back (would spin and spin and spin and never complete a backup) and stopped attempting to back up to it.  We have purchased a new TimeMachine for use with the new iMac, but have not had our AV guys out to the house to connect it to an otherwise overly complicated whole-house AV system.  So, I'm afraid TimeMachine is not the useful mechanism in transferring the library to the new computer.
    The thunderbolt connection evidently will not work with the old MacBook Pro, so this isn't the transfer mechanism either.
    Please tell me in very simple steps how to move my library over to the new computer.  Please!  I have read through the Aperture users manual and do not see this topic addressed directly, though it is vaguely mentioned within the discussion on vaults.  I have searched this community and do not find a simple enough explanation.
    Do I need to run out and get another external drive and set up a vault to do the transfer?  But, would that even work with the referenced library?  There is no way I can convert to a managed library on the MacBook Pro, as I am out of space.
    Please help!  I have tons of photo projects that I was wanting to complete for the holidays gift-giving, but I'm at a standstill until I can get up and running on the new computer.
    Many thanks for your feedback

    If you cannot connect the old mac via thunderbolt or firewire in target mode, an external drive - large enough to hold the library plus some additional free space - would really be the best option for the transfer. I would not use the network to copy a referenced library. You do not need to create a vault.
    Connect the drive to the old Mac.
    Make sure the external drive is formatted for Mac - MacOS X Extended (Journaled).
    Set the "Ignore Ownership on this volume" flag on the external drive.
    Copy the Aperture library over to the external drive by dragging it in the Finder.
    Now double-click it to open it in Aperture.
    To move all references images to the external drive select all images in Aperture in the Photos view and use the command "File > Relocate Originals" and select a folder on your external drive as the destination.
    Once the library and the referenced files are safely on your external drive, I'd run a "Repair" using the First Aid Tools: See this Manual page:  Repairing and Rebuilding Your Aperture Library: Aperture 3 User Manual
    Test the library on the new drive and check, if everything transferred safely.
    Now dismount the drive and connect it to your new mac.
    Copy the library to your new Mac by dragging it in the Finder from the drive to a folder on your new mac.
    Now double-click it to open it in Aperture. Aperture will now upgrade it to version 3.5.
    Use the command "File > Relocate Originals" to move the originals where you want them.
    Regards
    Léonie

  • Aperture Library is full

    My Aperture Library is full and I have just bought a G Drive. What is the correct way of making sure I am transferring all my photos to this external drive and creating space on my MacPro?
    Many Thanks

    Then you have a Managed Library.
    Make sure the drive is formatted Mac OS Extended (Journaled)
    1. Quit Aperture
    2. Copy the Aperture Library from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching Aperture. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    Regards
    TD

Maybe you are looking for