EXIF data corrupt

When I modify a picture with Adobe Photoshop Elements 10 it very often (but interestingly not always) happens, that afterwards the EXIF data are mostly lost. In Picasa I than only find a remaining block of about 5 values. Photo Me tells me, that "The EXIF data header of the chosen File is invalid", my smart TV is not able to view the picture any more. Even Microsoft Phot Gallery refuses to open the file.
When I open the corrupt file with CEWE foto viewer and restore it afterwards, the values are back again. But unfortunately the size of the file gets trasticly reduced.
Since this is not a general problem, I don't know where to look for a solution. Obviously it's not the program settings, since I haven't changed anything there.
My camera is a Pentax K5, But I don't think that there is a problem, because the original pictures are always ok.
Who knows more?

I may be wrong but it appears that all Adobe products strip out the camera maker notes data from EXIF Metadata.
Since EXIFtool and several other applications can properly read and write to and from the EXIF maker note area, I can only assume Adobe does not care about preserving this information.  I've been researching this topic for the past few days and it appears Adobe has known about the issue for several years but has never fixed it.  Since they have not fixed it, I can only assume they don't feel it is important enough to us users.  Some folks keep their original files and do not let any applications ever edit them in any way, including metadata.   That wouldn't be a problem if we didn't have 10's of thousands of images to deal with.  Originals, edited ones, backups, etc....   It starts to chew up space pretty fast but keeping your originals protected from ANY updates is the only way to ensure the maker notes stay in tact.  Of course this makes it really inconvenient to quickly look at the maker note of a particular photo.  This camera specific information can be used to help the photographer learn how he/she can reproduce a certain photo characteristic that they may really like.  Once again EXIFtool and several other software vendors have figured out how to read/write to the metadata without destroying it.

Similar Messages

  • GPS EXIF data corrupted for photos taken in portrait orientation

    With photos taken in portrait orientation, the GPS data is corrupted for the photos in the modified folder, specifically, the longitude is changed from -83.435516 to 83.435516. Doesn't happen with all photos taken in portrait orientation, and I haven't seen it with any photos taken in landscape orientation and modified. I understand that iPhoto rotates portrait photos and places them in the modified folder when importing. When I look at the originals with Preview, their GPS data is OK, but the photos in the modified folder have incorrect information. Looking at the GPS data from within iPhoto doesn't show a problem, but that's probably because it doesn't refresh the EXIF data.
    Anyway, is this happening to anyone else and is there a fix?
    I'm concerned because I've spent all this time geocoding these photos, and now I don't know which ones have the correct data, and which ones are messed up.

    Larry,
    I'll try that, just to be safe. I played with it some more and now I can't reproduce the problem even with auto-rotate on. So, maybe it was fixed with 7.1.4 and I'm still having problems because the photos were imported in a previous version. The release notes only say "addresses minor issues." Hard to tell what that's supposed to mean.
    Thanks!
    Karen
    Message was edited by: Karen P

  • 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.

  • 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.

  • 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.

  • Bridge CS6 overwrites EXIF data and changes image orientation.

    Hi,
    I seem to be having issue with Bridge CS6 overwriting or corrupting my image EXIF data.
    The situation is this, while in Bridge CS6, I open a folder with some images in it. There I select one image. Right-click on it and select File Info. In the XMP dialogue box I fill in the fields I need and save this file as a template. Then, I select the rest of the images, go to Tools and choose Replace Metadata. In the fly-out, select and click the template I've just created and this is where I have the issue. All the updated images now have the the same date and time. I NEVER had this happen in Bridge CS5. In Bridge CS5, while all the IPTC data was overwritten, the EXIF data was left alone. This does not seem to be the case in Bridge CS6 where both the IPTC and EXIF data now seem to be overwritten. If this is the case, need to ask why?
    Hope someone here can confirm and comment on this. Cheers.

    Then, I select the rest of the images, go to Tools and choose Replace Metadata.
    You have to choose 'Append Metadata'  this adds the template to the already existing data instead of overwriting the already existing data.
    And without knowing your needs or workflow, why don't you create a template (or some extra if you have specific difference you often use) with the most common and always used info (copyright etc) and add this to al your files.
    Then when in Bridge choose the metadata panel with IPTC core section in view.
    Select the files you want to alter and in the Metadata click on a field with the pencil icon (means you can add info to it) and fill in the fields you need the info in. If keywords needed switch to the keyword panel to add the wanted keywords to the selected files.
    Just another approach that might be more suitable and faster.

  • Wrong EXIF data for JPEGs in Bridge and PS

    Hello,
    My Nikon D300 files are not being properly read by Bridge and Photoshop. RAW files are fine. When I get file info for JPEGs, though, much of the EXIF data is corrupted. For instance, ISO Speed is shown as "51200" instead of 500, and Focal Length is shown as "2.0 mm" instead of 140mm, etc. This incorrect data shows up in Bridge (in the metadata panel and file info) as well as the file info dialog box in Photoshop.
    When I get the EXIF info in Preview.app, all the info is correct.
    Anyone know what might be going on?

    Update - this problem is not limited to my D300 files. I just realized that the JPGs from my Canon SD800IS point & shoot are also not being "seen" properly by the Adobe apps. The ISO value doesn't even show up in CS3 apps, but I can see that data in Preview.app.

  • Save keywords in exif data

    I am a new Mac user nearly completely reprogrammed from MS, but I have one issue that is keeping me from switching 100%.
    When I use Vista's image manager or Picasa, I can embed keywords(tags) right into the images (which are stored on a server), and that embedded keyword data is then available to all other users of the images. This to me seems fundamental to image management today (even Vista has it standard).
    Does someone have some method to get keywords into the exif data of the original file? I don't want to mess with exporting/copying etc.
    Apple? what's up with this? The keyword tool is fantastic, yet nearly useless to me...
    Thanks.

    mlwruble:
    Welcome to the Apple Discussions. On a one time or 30 day basis you can use the demo version of iView MediaPro to write the keyword, title and comments to the original file by following the instructions in first part of Tutorial #1. The demo is only good for 30 days so you can at least get your current files embedded.
    Happy Holidays
    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 created 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 and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • IPhoto exif data

    Does iphoto strip some of the exif data from photos? I'm currently using iPhoto as my photo management tool and I also use photoshop elements to do some editing. When I view the photo info in iPhoto, it seems like the data is pretty skimpy.
    Specifically, I'm looking for white balance data (right now). I'm taking a photography course and was testing different white balance settings... and those settings aren't showing up in my photo info. I REALLY don't want to have to buy another program like Aperture, especially considering I already have photoshop. If iPhoto has this info somewhere, can you help me find it?!?!
    Please help!! Thanks!
    Erin

    Erin:
    iPhoto doesn't strip the data it just doesn't read all of it. You can get all of the data read by using a 3rd party application likeEXIF Viewer. Just put the app in the Dock and drag a photo from iPhoto onto it. It will open and give you the following information:
    File name: 2008-06-12-Mateo graduates KB-137.JPG
    File size: 3060921 bytes (2816x2112, 4.1bpp, 6x)
    EXIF Summary: 1/60s f/2.8 5.8mm
    Camera-Specific Properties:
    Equipment Make: Canon
    Camera Model: Canon PowerShot SD700 IS
    Maximum Lens Aperture: f/2.8
    Sensing Method: One-Chip Color Area
    Lens Size: 5.80 - 23.20 mm
    Firmware Version: Firmware Version 1.01
    Owner Name: W. FRITTS
    Image-Specific Properties:
    Image Orientation: Top, Left-Hand
    Horizontal Resolution: 180 dpi
    Vertical Resolution: 180 dpi
    Image Created: 2008:06:12 13:07:51
    Exposure Time: 1/60 sec
    F-Number: f/2.8
    Lens Aperture: f/2.8
    Exposure Bias: 0 EV
    Flash: No Flash, Compulsory
    Focal Length: 5.80 mm
    Color Space Information: sRGB
    Image Width: 2816
    Image Height: 2112
    Rendering: Normal
    Exposure Mode: Auto
    Scene Capture Type: Standard
    Focus Type: Auto
    Metering Mode: Center-Weighted
    Sharpness: Normal
    Saturation: Unknown
    Contrast: Unknown
    Shooting Mode: Manual
    Image Size: Large
    Focus Mode: Single
    Drive Mode: Single
    Flash Mode: Off
    Compression Setting: Superfine
    Macro Mode: Normal
    Subject Distance: 0.540 m
    White Balance: Auto
    Exposure Compensation: 3
    Sensor ISO Speed: 224
    Image Number: 100-4933
    Other Properties:
    Resolution Unit: i
    Chrominance Comp Positioning: Centered
    Exif IFD Pointer: 196
    Compression Scheme: JPEG Compression (Thumbnail)
    Horizontal Resolution: 180 dpi
    Vertical Resolution: 180 dpi
    Resolution Unit: i
    Offset to JPEG SOI: 5108
    Bytes of JPEG Data: 6214
    Exif Version: 2.20
    Image Generated: 2008:06:12 13:07:51
    Image Digitized: 2008:06:12 13:07:51
    Meaning of Each Comp: Unknown
    Image Compression Mode: 5
    Shutter Speed: 1/60 sec
    Metering Mode: Center Weighted Average
    Focal Plane Horiz Resolution: 12515 dpi
    Focal Plane Vert Resolution: 12497 dpi
    Focal Plane Res Unit: i
    File Source: Digital Still Camera
    White Balance: Auto
    Digital Zoom Ratio: 1
    Base Zoom Resolution: 2816
    Zoomed Resolution: 2816
    Exposure Mode: Easy Shooting
    ISO Speed Rating: Unknown
    Digital Zoom: None
    Self-Timer Length: 0 sec
    Canon Tag1 Length: 92
    Flash Bias: 0.00 EV
    Sequence Number: 0
    Canon Tag4 Length: 68
    Image Type: IMG:PowerShot SD700 IS JPEG
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) 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 created an Automator workflow application (requires Tiger or later), 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 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
    Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

  • LR 6.0.1 EXIF-Data are buggy after export

    We export a Nikon D810-photo with Lightroom.
    Here you can see it: http://bilder.uchrin.de/test/DSC_1917.jpg
    With a simple batch in php - like this (array exif_read_data ( string $filename [, string $sections [, bool $arrays [, bool $thumbnail ]]] )) -
    we read out the EXIF data. here see the result: http://bilder.uchrin.de/test/simple.php
    Now you can see COMPUTED.Copyright, COMPUTED.Copyright.Photographer and COMPUTED.Copyright.Editor are corrupt.
    COMPUTED.Copyright: efan Uchrin, (C) by St
    COMPUTED.Copyright.Photographer: efan Uchrin
    COMPUTED.Copyright.Editor: (C) by St
    In LR 5.7.1 are the EXIF-data OK.
    Is there any help?

    Stefan,
    I examined the test file closely with Exiftool, and it shows all the metadata correctly.  I think the issue is another one: Lightroom CC: JPEG format tripping up other programs. Notice that many of the string-valued fields are corrupted, e.g. IFD0.ImageDescription, IFD0.Model, and IFD0.Make.  LR 6 writes JPEG metadata in a way that strictly conforms to the standards but is atypical of the common layout of metadata, tripping up other programs that aren't strictly conforming.
    Which version of PHP are you using? 
    The end of the thread I linked to contains a workaround, using the Run Any Command plugin and Exiftool.

  • EXIF data lost when edited and exported to Picasa web

    I use iPhoto 6. If a geotagged photo is scaled and exported to Picasa web, then the EXIF data are preserved and recognized by Picasa web. But if the same photo is edited (crop, contrast...) and then exported to Picasa web, then the EXIF data don't appear. I've tried the export operation manually and through the plugin, but it always happens the same. How to avoid this? Does it happen too with iPhoto 8? Thanks.

    Welcome to the Apple Discussions. Yes and no. With iPhoto 8 you can export with an option to include the keywords, titles and comments. But I don't know if geotags are included. Ask in the iPhoto 8 forum as I know geotags have been discussed there. Do a search in that forum for "geotags" or similar.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) 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 created an Automator workflow application (requires Tiger or later), 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 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
    Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

  • EXIF data questions

    I understand that EXIF data usually stores thumbnails  and that sometimes this data doesn't always update or get stored correctly.  Is there any way to add or correct this data when its missing?  If I ask PSE to update thumbnail does this get stored within each picture?
    Are the EXIF thumbnails that PSE 11 uses actually embedded in photo or as I suspect just uses a link to the catalog?  Since videos can also have EXIF data is it the same for video files?
    Thanks in advance

    The Old Fart wrote:
    I understand that EXIF data usually stores thumbnails  and that sometimes this data doesn't always update or get stored correctly.  Is there any way to add or correct this data when its missing?  If I ask PSE to update thumbnail does this get stored within each picture?
    Are the EXIF thumbnails that PSE 11 uses actually embedded in photo or as I suspect just uses a link to the catalog?  Since videos can also have EXIF data is it the same for video files?
    Thanks in advance
    Thumbnails are created by the organizer (that may take time with big raw files) and are stored ONLY in the catalog as you rightly think.
    If you are curious and have a look at a catalog folder (you can find the folder of your active catalog by using the menu Help/system info), you'll see a big file named 'thumb.5.cache'. Technically it's a sqlite database storing your thumbnails. If it is missing (or deleted) it is automatically rebuilt. That's good to know if you want to solve a problem of corruption with thumbnails. You can't have a look at what is inside, unfortunately, only the organizer can use the cache.

  • Seeing a photos exif data inside iPhoto

    Is there anyway to find and view the full realm of EXIF data of photos inside iPhoto? I want to be able to see the shutter speed, aperture, exposure value, etc. I know that I can see this in Photoshop but would like to be able to see it in iPhoto without opening the picture up in Photoshop. Can anyone help me here? Thanks.

    The only way would be to set up a 3rd party EXIF viewer as the editor of choice in iPhoto. Then you could double click on a photo and bring up it's EXIF data in the EXIF viewer. A good viewer is EXIF Viewer.
    Once you set up the viewer as the editor of choice you can reset the editor to iPhoto but still open the viewer by clicking on the photo and selecting "Open in external editor" from the contextual menu. That way you get the best of both worlds.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) 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 created an Automator workflow application (requires Tiger or later), 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 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
    Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

  • EXIF data - e.g., Flash Exposure Compensation - is it hidden someplace?

    I see in LR various pieces of EXIF data, but can't find FEC. Is it hidden someplace? Thanks.

    Rob, this looks very good! Would any possible bugs in the code be limited to problems in searching on or viewing metadata, or does it have the potential of corrupting the LR database itself? From my limited understanding of the internals of how LR works, it seems to me that plugins would not be able to damage the LR database. Thanks!

  • 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.

Maybe you are looking for

  • Nokia 3100/6610i Application Download "Unknown Error"

    Hi Folks, I am trying to download a 45 KB application on my Nokia 3100 and 6610i from server (Apache-JK2->Tomcat). Many times, i have found Unknown error in blank page during connecting to the server or installation of application. The JAD file setti

  • Can I prevent iMessage sending pictures as a costly text message?

    Hi, when I send a picture message to someone with an iPhone 4s who doesn't have wi fi on, the message goes as a text message. This is fine for normal text messages but pictures are expensive to send. Is there any way to set it so it sends normal text

  • Merge 2 librairie

    Merge 2 Itunes librairies I have 2 huge librairies. On on my iMac and another on a hard drive (1tb capacity). I want to merge the iMac librarie with the one on my hard drive. Thanks

  • Links from powerpoint document

    I created a document in powerpoint with links to different pages within in the same document. When I then convert this to a pdf file the links work fine when the document is being viewed in full screen mode, but if the document isn't being viewed in

  • SQL load with Oracle Wire Protocol

    Has anyone used this method? I'm not quite sure how to connect with it. The documentation seems to be a little lacking. Any advice would be greatly appreciated. I'd love not to load the Oracle client on all of our servers from now on.Thanks!