Deleting iPhoto after import to aperture

Hi,
After importing my iPhotos into Aperture can i then delete all the iPhotos?
Thanks
iMac 24" Mac OS X (10.4.9)

They would have been moved into the Aperture library unless you specified that they not be in Aperture's Preferences.
One way to check is to select an image and then see if "Show if Finder" is availiabe in the File menu. If it is, you can see where the file is stored, if it isn't, the file is in the Aperture library and you can delete the version in iPhoto.
Of course you could always back up the iPhoto version to DVD just to have one more backup. More is better when it comes to backups.

Similar Messages

Images disappear from camera menu in iphoto after import

After I import pictures from a canon camera to iphoto, they do not appear in the camera menu when I click on it in the program. Does that mean they are deleted from the camera or are they just hidden on the program but still on the camera?

sorry but your post is not clear
What version of iPhoto do you have? Of the OS?
After I import pictures from a canon camera to iphoto,
OK
they do not appear in the camera menu
Please explain this
when I click on it in the program.
What program? What are you clicking on? what happens? what do you expect to happen?
Does that mean they are deleted from the camera
Did you delete them after importing the photos? If so did you reformat the memory card using the camera (recommended) or have iPhoto delete then after importing (not recommened) or did you choose to keep the photos?
or are they just hidden on the program
Again what program?
but still on the camera?
No one but you can answer this - are they still on the memory card when you put it in the camera
BTW it is strongly recommended that you never have any computer program including iPhoto delete your photos - after importing keep the photos and then after at least one successful backup cycle you can use your camera's format command to reformat and erase the memory card - personally I rotate between three large cards so I do not delete the photos from my memory card for a year or more
LN

Extremely nasty Image Capture bug deletes video with import to Aperture

Image Capture allows one to specify Aperture as a target.
Nice feature, but Aperture can't handle video.
So what happens when the images you choose to import contain a video, and you've set IC to delete after import?
The videos are deleted, but not imported. If you were to import directly to Aperture they would be saved to the desktop by Aperture, but with this route they are deleted.
Lethal bug.

Terence Devlin wrote:
The moral of the story:
Never let your computer delete data before you know that the transfer has worked. Ever.
Don't let Image Capture, Aperture (oh, and btw, Aperture 3 does support video) or iPhoto delete pics. Ever.
After you have transferred the material to your Mac you can simply reformat the card with your camera - once you've verified the transfer. Reformatting the card with your camera is much faster - takes seconds - and has the added advantage of refreshing the directory structure on the card and so helping to avoid problems in the future.
And finally, given that both iPhoto and Aperture can import directly from your camera, why are you using Image Capture?
Regards
TD
After losing some images on my first attempts with iPhoto I quit using it. The whole program made no sense to me. I've been transferring images to the desktop with Image Capture, editing with Gimp, and storing in an image folder. I was hoping to give iPhoto another try and lost a couple of images... now trying to figure out where these things go. I'll try to import directly from the camera now that you've made me aware of the possibility. Any idea about this cache in the meantime? Maybe I'll find all the images I lost.

Deleted iPhoto photos showing in Aperture - can anyone help?

Having imported my iPhoto images (1000s of them) into Aperture using the option of keeping current location (i.e. iPhoto), i busily started to delete photos (particulalry RAW files) from iPhoto. Unfortunately, these photos are still showing in Aperture - albeit with a yellow warning triangle?
Questions:
1. Why are these appearing? Anyway I can make them disappear?
2. How can I put all my images into Aperture now and make iPhoto redundant so that it does not happen again? I have tried to import but Aperture says i need > 150GB of space in order to do the import (which I don't have).
Thanks!

What you are seeing in Aperture are the previews Aperture created of the imported images. The reason they have the yellow triangle is because the master is gone from where Aperture expects it to be.
As I understand your situation the images you are deleting are ones you don't want anymore in either iPhoto or Aperture, correct? (I hope so because if you deleted them and emptied the system trash they are gone from both programs for good).
So what you want to do is get rid of the preview images of the images you deleted. Not an easy task, most users want to get the masters back. You can try selecting all the images that are missing there masters and delete the previews but I'm not really sure this will get rid of them totally from Aperture.
The correct way to have done this would have been to do the deleting from inside Aperture. This way all remnants of the images would be removed from the Aperture library.

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?

Deleting images after importing

Aperture 2.0 won't delete images from the card after importing. I click the button to delete and eject, and then in the confirmation dialog again I click delete, but it quietly ejects the card with no errors and all of my images are still on it.
I'm using an 8GB SDHC card with a SanDisk USB reader. My camera is a Nikon D40x.

I'm getting frustrated (and somewhat annoyed) at the inability of Aperture 2.0 to delete images from a memory card.
Users that claim they don't get this option might like to set the "display alert when done" option in the Import panel. Once this is set, then the program displays an alert following successful import. There is the option to delete the imported images from the memory card.
The delete option worked flawlessly on versions 1.1 through to 1.5, but is now broken.
For reference, I'm using the new SanDisk Extreme IV Firewire (800) CF reader, and have been using a SanDisk Extreme III 4GB compact flash card.

Upgrade D300 to D700 : request to delete pictures after import

Hi,
I've recently upgraded from a D300 to a D700. After importing my pictures from the D300 into Aperture (via USB cable), Aperture always asked me whether I wanted to delete the pictures from the camera.
I noticed that when doing the same with the D700, Aperture does not ask this question after import.
Is this is known difference and is there any way to work around it (except for formatting the memory card after import)? I do know the USB mode/file system of the D700 is different from the D300, this might be related to the behaviour noticed.
Thanks in advance.

I'm a Canon shooter so I don't really know, but the camera may not allow that operation. You probably would not experience this with a card reader.
The option to erase the card being available but not working is a known issue, but you'll find that most people here don't recommend using that option anyway.
It's really best to let the camera reformat the card so that it's formatted by the camera that's going to shoot it. Another reason not to use this option is that the images should be backed up before the card is erased.
Most would recommend that you import using a card reader, back up the images then reformat the card in the camera. Some recommend not importing directly from the camera or the card but copying the files to the hard drive then importing from there to avoid card corruption.
DLS

Iphone 6 videos aren't showing up in iPhoto after import

After importing tons of photos from my new phone to iphoto, I noticed that none of the videos are showing up. I deleted after importing, so they're no longer on my phone either. All my old videos from my iPhone 5 are showing up, just not the videos from my 6+. In Spotlight, I typed in h.264 and the videos are showing up and directing me to iPhoto, they're just not showing up there at all. What's going on? Thank you!

Disconnect the external drive, choose Go to Folder from the Finder's Go menu, enter /Volumes/ as the folder's path, move all aliases out of this folder, and then reconnect the drive.
(27518)

Can i delete iPhoto after iOS8 installation?

iPhoto was been replaced by Photo after iOS8 installation, so my question is:
can i delete iPhoto?

iPhoto was been replaced by Photo after iOS8 installation, so my question is:
can i delete iPhoto?
Make a backup to save it.
Open "Photos" to migrated your photos to Photos, otherwise your photos will be deleted
Right now, iPhoto is unsupported on iOS 8 and does not run.
Unfortunately, Photos is not a full replacement for iPhoto. Many features are missing, as you will discover - no Journals, no books, no brushed adjustments, no tags, no Info panel.

Can I now delete iPhoto after upgrading to Photos

I have upgraded to photos synced everything across iCloud and everything seems to be fine.
I have a migrated library showing in iPhoto
showing a size of 43gb. I know it is not this size but is it safe to delete the iPhoto library. And also can I delete the iPhoto app its nearly 2gb

Do not delete iPhoto!
Remember, we now live in the world of downloaded software. Programs can get removed or changed and you have no ability to reinstall later. In fact this has already happened with iPhoto. You can still buy older versions of iPhoto sold on disk but not the current (download only) versions.

Delete photos after import into iPhoto

Is it possible to delete the photos on the mac after they have been imported to iphoto?

Yes, if you're running a default Managed Library. In that scenario the file are copied into the iPhoto Library on import.
A Managed Library, is the default setting, and iPhoto copies files into the iPhoto Library when Importing. The files are then stored in the Library package
A Referenced Library is when iPhoto is NOT copying the files into the iPhoto Library when importing because you made a change at iPhoto -> Preferences -> Advanced. (You unchecked the option to copy files into the Library on import) The files are then stored where ever you put them and not in the Library package. In this scenario you are responsible for the File Management.

Delete photo after imported into iPhoto?

I'm trying not to have duplicate photos staying on the same harddrive after I import them into iPhoto.
So, can I archive the original photo off my hard drive to an external after I import them into iPhoto?
I know it's perhaps a silly easy question, but I thought that I would ask before I start moving pictures off to my external drive.
Many thanks,

Assuming that you are using the default (and very strongly recommended) managed library you have no need to keep the source image
LN

Can I delete photos from iPhoto after importing them to an external hard drive?

For a while my family has been experiencing extreme slowness on our early 2008 iMac running OS X Lion. We tried many different ways to speed it up. I recently bought a new external hard-drive and was going to put some of our media on the hard-drive. Is it possible that I would be able to put my photos, videos, and music onto the hard-drive and delete them from my Mac to possibly speed it up. Also is there is any other possible way to speed it up?

Moving the iPhoto library is safe and simple - quit iPhoto and drag the iPhoto library intact as a single entity to the external drive - depress the option key and launch iPhoto using the "select library" option to point to the new location on the external drive - fully test it and then trash the old library on the internal drive (test one more time prior to emptying the trash)
And be sure that the External drive is formatted Mac OS extended (journaled) (iPhoto does not work with drives with other formats) and that it is always available prior to launching iPhoto
And backup soon and often - having your iPhoto library on an external drive is not a backup and if you are using Time Machine you need to check and be sure that TM is backing up your external drive
LN

Delete Originals after Import

When I import into iPhoto - once the import is completed, it asks if I want to delete the Originals (which I generally do!).
Does Aperture have the same feature - and if so - where ('cause I can't find it!).
Thanks.

Supposedly, but people here have reported that 2.0 doesn't delete originals off the card, even when you tell it to.
Frankly, my best advice is to not ever do this. Just manually format in the card when you use it. You'll have fewer issues this way (the camera is the only thing that TRULY knows what format it wants to use), and you have a backup if something should go wrong -- until you erase the card in the camera. If you ever have a situation where an import goes wrong and then the importing app does it anyway (I had this happen with iPhoto a few years back and lost some images), you'll NEVER have your importing app delete images automatically again.

Videos deleted shortly after importing

Hello everyone,
I'm trying hard to migrate my photo collection from iPhoto (and eventually Aperture, which I still use for professional work) to the new Photos app.
What I have noticed, though, is that, besides all photos from iPhone being imported rotated 180°, which is (annoyingly) fixable by hand, Photos will just delete videos from its catalogue. Needless to say, they open fine in iPhoto.
Basically:
On first launch (or consequent start-ups of the app when deleting the Photos library), Photos asks to import a library.
It goes through the import process.
All files are imported correctly (besides the 180° issue), including videos, which play back normally.
Under Preferences, I set the library as System library (in case I deleted the previous Photos library), and turn on the iCloud Photo Library feature.
Somewhere along the process, when I try to access some videos, it says "Photos can't reproduce the file" (translation from my OS X language). In some other videos, a small progress wheel appears on the bottom right, and gets stuck at about one quarter.
I have also tried to import everything by opening manually the "Masters" folder in the old iPhoto library, but then, Photos will give an error regarding duplicate files.
Honestly, all these problems are so un-Apple-like. I'm very frustrated; I've tried to give Photos a chance, but I can't even START using it.
Any suggestions?

Sorry, wrong section; please delete.

Deleting iPhoto after import to aperture

Similar Messages

Maybe you are looking for