EXIF data is stripped when e-mailing images out of iPhoto '09

I teach photography classes as well as exchange a lot of photos with friends. Prior to installing iPhoto '09, my e-mailed images contained most of the important exposure info - f/stop, shutter speed, ISO, etc. Being able to discuss my images with friends and students has always been a great learning tool when we both could see the EXIF info.
When receiving images from a student with a brand new iMac, I noticed none of her images contained the EXIF info and we could not figure out why.
Last month, I installed iPhoto '09.
I realized today that iPhoto '09 is stripping all of the shooting info when you select the images in iPhoto and then click the "Mail" button. I did figure out 2 workarounds:
1. If you make your iPhoto and Mail windows fit on the screen at the same time and simply drag the images into a "New Message" window, the shooting info is retained.
2. If you open the Photo Browser window from within the "New Message" window, select your images and drag them into the body of the message, the shooting info is retained. You may need to use the dropdown "Size" button at the bottom right if the images exceed the max file size.
I have a hard time believing some iPhoto programmer made a conscious decision to change the handling of EXIF info when e-mailing out of iPhoto '09 and feel this is a classic case of deleting functionality by accident with a new release.
I also fear that fixing this will be far down the list of iPhoto '09 fixes...
My workarounds are just that. They are much slower than running iPhoto full screen and launching Mail.
Any thoughts from the experience forum users?

Bruce
I can confirm exactly what you say. Images that are emailed from within iPhoto have their basic Exif stripped. Images dragged to a Message Window from either the iPhoto Window or the Media browser in Mail have their Exif intact.
IPhoto menu -> Provide iPhoto Feedback
And mark it a bug report.
Regards
TD

Similar Messages

  • Exif data gets stripped exporting to camera roll

    I import pics from camera roll to edit in PST. I then export back to camera roll so tha I can use another picture management app to sort my edited pics into files. However the original exif data seems to get stripped out, especially the original date an time the original photo was taken. Apps like Photogene and Filterstorm do no do this. Is there a way of stopping this happening ? Or is it a bug ..... Why can the original exif data not be left intact ?

    Sounds daft as it would probably be easier for the app to eave the exif data intact rather than deliberately alter it !
    I hope adobe can put his right as preserving the original date and time of a photo is crucial for some photographers. This kinda prevents me from using PST as it is very important for me, and I no need to resort back to using Photogene.

  • Transferring images out of iPhoto but keeping original date

    I'm currently backing up all my images from iPhoto 4 onto CD (and elsewhere). When I transfer them the copy has todays date rather than the date they were originally created. Is there anyway to transferring them to back up and keep creation date so I retain the timeline.
    thanks in advance

    Hello -
    I recently backed up my photo archive from my old G4 desktop to an external hard drive, then imported everything into iPhoto on my new MacBookPro. A number of photos are now categorized with 'original date' as 2007, though I know they are from a trip in 2006.
    Is there any way to change this original date to the correct date, or otherwise weed them out of the calendar view under 'library', or do I simply need to distrust / ignore the annual organization and make my own 'album' and/or folders to deal with the mislabel?
    Assuming the original files are correct (I unfortunately cannot check right now), would transferring the files directly between the computers solve the problem? Is there a way to back up without corrupting the original date field?
    Thanks,
    D.G/C.A

  • Mail Image Compression vs. iPhoto Compression

    When I attach jpegs directly in Mail.app, choosing the medium imagesize results in an image of 421KB.
    When I choose the same image in iPhoto, click the E-Mail-Button and choose medium imagesize too, the resulting Image in Mail.app is only 122KB with no noticable quality loss.
    Is there any way to influence the imagequality Mail.app so the results are the same?
    Thanks for any ideas,
    jan

    I've had this experience too, with Tiger and Leopard. It's a serious problem -- the only way to get a reasonably small mail message is to use the "small" setting, which gives you 320 x 200 -- yuck! And it's still big. There should either be a quality slider or better yet just default to decent (70%?) compression. And the scaling problem is all over OS X -- resizing something in Preview or iPhoto for example. I think it's because they use Core Image and it's done in the video card, which can't do anything sophisticated.

  • EXIF Data Lost for Edited DNG Files

    I'm having an issue where my photo's EXIF data is lost when I export the picture from iPhoto. This only happens after I edit a RAW (DNG) file and export it. If I export the RAW file before editing the EXIF data is fine. Is this a bug?
    System Info:
    iPhoto v.7.1.3
    RAW format type is Adobe DNG.
    Camera is Pentax K10D
    Mac OS X v.10.5.2.

    I've been having the same trouble for a few months now. All EXIF is lost, including GPS and focal info. It only occurs when you edit a RAW/DNG file and have the "save edits as 16-bit tiffs" selected in the preferences. Please, Apple, help! This is a significant issue when exporting photos! That info is essential.
    thanks,
    Brett

  • Lightroom strips very valuable EXIF data - details

    Hey everyone - I've just been playing around with some EXIF stuff, and I noticed something very concerning.
    I do a lot of macro photography, specifically with Canon's MP-E 65mm 1x-5x Macro. This lens records its macro magnification factor in the EXIF data, and does so far more accurately and conveniently than I can.
    I know that Lightroom and Photoshop strip out A LOT of obscure EXIF data when processed, but this magnification data is extremely valuable when reviewing my photos at a later date.
    I can provide sample files if needed, and here is my observations so far:
    - data stays intact when converting from .CR2 to .DNG
    - data is stripped when converting to JPG, TIFF, and other formats
    - data is stripped by both Lightroom and Photoshop
    Here is the EXIF data (from exiftool) right from the Canon CR2 or DNG file (both are identical):
    http://don.komarechka.com/exif/exif-original.txt
    Here is the EXIF data (from exiftool) from a jpg that has gone through Lightroom:
    http://don.komarechka.com/exif/exif-lightroom.txt
    You'll notice a HUGE amount of extra data in the original raw file. It is certainly worth noting that the EXIF data in a JPG, unaltered from the camera, contains all of the same data as the RAW file.
    So, is this something that has been overlooked, is there any way to change this behaviour? Even though Lightroom might not be able to decode this data, I don't see a reason why it cannot be left intact.
    Thank you.
    - Don Komarechka
    http://don.komarechka.com

    donkom wrote:
    clvrmnky, thanks for your response.
    Here's an example for you, the one I've been giving:
    I shoot with a special macro lensm the Canon MP-E 65mm f/2.8 1-5x Macro. This lens does not zoom, but the magnification can change from 1x to 5x.This lens communicates its magnification to one decimal point accuracy to the camera, which adds it to the maker notes.
    This is important in reviewing images for a number of reasons, including calculating the effective aperture and depth fo field. This is a valuable piece of information that is stored within the makernotes that is removed from the image when sending it through LR, Photoshop, or ACR.
    That isn't the only valuable information, however.
    The makernotes will tell me if the image was captured using LiveView, if Mirror Lockup was used, if the shot is part of a bracketed set, what the internal camera temperature was, etc. etc.
    I'm not sure you've justified your reasoning behind why this block of data shouldn't be blindly copied. If it is removed simply because it is not understood, I would like the option to understand this data on my own, using third-party tools, after the image has left LR.
    I understand that this can be proprietary, but likely far less so than the RAW file formats that LR and ACR already understand. It would be trivial to understand where this block of data begins and ends and to leave it in the file on export.
    I think this would allow for more in-depth searching based on metadata, for whoever wants to take up that torch. For example, what if I want to see all macro photos I took at a 4x magnification or higher. What if I want to see all photo I took using LiveView. Even if LR doesn't want to do this, stripping the data out prevents anyone else from doing it in the future.
    Well, there is an SDK for metadata that has been around for awhile, which allows for custom metadata definitions. But, according to the SDK:
    "Values stored in custom metadata fields are stored only in Lightroom's database. In the current release, a plug-in cannot link custom metadata fields to XMP values or save them with the image file."
    So, this is more for searching and interfacing with tagset plugins.
    Even so, using the SDK to get at maker notes is a losing proposition.
    Note that some metadata is proprietary and will not be read into the database. This is to be expected. Lr is not an arbitrary metadata reading app, and there is no guarantee that any app could read all metadata. For example, Lr tries its best to get the serial number info, but this is because there is a lot of value in that for other Lr operations. So the contortions necessary to reliably get that is worth it. Another example is lens info (which is a twisty maze of passages; no app is ever guaranteed to actually retrieve lens info reliably in all cases) where there is a lot of value trying to extract the information that makers often store in very interesting ways. In some of those cases I think Lr will look in the maker notes, but only after exhausting other avenues, and with the caveat that it may never be able to get some information. The app does its best to get at the most valuable info it can get that fits with the standardized metadata models in place.
    However, the key here is that maker note data is not in exported files that Lr makes, because it is not normalized data that belongs to the vendor. (This obviates the recommendation of using Metadata Wrangler, which can filter out only that metdata that exists in Lr; I had vaguely remembered a setting that referred to this section but was wrong.)
    The field and data formats are not standardized, so you are asking Lr to understand most or all data from all or most lenses and bodies (all of it in varying degrees of similarity and difference) not just data from this lens and this body.
    This is also not a trivial matter of "copying" the maker notes over, because copying implies parsing and duplicating what is essentially unknown formatted data containing proprietary data, possibly by custom serialization routines. Remember that maker notes were never intended to be editable, and could be composed of any number of data formats. Some cameras make maker notes that are megabytes of nulls and nothing else!
    I think you are out of luck for this specific case.  Perhaps with EXIF 3 we will have a more standardized interface cameras and software can more easily interoperate on shared data. Makers need to stop using the maker notes! It was always an egregious hack.
    One workaround I can think of is to have a post-export action that uses EXIFTool to update exported images. For those cases where it matters, you could create your own "sidecar" file that has only the maker notes, and then shove those into the JPEG after they are created, or just read it from the on-disk copy and then put it in the new file (possibly in the same directory and added back into the catalogue for convenience.)

  • Inconsistent import of EXIF data for RAW images

    As of the last month or so I have started to notice import issues related to EXIF data within Aperture. When I import images from a card into a new album, some of the images import EXIF data and others do not. This behavior is seemingly random and affects a subset of all images. Even images taken on the same card with the same camera seconds apart can have differing behavior. At first I presumed that it was a faulty CF card but I now see this behavior across multiple cards (CF, SDHC). Even more perplexing is that the EXIF data will be associated to some images when I import once, and after reimporting the same images once agin from the same source, some do not have the EXIF data. This inconsistent behavior leads me to believe there may be a bug in the import process.
    Has anyone had a problem like this? Any advice?

    Yes, it is weird.  My experience matches zeroorone's.  No EXIF inf. showed.  I wasn't using a metadata preset that showed _all_ EXIF, but a lot of it, and all the "important ones".  It seems reasonable to assume that none of the EXIF was showing.
    Brand new installation of everything, less than 1 week old, all up-to-date (I am re-installing everything, slowly; porting nothing except some pref and support files, and data files).  Only happened once so far (but on three consecutive imports).

  • How can I preserve the date and time of photos when moving them from iPhone to iPhoto and then to other folders on my computer?

    In the past I’ve had no problem moving photos from my iPhone 4 into various folders on my computer while retaining their original date and time. I would import into iPhoto, then drag the photos from iPhoto into other folders via the Finder or Adobe Bridge (which is my principal image organizer). The original date and time of the photo would always travel with the jpeg into iPhoto and then into other folders. However, sometime during a recent session transferring photos in this way, the dates of the photos started to change at the point when I copied them out of iPhoto. Within iPhoto itself, the various original dates of the photos are retained. But in Finder and Bridge, copies of those same photos all carry the same (worthless) date: the date and time that they were imported from my iPhone. I can’t figure out what would have changed on my Mac to make it start re-dating my photos. I was happily dragging and dropping photos, and suddently I started to lose the original dates. Did I inadvertently change some settings? (I am running OS 10.6.8 and using iPhoto 8.)

    (I use iPhoto only to import from my iPhone; I organize all my images, including thousands of RAW files, in folders on a big external drive.)
    Why are you using iPhoto at all? use image capture or drag and drop the photos
    The problem is that the files I am copying are getting stripped of the EXIF metadata
    eliminating iPhoto from your work flow will eliminate one oppertunity to have this happen  For photos in iPhoto it is best to export them rather than drag an drop them - this assures your EXIF and IPTC data is correct and uptodate
    Why would I be able, over many years, to retain EXIF metadata in photos imported from an iPhone--then one day find that the same workflow strips such photos of EXIF data?
    Because exporting is the supported way to "export" photos - I never drag and drop photos out of iPhoto and I never use thrid party programs on the photos in the iPhoto library - try exporting as suggested above and see if that is the solution
    LN

  • EXIF data included with emails?

    Does EXIF data get included when a photo is attached to an email?  What about tags & when you send pictures that aren't jpegs?

    Before attaching to your Email use save for web to strip out meta data and to optimize your image size.

  • Export EXIF data

    Hello,
    I have just started using Lightroom to convert RAW images. Although this is a bit of a "nit", one of the frustrating issues with any
    of the various RAW image processors is the manor in which EXIF data is handled. It appears that Lightroom handles EXIF data
    somewhat differently when compared to other image processors.
    The issue is the application I use to generate photo albums (JAlbum)not picking up "Resolution" from JPG images
    produced by Lightroom. As an example please take a look at
    http://www.wideeye-photo.com/Just%20Things/Sand%20Frogs/slides/IMG_0031.html
    and
    http://www.wideeye-photo.com/Just%20Things/Sand%20Frogs/slides/IMG_0031-a.html
    IMG_0031 is produced with Lightroom. IMG_00031-a is produced with Canon DPP. You will notice that "resolution" is missing
    for the Lightroom image and is present for the DPP image. Also notice that for the Lightroom image, "Photographer" present
    but missing for DPP.
    I had not had a problem with EXIF data until I started using Lightroom to develop my RAW images. Is there a parameter or setting I'm missing somewhere?
    Thanks,
    Ron

    I have seen that Lightroom moves some information from standard EXIF fields to XMP. I don't remember if this is the case with resolution, but it may be the explanation if jAlbum does not read XMP.
    Henrik

  • 'Date created' instead of EXIF date getting used for batch naming/folders?

    I've noticed that Aperture is using the file creation date as opposed to EXIF date/time info when it imports my photos. Camera is a Nikon D200. Images are .NEF files.
    If I allow Aperture to apply new master file names, based on Image Date - Image Time, it uses the Mac's file creation date (whenever the file was copied to the machine) as opposed to using the EXIF date and time.
    I've already filed a bug with apple, but wanted to put it up here as well to see if others were having the same experiences.

    Hello,
    I use exiftool to modify the  Creation and Modification time of the files. After that I use LR "Ajust time" feature to set the time of the movies in LR to the file creation time (last point). This works fine for me.
    For MOV (Quicktime):
    exiftool "-FileModifyDate<TrackCreateDate"  "-FileCreateDate<TrackCreateDate"
    For AVI:
    exiftool "-FileModifyDate<DateTimeOriginal"  "-FileCreateDate<DateTimeOriginal" *.avi
    Depnding on your camera (and container format mov, avi) you may also ajust the time zone, e.g.
    exiftool -FileModifyDate+=1 -FileCreateDate+=1 -if "$CameraModelName =~ /EOS 600D/i" *.mov
    Which time in the container (MOV, AVI) you use as source, depends on your workflow. I edit my mov files before import. Therfore "CreateDate" is the time when I edited the file. Quicktime and (some) avi file contain a time when the containing stream was created. I use this vaule as source.
    exiftool <filename> gives you detailed information about all available times.

  • Any way to change/replace EXIF data like the original date of photo?

    I'm importing into Lightroom several thousand photos I took with my first digital camera, back in 2000-2004. It's all gone very smoothly. But here's my problem:
    In my old workflow, photos I spent time editing wound up as TIF files, and whatever program I used to edit them stripped out the EXIF information from them. As a result, for example, a photo which was actually taken on March 4, 2001 will have EXIF information showing it was taken on March 10, 2001, the date on which I edited it and made the TIF. All of the other EXIF data is stripped as well, the exposure data, lens information, ISO, whether the flash fired, etc. The TIF file basically seems to have no EXIF data other than the file size and my name.
    I can live without the other info, really, but the changing of the information about the original date/time means that the TIF file doesn't sort next to the original file in Lightroom, which I'd like it to do. There's not thousands of photos for which I have TIFs, just a few hundred at most.
    Is there any way, with a plug-in or some external program, to copy the EXIF information from the original program and insert it into the TIF file?

    I'd suggest just using ExifTool.
    The command is:
         exiftool -tagsFromFile {SRCFILE} {DESTFILE}
    So, if you have a tif sans exif named my.tif, and an original jpg with exif named my.jpg, it would be:
         exiftool -tagsFromFile my.jpg my.tif
    There may be a batch-y way to do this with exiftool, or you could make your own batch file to do this in bulk...
    Main link: http://www.sno.phy.queensu.ca/~phil/exiftool/
    Examples: http://www.sno.phy.queensu.ca/~phil/exiftool/exiftool_pod.html#copying_examples
    PS - To sync changes from files into catalog, use 'Read Metadata from File' function on Library Metadata menu.
    Rob

  • External editor getting error window when trying to load photo in iphoto yet I can drag out of iphoto to the desktop then load right into photoshop with no errors

    I use Photoshop elements 9 to edit , since the last up-date when I'm in iPhoto and click edit in external editor when photoshop opens it sits there a minute and  and then a error window comes up saying something about an unvalead jpeg marker can't open but I came drag the image out of iPhoto to the desktop and then open it with photoshop with no trouble ? help I'm running 10.6.7 on a 2007 mac pro iPhoto 11 Ver. 9.1.3

    There's a bug in iPhoto 9.1.3 when using Photoshop as the external editor when trying to edit a tif, png or psd file.  That's because iPhoto is just duplicating that file and changing the extension to jpg without acutally changing the photo's format.  That's why PS says it's an unknown format. 
    No know solution at this time except edit only jpgs and raw files in iPhoto with Photoshop.  Also send a bug report to Apple via http://www.apple.com/feedback/iphoto.html.
    OT

  • Why am I getting an "!" when I open up pictures in IPhoto

    Not sure what is going on, but my hard drive was replaced at the Apple Store after a crash from their recent software update. They saved my data but now when I open up picutes in Iphoto I can only view thumbnails and the large size puts a big exclamation point on my screen like maybe a resolution problem or bad photos? Never seen this before, any suggestions?

    The ! or ? turns up when iPhoto loses the connection between the thumbnail in the iPhoto Window and the file it represents.
    Back Up and try rebuild the library: hold down the apple and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild.
    If that fails, then...
    Try these in order - from best option on down...
    1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library (Right Click -> Show Package Contents) allowing it to overwrite the damaged file.
    2. Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
    3. If neither of these work then you'll need to create and populate a new library.
    To create and populate a new library:
    Note this will give you a working library with the same Events and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
    In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'
    Move the iPhoto Library to the desktop
    Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
    Go into the iPhoto Library (Right Click -> Show Package Contents) on your desktop and find the Originals folder. From the Originals folder drag the individual Event Folders to the iPhoto Window and it will recreate them in the new library.
    When you're sure all is well you can delete the iPhoto Library on your desktop.
    In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
    Regards
    TD

  • Images resized and exif stripped when emailed ?

    Does any know why the iPhone resizes images (to 640x480) and strips out EXIF data when you email a photo. However, if you download the photos you get the full size and EXIF data ?
    As i often like to email photos direct to Flickr from my iphone it is very annoying to end up with a poorer image than what i should have.

    Hello All,
    Great news for the Apple iPhone.
    Just downloaded 2.1 software update, and the Geotagging correctly geotags the southern hemisphere, now adds a GPS Time-Stamp as well as the GPS longitude & latitude info to the EXIF.
    AND, when you e-mail it or transmit the image to a secure server, mobleme, Flickr . . . ALLL OF THE EXIF DATA STAYS INTACT, INCLUDING THE GPS METATAGS . . .
    AND THE SIZE OF THE IMAGE HAS BEEN REDUCED FROM 1200 X 1600 TO 600 X 800 . . .

Maybe you are looking for

  • Function module to get the cost estimate

    Hi all while running the standard  costing run the cost estimate is stored in the table keko and keph.can anyone tell me whether is there any function module to get that cost estimate of a material  which is in released status

  • Converting Pdf page into word without distortion

    I am trying to copy a single page from a pdf file into a word document.  How do I do this without getting a lot of distortion.  The small numbers are hard to read when I do this.  If I just print the page I can see the numbers clearly.  Thank you

  • ESR objects after re-importing SWCV into ESR from SLD

    We created two SWCVs in SLD and imported into ESR. I_MYCOMP_SWCV_ONE I_MYCOMP_SWCV_TWO I created few design objects like DTs MTs SIs like  dtA, dtB, siC in I_MYCOMP_SWCV_TWO but later, for some reason, to enable usage of objects of I_MYCOMP_SWCV_ONE

  • Any way to search by document type?

    New to mac. I'm trying to search out all Pages or all Doc files. (Clicking "docutments" gives me too many doc sytles, including .jpg.) I tried *.pages or *.doc and it obviously is not the answer. I'd like to save this search or others that target spe

  • Rendering Project - Audio failure

    Hi, I've just finished a music video, where the sound was recorded separately. I synchronized the sound with the picture by slowing it down 1%. Everything works fine in the work area, but after rendering or exporting the project the sound goes back,