Missing photos when importing from a Fuji s602zoom digital camera

I noticed that when I import the photos from my digital camera (as above), sometimes there are some missing. No error messages displayed and the import seems to finish OK.
This makes life difficult as I cannot now trust iPhoto and have to check every import.
Any suggestions would be helpful.

Neville:
On those occasions where the camera drops some photos are there any movies on the card?
A workaround is to use Image Capture to upload either to a folder on the Desktop first or directly into iPhoto. It's not recommended that you have iPhoto erase the card after import as there have been too many cases, yours for one, that have incomplete uploads and complete erasures.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Message was edited by: Old Toad

Similar Messages

Loss of quality of photos when importing from iphoto to imovie

A question... When I import high resolution photos from iphoto and look at the preview on imovie HD, the quality is the same great quality that I can see on iphoto. Once I import the photo clip onto imovie, however, the quality is very poor on the imovie playback. This drop in quality is regardless of whether Ken Burns effect is used or not.
I already checked the quality on imovie preferences and it is already selected as the highest quality (default setting)
Any clues as to why the photo image quality should drop to such a poor image when importing a photo from iphoto to imovie?

Hi L
There are a great difference on photos shown on a Mac with eg. iPhoto or
PhotoShop and what's going to video.
a. Different resolution. Just the number of lines as the selected type of project
eg: PAL 4x3 = 625 lines ≈ same in pixles (But square not elongated or visa versa)
b. iMovie "Viewer" is just an approximation. I connected my miniDV Camera
to FW and analog to a TV. Select in pref - Play back via Camera. Now I see
the final quality on my TV. Usally much better.
Yours Bengt W

Why is Lightroom 5.4 not recognizing existing photos when importing from another catalog?

I have lightroom 5.4 now updated on my studio desktop computer and my laptop when working in the field. I have a folder of images on both computer catalogs and that inlcudes the negatives on each computer. I made a bunch of edits and changes on my laptop of that folder of images and then exported the changes as a catolog to import into my studio catalog but lightroom doesn't recognize the photos when I import from another catalog. Lightroom tries to add the photos as another folder even though the negatives are there and they are already imported into the desktop catog. Why doen't lightroom recognize they are the same images when I'm importing as catalog? I've always done this with past versions of Lightroom with no problems. I'm just exporting the previews since the negative files are already on both computers. What is wrong?

The folder hierarchy has to be exactly the same; the slightest thing can throw it off, an upper case on one machine and lower case on the other or a misspelling.

Blurry photos when imported from iPhoto?

I'm noticing that when I insert photos from iPhoto into a movie project, they are blurry and this is hurting the quality of my projects. Does anybody know if there are resolution issues or compatibility issues that will help me with this? I've tried just sharpening the image in the editing pane but it's never very good! What am I doing wrong? Thanks.

Here's the deal a little more clearly. I'm simply taking photos on my digital camera on "super high quality" - 3072 x 2304, and when I import them into my iMovie project, they go a little blurry.
Not sure if you are referring to preview window, full-screen previewing, or the final output video being "blurry" here. Suggest yo start off by tracing the image flow. Start off by opening your project package by "Control-Clicking" it in the finder and selecting the "Show Contents" menu option. Then look for a movie file names "Still Images" at this level. Double click this file to open it in the movie player but do not "Play" the movie. Instead, use the right and left arrow keys to step through the file and examine your images carefully. These images should be scaled down from your source images as previously explained. These are the images that iMovie '08 will use when creating your export/shared movie file later. How do they look and what are their dimensions? If all looks okay here and your "softening" is only in the "preview" display, I would likely try making a test export/sharing to see if the actual output looks as "poor" -- i.e., try to determine at what point things may be "going bad." At this point I'm not sure if you are simply "hyper-sensitive" regarding you photos, if iMovie is actually introducing a "normal" loss in quality due to processing, or if you may have a more serious application problem unique to your install for some particular reason.
Can I change settings anywhere so that the resolution's match? How do I know for example, if my project is set at 1920 x 1080 (all I know is I'm working in iMovieHD. Is it possible to import photos so that the resolution isn't automatically scaled up or down?
You can of course pre-scale or crop/scale manually before import into iMovie. However, if you do so in iPhoto/Aperture, I suspect the same scaling algorithm will be used as in iMovie. Have not done so myself, but if I did, I would likely use Photoshop to do this since you can try various resampling options to see which you may prefer for the given content.

Missing photos after importing from iPhoto

I have a big iPhoto library that span from 2002 until today.
Launching Photo for the first time started the import of the default iPhoto library, when finished the problem is not everything has been imported.
I have not done photo by photo check, but for instance all 2014 photos are missing and since I see less photo in previous years and in 2015 also photos from other years are missing.
I can't reimport the iPhoto library (I have not been able to find how), so my question is how can I import the whole iPhoto library to Photos?

First off that is a bad practice - never have any computer program delete things - import photos and keep them - after at least one successful backup cycle has taken place and you are sure your photos are safely on the Mac and backed up then use the camera's format command to erase and reformat the card
You can try to backup your iPhoto library and hold down the option and command keys while launching iPhoto - repair permissions and rebuild the database form the resulting first aid window - that may recover your photos - if it does not then photo recover software like media recover is the next step
LN

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?

Grayed out, weird photos when importing from Camera Roll

OK, wondering if anyone else is experiencing this? I use Photoshop's Bridge import to pull my photos of my iPhone 3Gs. When I do, I often have these weird photos - I'm not totally sure why they are happening. And, the good news is that once they are pulled, they appear to be fine, but I'm just looking to see if I'm not the only one.
They seem to be possibly related to:
a) being taken by an alternate camera app (I've tried several, Camera Genius, Snapture, CameraFlash and CameraZoom - yep, trying to get a better photo!),
b) being altered in some way (I've used Photogene to improve some, but it makes a duplicate?), or
c) being copied or saved to the CameraRoll from another program (I'm a Phanfare user and their Photon app is phenomenal).
So, some pictures of examples below, but as long as they images are OK when they come in, is it just fine? I always worry when something is not what it should be on an Apple device or within an Apple software.
Thx - Alexa
(Saved to Camera Roll from Photon - you can see though that others saved the exact same way are fine?):
!http://www.alexacorcoran.com/misc/Picture4.png!
(Photo taken in Genius app)
!http://www.alexacorcoran.com/misc/Picture2.png!
(Photo edited with Photogene - is still vertical when I pull it off and obviously color, etc.)?
!http://www.alexacorcoran.com/misc/Picture3.png!
Message was edited by: akcorcoran

Hi Lawrence -
Thanks for your response! I'm on a Mac so my options are different, but I think about using a more basic viewer and went to iPhoto and looked at the pictures on my phone as a device, and they all look fine (or some are not duplicates) - so maybe it's just a Photoshop import thing or ghosting issue?
Alexa

How can I delete photos when importing from iPhone 4

I'm using Aperture 3.13 on Mac OS X 10.7.1. When I import photos from my iPhone 4 I am never asked to delete files from the camera roll.
What am I doing wrong? How can I have Aperture delete photos from the camera roll once they are imported?

Aperture won't delete the photos from your iPhone. Most users have settled on using Image Capture ater importing into Aperture to delete the photos from the iPhone.

When importing from a certain Atmos Ninja Camera, I get a "unsupported or damaged file" message and can't import. Help?

These files are MOV format from a Apple Pro-rez 422. I have a pc. Any ideas on how to fix this? The files work fine in Quicktime.

Hi SkyeRyder,
These files are MOV format from a Apple Pro-rez 422. I have a pc. Any ideas on how to fix this? The files work fine in Quicktime.
Sorry to hear that.
What you might try is deactivating Premiere Pro, then reactivating it: Features and Sequence Presets missing | Adobe Premiere Pro CS6, CC, CC 2014
If that does not help, try moving the .mov files to a new folder and then import.
Also, always import files via the Media Browser, not File > Import
Thanks,
Kevin

Cannot load pictures from Fuji F10 digital camera onto OSX 10.5.2

I cannot load pictures from my fuji F10 digital camera. The Fuji support site does not appear to have any firmware that would allow compatibility between the two but was wondering if anyone has any ideas. I can't even bring them over using a zip drive because I get an error stating that the files are corrupt. any help is appreciated.
Thanks,
Chuck

What brand of camera do you have? Perhaps you might take it up with the manufacturer, after all, they are the ones who decide whether to support mounting on the OS X Desktop.
Given the amount of pictures I take, constantly taking my card in and out of the camera puts wear and tear on it,
Using a USB Card Reader is a much better and safer way to transfer your photos:
1. Less risk of your images being lost if your camera shuts down during transfer.
2. It saves the battery on your camera
3. It saves wear and tear on your camera ports - and replacing a worn USB port on a camera is somewhat more expensive than replacing a camera card - and what "wear and tear" is there on a card?
4. It’s almost always faster.
Regards
TD

When importing from camera into aperture, photo's are also copied to my desktop, if i delete from desktop i am unable to edit photo in aperture. Must have done something, but what?

When importing from camera into aperture, photo's are also copied to my desktop, if i delete from desktop i am unable to edit photo in aperture. Must have done something, but what?

Have a look at your import setting specifically Store Files:
Make sure it is set to where you want the originals to go.
Message was edited by: Frank Caggiano - Don;t empty the system trash. The originals that you deleted from the Desktop are in there and are the only copies you have unless they are still in the camera.

Photos sent to file on desktop when importing from memory card

The photos sent to a file when importing from a memory card appear in the file as Adobe documents and cannot be opened. If I try to open a message appears 'Adobe Reader cannot open this document as it is not a supported file/
What has gone wrong?

You have already opened a thread on this issue, we don't need a second thread on the same issue.

HT4101 How is the photo size affected when importing from the SD card to ipad (2) ?

How is the photo size affected when importing from the SD card to ipad (2) ?
If they stay the same, any options I can have to "re-size" the photos so that I could use it for a photo storage when traveling?
Thanks.

To re-size, you can use:
https://itunes.apple.com/sg/app/simple-resize/id327776379?mt=8

Why are missing items when import pst files to Outlook 2011 for mac?

Hello.
After installing Office 2011 for Mac I configured Outlook and it was allright.
But when I tried to import a pst file from the old laptop who has Office 2007, I found that in the Outlook 2011 Inbox I have only ~60% items comparative with the Outlook 2007 Inbox.
From Microsoft Office forums I've got an answer that there are indeed some reports with missing items when import pst in Outlook 2011 but the solution they gave me (create folders in Inbox before import) doesn't work.
Do you know something about this kind of problems?
Is it a feature in Outlook 2011 which automaticaly select/delete/combine items based on the similarity between them or based something else?
Have you an ideea how to finally use this macbook and in the same time all my old emails?
Thanks.

Hi Steve,
Thanks for this-yes, eventually, I do send/receive fine, once I've poppedd my passwords in.
I think you are right in that BT seem to be having unique server/login issues...at least this is what I've read elsewhere too.
Iroonically, this AM I opened my new Mac and have *not* been asked for passwords so perhaps the changes I made in the settings yesterday (keychain reset in Mac) and also changing it from smtp.....to mail.btinternet.com solved the issue...who knows? All I know is this last week I've nearly lost the will to live on more than one occasion, from the transition from PC Windows Live Mail to Outlook for Mac.

Aperture Import destination grayed out when importing from iPad

I'm trying to import a bunch of photos from my iPad. I want to dump them all in one project in Aperture, but after selecting the iPad from the import source list, it grays out the options to select the destination. It also grays out the option to uncheck the Autosplit events. I do not want to do this import and then have to go back and merge 20 projects. Any ideas?

It' how Aperture works with the iPad see Aperture 3: Photos are not split into projects by date when importing from iPad as well as other threads here asking similar questions

Missing photos when importing from a Fuji s602zoom digital camera

Similar Messages

Maybe you are looking for