Importing from Aperture

why doesn't it say anywhere on the whole internet that a large image library is considered over a certain amount(10k??) of images??
Why doesn't it say ANYwhere that you must be prepared to keep your computer and external harddrive on for 2 WEEKS if you wish to use the Aperture importer plugin??
I am now STUCK importing what I considered to be a normal sized library, 265 GB, 40,000 or so images, at some kind of snail's pace. The whole process is SO infuriating - and I don't even know what size image or preview it's importing or what data it's bringing with it.
This is doing my head in.
Anyone know what the default settings are?
Anyone else waited two weeks for the import and found it was all ok in the end? I don't know what to do. I just wish, after spending 4 days researching this and thinking it would all be a smooth operation, that any of those blogs or instructions had warned that the plugin takes this long and that transferring your photos from Aperture - (which some of us only bought last year for God knows how much, GREEDY Apple!) would be a complete NIGHTMARE!!

Pets73 wrote:
Yes I want to move my master files to an external hard drive so i am asking it to copy the images.
Yes Aperture was/is managing them, there are no referenced.
Disk space is not an issue as I had 750GB free on my external drive, and my library is 265GB. On my main mac drive there is about 100GB free.
What if I was to interrupt the process? Would I end up with a total mess, because I wouldnt know what LR has imported and what it hasn't. Plus, it hasnt got around to the process of sorting them into my original structure yet, so the ones that have arrived in LR are useless...
I'm not near my Mac right now, and I just can't recall if it's possible to choose an alternative destination for the copied files.
But in Finder look for a Lightroom Masters folder under Pictures. By default this is where the plugin copies files, so has this default copying already filled up the internal drive? I wonder if this is the problem.
If you interrupt the process, the copies will be in Lightroom Masters and referenced in LR. You could simply delete this entire folder in Finder, and then remove that folder from LR.

Similar Messages

Error when trying to import from Aperture Library

I'm trying to import my Aperture Library into Lightroom using the "Import from Aperture Library" plug-in. Every time I get a "?:0: attempt to index a nil value" error as soon as I click the Import button. I've tried removing Lightroom (and its ancillary files) and re-installing, I've tried different destination disks for the import, I've repaired the Aperture Library, nothing helps - the same error appears every time. I'm using a Retina iMac with OS X Yosemite and LR 5.7.1. Any suggestions? Thanks, Jack

Hi Jack
I think it may still be work in progress and you may need to wait a little. Problems have also been reported importing from iPhoto. See this thread:
https://forums.adobe.com/message/7088434

Import from Aperture Created Extra Collections (2 for 1)

I used the Aperture Import plugin to import my Library to start fresh with Lightroom 5. It created many extra "collections" that I now don't know what to do with. It would take me hours to change the hierarchy in Lightroom now that this has occured.
Sample Aperture Hierarchy:
PERSONAL FOLDER
     FAMILY FOLDER
          SISTER PROJECT - contains photos
          DAD PROJECT - contains photos
          MOM PROJECT - contains photos
How they transferred to Lightroom 5 Hierarchy using SISTER as example:
PERSONAL COLLECTION SET
     FAMILY COLLECTION SET
          SISTER COLLECTION SET
               SISTER COLLECTION (NAMED "PROJECT PHOTOS") - contains photos
Essentially, it duplicated efforts and created two (a collection set and a collection) for every one project in aperture. (see SISTER above)
It did this for hundreds of collection sets/projects! It seems in order to correct this I would have to go back and remove the last COLLECTION SET for every COLLECTION and Change it to a COLLECTION INSTEAD (renaming it from "PROJECT PHOTOS" to the COLLECTION NAME). I tried some of this but it didn't seem to want to let me move the COLLECTIONS named "Project Photos" into the COLLECTION SET?
My questions are:
Is there a way to change or clean up my aperture library so it won't import this way? (Considering just deleting the Lightroom Catalog and starting from scratch with a new import). I have to have the sub categories for organization.
Is there an easy way to change a collection set to a collection and have all the pics show up there. I tried moving photos from the collection into collection sets and it would not let me.
Is there a way to choose/customize how it imports from Aperture and select whether things = collection sets or collections?
Should I use regular import instead? Will that work differently and if so what are the steps?
What is the correct hierarchy based on the Aperture example above as to how I should be organizing my photos?
Finally, In terms of my CATALOGUE; I am not thrilled that it brought everything in by day (3/13/2015, 3/12/2015) into my catalogue! Is there an option to tell it HOW to import? Say by month? Will I have to keep up this sequence every time I import now? (I plan to import/sync with SmugMug from now on: Iphone to SmugMug to Lightroom)
Thanks and any help is appreciated!

and obviously that's not possible directly from Aperture (why not?),
Obviously it is, consult your Aperture Manual. But here’s a hint: Start with File -> New -> Book...
What do I do wrong?
You’re using the iPhoto command: Show Aperture Library, correct?
When you do this you’re accessing your Aperture Previews. IF you want to use better quality images either a: use better quality Previews in Aperture, or export the images from Aperture and import to iPhoto.
Regards
TD

I am trying to use the new plug-in for import from aperture. But the "import" button always disappears ... any help out there?

Hi there
I have up-dated LR to the latest version and like to use the plug-in for the import from the Aperture library. I follow the steps suggested by an article, have saved all picture into separate folders (folder = project name) and still, after the analysis of the library, the "import" button disappears and I am stuck and can't import.
Any ideas what can be done/must be done to get this working?
Regards
Diethard

I am having the same issue, i've selected my Aperture library, and the "import" button does not activate. Any idea how to fix?

Images imported from Aperture showing up 'washed out' in Lightroom.

I am aware that Lightroom uses ProPhoto RBG. When i export images from Aperture to a folder then import into Lightroom the images appear very different. Is there a setting i am missing as the images seem 'washed' out in Lightroom. When i export to the desktop and open in Photoshop they look the same as in Aperture. After i import to Lightroom and open in Photoshop they still look washed out.
New to Lightroom and trying to find the right alternative to Aperture.
Many Thanks in advance.

You are probably right, it is an issue with color profiles and gamut. Aperture does use a different raw converter, which will create some variance. In fact, many like the look of straight Aperture raw conversions over straight ACR conversions. But if the washed out look is dramatic, and Photoshop opens your raw files okay, then it must be a profile issue.
It may help to explain how you are exporting from Aperture. Are your source files raw files, PSDs, TIFFs, or JPEGs? Are you exporting masters, or are you exporting versions? If you're exporting versions, take a look at your "source preset" when exporting. What color profile are you embedding?
Although if you are embedding any color profile, Photoshop and Lightroom should pick it up.
All I've read is that Lightroom manages profiles more transparently than Photoshop, but perhaps someone could jump in here and say how it is managed.
Finally, what purpose are you exporting and importing into Lightroom? If you're migrating your library to a Lightroom catalog, you may be best served by using the Aperture migration plug-in.
Aperture import plugin now available
The plug-in still has issues with foreign characters, importing all previews, and face keywording and keywording previews. You'll be better off waiting until these issues are fixed. Even if you can't, the plug-in would still be a better option than a manual attempt, unless you're doing something other than migrating your Aperture library.

Downsized images when imported from Aperture

The latest batch if images I imported into iPhoto from Aperture were somehow downsized to half the size, ie from 3888x2592 to 1944x1296. In other words, cut in half. This has never happened before. Previously, the iPhoto image had the same dimensions as the image in Aperture. Would this have something to do with Lion? I need images with over 3000 pixels on at least one side to sell them. Thanks. Larryt

How did you "import into iPhoto from Aperture"?
If you're using the media browser (File -> Show Aperture Library) then what you're getting are you Aperture Previews. The size of these is set in your Aperture Preferences.
If you exported from Aperture then the export preset you used in Aperture is what defines the size of the image.
So, no, this has nothing to do with Lion and only to do with the settings you are using in Aperture.
I can't help but wonder though, why you are using iPhoto at all, if you use Aperture. Is this complexity necessary?

Unlogged Missing Photos After Import From Aperture

Hi!
I have just made the switch from Aperture to Lightroom, and have use the 1.1 version of the Aperture import plugin.
In my Aperture Library I have, according to the Library -> Photos: 11105 Photos, however after importing to Lightroom, I have only 10967 photos. I have checked the import log, and there were 4 items which failed to import - 3 were .mpo files (panoramas from an xPeria) and 1 was a .gif file. This leaves a deficit of 133 photos that I can't account for.
Is there any way to compare the aperture library to the lightroom library to see what is missing?

*WARNING* Once agin, this is a VERY long post! And this contains not only SQL, but heaps of command line fun!
TLDR Summary: Aperture is storing duplicates on disk (and referencing them in the DB) but hiding them in the GUI. Exactly how it does this, I'm not sure yet. And how to clean it up, I'm not sure either. But if you would like to know how I proved it, read on!
An update on handling metadata exported from Aperture. Once you have a file, if you try to view it in the terminal, perhaps like this:
$ less ApertureMetadataExtendedExport.txt
"ApertureMetadataExtendedExport.txt" may be a binary file. See it anyway?
you will get that error. Turns out I was wrong, it's not (only?) due to the size of the file / line length; it's actually the file type Aperture creates:
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: Little-endian UTF-16 Unicode text, with very long lines
The key bit being "Little-endian UTF-16", that is what is causing the shell to think it's binary. The little endian is not surprising, after all it's an X86_64 platform. The UTF-16 though is not able to be handled by the shell. So it has to be converted. There are command line utils, but Text Wrangler does the job nicely.
After conversion (to Unicode UTF-8):
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: ASCII text, with very long lines
and
$ less ApertureMetadataExtendedExport.txt
Version Name Title Urgency Categories Suppl. Categories Keywords Instructions Date Created Contact Creator Contact Job Title City State/Province Country Job Identifier Headline Provider Source Copyright Notice Caption Caption Writer Rating IPTC Subject Code Usage Terms Intellectual Genre IPTC Scene Location ISO Country Code Contact Address Contact City Contact State/Providence Contact Postal Code Contact Country Contact Phone Contact Email Contact Website Label Latitude Longitude Altitude AltitudeRef
So, there you have it! That's what you have access to when exporting the metadata. Helpful? Well, at first glance I didn't think so - as the "Version Name" field is just "IMG_2104", no extension, no path etc. So if we have multiple images called "IMG_2104" we can't tell them apart (unless you have a few other fields to look at - and even then just comparing to the File System entries wouldn't be possible). But! In my last post, I mentioned that the Aperture SQLite DB (Library.apdb, the RKMasters table in particular) contained 11130 entries, and if you looked at the Schema, you would have noticed that there was a column called "originalVersionName" which should match! So, in theory, I can now create a small script to compare metadata with database and find my missing 25 files!
First of all, I need to add that, when exporting metadata in Aperture, you need to select all the photos! ... and it will take some time! In my case TextWrangler managed to handle the 11108 line file without any problems. And even better, after converting, I was able to view the file with less. This is a BIG step on my last attempt.
At this point it is worth pointing out that the file is tab-delimited (csv would be easier, of course) but we should be able to work with it anyway.
To extract the version name (first column) we can use awk:
$ cat ApertureMetadataExtendedExport.txt | awk -F'\t' '{print $1}' > ApertureMetadataVersionNames.txt
and we can compare the line counts of both input and output to ensure we got everything:
$ wc -l ApertureMetadataExtendedExport.txt
 11106 ApertureMetadataExtendedExport.txt
$ wc -l ApertureMetadataVersionNames.txt
 11106 ApertureMetadataVersionNames.txt
So far, so good! You might have noticed that the line count is 11106, not 11105, the input file has the header as I printed earlier. So we need to remove the first line. I just use vi for that.
Lastly, the file needs to be sorted, so we can ensure we are looking in the same order when comparing the metadata version names with the DB version names.
$ cat ApertureMetadataVersionNames.txt | sort > ApertureMetadataVersionNamesSorted.txt
To get the Version Names from the DB, fire up sqlite3:
$ sqlite3 Library.apdb
sqlite> .output ApertureDBMasterVersionNames.txt
sqlite> select originalVersionName from RKMaster;
sqlite> .exit
Checking the line count in the DB Output:
$ wc -l ApertureDBMasterVersionNames.txt
 11130 ApertureDBMasterVersionNames.txt
Brilliant! 11130 lines as expected. Then sort as we did before:
$ cat ApertureDBMasterVersionNames.txt | sort > ApertureDBMasterVersionNamesSorted.txt
So, now, in theory, running a diff on both files, should reveal the 25 missing files.... I must admit, I'm rather excited at this point!
$ diff ApertureDBMasterVersionNamesSorted.txt ApertureMetadataVersionNamesSorted.txt
IT WORKED! The output is a list of changes you need to make to the second input file to make it look the same as the first. Essentially, this will (in my case) show the Version Names that are missing in Aperture that are present on the File System.
So, a line like this:
1280,1281d1279
< IMG_0144
< IMG_0144
basically just means, that there are IMG_0144 appears twice more in the DB than in the Metadata. Note: this is specific for the way I ordered the input files to diff; although you will get the same basic output if you reversed the input files to diff, the interpretation is obviously reversed) as shown here: (note in the first output, we have 'd' for deleted, and in the second output it's 'a' for added)
1279a1280,1281
> IMG_0144
> IMG_0144
In anycase, looking through my output and counting, I indeed have 25 images to investigate. The problem here is we just have a version name, fortunately in my output, most are unique with just a couple of duplicates. This leads me to believe that my "missing" files are actually Aperture handling duplicates (though why it's hiding them I'm not sure). I could, in my DB dump look at the path etc as well and that might help, but as it's just 25 cases, I will instead get a FS dump, and grep for the version name. This will give me all the files on the FS that match. I can then look at each and see what's happening.
Dumping a list of master files from the FS: (execute from within the Masters directory of your Aperture library)
$ find . -type f > ApertureFSMasters.txt
This will be a list including path (relative to Master) which is exactly what we want. Then grep for each version name. For example:
$ grep IMG_0144 ApertureFSMasters.txt
./2014/04/11/20140411-222634/IMG_0144.JPG
./2014/04/23/20140423-070845/IMG_0144 (1).jpg
./2014/04/23/20140423-070845/IMG_0144.jpg
./2014/06/28/20140628-215220/IMG_0144.JPG
Here is a solid bit of information! On the FS i have 4 files called IMG_0144, yet if I look in the GUI (or metadata dump) I only have 2.
$ grep IMG_0144 ApertureMetadataVersionNamesSorted.txt
IMG_0144
IMG_0144
So, there is two files already!
The path preceding the image in the FS dump, is the date of import. So I can see that two were imported at the same time, and two separately. The two that show up in the GUI have import sessions of 2014-06-28 @ 09:52:20 PM and 2014-04-11 @ 10:26:34 PM. That means that the first and last are the two files that show in the GUI, the middle two do not.... Why are they not in the GUI (yet are in the DB) and why do they have the exact same import date/time? I have no answer to that yet!
I used open <filename> from the terminal prompt to view each file, and 3 out of my 4 are identical, and the fourth different.
So, lastly, with a little command line fu, we can make a useful script to tell us what we want to know:
#! /bin/bash
grep $1 ApertureFSMasters.txt | sed 's|\.|Masters|' | awk '{print "<full path to Aperture Library folder>"$0}' | \
while read line; do
openssl sha1 "$line"
done
replace the <full path to Aperture Library folder> with the full path to you Aperture Library Folder, perhaps /volumes/some_disk_name/some_username/Pictures/.... etc. Then chmod 755 the script, and execute ./<scriptname> <version name> so something like
$ ./calculateSHA.sh IMG_0144
What we're doing here is taking in the version name we want to find (for example IMG_0144), and we are looking for it in the FS dump list. Remember that file contains image files relative to the Aperture Library Master path, which look something like "./YYYY/MM/DD/YYYYMMDD-HHMMSS/<FILENAME>" - we use sed to replace the "./" part with "Masters". Then we pipe it to awk, and insert the full path to aperture before the file name, the end result is a line which contains the absolute path to an image. There are several other ways to solve this, such as generating the FS dump from the root dir. You could also combine the awk into the sed (or the sed into the awk).. but this works. Each line is then passed, one at a time, to the openssl program to calculate the sha-1 checksum for that image. If a SHA-1 matches, then those files are identical (yes, there is a small chance of a collision in SHA-1, but it's unlikely!).
So, at the end of all this, you can see exactly whats going on. And in my case, Aperture is storing duplicates on disk, and not showing them in the GUI. To be honest, I don't actually know how to clean this up now! So if anyone has any ideas. Please let me know I can't just delete the files on disk, as they are referenced in the DB. I guess it doesn't make too much difference, but my personality requires me to clean this up (at the very least to provide closure on this thread).
The final point to make here is that, since Lightroom also has 11126 images (11130 less 4 non-compatible files). Then it has taken all the duplicates in the import.
Well, that was a fun journey, and I learned a lot about Aperture in the process. And yes, I know this is a Lightroom forum and maybe this info would be better on the Aperture forum, I will probably update it there too. But there is some tie back to the Lightroom importer to let people know whats happening internally. (I guess I should update my earlier post, where I assumed the Lightroom Aperture import plugin was using the FS only, it *could* be using the DB as well (and probably is, so it can get more metadata))
UPDATE: I jumped the gun a bit here, and based my conclusion on limited data. I have finished calculating the SHA-1 for all my missing versions. As well as comparing the counts in the GUI, to the counts in the FS. For the most part, where the GUI count is lower than the FS count, there is a clear duplicate (two files with the same SHA-1). However I have a few cases, where the FS count is higher, and all the images on disk have different SHA-1's! Picking one at random from my list; I have 3 images in the GUI called IMG_0843. On disk I have 4 files all with different SHA-1's. Viewing the actual images, 2 look the same, and the other 2 are different. So that matches 3 "unique" images.
Using Preview to inspect the exif data for the images which look the same:
image 1:
Pixel X Dimension: 1 536
Pixel Y Dimension: 2 048
image 2:
Pixel X Dimension: 3 264
Pixel Y Dimension: 2 448
(image 2 also has an extra Regions dictionary in the exit)
So! These two images are not identical (we knew that from the SHA-1), but they are similar (content is the same - resolution is the same) yet Aperture is treating these as duplicates it seems.. that's not good! does this mean that if I resize an image for the web, and keep both, that Aperture won't show me both? (at least it keeps both on disk though, I guess...)
The resolution of image 1, is suspiciously like the resolutions that were uploaded to (the original version of) iCloud Photos on the iPhone (one of the reasons I never used it). And indeed, the photo I chose at random here, is one that I have in an iCloud stored album (I have created a screensaver synced to iCloud, to use on my various Mac's and AppleTVs). Examining the data for the cloud version of the image, shows the resolution to be 1536x2048. The screensaver contains 22 images - I theorised earlier that these might be the missing images, perhaps I was right after all? Yet another avenue to explore.
Ok. I dumped the screensaver metadata, converted it to UTF-8, grabbed the version names, and sorted them (just like before). Then compared them to the output of the diff command. Yep! the 22 screensaver images match to 22 / 25 missing images. The other 3, appear to be exact duplicates (same SHA-1) of images already in the library. That almost solves it! So then, can I conclude that Lightroom has imported my iCloud Screensaver as normal photos of lower res? In which case, it would likely do it for any shared photo source in Aperture, and perhaps it would be wise to turn that feature off before importing to Lightroom?

How to preserve order of photos imported from Aperture

I've imported my Aperture library into LR.
The process went generally fine, however I'm unable to figure out how to get the original image order.
I was using custom ordering for Aperture's "projects" and "slideshows". Both got translated to collections, however the image order doesn't seem to be preserved. This is crucial feature for slideshows...
Does the import plugin translate the Aperture order into the Lightroom "Custom Order" ?
If not, what would be the suggested way to restore the proper image order in slideshows?

When you select a collection the tool bar above the filmstrip lets you reverse the order by clicking the A/Z symbol. It also has a drop-down menu to the right of sort. You can choose a number of options. But the beauty of collections is that you can drag thumbnails around into any order. They then remain fixed in your own user order. Useful for slideshows, web galleries etc.

Import from Aperture not working - Import Button Disabled?

Hi
I am trying to migrate my Aperture library to Lightroom 5.7.1
I open Lightroom and start the plug-in. It "thinks" for a while then stops; the Import button is disabled.
I put a screenshot below. It is in Portuguese but you can see the Aperture Library is configured; Number of files is "undefined" for some reason. As is the "Required Disk Space".
And the "Import" button is not enabled.
Any hints on how to proceed? I've been trying to do it for the past 5 days - and I do hope I have enough evaluation days to actually evaluate Lightroom rather than get stuck on step one
Thanks
Alex

hi
To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.
regards,
Ashok Reddy

How to import from Aperture into LR?

How do I import photos (which have been uploaded automatically from SD card to Aperture) to Lightroom? Thank you for your help.
Moms90

Can anyone help me in moving my pictures out of Aperture 3 and into iPhoto?
Aperture and iPhoto are entirely different applications that work in very different ways.
iPhoto has no knowledge of, and knows nothing of how the Aperture Library works. It cannot read the Aperture library. So,
1. Export all your Masters
2. Export all your Versions
You can write the metadata to the files on export - check out the Export presets. Note that you cannot export Faces. There is no convention for sharing Faces. The best you can do is use Faces as a basis for keywording.
Import them into iPhoto. Note that there is no way to associate the masters with the versions in iPhoto, so you'll have apparent duplicates.
I assume some photo's which were taken on my Canon 550d won't show up? And it will show a blank picture instead?
Why do you assume this?
Regards
TD

How to import from Aperture to iPhoto

Hello all,
Can anyone help me in moving my pictures out of Aperture 3 and into iPhoto? It was fairly simply to move them over into Aperture however I can't seem to work out how to do the reverse.
Also I currently have iPhoto '08 but will be shortly purchasing iPhoto '11 from the App Store. Till this happens I assume some photo's which were taken on my Canon 550d won't show up? And it will show a blank picture instead?

Can anyone help me in moving my pictures out of Aperture 3 and into iPhoto?
Aperture and iPhoto are entirely different applications that work in very different ways.
iPhoto has no knowledge of, and knows nothing of how the Aperture Library works. It cannot read the Aperture library. So,
1. Export all your Masters
2. Export all your Versions
You can write the metadata to the files on export - check out the Export presets. Note that you cannot export Faces. There is no convention for sharing Faces. The best you can do is use Faces as a basis for keywording.
Import them into iPhoto. Note that there is no way to associate the masters with the versions in iPhoto, so you'll have apparent duplicates.
I assume some photo's which were taken on my Canon 550d won't show up? And it will show a blank picture instead?
Why do you assume this?
Regards
TD

IDVD changed the order of photos imported from Aperture

I created a project in Aperture from two different camera inputs. One had EDT and the other had PDT. I didn't think to make them the same time zone. After putting the combined photos in the order I wanted, I called the Aperture file from iDVD to create the slide show. IDVD changed the order. I am not sure what piece of Meta data it looked at to create its order. I had to go back into iDVD and recreate the order I wanted.
How does iDVD decide which order when the file has a mix of photos not from the same camera?
Thanks

How does iDVD decide which order when the file has a mix of photos not from the same camera?
Good question and frankly I don't know the answer.
But let me know if this helps:
http://www.automator.us/aperture/example-03.html

Missing 1,693 items after import from Aperture

My Aperture library had 42,817 originals (46,331 versions; according to the Aperture library selector).
My new Photos library following the migration has 39,835 photos, 1,287 videos, 2 items.
Assuming the Aperture count includes everything, this means I'm somehow missing 1,693 items in my new library.
I'm sort of at a loss as to figuring out how to identify these missing items (photos/videos/whatever). Any ideas?
I suppose I could just try importing the Masters folder inside the Aperture Library file; in theory it shouldn't import duplicates, but I'm naturally wary.
Thanks for any tips.

So it looks like I may have just added back a bunch of duplicates that were sitting in my Aperture trash folder. Better safe than sorry? I'm not so sure.
The worst part of this is that my library had just finished uploading the 40K items. And after mucking around last night, it looks like it's re-uploading the whole library...again.
Kill me now.

Many duplicates after import from Aperture to Photos

After a very long import process taking my 155Gb Aperture library and going into Photos, I see many many duplicates of photos.
I tried to re-import with the same result.
What's the best way to mitigate this?

I tried to re-import with the same result.
What's the best way to mitigate this?
How exactly did you do that?
The usual way is to launch Photos by holding down the alt/options key and double clicking the Photos icon in the Dock.
That will bring up a Library Chooser panel. Select your Aperture library in that panel.
The upgrade of the aperture library may take a long time for a large library.
If that is, how you have done it, you may need to repair your Aperture library before migrating it.
Open the Aperture library again in Aperture, that you just migrated. Are there any duplicates in the original library, for example in ProtoStream auto import projects, or in recovered folders?
Then try to delete these duplicates, while still in Aperture.
To try to repair and rebuild the Aperture library and the permissions of the library before upgrading it to Photos. do the following:
Firmly hold down the key combination ⌥⌘, while double clicking your Aperture Library in the "Pictures" folder to launch into the Aperture Library First Aid Tools. Select "Repair Permissions".
See: Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library
If permissions repair does not fix it, try the other first aid options, but make sure, you have a backup copy of your Aperture Library.

Problem with importing videos from Aperture

I was able to import videos from Aperture within FCPX. However, when I tried to import some older videos, the following error message appeared:
"No importable files
None of the selected files or folders can be imported. Change the selection and try again."
I noticed that all the video files older than about three months didn't work, and all the newer files worked, regardless what camera it was from (D800, iPhone, m4/3 camera)
I opened up the aperture library package and compared the permission for one video file that I could import, and one that I couldn't. They have the same permissions, so it isn't a permission issue. I tried exporting the problem video from Aperture and importing it into FCPX, and it accepted it.
The other thing I've noticed that is for the files that I imported from Aperture library, the video files in the Original Media folder are only around 250 KB. It seems that they are only aliases. All the more reason I need to find a way to drag videos from Aperture into FCPX, as the files aren't duplicated.
Does anybody know a solution to this problem?
Thanks a lot!

Aperture drag'n'drop export only creates reference movies (which can break!)
Background of your issue:
If you simply drag your video file(s) from the Aperture window to the Desktop (in my case a MP4 from my Galaxy Nexus, the original having 70 MB), Aperture does not copy the master or the version file, but instead it creates a reference movie file, which is a very small video container file (in my case: MP4, 26 KB) with no AV-content but only a reference to your master video file in your Aperture library, ~/Pictures/Aperture Library.aplibrary/Masters/YYYY/MM/DD/YYYYMMDD-hhmmss/filename.
So by principle it acts like an "alias", but technically it is not a filesystem alias (filepath, ID within filesystem (inode), metadata), but a so called reference movie. If you meanwhile deleted/manipulated the master file from the Aperture Library, or changed something from the filepath (volume name, home directory name, etc) import in Final Cut Pro will fail of course, as it loads a mere reference movie, and fails to load the AV-content, as the master movie file cannot be found at the given filepath anymore.
Solution 1 (for the "tidy" users):
Make sure the filepath to your Aperture Library does not change (volume name, user name, custom library name), and hopefully Apple does not change their Aperture Library filepath scheme in future updates. Then the reference movie will remain pointing to a valid master file.
Solution 2:
In Aperture, select the file(s)
File > Export Master (CMD-SHIFT-S)
Save file(s) to your desired destination
Import them into within Final Cut Pro
Of course this creates unnecessary duplicate content, which is specially painful with video files, which tend to be large.
Solution 3 (advanced users):
Locate the master file (within the Aperture Library.aplibrary bundle) and import that in Final Cut Pro.
The import dialogue of many Mac OS X apps does not allow browsing into bundles.
A possible work around is to open the bundle in Finder (right click > Show package contents), locate the file, and then drag'n'drop it onto the import dialogue of Final Cut Pro.
Message was edited by: putzfetzenORG. Added post title.

Importing from Aperture

Similar Messages

Maybe you are looking for