Photo Orientation in Referenced Aperture Library

I am taking my Managed Aperture Library and moving it to Referenced. As I do so, I am noticing that many of the "portrait" shots in the library don't seem to maintain that orientation in the Finder. The portrait orientation shows up correctly when I look at the photo in Aperture, but when I go to "check" on the original file in the Finder, the icon of the photo and the photo itself when I open it with Preview revert back to "Landscape". Any thoughts as to why?
I have also noticed that when I export the "version" then the orientation is correctly saved with the file. When I export the "original" the orientation is NOT saved with the file.
Ideally I would like the "originals", which are referenced and consequently simply stored in the Finder, to correctly reflect orientation when I view them outside of Aperture, for example with Preview.
I am also aware that Aperture does not modify the original photo. But when I take a photo in "Portrait" orientation, my camera (and most modern digital cameras) record the orientation in the EXIF data in the photo. It is my understanding that this is how the Finder/Preview or any other application knows how to display the photo from an orientation perspective. Indeed, if I take a portrait photo straight from my camera and place it on the Mac Desktop, the orientation is correctly displayed. When I them import that photo into my referenced aperture library, the photo's orientation appears correctly in Aperture, but if I look at the original in the Finder or Preview, the orientation is lost.
Hopefully this makes sense.
Thanks in advance for any assistance.

I just ran into this issue and found your post from a search. Maybe too late for you, but for anyone else who finds this, here is the solution:
In the export dialog when exporting "Originals...", select "Don't Include IPTC" for "Metadata".
The behavior doesn't make any sense, but that's how I fixed my exports!

Similar Messages

Referenced Aperture library larger than iPhoto library?

My iPhoto library is 232 GB , so to save space, I deciced to imort them to Aperture 3 as a referenced library.
A few hours later, 'processing' has stopped and my Aperture Library is now a whopping 283 GB. If Aperture is simply pointing to the pictures in iPhoto why is the library now so large?

I'm not sure how I search for Managed Masters, but there will be some there as I have been downloading pictures from my camera directly to Aperture before I Referenced those in my iPhoto Library.
However I can see that the iPhoto images are all badged indicating that they are Referenced and when I use 'Locate Referenced Files' to display a list of Referenced Images it shows that there are 34,440 in my iPhoto Library.

Problem Using iTunes To Sync Photos To iPhone4 From Aperture Library

hello, i have 1400 pics in my aperture library and when i sync it to my iphone4 it's only show me 114 photos.. i don't know why?
may u help me?

Do matters improve if you update to iPhoto 9.4.1?
iPhoto 9.4.1
From the release notes for the new version:
What's New in Version 9.4.1
Improves the reliability of syncing to iOS devices via iTunes
Fixes an issue that could cause iPhoto to quit unexpectedly when using the Export command
Addresses an issue that could cause iPhoto to quit unexpectedly when upgrading multiple books, cards, and calendars
Resolves an issue with downloading and viewing photos synced from Facebook albums

HT3805 Aperture (Current version) won't populate photo place holder from Aperture Library, found one photo that would, what's wrong?

Yesterday 10-4-2011, I downloaded the Aperture App. I haven't gone to my Aperture class yet, but wanted to know why the photo place holder in an email stationary application will not accept a drag and drop from the Aperture library. I did find only one photo that actually did populate, what do you think is the difference with all the rest of my photos?
I did import all my photos and movies to Aperture from the iPhoto Library and then deleted my iPhoto Library.
Thanks

Yesterday 10-4-2011, I downloaded the Aperture App. I haven't gone to my Aperture class yet, but wanted to know why the photo place holder in an email stationary application will not accept a drag and drop from the Aperture library. I did find only one photo that actually did populate, what do you think is the difference with all the rest of my photos?
I did import all my photos and movies to Aperture from the iPhoto Library and then deleted my iPhoto Library.
Thanks

HT203156 iTunes no longer syncs Aperture pictures with iPad & iPhone despite emptying iPod Photo cache in my Aperture library

Tried to repair and even rebuild Aperture database as suggested in Help with iTunes Sync - Stuck on importing photos . . . and it does not help.
I also have followed https://photoapps.expert/help/faqs/common-aperture-questions-issues-and-rep/aper ture-photos-arent-syncing-to-my-ipadiphoneipod-correctly.html#.VTVQ3s41TA4
looks like this issue arose with OS X 10.3 and the new Photos app

Just two edits
1/ Sync works with the new Photos app.
2/ iTunes does display Apertures folder / project tree in the photos sync section (allowing you to pick what to sync) yet does NOT display the corresponding number of pictures

Problem syncing photos to iPad from Aperture with a merged iPhoto/Aperture library

I recently 'upgraded' to us Aperture instead of iPhoto. One of the features of this was that I could continue to use the old iPhoto library in Aperture, and it automatically configures to Aperture settings - and it works great in Aperture.
The problem is that when I come to sync photos to my ipad, I have the drop down options for iPhoto and Aperture. The Aperture option shows zero photos, and the iPhoto option shows all the complete list of all my photo event/projects (from both my iPhoto days, and the more recent stuff in Aperture); but anything that I have created since moving to Aperture is greyed out and not accessible.
Any clues as to how I can sync the new photos as well as the old ones?
Thanks

Have you enabled the sharing and creation of previews in Aperture? That is one big difference between Aperture and iPhoto - in iPhoto it is impossible to disable previews, but in Aperture you can create previews selectively, see: Working with Preview Images
Check Aperture's Preferences > Previews settings for "New Projects automatically create Previews".
Then select the images with missing previews in Aperture in the Browser and use the command "Photos > Update previews".
If that is not the problem, the iPod Photo Cache or the Aperture library may need repairing or rebuilding, see these documents on how to repair the Aperture Library:
Repairing and Rebuilding Your Aperture Library
iTunes: Understanding the iPod Photo Cache folder
First try, if a simple repair of the Aperture library will suffice, then delete the iPod photo cache folder. Make sure, that the backup of your Aperture library is current, before try any of this.
-- Léonie

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

Duplicates when importing photos from iPhoto to Aperture 3

I have recently purchased Aperture 3 & am trying to import my events from Iphoto to A3 but each event I import has duplicates of EVERY image. Even if I have never edited the photo in Iphoto it always shows 2 photos of every shot? Any solutions to avoid this as it will be too hard to go thru each event & delete the duplicates. Too many!!

When I check my system info it reads that I have 2 memory slots x 2GB (don't really know what that means) and I am running MacOS 10.7.4 yes. I have 63GB of 499GB free so nowhere near 30%. Explains why it is running slow I guess :-)
So you have 4GB RAM, that should do if you do not run many applications in parallel, and you really need to free some disk space! There is a nice utility in the Applications > Utilities folder: Activity Monitor. Launc it and look at the runtime and memory usage. That will tell you if your system is running low on RAM. My MBP profited considerably from an upgrade to 8GB.
I am trying to back up on a WD external drive USB. I don't understand what a firewire port is?
Firewire is a fast connection to external devices, and many external disks offer a firewire cable connection; the port usually is marked by a Y-Symbol:
Leonie, I have read something about duplicate annihalitor (or something like that). Would it pay to run that on my Iphoto first and delete duplicates? Have u used that programme?
I have never used it myself, but Terence Devlin recommends it frequently. It will find exact duplicates, if you imported the same image twice or made copies, but it will not remove the original masters of a version, afaik. Check it out here:
Duplicate Annihilator:
Can I store my library on my external HD and just access it each time I enter Aperture so that my Mac HD doesnt get overloaded?
There is a better way in Aperture:
What I do on my MBP with limited space is to keep the Aperture library on the System volume, but (most of) the original master image files on an external drive. This is what is called a referenced Aperture library. I set the Aperture preferences to enable the creation of Previews. THis way I can browse my images, tag them, and rate them with stars even if I am on the road. The images can be accessed from the Media Browser and used in other iApps or the screen saver. Only when I want to edit an image I need to connect the external volume and to mount it.
To turn an image into a referenced image select it (or select several images at once) and from the main menu bar select: File -> Relocate master(s). Then select a location where to store your masters on the external volume.
I usually import the new images as managed (stored inside the Aperture library) and relocate them to the external volume when I am through with editing. Perhaps this kind of workflow will be suitable for you too. Bt do not forget to backup the master images on the external volume as well.
Regards
Léonie
Thanks again for your patience with me and time in answering Leonie.
You are welcome! My pleasure

Ref. aperture library issue

Hey!
I use my macbook for photo editing. I have one Aperture library locally and ca. a 200 gb referenced library on a external hard drive.
Unfortunately my external hard drive failed recently. On it I had a referenced aperture library of ca. 200 gb. Fortunately I had a copy of the library on my iMac!
However, when I copied my library over to a new ext. hard drive and connect it, the 200 gb of referenced files all seem to be offline still when working from my main library on the macbook. I tried naming the hard drive to the same as the old one, still it doesn't find it.
I tried fiddling around with File --> Locate Referenced Files ---> Located my hard drive BUT the aperture library with the referenced files doesn't show! The folder it lies in is shown as empty. Can anyone help a poor boy out?
Relevant information:
Aperture Version name: 3.5.1
Hard drive: Max OSX Extended (Journaled)
Mavericks
Thank you for any response!

Hi. Frank is trying hard, but it is impossible to communicate without well-defined, shared terms. Since the terms are specific to Aperture, and shared by all who know Aperture, it is your responsibility to help yourself first, by learning the terms and using them. Then we can help you.
Please see my concise guide to the parts of Aperture.
The Library is a database of Images. It shows in Finder as a file, but is actually a Finder Package. You can right-click the Library file, select "Show contents" and view the many (hundreds to millions) of files in the Library package. (Don't change _any_.)
In Aperture, what you see are Images. Every Image has an Original. "Original" is the term Aperture uses to refer to an imported image-format file.
Aperture is non-destructive: your Originals are _never_ altered.
You can store your Images' Originals wherever you want. It is _highly_ recommended that you store them on a locally mounted drive. Aperture provides robust tools to move any Image's Original in and out of the Library, or to any available drive, at any time.
The convention of calling a Library "referenced" or "managed" misleads. Each Image's Original is either managed or referenced. If all of the Images in a Library each have the same relationship to their Originals, the Library can be said to be either "managed" or "referenced". Since any Image's Original can be either, a Library can be "mixed".
It is possible to import a file into each of two Libraries. This is foolish and should not be done.
All computers have at least one built-in drive. This drive is called the "System Drive" because it holds the OS (= Operating System).
As an additional effort to communicate precisely, please do not use "it" to refer to anything. Specify all referents.

Merge two iPhoto libraries into an Aperture library for my Macbook Air

Hey,
I've searched around a bit for this but can't seem to figure out how to to it.
I'm trying to manage my ~140GB photo library on my Macbook Air which has 128GB of HDD. On top of that, you can imagine that most of that 128GB is filled with system stuff.
My objective is to keep most of my library offline from the Macbook Air, but still keep it all together.
I kinda went "all-in" with iPhoto a few years back to organize my photos so gave up on Aperture. I'd always wanted to move to Aperture or Lighroom but the migration appeared to be a complete disaster. Now with "transparent" compatibility it seems like a no brainer to get the best of both worlds.
I thought that Aperture allowed you store files on external hard drives but still have "thumbnail" access to them even when the drive wasn't connected. Or did I misread that? (Is that Lightroom?)
Anyway with the new update I thought that I could merge my available iPhoto libraries into one Aperture library that I could always have access to, while offloading the actual photos somehow to an external HDD.
This would be a real winner for me. It seems tho that an iPhoto library stays an iPhoto library. So while merging might be helpful for someone with a big hard drive, it's completely useless for me as if anything, I need to split. Or create more. Or some other form of adding complexity.
Any ideas here?

Figured this out on my own.
Make a backup of everything - Aperture seems to require rebuilds and stuff and stories abound of "things going a bit wrong."
Did you make a backup? If you don't want to or can't, I wouldn't do this. After all, it's your photos!
Setup your Aperture library on a USB drive.
Update iphoto to the newest version. Open all your libraries in iPhoto to update them. This may take awhile depending on library size.
Import whatever iphoto libraries you have to Aperture. This make take awhile (hours!) - if your stuff is more than say 25 gigs I'd recommend setting it up for overnight.
Once everything is in Aperture - check its all working right. Then go ahead and maybe make another backup
Then migrate your photos out of the library. This takes all the originals and stores them elsewhere, called "offline". Once they're there, you can't move them around, so pick a good spot!! This also takes forever.
Once this is done your Aperture library should be smaller and just copy it to your MacbookAir
I'm still working on this as it looks like something went funky and I have to rebuild my thumbnails, another overnight processing thing. Like I said, keep a backup But I have a slimmed down Library on my Macbook Air now which is what I wanted.
This whole thing is kinda a mess and while it's feasible Apple hasn't made it easy. There's also some crazy stuff Aperture does with thumbnails and "previews" so that they take a bunch of space up (in my case almost as much as my photos), so you might have to work with that.
The guy at Apertureexpert.com is a genius.
Check out this post for more on slimming your Aperture Library:
http://www.apertureexpert.com/tips/2010/1/20/reducing-library-sizedramatically.h tml
Edit:As a side-note I put some HTML in my message and it looks like it isn't used in the forum - why does Apple bother having the formatting tools if they don't work? Kinda like the close-door button on an elevator?
Edit2: Haha it shows up in the answer but not in the normal thread. Strange, eh?

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!

IDVD 6 - can't acess photos or movies from my library after software update

Any Way of turning back the clock?
i purchased the iLife '06 package and since Apple brought out their new version i can't use it.
when opening a new product with an old theme and click on "MEDIA" button and then" Photos" it gives a message 'Open iPhoto 2 or later or Aperture 1.5 or later to see photos from your iPhoto Aperture library list.'
Grrrrrrrr!
Message was edited by: Bellissimojo

The software updates since i last used iDVD '06 (about 3 months ago) were the the updates prompted automatically from the apple website triggered by the system preferences.
The iDVD '06 software has been remained on this computer since i bought it in '06 and has been used successfully before.
This is a recent problem and i've recently tried a maintenance program (ONYX) which did'nt cure it and then tried installing MAC OS X and bundled software from the original discs(Which archived and restored my files and desktop exactly as they were as far as i could tell?) followed by software updates.
This has resulted in a minor change - in the "select a media source options" The audio still comes up as normal showing my itunes library,The PHOTO button still gives the greyed out message "Open iPhoto 2 or later or Aperture 1.5 or later to see photos from your iPhoto Aperture library list."
but when i click on the MOVIES option i get a spinning beachball which makes the APP hang untill i quit it.
Any thoughts?

How to modify photos being streamed from Aperture

I set up photo streaming from the Aperture library to Apple TV2 awhile ago. I am not sure how to modify the album/photos accessible from Apple TV2?

If you want to remove all photos and not have them sync back to the iPad, with your iPad connected to your computer, while iTunes is running and with the iPad selected under the Devices icon at the top of the iTunes window, click on the Photos Tab and then uncheck the box next to Sync Photos From and click on Apply in the lower right corner of the iTunes window.

Aperture Library on 2 computers

I have Aperture 3.5.1 and Mavericks on an iMac 27 and a MBP.
I use the MBP when I am travelling.
I copied the Aperture library from the iMac to the MBP - no problems.
All photos, albums etc show up identically in both places.
I do this because I like to look at all my photos sometimes when I am traveling.
Here is the problem.
When I add photos to the MPB Aperture library they show up in Photostream but are not otherwise added to the iMac Aperture library.
However if I create a new Aperture library on the MBP, any photos added to that library still show up in Photostream but also are added to the iMac Aperture library.
The symptom appears to be that on the iMac, Aperture somehow recognizes that the MBP library is the same and does not therefore add the MBP photos properly on the iMac.
Changing the name of the Aperture library on the MBP does not help. There is apparently some internal ID which is still recognized.
Is this a feature or a bug?

This is intended more as a discussion than making any specific point.
I'm not sure what you mean by keeping the copies in sync. That's not what photo stream is trying to do (as you said yourself in your original response).
Besides, 'Sync' is perhaps the most tricky concept in computing. While superficially simple, once you get to the detail you realise it actually needs telepathy and artificial inteligence (or a huge transaction log) to work how everyone wants it to.
Take two libraries A and B that have the same UUID so you think should be synced.
Add an image to A.
Because you added an image to A, it's natural to assume when you open B, you want the same image to be added to B.
However, instead of adding an image to A, now delete an Image from B instead. Now it's natural to assume that when you open A, the image should be deleted from A.
Both seem sensible and natural.
Yet if you examine A and B after either step, they are identical in both scenarios. That is, there is an image in A that is not in B. In the absence of a sync control protocol it is impossible for the application to determine if the correct response is to delete the extra image from A, or add the extra image to B.
Now consider a scenario where you have taken a copy of the library as a backup before doing some work on it. You do the work and mess things up badly so decide to revert to your backup copy. How would you feel if you then opened your backup, and it dutifully tried to keep it in perfect sync, by applying the same mess-up to your backup that you had just done to your original?
A copy is simply a backup, not a sync target.
All Photo Stream is is a distribution protocol for sharing. Anything you put into the stream will be distributed to all subscribers. It distributes only once (automatically) to each subscriber, and only to the subscribers that are not the origin. If it distributed more than once, it would be impossible to delete anything sourced from the stream without it magically re-appearing after the delete.
The stream section in the browser is simply a window into the stream.
The 'correct' way to work with multiple libraries is to have each library created by Aperture to have a different UUID, and then use 'export as library' and 'import library' to share between them.
Any projects you export and import this way will keep the same UUIDs in both libraries but the libraries will have different UUIDs, which then allows the merge process to work correctly, and also allows the stream to work more inteligently. For example, if you have the same project (same UUID) in two libraries, if you add a photo to a project in one library and then share it to the stream, when it gets downloaded to the second library it will store itself in the same project (even if the project name and folder heirarchy has been changed in the second library).
Andy

11,000 referenced photos = 13 GB Aperture library! Help!

I'm coming from Lightroom 2 where I have 11,000 images in my library and the size of the preview file is about 5 gigs. I decided to import all the images as referenced files to Aperture 3 to test it out. However, the size of the Aperture library file is 13 gigs, i.e. more than twice that of LR.
I know there have been a lot of posts about memory leaks, but I just felt I had to share my experience. So far I'm really liking A3 but my iMac is really low on space as it is, so I can't afford 13 gigs just for the library.

Thanks Ian, I wasn't aware of the option to turn off previews. I have turned off all preview options in the prefs and selected all images in my library and chosen Delete Previews. I let the operation complete and quit Aperture. My library only decreased to 11.1 gigs.
Is there any other pref I can turn off to decrease the library size? Thanks!

Photo Orientation in Referenced Aperture Library

Similar Messages

Maybe you are looking for