IPhoto '08 corrupts EXIF data on export

Hello All,
In using iPhoto '08 (including the latest update to 7.1) I am noticing the when I export files the EXIF data is getting corrupted.
My original files are fine--all EXIF data shows up properly, and galleries which I post to that are capable of displaying EXIF data display it just fine. However, when I export a file from iPhoto to JPG format, the galleries are unable to display the EXIF data. Using the Firefox extension, 'EXIF Viwer' ( https://addons.mozilla.org/en-US/firefox/addon/3905 ), I see there are errors in the data (screenshot here: http://jaaulde.com/exif_viewer.png )
Thanks for any help you can provide.
Jim

Jim:
It may be the server side software that's causing the problems. Another thread went thru something like this extensively and we found that files from some cameras, Canons for one, are not read properly by the software. We've downloaded the files and read the EXIF data and it was all there. I have a gallery of files from various cameras as an example: http://gallery.mac.com/toad.hall/100196. Click on the "i" button in the slideshow and you'll see those that get the EXIF data correct, primarily the shutter speed, and those that do not. I don't remember the thread but you can search this forum for "EXIF web gallery" or similar.
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. iPhoto doesn't not have to be closed to run it, just idle.
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. It's compatible with iPhoto 08 libraries. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Similar Messages

  • IPhoto '08 loses exif data when exporting RAW to JPG

    I'm using a Canon 40D shooting only RAW. I just recently noticed that when I export to JPG, iPhoto loses quite a bit of important EXIF data, including, aperture info.
    Is this a known issue, or is it something unique to my system?

    I guess I misworded it. I understand that the info doesn't go away or come back. Either there's a problem in both Finder and flickr (I've uploaded the file to flickr.com) where neither finds the info in the jpeg or there's a problem in the way iPhoto writes the EXIF data to the file.
    Today, I downloaded EXIFViewer for an alternate look at the EXIF fields and the aperture data is there according to EXIFViewer. So, now I think the bug may be with flickr. Can't really call it a bug in Finder, since the expected functionality for finder is not to get "aperture info", but "More info."
    In any case, these are the fields in the More Info:
    |RAW:Name_|_RAW:Value_|_JPEG:Name_|_JPEG:Value|
    |Dimensions|2586x3892|Dimensions|2586x3892|
    |Device make|Canon|Device make|Canon|
    |Color space|RGB|Color space|RGB|
    |Profile name|Adobe RGB (1998)|Profile name|Generic RGB Profile|
    |Focal Length|44|Focal Length|44|
    |Alpha channel|0|Alpha channel|0|
    |Red eye|0|Red eye|0|
    |FNumber|4|
    |Exposure|1/60|Exposure|1/60|
    |Last opened|Monday, May 19, 2008 6:31 PM|Last opened|Today, 9:31am|
    And the meta info on flickr is here:
    http://www.flickr.com/photos/carloscervantes/2536040124/meta/
    Again, no aperture data in either flickr or Finder.

  • Where can I give feedback regarding Aperture? I'd love to see the ability to removes EXIF data when exporting, especially to social networks.

    Where can I give feedback regarding Aperture?
    I'd love to see the ability to removes EXIF data when exporting, especially to social networks.

    Robert,
    For any normal Export, simply cilick the list of option and further click on Edit.  There deselect to include Metadata, and there will be no EXIF data exported.  But no copyright info either.
    The option already exists to do what you want.  Once a normal Export has deselected that, I believe even exports via plugin for say FB will not have it either.  I tested with an export to SmugMug after deselecting in an earlier ordinary export, and EXIF info was not transmitted.
    Ernie

  • Corrupted EXIF data in photos exported from Lightroom CC

    After upgrading to Lightroom CC EXIF can't be read by some apps. "Re-saving" a file in Photoshop fixes the problem. I'm using Mac OSX 10.9.5. Are there any plans to update and fix the EXIF data generated when exported from Lightroom CC?
    Also, this command fixes the issue with Create Date part of EXIF.
    #!/bin/sh
    exiftool -AllDates="$(exiftool ${1} | grep 'Create Date' | awk '{print $(NF-1), $NF }')" -overwrite_original ${1}
    The reason I'm asking is because we run a site where "Create Date" read from JPG's EXIF is crucial and it's a matter of letting users upload the pic or deny uploading.
    So again, any plans on the fix?
    Regards,
    Pawel Kadysz

    I confirmed that the Exiftool command line:
    exiftool -m -all= -tagsfromfile @ -all:all -unsafe file.jpg
    removes the ICC Profile, which could account for significant color differences, considering that the profile is Adobe RGB.  I think this may be a bug in Exiftool, so I filed a bug report.  (But it might be that Exiftool just can't handle the non-standard layout of LR's JPEGs.)  The author is typically very responsive.
    I tried some alternate Exiftool command lines that touch as little metadata as possible, and this one seems to address both of LR 6's JPEG problems:
    exiftool -m '-exif:datetimeoriginal<exif:datetimeoriginal' -xmp-crs:all= file.jpg
    The -m option ignores minor errors and issues, in particular, when there are more than 1000 entries in the XMP metadata.
    The '-exif:datetimeoriginal<exif:datetimeoriginal'  option sets the EXIF Date Time Original Field with its current value; this tricks Exiftool into rewriting just the EXIF metadata without touching the other metadata segments (e.g. the ICC profile), addressing the first JPEG problem.   (You could use any EXIF field that's present -- I picked DateTimeOriginal since every camera adds that.)
    The -xmp-crs:all= option option deletes all of LR's develop settings from the XMP metadata, addressing the second JPEG problem.That metadata is not ready by any programs other than LR, as far as I know. 
    I've tested this new command line on a couple of pics, including the example you provided above, and it appears to work correctly.  But given that we're dealing with buggy output from LR that doesn't conform to the de facto and de jure standards, it's hard to have high confidence without testing on dozens if not hundreds of pics.

  • GPS Altitude Not in Extended Photo Info or EXIF Dat ahwne exported

    Hi,
    I have my own website that uses a Goggle Maps plugin to read and show GPS info for photos I upload. When I use Places to capture that info the Altitude info is not stored either in iPhoto's database or in the EXIF info for the photo when exported. Is there anyway get this info stored in the database and phot when exported?
    The Google Maps plugin on my site makes use of the Altitude details to show a more close up image depending on the altitude chosen. Without this info the site just shows a extremely high level world map with a pin showing in the country where the picture was taken. Not particularly useful. So I have to go and edit each file on my website and manually add this info. Which is very time consuming.

    Jennec
    iPhoto menu ==> provide iPhoto feedback
    There is no provision in iPhoto to add altitude at this time - iPhoto should maintain the EXIF data that is imported - if it is not then I certainly would report that as a bug
    When I show extended photo info in iPhoto for photos it shows the altitude - I presume it exports - will test later
    LN

  • IPhoto 11 - Extended EXIF data where?

    Hi,
    I've just upgraded to iPhoto 11 and can't access the extended EXIF data for each photo that was available with "Show Extended Photo Information" in '09. I regularly retrieve the long and lat of the photo from here so if it is gone it is a problem for me. Anyone else found a way to get to the full EXIF data?
    Thanks

    It's at the top of the Info window on the right (when displayed)
    Click to view full size
    OT

  • Missing/Corrupt EXIF Data

    I was looking at a folder of images today, and noticed that the camera data was not showing up and the images looked out of focus. Moments later the camera data showed up but the images still looked blurry (thumbs). Suddenly all the thumbs in the folder disappeared, being replaced by the .nef icon. I mean instantly, they all changed to the icon. I tried to open but got the message:
    "Could not complete the request because it is not the right kind of document. "
    So I tried to open it using DXO and it returned :
    "This image cannot be processed since its EXIF data cannot be read or is missing".
    Right click the image and the File Info is missing from the menu.
    How does this happen? I have opened these images in the past. I can imagine the instant insanity should all my .nef's suddenly do this!
    I am using Bridge running Photoshop CC on Win 7 64 bit. The .xmp data exists according to Win Explorer. There is no Bridge cache showing for the folder in Win explorer.
    I am unsure as to whether this belongs here or in Bridge or???

    I don’t think WFW would know about any outsider accessing the file on dropbox since it runs on your local computer.  If this is the first time you’ve used dropbox, it may have been asking for permission for dropbox to access your local system via the public network (there are local, domain and public tiers in the firewall rules) since dropbox synchronizes things between computers via the data stored in the dropbox cloud storage. 
    In other words, I downloaded the file to my local computer using the public link you provided, and wasn’t logged in as you, so would have been accessing the dropbox cloud for retrieve the file but not be logged in as you, but I don’t think the WFW would know I was doing anything for that interaction because that is between me and the cloud, not something on your local computer.  Depending on how you answered the WFW question, you may have blocked dropbox from doing its normal things.  You can get into the WFW configuration in Admin Tools (or maybe Control Panel) and enable things for a particular program that you may have disabled by mistake.
    Back to the corrupted file issue:  spot-check a few of the bad files on the backup, right-click Properties, and look at the Created Date and Modified Date, compared to the expected date the backup first would have copied them, to see if either indicates the date the zeros were written.  You might want to compare those dates on files that are ok, to see if there is some difference in pattern.  It is possible the backup software updates those dates to be what the source files dates are which might mask the backup-software's last-copy date, which is what you want.
    If you can determine the date for the zeros and it is fairly recent, then the system event log might list something as having occurred. 
    If there haven't been any viruses, then I'd say it was a transient condition, either in the circuit-boards or cabling or the hard-drive media, itself. 
    Has the computer ever locked up so you had to turn the power off to get control back of the mouse? 
    You can test the hard-drive media for errors by chkdsk d: /r or chkdsk d: /b (or the gui-scandisk equivalents) to scan for data errors--iffy media problems.  Move any virtual-memory swapfile off that drive if you want to test it while the computer is running.  Maybe do a plain chkdsk, first, one where you don't fix problems and don't test the media, which would find problems indicated with zeros in the directory-structure, first.  And if you find any of those, disconnect your backup drive in case the "fixes" corrupt even more things and that gets replicated.
    A chkdsk that fixes media problems will likely take several/many hours.

  • Missing EXIF Data on Export

    Over the last few months I have developed quite a love/hate relationship with A3. It has so many great features, but at times they are over shadowed by slow performance and bugs. The most recent bug to drive me nuts is missing EXIF data, specifically lens model/serial number, flash exp. comp., and focus mode/distance. It doesn't matter how the file was exported, the aforementioned data disappears every time.
    A quick forum/web search shows that I am not the only one experiencing this phenomenon, but I was unable to find any solutions. So I guess my question is, has anyone found a fix for this problem?

    I share your views. A3 has a lot of great functions. But for this price I would expect to have full geotagger functionality i.e. not only positioning, but also direction inclination angle all kind of data my great Solmeta Geotagger Pro stores in the picture metadata.
    Geosetter e free software on PC has all that so why is Apple not able to deliver the same package?

  • Exif data when exporting images

    Hi, I have question about Aperture writing its signature in the exif data when i export pictures to websites like Flickr, in the past i used DPP, and it always shoved "digital photo professional" under more properties, just this is missing all the rest is there.
    Is there a way i can get Aperture to get that pice of information in there......?
    Jess Thorsen

    There's a simpler method which you might consider using.
    What file naming convention are you using on import? Why not rename your camera files on import into Aperture something like " dateclient_joboriginalfilename ". You could then either use that, or export with that name plus a sequential numbering scheme.
    Or -- the same as Viren's excellent suggestion -- select all the files you are going to export, create duplicate versions, with the duplicates still selected create a new Album containing all of them, then use Aperture to rename the Versions prior to export and export using the Version name. Versions don't use much space (they are text files), and you end up with an Album of neatly numbered Versions of just the photos you've given to your client +with the file names of their files exactly the same as your Aperture Version names+.

  • Hvordan fjerner jeg Exif data under export i aparture

    Remix aner how that in this Dyre fotoprram fjerner mine data from pictures, da de is følsomme. not want folkemusik Ude i WEP, can se where that has fotograferet
    Bla is the GPS-data there hendes are Vejen the about ved

    Where are you checking the EXIF data and GPS?  When I am looking with "Preview > Tools > Inspector" at the exported versions, the GPS is gone.
    Alternately, try to edit the EXIF with exiftool:   ExifTool by Phil Harvey
    You need the Terminal for that, however.
    Hvor skal du kontrollere EXIF-data og GPS? Når jeg søger med "Preview> Værktøjer> inspektør" på de eksporterede versioner, er GPS væk.
    Alternativt, kan du prøve at redigere EXIF ​​med exiftool:ExifTool by Phil Harvey
    Du skal bruge Terminal til det, dog.

  • EXIF data stripped on export??

    Why on earth would FW strip a photo's exif data when exporting? Web graphics are sometimes contractually required to retain metadata. This opens users up to liability if they don't realize that a photographer's credit is removed during compression.
    Is there any way to have this reversed??

    I'm aware of the fact that image copying is widespread. This is why exif data is often a requirement to inclusion in web-displayed images; it reduces liability of web publishers, because we've done all we can to prevent copyright attribution from being removed from the image. Are you aware that many photographers' contracts stipulate harsh penalties for publishers who remove metadata from provided files?
    Photoshop has 2 problems. The first is that it seems impossible to automate a batch to export a folder of images with "save for web" settings. All my research suggests that it's impossible without digging into actual scripting, rather than relying on actions.
    The second problem is that the fireworks "save for web" option is roughly 40% more efficient than the photoshop method, for comparable compression artifacts. I have no idea why photoshop wouldn't use the more efficient fireworks algorithm, but it simply doesn't.
    In the past I've used imageready, which provided slightly better compression ratios than photoshop, retained all exif data, and allowed the creation of droplets. With the nonsensical removal of imageready from photoshop, and its replacement with the comparatively crippled fireworks (the compression efficiency is nice, no droplets is tolerable, but exif stripping is unforgivable in this day and age), I'm left searching for a product that will serve my needs.

  • Corrupted jpegs from LR export

    Hi all,
    I just finished processing my first wedding photos in LR2. After exporting the photos to jpegs I am checking them in bridge and see that roughly a little over half (about 350 photos) of my exported images were showing some random vertical and horizontal lines as if those files were corrupted. That never happened before in LR1. Has anyone here experienced the same problem?
    I had to re-export these images consuming a lot of my time. I am using a Windows XP sp3, though when I exported the images I was still in sp2.
    ps.: The images took literally 3 hours longer to export in LR2 than it used to in LR1.
    Any help is appreciated,
    Lisa

    Yes I confirm. I first posted a problem regarding the Exporting of JPG's out of Lightroom in this thread here:
    http://www.adobeforums.com/webx/.59b63f9d/2
    Following advice contained in that thread my thinking changed somewhat and I believed that the problem might have been in dpMagic - a small application that allows one to view CR2 images in Windows Explorer along with other file formats. I subsequently contacted dpMagic who asked me to forward a few problem images along with screenshots from Explorer when it crashed along with a screenshot of the Event Log. Here is the reply that I received from them this morning:
    thanks you for the detailed information. We were able to reproduce the
    problem. It is originated from the corrupted exif info in the jpeg image.
    The next published version of the application will be resistable to such
    kind of errors.
    with the best regards
    Eugen Shashkou dpMagic DEV
    It would appear after all then that Lightroom is causing corruption of Exported JPG files. I have no way of knowing in which way the EXIF data is being corrupted, and whilst dpMagic say that the next version will be 'resistable' I would much prefer Adobe to see what is causing the corrupted EXIF data in the first place.
    Could one of the mods kindly post a bug regarding this matter referring Adobe to this thread if necessary. It would be appreciated - thanks.

  • EXIF data for PNG files

    I seem to have lost all EXIF data for pictures that I first converted to PNG format, and then edited in iPhoto.
    The EXIF data is still there in the copies of the files in the "Originals" folder in the iPhoto Library. If I open these files with Graphic Converter, I can see the EXIF data.
    But the EXIF data seems to be missing from the PNG files in the "Modified" folder.
    Is this some sort of quirk with PNG files in iPhoto?
    Dual 867 G4   Mac OS X (10.4.9)  

    smbrannan
    I just googled this and the issue appears to be that png does not support EXIF data, or if it does, only in a very limited way. I'm no expert in this field but have a read of this:
    http://heim.ifi.uio.no/~gisle/blog/?p=3
    or this
    http://www.flickr.com/forums/bugs/14168/
    as this person obviously knows something about it.
    Regards
    TD

  • IPhoto not exporting Aperture EXIF data

    Does anyone know why iPhoto will store the aperture value from the original EXIF data, however it will drop this information when exporting? I store my pictures on flickr and keep the EXIF data visible, but no matter how I export it will continually cut out a lot of EXIF data, including this important piece of information.

    How are you exporting? Are you using a flickr plugin for iPhoto? If so that's what's stripping the info from the file. If you export from iPhoto to the Desktop via the File->Export->File Export all of the EXIF data is preserved and you can include the keywords, comments and file name.
    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. It's compatible with iPhoto 08 libraries. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Batch Change "Date Modified" to match Exif Data After iPhoto Export

    Among several other posts about similar situations, I have found none that directly and simply resolve this issue.
    My wife imported a bunch of photos into iPhoto directly, but I wanted them in a folder on the hard drive.
    I pulled them out of iPhoto into a folder, then deleted the ones in iPhoto so that I could sort them and reimport.
    I then realized that the photos all now showed the date they were imported into iPhoto as their created/modified dates, which makes it impossible to easily sort them by the date of the pictures.
    I checked the Exif data, and it has preserved the correct creation date event though checking "info" on the pictures shows create date the same as modified the same as iPhoto import.
    Is there an easy way to batch change an entire folder of pictures to change the Created/Modified dates to match the Created date from the Exif data?
    The only other similar posts had answers that reccomend a piece of software that does not seem to actually do this, and one that suggests some sort of confusing script that I don't really understand.
    Please help - I have a bunch of family photos that I really need to fix.

    shootShifter helps to redate and rename complete folders of images based on the EXIF data or Finder dates.
    So it will do batches.
    I also believe that exporting the Original (File -> Export: Kind Original) will make all of this unnecessary.
    I don't like having them only in iPhoto so I organize the originals into folders by choronological event then import them so I have copies outside the iPhoto library to put elsewhere.
    You understand that you're using twice the disk space there, right? And that it's quite unnecessary. All iPhoto does is to put them in folders too. Have you looked inside the iPhoto Library ever?
    Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed. Your photos are in the Masters folder.
    Standard warning: Don't change anything in the iPhoto Library Folder via the Finder or any other application. iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things,, deleting them or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
    Regards
    TD

Maybe you are looking for