-
All replies
-
Helpful answers
-
-
Aug 4, 2016 11:52 AM in response to léonieby Macmanias,Hi,
Yes I checked also that, but the solution was other.´
I keep the older Aperture library file, and choose it again to open Aperture updated it to the version 3.6 and boom get it again.
I have other issue regarding Aperture migration, do you think I can post it here?
-
Aug 4, 2016 12:22 PM in response to Macmaniasby léonie,I have other issue regarding Aperture migration, do you think I can post it here?
Try it, perhaps we can help.
-
Aug 4, 2016 12:24 PM in response to léonieby Macmanias,Ok,
I'm thinking on migrate from Aperture to Lightroom, my doubt is should I use the Lightroom plugin or a 3rd party solution such as "Aperture Exporter" by Bluepil?
-
Aug 4, 2016 12:31 PM in response to Macmaniasby léonie,I did not migrate to lIghtroom, so you have to compare on your own.
The Lightroom plug-in will migrate these items: http://blogs.adobe.com/lightroomjournal/2014/10/aperture-import-plugin-now-avail able.html
The Aperture/iPhoto plug-in is expected to import the following data from an Aperture or iPhoto library into a Lightroom Catalog:
- Flags
- Star Ratings
- Keywords
- GPS Data
- Faces (face naming tags are mapped to keywords)
- Rejects (files designated as Rejects in Aperture will be imported into Collections > From Aperture > Photos Rejected in Aperture)
- Hidden Files (files designated as Hidden in iPhoto will be imported into Collections > From iPhoto > Photos Hidden in iPhoto)
- Color Labels (Aperture Only – Color Labels are mapped to keywords: Red, Orange, etc…, including support for custom label names)
- Stacking (Aperture Only – Stacks information is mapped to keywords: Aperture Stack 1, Aperture Stack 2, etc…)
- Aperture project/folder/album hierarchy will be mapped as closely as possible into Lightroom collection sets and collections
- iPhoto events/folders/albums will be mapped as closely as possible into Lightroom collection sets and collections
- Import ‘Full size’ previews from Aperture/iPhoto (optional, off by default), provided that they are up-to-date
- Aperture ‘Versions’ will translate into Virtual Copies in Lightroom (without adjustments)
- Metadata that can be entered in the ‘Info’ panel in Aperture
Information that is not imported into Lightroom:
- Image adjustments
- Smart Albums
- Face Tag Region of Interest (face naming tags are mapped to keywords)
- Color Labels (other than optionally as keywords)
- Stacks (other than optionally as keywords)
- Any kind of creation (books, web galleries, etc) other than the collections that correspond to them
The Aperture Exporter can migrate these items: https://apertureexporter.com/content/aperture-exporter-vs-adobes-importer-plugin
A fair number of folks have been asking about the differences between AE and Adobe's Importer plugin. Some highlights are:
- AE requires a working copy of Aperture 3.x, Lr is standalone (not sure about it’s database schema capability).
- AE maintains your Aperture hierarchy in the saved folders. Lr destroys that and saves it in a YYYY/MM/DD scheme.
- AE allows control over which images are saved with baked in adjustments.
- Lr saves images with baked-in adjustments by finding the Aperture preview files (low quality) and saving those.
- AE allows images with baked-in adjustments to be saved as high quality TIFFs or JPEGs (adjustable quality).
- The Lr importer tends to loose location metadata especially when added using Aperture's locations feature.
- Lr importer looses any version names you've added to your images. AE maintains them and can also rename the exported files based on the version name.
- AE can name images based on image naming profiles.
- AE saves metadata in a text file even when the original file is missing (offline).
- AE doesn't require Lightroom
- AE's exported results can be used with products other than Lightroom.
- AE is actively supported and maintained.
- you can actually get support for AE.

-
Aug 4, 2016 1:07 PM in response to léonieby Macmanias,Ok, I will take a close look on both to take a decision.
By the way why you choose no to migrate?
-
Aug 5, 2016 2:49 AM in response to Macmaniasby léonie,By the way why you choose no to migrate?
i did not migrate to Lightroom - that are personal reasons. I simply cannot stand the cluttered Adobe graphical user interface and use Adobe Acrobat oe Photoshop, only only as the last ditch ressort.
I am using Photos now to keep my library with my favorite photos in sync across all my Macs and my mobile devices. That is a great time saver - having my photo library with the most important photos in the same state of edit and tagged consistently on all devices. The older libraries are still in Aperture. I am currently testing digiKam as a new long term solution for the main photo library. I like open source software, the only problem is, that the Mac versions are always way behind the newest OS , and there is always a gap of several months before it will be supported on the newest OS X. Since I always like to start with a new OS X as fast as possible, that is a big problem for me.
