Bug handling XMP:DateTimeOriginal?

It appears that LR 3 doesn't correctly interpret the "Z" format of the XMP:DateTimeOriginal metadata field -- it interprets it as local time rather than UTC.
To illustrate, using Exiftool, I set XMP:DateTimeOriginal of a photo to "1957:12:23 20:14:38-08:00", and after import LR correctly displays it as "12/23/1957 8:14:38 PM" (my local time zone is UTC-8).   But if I set XMP:DateTimeOriginal to "1957:12:24 04:14:38Z", which the XMP standard says should be equivalent, LR shows it incorrectly as "12/24/1957 4:14:38 AM".
Is this a known bug?  I see in older posts that LR 1 had lots of issues with date handling and time zones but LR 2 seemed to have fixed them?  I have thousands of photos using the Z format, produced by Photoshop Elements 7 and 8.

Lightroom should provide an option for displaying the time zone as stored in the XMP:DateTimeOriginal field, to remove ambiguity when working with programs and processes that use that field as defined in Adobe's XMP specification.   For example, dates/times would display as 12/23/1957 8:14:38 PM -8:00.
Details:
After a little investigation, I see that LR ignores the time-zone indicator in the XMP:DateTimeOriginal field. For example, both of these DateTimeOriginal values:
1957:12:23 20:14:38-08:00
1957:12:23 20:14:38+00:00
display as "12/23/1957 8:14:38 PM".  As another example, when sorting by increasing capture time, given these two photos:
a) 1957:12:23 20:00:00-08:00
b) 1957:12:23 19:00:00-10:00
LR will show photo b before photo a, even though b was taken after a in absolute time.
This is consistent and workable for users who only care about local time (just as the legacy EXIF:DateTimeOriginal field, which doesn't store time zones, has been workable).
My initial confusion arose because, in most other programs and non-computer contexts, when a time is displayed without a time zone, it is meant to be interpreted as local time relative to where the person is located.  But that is not the case with LR -- when it shows the date/time stored in XMP:DateTimeOriginal, it silently drops the time zone, and the user can't assume that it is in local time.
It would be better for LR to provide an option for displaying the time zone stored in the XMP:DateTimeOriginal field.  That would remove ambiguity for those who are integrating with other processes and programs that do pay attention to the absolute time a photo was taken and thus need to look at the time zone indicator.   Here's a use case illustrating the ambiguity:
1. I set my camera clock to California time (-08:00).
2. I travel to London, neglect to change my camera's clock, and take a pic at noon, London time, on 1/30/2010.  The pic's EXIF:DateTimeOriginal is set to 2010:01:30 04:00.
3. I import the pic into LR and see that it displays as 1/30/2010 4:00 AM.  
4. I do Save Metadata, and see that XMP:DateTimeOriginal is set to 2010:01:30 04:00:00-08:00.
5. I use the Edit Capture Time > Shift By Set Number Of Hours (Time Zone Adjust) command to add an offset of +8 to the pic, which now shows in LR as 1/30/2010 12:00 PM. 
6. I export the pic and send it off to a colleague in London. 
7. The colleague's processes in London sees the XMP:DateTimeOriginal field as 2010:01:30 12:00:00-08:00 and incorrectly thinks the picture was taken at 12:00 California time (20:00 London time). 
Adobe's XMP standard provides programs with the mechanism for avoiding ambiguity in times due to time zones, so it's unfortunate that LR doesn't take advantage of it.

Similar Messages

  • Adobe Preflight 9.2 bug in XMP by pdf/a-1b validation ?

    Hello,
    I am trying to validate my pdf/a-1b document conformance using Adobe Professional 9.2  Preflight function and becoming and error in XMP complaining that "http://purl.org/dc/elements/1.1/dc:date" property is not defined and no extension schema for this property found.
    Can you please confirm or deny this  Preflight bug ?
    Best Regard,
    Virginijus Kandrotas

    Hi,
    I don't have any problems by resolving this URL, tested on different browsers and PC's. This is a plain copy from it "http://www.kandrotas.com/wp-content/uploads/2010/06/pdfa-demo.pdf", What error are you getting ?
    regards,
    Virginijus Kandrotas

  • Bug handling Exchange password changes

    My colleagues and I believe we have uncovered a bug with the way iOS 5 handles situations when a user's Exchange password has changed. The iPhone or iPad appears to hit the Exchange server repeatedly with the incorrect password. In my company's environment, this causes the Exchange account to be locked out, as we have a policy in our Active Directory locking the account after a number of bad password attempts.
    We had an unrelated incident yesterday that required us to issue new passwords to a number of users. Many of them are now having trouble getting back on Windows PCs and Exchange email because they are iPhone or iPad users and this bug is locking out their accounts.

    We have a simular problem, only the account is not locked out (Normaly after 3 tries the user is locked out) and users can still access their e-mail with a wrong password. Sometimes even after 4 days the iphone prompts that the password needs to be changed, but untill that time you can still send and receive e-mail.

  • LR3 Bug when JPEG EXIF DateTimeOriginal ends in 00 Seconds?

    I am observing a strange behavior when working with JPG files where the EXIF DateTimeOriginal and the CreateDate fields have a date / time where the seconds part of the time is 0 seconds.
    The library filter shows these pictures under "unknown" date instead of the correct year like with other pictures where everything is the same except they are taken a few seconds later so the time is e.g. 10:13:22 instead of 10:13:00
    I am seeing this with 180 pictures out of 18.000 so it looks like not all pictures with this attribute have the problem however all pictures that appear in the library filter date column as "unknown" have a date/time with 00 seconds ...
    The metadata section on the right side in LR displays the date/time when the picture was taken correctly. It is just in the library filter that it is treated as "unknown"
    Is this a known bug?
    regards,
       Stefan

    Stefan,
    I recently converted from PSE 8 to LR 3 and encountered the same issue, with about 150 photos out of 20K showing up in the LR Library Filter with date "unknown".  Thanks for identifying the problem.
    I'm the author of "psedbtool", so I tracked down more details on the problem:
    1. LR 3 is buggy -- Library Filter Date does not recognize XMP:DateTimeOriginal values that are missing seconds, even though Adobe's XMP spec specifically allows that form:
    http://www.adobe.com/devnet/xmp/pdfs/XMPSpecificationPart2.pdfhttp://www.adobe.com/devnet/xmp/pdfs/xmp_specification.pdf
    Date
    A date-time value which is represented using a subset of ISO RFC 8601 formatting, as described in http://www.w3.org/TR/NOTE-datetime. The following formats are supported:
    YYYY-MM-DDThh:mmTZD
    Note that when examining metadata fields, one must always be careful to figure out whether you're looking at the EXIF fields or the XMP fields.  For example, if a file has XMP metadata, than LR will show fields taken from the XMP metadata, but the Metadata panel will call it "EXIF" (this confusion has its roots in the multiple, ambiguous meanings of the term "EXIF" in the standards).
    The EXIF:DateTimeOriginal field does indeed require seconds and does not allow time zones, while the XMP:DateTimeOriginal lets seconds and a time zone be optional.
    Note that the LR command Metadata > Edit Capture Time also doesn't recognize date/times that are missing seconds.
    2. PSE 8 (and probably earlier versions) sometimes omitted seconds from XMP:DateTimeOriginal when it wrote metadata.  I haven't figured out under which conditions it does that (and I certainly don't plan on spending any more time on PSE 8!).  Technically, this isn't a bug, since it conforms to the standards, thought it could fairly be called a minor inconsistency, since in almost all cases it includes seconds.
    3. The version of Exiftool included in the most recent version of psedbtool (7.89) had a bug -- it always added ":00" to the end of XMP date/time values if they were missing seconds.   This prevented psedbtool from ensuring that XMP:DateTimeOriginal always had seconds, as was the intention.  This appears to be fixed in Exiftool 8.24 (but I doubt that I will update psedbtool with that version).

  • Bugs I've Encountered In PSE 7

    Here are all the reproducible bugs I’ve encountered in PSE 7.  Problems added since my last posting are marked [N].  In the coming weeks, I’ll evaluate PSE 8 to see how many of these have been fixed.
    I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer.  Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer.   Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    File Management and Tagging
    Major Problems
    [N] The conversion of a catalog from PSE 6 to PSE 7 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup).  As a result, it isn’t possible to save photos in version sets, and PSE 7 will create duplicate thumbnails in the Organizer for an edited file.
    File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
    Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
    When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 7 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
    After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate.  The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
    The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    I’m very disappointed that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number.  While most people will never encounter this, when it strikes someone, its symptoms are very mysterious.
    The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files.  This bug and the previous one with Reconnect have the same underlying cause – the Organizer doesn’t update drive letters in its catalog.
    Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
    The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
    Minor Problems
    In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
    You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
    Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
    Integration with Photoshop.com
    Major problems
    [N] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
    For photos taken in years prior to 1970, the date/time shows as 12/31/1969 08:00 AM.  For photos with year taken 1970 or later, the date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
    [N] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
    Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
    Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
    If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
    Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
    When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
    Map View
    Major Problems
    Map view is unusably slow with more than about 6-8,000 mapped photos.
    When I tested PSE 7 by importing 12,000 photos (the size of my catalog) that had GPS locations, the red push-pins didn’t blink uncontrollably as they did in PSE 6.   But the Organizer crashed a number of times when I tried to zoom and pan the Map view until I was able to scroll the map to another country and then back again.   The CPU continued to consume 80% of a single CPU (40% of two), even 10 minutes after I closed Map view. When I selected Limit Search to Map Area, PSE took over a minute to respond.
    It takes 5 seconds to assign a keyword tag to a photo if there are 1,000 or more photos with map locations.
    In PSE 7, it takes 3 seconds with 1,000 photos, 12 seconds with 8,000 photos, and 18 seconds with 12,000 photos.
    Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
    Giving a map location to a tag assigned to 2000 photos makes assigning any keyword tag to a photo very slow (see above).    Searching on keyword tags takes 15 seconds, and a Show All takes 15 seconds.
    Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
    The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
    Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
    If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
    Scrolling the map or restarting the Organizer causes the pin to appear.
    Color Management
    Major Problems
    The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
    Metadata
    Major Problems
    When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007.
    Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
    In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
    If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
    The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
    New dates set by Edit > Adjust Date and Time sometimes get silently lost.
    See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
    [N] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
    File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
    File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
    [N] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
    Minor Problems
    [N] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
    The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
    Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
    When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
    With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
    Searching
    Major Problems
    The timeline doesn’t correctly display date ranges spanning many years.
    Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
    The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6 or 7.  Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”.   But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want.
    Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time, and it takes a couple of minutes on a large catalog, making the command almost useless; and it shows a scary message “Deleting Keyword Tags”.
    [N] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
    Find > By Details > Rating Is Lower Than 1 Star does work.
    Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
    Searching with date ranges doesn’t properly handle time “unknown”.
    Minor Problems
    The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
    Setting a date range and then excluding two tags from the search clears the date range.
    Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
    Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
    When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
    User Interface
    Major Problems
    On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
    This bug occurred with higher-resolution displays in PSE 6.
    The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
    There is a workaround for both PSE 6 and 7. Set the option > Edit > Preferences > General > Use System Font.  The result isn’t that pretty, since some of the application text will be large and some will be small, but it’s functional, and you’ll still be able to use the higher DPI with all your other applications.
    Minor Problems
    In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
    In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory.  (The command reports the correct amount in the Editor.)
    The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
    Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
    Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
    Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
    In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
    Dialogs in the Editor sometimes bounce back when you try to move them.
    Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
    In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
    Escape doesn’t close the full-screen-mode Properties dialog.
    You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
    The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
    Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
    The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
    Slide Shows
    Major Problems
    The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
    For video clips, PSE 7 doesn’t enable the command to change the duration as it does for photos. But you can work around this by using Add Media > Photos And Videos From Folder to add the clip to the show.
    An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
    Editor
    Minor Problems
    [N] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
    The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
    For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.

    Just kidding.    But, are you going to give us a bug comparison between 7 and 8 ?   I will probably sit version 8 out and get 9 next year.  Thanks for the list!
    Juergen

  • Bugs Ive Encountered In PSE 7

    Here are all the reproducible bugs Ive encountered in PSE 7. Problems added since my last posting on 10/5/08 are marked [N]. Because of limitations of the forum, this list is split across several messages.
    Ive reported all of these problems to Adobe. Almost all of them are in the Organizer. Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer. Perhaps thats because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange Vista laptop with a dual-core 1.8 GHz processor, 3 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    File Management and Tagging
    Major Problems
    [N] File > Backup/Restore Catalog doesnt backup and restore audio in slide shows.
    [N] Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
    [N] When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when youve previously used File > Restore Catalog with New Location, PSE 7 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isnt enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
    [N] After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate. The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
    The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    ]Im very disappointed that Adobe didnt add the three lines of code that would have issued a warning when it discovered two drives with the same number. While most people will never encounter this, when it strikes someone, its symptoms are very mysterious.
    The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    ]This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files. This bug and the previous one with Reconnect have the same underlying cause the Organizer doesnt update drive letters in its catalog.
    Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    ]Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they havent been easy to reproduce.
    The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named houses, and a folder containing photos in the catalog is named houses photos, files in the restored catalog will have the path houses\ photos\ instead of houses photos\.

    <i>Part III</i><br /><br /><b>Color Management</b><br /><br /><i>Major Problems</i><br /><br />The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.<br /><br />The Original (left) image in the Save For Web window is displayed without using the photos profile, making it hard to compare the preview with the original.<br /><br /><b>Metadata</b><br /><br /><i>Major Problems</i><br /><br />[N] When setting the Organizers date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesnt properly handle US Daylight Savings Time in years prior to 2007.<br /><br />[N] Edit > Adjust Date and Time doesnt properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.<br /><br />[N] In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.<br /><br />[N] If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.<br /><br />[N] The File > Write Keyword Tag command doesnt create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).<br /><br />New dates set by Edit > Adjust Date and Time sometimes get silently lost. <br /><br />]If you set the date/time for a BMP, PDF, or Quicktime movie, or a file thats marked readonly, invoking the full Editor or Edit > Update Thumbnail will discard the adjusted date/time. <br /><br />Edit > Adjust Date and Time sometimes sets the wrong date/time for the EXIF:CreateDate and DateTimeOriginal, causing other tools to show the wrong date/time.<br /><br />File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).<br /><br />File > Write Keyword Tags doesnt write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.<br /><br /><i>Minor Problems</i><br /><br />[N] The Properties  Metadata window shows the wrong value for Date Time Original when the day is unknown.<br /><br />Edit > Adjust Date and Time applied to a file with time unknown decrements the date by one day.<br /><br />When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.<br /><br />With the Import EXIF Caption option turned off, captions pre-existing in a files EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.<br /><br /><b>Searching</b><br /><br /><i>Major Problems</i><br /><br />The timeline doesnt correctly display date ranges spanning many years. <br /><br />Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category. <br /><br />]The User Guide gives two examples of how to use category exclusion that just dont work in PSE 6 or 7.  Interestingly, you can almost work around this by doing a text search of not <category tag>, e.g. not People.   But this will also exclude photos that happen to have the word people in their filenames, captions, or notes, probably not what you want.<br /><br />Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time, and it takes a couple of minutes on a large catalog, making the command almost useless; and it shows a scary message Deleting Keyword Tags. <br /><br />Searching for 0 stars only doesnt work for photos in a catalog converted from PSE 5.<br /><br />Searching with date ranges doesnt properly handle time unknown. <br /><br /><i>Minor Problems</i><br /><br />[N] The Show All button sometimes doesnt appear if you quickly type a query into the Search text box and hit Enter.<br /><br />Setting a date range and then excluding two tags from the search clears the date range. <br /><br />Show All doesnt clear a date range set by Find > Set Date Range (can be very confusing). <br /><br />Save Search Criteria As Smart Album isnt available if a date range has been set but no other search criteria have been. <br /><br />When searching, you can exclude a keyword tag and then include an album, but you cant do it in the other order.

  • Umlaut bug in iTunes 5 (Entering song info)

    There seems to be a bug handling Umlauts in iTunes 5.0:
    You cannot enter one as a first or second letter when entering artist or composer info. E.g.: Ü is automatically converted to U. So to enter "Jürgen" you'd have to enter Juürgen, then delete the u. I haven't tested this exhaustively but I imagine this also applies to other non-standard characters. Any similar experiences?

    Dear Michael,
    what exactly are you trying to say? That all discussion should be in English? That German problems should not be discussed in English? My original post was in English since I wanted to know if people with other "funny characters", like the scandinavian ae might have the same problem. Sorry for not speaking Danish or Swedish. I do hope that Apple programmers scan these forums for user feedback so they might want to read the post, too. Are you offended now by the German insider discussion about Ü? FYI, now that we seem to have analyzed the problem I posted a message to OS-X feedback (in English). So, really. What is your problem?

  • New option: "Export XMP when idle"

    like many, for performance reason i do not have "Automatically write changes into XMP" checked. yet i am a firm believer that the changes *belong* in the files themselves (for portability), so i must constantly do manual XMP exports when im finished w/ a set.
    in my book, "dumb" (not image-specific) manual steps are, well, dumb, and should be removed for an ideal workflow.
    therefore, i think it would be cool if LR handled XMP-to-file in a slightly different way -- a new checkbox for:
    "Export XMP metadata to files when idle"
    ...so whenever you leave LR open and you arent doing anything w/ it, it will auto-export all not-yet-embedded XMP changes to the files. this gives you portability, and piece of mind at no manual cost.
    just my thought.
    matt

    > Select only the images you want to write the metadata and/or settings
    > to!
    that is an added manual step. as i said, dumb (generic) manual steps that dont relate to the images in question are to be avoided.

  • XMP and IPTC mapping

    Is there a document that identifies which fields in Photoshop and Illustrator "file info" map to the corresponding IPTC field and XMP field repectivly. Also, if I enter a value in a field that is represented in both standards will both fields be populated in the image file?
    Regards
    Chris

    The 'File Info' in Photoshop since version 3.0 is stored in numerous places in a given file for various formats.
    On the Macintosh, some information is stored in the resource fork for any file format:
    The keywords are stored in a 'KeyW' resource and the caption is stored in a 'TEXT' resource. These resources are referenced by the 'pnot' resource. This information is readable by Aldus Fetch (now Extensis Portfolio). For more information on the format of these resources see:
    Inside Machintosh: QuickTime Components
    Aldus Fetch Awareness Developer's Toolkit
    All of the data from File Info is stored in an 'ANPA 1000' resource. The data in this resource is stored as an IPTC-IIM version 2, record 2. For more information on the format of this resource see:
    "Information Interchange Model (IIM) version 4"
    Available online at:
    Telephone: +44 1753 705051
    Facsimile: +44 1753 831541
    E-mail: David Allen, Managing Director
    Post: IPTC
    Royal Albert House
    Sheet Street
    Windsor
    Berkshire
    SL4 1BE
    UK
    On all platforms, the IIM is also stored in the data fork of the file. For file formats that can support Photoshop's image resources the data is stored as an image resource '1028' (kCaptionID) in IPTC-IIM record 2 format.
    For TIFF files the caption data is stored in an image description tag '270' and all the information is stored as an IPTC-NAA record 2 in tag '33723' the tag number was chosen by inspecting files written by Iron Mike software, and is supposed to be defined in a Rich TIFF specification that I haven't been able to track down. The tag is also specified in:
    NSK TIFF
    The Japan Newspaper Publishers & Editors Association
    Nippon Press Center Building
    2-2-1 Uchlsaiwai-cho
    Chiyoda-ku, Tokyo 100
    For more information about the TIFF format see:
    "TIFF Revision 6.0"
    Available online at:
    In reading the files, the following order is used with information read
    lower on the list replacing information read higher:
    * kCaptionID image resource
    * For old Photoshop files, the caption data is read from the image resource '1008' (kOldCaptionID) or '1020' (kPrintCaptionID) (it cannot appear in both). Old PrintCaption data could coinside with caption data in some beta releases in this case the print caption data is ignored.
    [NOTE version 3.0 and 3.0.1: Print caption was appended to the caption
    information but this caused duplicate captions in TIFF files. This bug was fixed for version 3.0.2]
    * Image Description Tag (TIFF only)
    * IPTC-NAA Tag (TIFF only)
    [NOTE version 3.0 and 3.0.1: TIFF data did not override the previous image resources. This bug was fixed for version 3.0.2.]
    * 'pnot' resource related data (keywords and caption) (Mac only)
    * 'ANPA' resource (Mac only)
    [Additions for Photoshop 7.0]
    * XMP Data - The kCaptionID image resource is written out with a digest
    signature. The digest is re-generated from the above information when
    a file is opened. If the digest doesn't match then the XMP information
    for properties that that are contained by the kCaptionID resource
    (IIM records, photoshop:WebStatement, and photoshop:Marked) are
    dropped from the XMP Data. Otherwise, the XMP Data takes precedence over all previous data.
    NOTE: The TIFF information comes prior to the image resource information on this list. This means that an edit to the TIFF info will not be recognized unless the image resource information is removed.
    Photoshop Schema
    The namespace prefix is ÒphotoshopÓ. The namespace is http://ns.adobe.com/photoshop/1.0/.
    Property Type IIM Record Alias Category
    photoshop:Caption Text 2:120 Caption/Abstract dc:description/*[@xml:lang='x-default'] External
    photoshop:Author ProperName 2:80 By-line dc:creator/*[1] External
    photoshop:Title Text 2:05 Object Name dc:title/*[@xml:lang='x-default'] External
    photoshop:Keywords bag Text 2:25 Keywords dc:subject External
    photoshop:WebStatement URL xapRights:WebStatement External
    photoshop:Copyright Text 2:116 Copyright Notice dc:rights/*[@xml:lang='x-default'] External
    photoshop:CaptionWriter ProperName 2:122 Writer/Editor External
    photoshop:Headline Text 2:105 Headline External
    photoshop:Instructions Text 2:40 Special Instructions External
    photoshop:AuthorsPosition Text 2:85 By-line Title External
    photoshop:Credit Text 2:110 Credit External
    photoshop:Source Text 2:115 Source External
    photoshop:DateCreated Date 2:55 Date Created (1) External
    photoshop:City Text 2:90 City External
    photoshop:State Text 2:95 Province/State External
    photoshop:Country Text 2:101 Country/Primary Location Name External
    photoshop:TransmissionReference Text 2:103 Original Transmission Reference External
    photoshop:Category Text 2:15 Category (2) External
    photoshop:Marked Boolean xapRights:Marked External
    photoshop:SupplementalCategories bag Text 2:20 Supplemental Category External
    photoshop:Urgency Integer 2:10 Urgency (3) External
    photoshop:JobName (4) Text xapBJ:JobRef/*[1] External
    xapMM:ManageTo (5) URL Relational
    xapMM:Manager (5, 6) AgentName Relational
    xapMM:DocumentID (7) URI Internal
    (1) Explicitly not aliased to the internal creation date which denotes the document creation. This field is intended to follow the IIM conventions:
    Designates the date the intellectual content of the document was created rather than the date of the creation of the physical representation. Thus a photo taken during the American Civil War would carry a creation date during that epoch (1861-1865) rather than the date the photo was digitized for archiving.
    (2) This field is limited to three 7 bit ASCII characters only.
    (3) Valid range is 1-8.
    (4) Not aliased in Photoshop 7.0 due to bug in XMP.
    (5) If xapMM:Manager is not "AdobeARM" and the ARM is not managing this
    document then these properties are preserved.
    (6) Set to "AdobeARM" for managed files.
    (7) DocumentID will be set if it was previously blank and once set it is especially "sticky" and won't be lost even if other metadata takes
    precedent and can not be set by loading XMP data from File Info although plug-ins are able to set, but not clear, this property.

  • BIS GMail Bug!

    Like many people I had a problem (recent) adding my gmail account to my Blackberry.
    When setting it up on the BB the error message pop-up was "Update Failed" after entering my username and password.
    When trying to set it up via the Digicel BIS I got an invalid username/password error.
    I tried the CAPTCHA workaround, to no avail.
    I tried disabling Advanced IMAP in my GMail account, still no progress.
    I tried adding a different GMail account that I used to administer a club website and that worked flawlessly!
    So, something specific about my own GMail account.
    After much trial and error I tried entering my GMail account without the "." that separates my first and last name.  And voila!  It lets me in.
    However there are still issues.  It won't find my Google Calendar since that seems to insist on identifying itself with the "." in the email address, and likewise it can't sync my Contacts.
    So there is clearly a BIS/GMAIL bug handling a "." in an email address (before the @gmail.com of course!)
    So who do we yell at to get that fixed?  It's a stupid bug that was introduced recently as I had previously used my GMail account (period and all) on the same Blackberry and it worked fine.

    Hello,
    mikeszeller wrote:
    So who do we yell at to get that fixed? 
    Since your post basically boils down to this question, here's the answer. All formal support for BB's is provided by the carriers and authorized resellers. Therefore, that would be the proper channel for pursuing your chosen course of action (though I can only wonder how they will take to getting yelled at).
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • PSE 7 Problems Fixed in PSE 8

    Since PSE 6 was released, I’ve tracked all the reproducible bugs I’ve encountered and reported to Adobe.  I’ve tested these problems in PSE 8 and listed the results below – problems that appear to have been fixed in PSE 8 are marked [F], and problems that remain unfixed are marked [U].
    Overview
    There’s good and bad news. Adobe has fixed a number of serious bugs in the Organizer, but it has left most unfixed, even though they’ve been present since at least version 6.  Even worse, the two major features introduced in the PSE 8 Organizer, face tagging and the keyword-tags text box, have show-stopper problems. And even worse yet, Full Screen view is now painfully slow with large catalogs.
    The most important fixes address serious problems with PSE’s handling of drives that were introduced in version 6. PSE now notices when a drive’s letter has changed, a problem that has bedeviled many users upgrading or rearranging their drives. Also, PSE now ignores the case of UNC pathnames (network drives), no longer creating duplicate volumes for the same network drive.  Unfortunately, one serious bug remains: PSE still gets horribly confused when there are two drives with the same volume serial number, and it still doesn’t even issue a warning.
    But many long-standing problem areas remain: The Map View is an unusable toy.  The handling of metadata is riddled with bugs.  Folder Location view shows the wrong contents of folders. Searching has numerous bugs making it clumsy and confusing.
    Overall, of all the bugs I’ve reported, PSE 8 fixes 8 of 46 major ones and 8 of 28 minor ones:
    Major
    Minor
    Fixed
    Unfixed
    Fixed
    Unfixed
    File Management and Tagging
    4
    6
    2
    Integration with Photoshop.com
    2
    5
    Map View
    6
    Color Management
    1
    Metadata
    10
    2
    3
    Searching
    8
    5
    User Interface
    1
    1
    5
    9
    Slide Shows
    1
    1
    Editor
    1
    1
    Total
    8
    38
    8
    20
    I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer.  Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer.   Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    New Problems in PSE 8
    [U] PSE 8 crashes or gets intolerably slow after using the new Keyword Tags text box a small number of times.
    On my 4 GB Vista 32 system, PSE crashes after tagging 41 photos.
    [U] If you use the new Keyword Tags text box to apply an existing tag name with a comma in it, PSE will silently create two new tags instead.
    Apply the existing tag “San Francisco, CA” will create two new tags, “San Francisco” and “CA”.
    [U] After applying a tag, the Keyword Tags text box loses keyboard focus and you need to mouse-click in the box again to enter another tag.
    Forcing the use of the mouse defeats the purpose of the Keyword Tags text box, which is to make tagging much faster.
    [U] The Find > Find People For Tagging command locks up the Organizer for about 30 seconds after you click Done (even if you haven’t made any changes), when using larger catalogs.
    On a catalog with 10,000 thumbnails showing, the cursor spins for 30 seconds after clicking done.  But you can work around this by doing a tag search or setting a date range to have only a small number of thumbnails showing before you invoke the command.
    [U] In the Find > Find People For Tagging command, when you select Add Missing Person, you usually can’t resize the selection box by grabbing the lower-right or lower-center handles, which are the handles that most right-handed people are likely to use.
    If you move the mouse very quickly so that it is over the photo before the selection box appears, you can usually resize the box with those handles.  But you have to be very quick.
    [U] The Find > Find People For Tagging command doesn’t do auto-complete on pre-existing People tags, making it very hard to use with existing catalogs.
    I have over two hundred People tags in my catalog.  Because the command doesn’t auto-complete on pre-exisiting People tags and will silently create new tags, and because I don’t remember exact spellings (that’s the point of auto-complete!), I found myself creating duplicate tags (e.g. “John Ellis” instead of “John R. Ellis”, “Bob Smith” instead of “Robert Smith”).  It’s painful to clean up such a mess.
    [U] Full Screen view (F11) is much slower than in PSE 7 on larger catalogs.
    With a 14,000-file catalog and all thumbnails visible, PSE 7 takes 6 seconds to invoke F11, while PSE 8 takes 13 seconds.   With just 20 thumbnails visible (e.g. when working on the most recent import batch), PSE 7 takes 1 second, while PSE 8 takes 7 seconds. This makes selecting the good and weeding out the bad significantly slower.
    [U] PSE doesn’t remember the settings if you toggle the Full-Screen Quick Edit Panel and Quick Organize Panel to disappear completely.
    On 4:3 displays, it’s desirable to hide the panels completely in full-screen view, so you see the entire image without the panels overlapping them (that’s the point of full-screen view, no?).  But PSE forgets the toggle settings, even in the same session.
    [U] The keyword tagging in the Quick Organize Panel doesn’t auto-complete tags you type, making it useless with more than a dozen or so tags.
    It’s worse than useless, since it will silently create a new tag if you mistype the name of an existing one.  And the “tag cloud” is a silly toy that doesn’t help with hundreds of tags.
    File Management and Tagging
    Major Problems
    [F] After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate.  The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
    [F] The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    [F] If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files.  This bug and the previous one with Reconnect had the same underlying cause – the Organizer didn’t update drive letters in its catalog.  Fixed in PSE 8.
    [F] The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
    [U] Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
    [U] The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    I remain mystified that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number.  While most people will never encounter this, when it strikes someone, its symptoms are very mysterious (and a lot of people using cloning utilities).
    [U] The conversion of a catalog from PSE 6 to PSE 8 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup).  As a result, it isn’t possible to save photos in version sets, and PSE 8 will create duplicate thumbnails in the Organizer for an edited file.
    [U] File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
    [U] Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
    [U] When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 8 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
    Minor Problems
    [U] In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
    You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
    [U] Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
    Integration with Photoshop.com
    Major problems
    [F] Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
    [F] If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
    [U] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
    The date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
    [U] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
    [U] Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
    [U] Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
    [U] When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
    Map View
    Major Problems
    [U] It takes 4 seconds to assign a keyword tag to a photo if there are 2,000 or more photos with map locations.
    It takes 2 seconds with 1,000 photos, 6 seconds with 4000 photos, and 11 seconds with 8,000 photos, and 21 seconds with 12,000 photos.
    [U] Map view is unusably slow with more than 8 - 10,000 mapped photos.
    When I imported 12,000 photos (the size of my catalog) that had GPS locations, the Organizer crashed a number of times when I tried to zoom and pan the Map view.   When I selected Limit Search to Map Area, PSE took over a minute to respond.
    [U] Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
    Giving a map location to a tag assigned to 1700 photos makes assigning any keyword tag to a photo very slow, 12 seconds.    Searching on keyword tags and Show All each take 13 seconds.
    [U] Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
    The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
    [U] Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
    [U] If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
    Scrolling the map or restarting the Organizer causes the pin to appear.
    Color Management
    Major Problems
    [U] The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
    Metadata
    Major Problems
    [U] The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
    The PSE 8 Write Keyword Tag command now gives a warning when you try to invoke it on a D300 .NEF raw file. Why PSE can write sidecars for Canon but not Nikon raw files is a mystery – it’s no harder to handle one than the other.
    [U] File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
    [U] File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
    [U] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
    [U] New dates set by Edit > Adjust Date and Time sometimes get silently lost.
    See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
    [U] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
    [U] In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
    [U] If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
    [U] Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
    [U] When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007, e.g. October 31, 2006 12:00 PM.
    Minor Problems
    [F] The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
    [F] When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
    Now, the edited version picks up date/time, caption, notes, and keyword tags, but not the star rating, which could be charitably interpreted as a plausible design decision.
    [U] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
    [U] Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
    [U] With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
    Searching
    Major Problems
    [U] The timeline doesn’t correctly display date ranges spanning many years.
    [U] Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
    The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6, 7, or 8.  Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”.   But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want.  You can also use the text query “not tag:<category tag>”, .e.g. “not tag:places”, but this will exclude all tags containing “places” as part of their name – there is no way to get an exact match of a tag name.
    [U] Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time.
    When the results first display, they are now sorted by Imported From then (correctly) by Date/Time. However, if you click on the Date/Time column header to sort by that column, the dates are sorted alphabetically (incorrectly).
    [U] Find > By History > Imported On takes a couple of minutes on a large catalog, making the command almost useless.
    [U] Find > By History > Imported On shows a scary message “Deleting Keyword Tags” that is apparently harmless.
    [U] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
    Find > By Details > Rating Is Lower Than 1 Star does work.
    [U] Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
    [U] Searching with date ranges doesn’t properly handle time “unknown”.
    Minor Problems
    [U] The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
    [U] Setting a date range and then excluding two tags from the search clears the date range.
    [U] Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
    [U] Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
    [U] When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
    User Interface
    Major Problems
    [?] On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
    I can’t reproduce this in PSE 8.  The Editor’s Print dialog is all rearranged.  But this bug struck some people and not others, so it may be still lurking.
    [U] The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
    Adobe should be embarrassed about this, given that more and more computers are shipping preconfigured with higher DPIs.  See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#The_Organizers_Menu_Bar_ doesnt_show for a workaround.
    Minor Problems
    [F] Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
    [F] In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
    [F] The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
    Well, almost – you can grab the left, right, and bottom edges but not the top.
    [F] Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
    Both the Editor and Organizer don’t show the underline until you let up on the Alt key, whereas other Windows program show the underline when you first press the Alt key.
    [F] The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
    [U] In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
    [U] In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory.  (The command reports the correct amount in the Editor.)
    [U] The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
    [U] Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
    Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
    [U] Dialogs in the Editor sometimes bounce back when you try to move them.
    [U] Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
    [U] In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
    [U] Escape doesn’t close the full-screen-mode Properties dialog.
    [U] You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
    The Editor can now be tiled by Windows Explorer and other window managers, but the Organizer still can’t.
    Slide Shows
    Major Problems
    [F] The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
    PSE now sets the duration to the length of the clip.  You can’t edit the duration, though – you can invoke Edit Duration, but PSE ignores the new value.
    [U] An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
    For an individual slide, you can give the Use Existing Audio Caption command to import that photo’s existing audio caption.
    Editor
    Minor Problems
    [F] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
    [U] The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
    For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.

    John,
    Firstly, my apologies for the length of this post – it has been fermenting a while.  For those in a hurry I have split it into two sections – the first contains some general comments on the situation with PSE (v 7 in my case) and Adobe (as I see it) and the second contains a list of issues that I have encountered and some suggestions for improvement.  As with you, my comments are largely directed at the Organiser module within PSE.
    Part 1:
    Before going any further I’d like to say what an excellent job you’ve done in cataloguing, understanding and in many cases providing solutions to a number of bugs.  Adobe should be paying you a hefty sum for doing this work.  It’s a welcome change from a large percentage of what you read in blogs and forums to see things dealt with systematically, objectively and in an informed way.
    I’m less impressed with Adobe’s approach.  In my opinion, if you choose not to provide program updates to your customers (i.e. you get what you bought in the box and that’s it) then you have a moral obligation to make sure that what you sell is as robust and free of bugs as possible.
    I would be very surprised if they were not well aware of the comments you have made (if they aren’t then that would indicate an appalling failure of their ability to process feedback).  The fact that they have not, in subsequent releases, dealt with all of the issues that have been highlighted is not good.  I would go further and suggest that it is actually a breach of fair trading practice and disingenuous to sell the product as “fit for purpose” knowing these bugs are still in place.
    It’s unreasonable to expect software to be absolutely faultless, and this is why the issuing of updates is a much “fairer” system.  The problem, I think, with Adobe’s approach is that to entice new customers to each release they need to provide new features.  A natural consequence of this is that there is a temptation to prioritise development of new features rather than providing solutions to existing issues.  There is no incentive for Adobe to change this state of affairs for as long as customers are purchasing their products.  In this respect one of the problems is that many of the reviewers to whom prospective customers go will rely on first impressions and will not uncover many of the issues.  Adobe may be comfortable with this situation (and on relying on the reflected aura of Photoshop) but their product is not cheap and there is plenty of scope for competitors to provide a more robust, dependable product at cheaper price.  With free applications like Picasa they will need to be very careful they don’t drop the ball.
    Don’t get me wrong I think the concept of PSE organiser is excellent (I actually prefer it to my experience of Lightroom), it is the quality of execution that I have issues with.
    My first experience of PSE was version 3 and this was positive enough for me to purchase PSE 7.  However, my biggest disappointment with PSE 7, because to me it is fundamental, has been the quality of rendering images in full screen mode.  Yours is the first comment I have seen that comments on the appearance of “jaggies” when displaying images in PSE.  My understanding is that this relates to the anti-aliasing which is carried out when converting from image to display resolution and the level to which this smoothes out gradients in hue, saturation and luminance.  I never observed this problem is PSE 3.  Although the degree of anti-aliasing is a subjective preference, I was deeply disappointed and still find it hard to believe that free or bundled software (picture manager, windows picture viewer, etc) can manage this when PSE 7 can’t.
    Anyway, I’m not sure how to illicit a change from Adobe.  One way is to write the sort of rant I have above although I doubt this will make much difference.  In any case keep up the good work and hopefully something will come of it.
    Part 2:
    Some issues I’ve encountered:
    Migration from Windows XP to Windows 7 – change in directory structure means that the “documents and settings” part of the user directory path in XP (i.e. c:\documents and settings\<<username>>\etc.) is now a shortcut which redirects you to the new location for user files which is c:\users\<<username>> \etc.  If you are migrating from an old XP machine to a new Windows 7 one, you’ve kept your username the same and you have tried to retain the same directory structure then PSE 7 will still find files in your catalogue with the old style path.  However, it will not recognise duplicates if you accidentally re-import the same files now they are on your Windows 7 machine.  My workaround for this is to use an external file manager (e.g. windows explorer) to change the name of the directory that contains all of your photos.  This causes PSE 7 to fail to resolve the path locations.  You can then can select the relevant files and reconnect using the reconnect facility (File-Reconnect-Missing Files);
    Watched folders are lost for any drive other than C when PSE 7 is closed and then reopened;
    Duplicate files are not recognised and can be imported if they are not on the C drive (i.e. on an external drive);
    Selecting a category selects all of the keyword tags/subcategories beneath it but excluding it does not exclude all of the keyword tags/subcategories beneath it; however, both selecting and excluding a sub-category selects and excludes the tags/sub categories beneath it;
    Searches bring back the entire version set or stack even if only one of the files within meets the search criteria;
    The instant search facility will sometimes decide that a number typed in is a date and will not find some files you would expect it to e.g. those where the number typed in is part of the filename rather than a date;
    Anti-aliasing is insufficient – jaggies appear on jpegs displayed at certain zoom level.  Interestingly this does not seem to occur if a jpeg has been created from a raw file through PSE 7 rather than an external application (at least for the camera I have).
    Some suggestions:
    Find duplicates facility;
    Sort by filename and other file data;
    Hide directories in the folder directory pane of the folder view if they contain no imported files – in PSE3 this was the only option and was actually quite useful to confirm that there were no imported files in a certain location (e.g. if e:\...etc was not in the list then you knew that you had no imported files located on the e:\ drive).  It would be good to have this a display option.
    Allow filters to be applied only to selected files;
    Allow files to be rotated in the organiser without actually resaving them as a rotated file.

  • Date created in IPTC not in slide show

    Hi,
    Currently I am processing analoge pictures in Lightroom 3.6.
    When adding IPTC data to a slide show, I am able to add almost every item, except "Date created". That does not apear in the ABC list.
    Does somebody have a clue how to fix that?
    Thanks, Henk

    Let's tease apart the issues, because they're messy:
    The ABC "Date" field in the LR slideshow shows the capture time of the photo, as recorded in the LR catalog.
    When you first import a photo into a catalog, LR reads the catalog capture time from the fields EXIF:DateTimeOriginal, XMP:DateTimeOriginal, or XMP:DateCreated.  (According to the standard, it should also get it from IPTC:DateCreated, but it doesn't, which is a bug.)
    You change the catalog capture time using the Metadata > Edit Capture Time command.  Using this command will change the metadata fields EXIF:DateTimeOriginal, XMP:DateCreated, and IPTC:DateCreated.   Changing the IPTC Date Created field in LR's Metadata panel does not change the catalog capture time.
    So, if you have a lot of photos in your catalog with just the IPTC:DateCreated field set and not EXIF:DateTimeOriginal or XMP:DateCreated set, and you want the LR catalog capture time to be set to the value of IPTC:DateCreated so you can show the capture time in slideshows, you have a couple of options:
    - Use the Metadata > Edit Capture Time to change each photo individually.
    - Write all the metadata from the catalog back to the photos using Metadata > Save Metadata To File, then use the free Exiftool to copy IPTC:DateCreated to XMP:DateCreated.  (Exiftool has a fairly steep learning curve unless you're comfortable with command-line tools.)  Then reread all of the photos' metadata back into the catalog using Metadata > Read Metadata From File.  (I don't know of a plugin that will do this -- the Search Replace Transfer plugin can't do it.)

  • LR3: sorting by capture time

    Sorting by "Capture time" does not seem to work right in LR3.4.1. In Grid view, with compact cells, top label: capture date/time, and using Sort: Capture time, I see pictures from 2009, then 1900, 1910, 2010. The files are .jpg and .psd - no movies. Metadata -> Edit capture time... also shows the correct date/time. It's just the sorting that does not get things in the right order. Most of the files are imported from PSE6, which sorted correctly. For some JPGs, LR3 seems to show the windows file creation date (as can be seen in the Windows file properties), not anything in the metadata. For the PSD files, the correct date I want to sort by (the one PSE6 showed) is shown as Exif metadata "date time original" and "date time digitized".
    This makes me wonder what date is actually used by LR3 for sorting by capture date?
    Any suggestions for getting LR3 to sort the way I want?
    Tia,
    Alex

    Interesting -- I was able to confirm the same thing.  It appears that if an image is missing metadata date/time fields, then LR uses the file date-modified for filtering and sorting, and it uses file date-created to display in the grid view.  Seems like a blantant bug to me -- you could report it at the new feedback site, http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om, where Adobe employees reguarly participate.  Adobe may not make this a priority to fix, since their priority is LR's focus on images taken with digital cameras (which always attach a date to the metadata), and those of us using LR to manage non-digital-camera images get lower priority.
    So there are two problems:
    1. You have images with metadata fields XMP:DateTimeOriginal that omit seconds, and when these were imported by a LR version earlier than 3.4, they produced corrupted catalog capture-date entries. You could try doing Metadata > Save Metadata To File followed by Read Metadata To File for these images -- that may clear the corrupted catalog dates and be a little bit easier than removing the images and reimporting them (which would lose your stacking and collections).
    2.  As described above, LR uses file date-created and date-modified inconsistently for images without metadata date/times.  A workaround is to make sure all your images have the field EXIF:DateTimeOriginal in their metadata.  You could do that one photo at a time using the Medata > Edit Capture command.  Alternatively, you could use Exiftool to copy the file date-modified or file date-created into the EXIF:DateTimeOriginal field for just those images that don't already have that field.  That will take some study of Exiftool documentation to come up with the precise command line -- it's a powerful tool but not easy to use at first.
    You'll have to figure out whether the file date-modified or the date-created is the best date to use for your images.  Beware that on Windows, date-modified is generally preserved when a file is copied, whereas date-created is not, and some backup programs won't properly preserve date-created.

  • 3.4RC not exporting Exif data in jpegs?

    I just checked and there seems to be no Exif data in my exported jpegs, even though Minimize Metadata is not checked. Anybody else experiencing this? DId I miss some new setting or way of specifying this? Win 7 64-bit, 64-bit LR.

    In terms of the XMP standard, the EXIF schema properties have been omitted from the LR 3.4RC version of the image.  For example, the 3.3 version has the property XMP:DateTimeOriginal, while the 3.4RC version does not.  See below for all differences in the metadata.
    I think this may be a bug. The XMP standard was designed to encapsulate legacy metadata such as EXIF, and it was intended that the XMP metadata contain duplicates of the EXIF properties.  Unlike the EXIF standard, XMP allows multi-byte characters and time zones, so not exporting the XMP EXIF properties means that it won't be possible to export multi-byte characters and time zones.
    Differences in metadata:
    8d7
    < [Composite]     Date/Time Created               : 2011:04:09 13:03:22
    10d8
    < [Composite]     Digital Creation Date/Time      : 2011:04:09 13:03:22
    18c16
    < [Composite]     Thumbnail Image                 : (Binary data 12845 bytes, use -b option to extract)
    > [Composite]     Thumbnail Image                 : (Binary data 12854 bytes, use -b option to extract)
    22c20
    < [EXIF]          Copyright                       : ©2011 Eulogio Garcia / Dhananjaya
    > [EXIF]          Copyright                       : (C)2011 Eulogio Garcia / Dhananjaya
    26c24
    < [EXIF]          Exif Version                    : 0230
    > [EXIF]          Exif Version                    : 0221
    43c41
    < [EXIF]          Modify Date                     : 2011:04:25 20:34:48
    > [EXIF]          Modify Date                     : 2011:04:25 20:38:26
    50d47
    < [EXIF]          Software                        : Adobe Photoshop Lightroom 3.4
    53,54c50,51
    < [EXIF]          Thumbnail Length                : 12845
    < [EXIF]          Thumbnail Offset                : 870
    > [EXIF]          Thumbnail Length                : 12854
    > [EXIF]          Thumbnail Offset                : 828
    63c60
    < [File]          Current IPTC Digest             : f6e139c9a1abb4f443dbcad907844238
    > [File]          Current IPTC Digest             : c620bc8bc4f36f55110ec1c719189bf7
    67,68c64,65
    < [File]          File Modification Date/Time     : 2011:04:26 00:32:58-07:00
    < [File]          File Name                       : image_pjpeg.jpg
    > [File]          File Modification Date/Time     : 2011:04:26 00:33:13-07:00
    > [File]          File Name                       : image_pjpeg.good.jpg
    70c67
    < [File]          File Size                       : 143 kB
    > [File]          File Size                       : 144 kB
    102,103c99
    < [IPTC]          Application Record Version      : 4
    < [IPTC]          Coded Character Set             : UTF8
    > [IPTC]          Application Record Version      : 2
    106,108d101
    < [IPTC]          Digital Creation Date           : 2011:04:09
    < [IPTC]          Digital Creation Time           : 13:03:22
    < [IPTC]          Time Created                    : 13:03:22
    112,113c105,106
    < [Photoshop]     IPTC Digest                     : f6e139c9a1abb4f443dbcad907844238
    < [Photoshop]     Photoshop Thumbnail             : (Binary data 12845 bytes, use -b option to extract)
    > [Photoshop]     IPTC Digest                     : c620bc8bc4f36f55110ec1c719189bf7
    > [Photoshop]     Photoshop Thumbnail             : (Binary data 12854 bytes, use -b option to extract)
    116a110
    > [XMP]           Aperture Value                  : 16.0
    119a114
    > [XMP]           Camera Model Name               : Canon EOS-1Ds Mark III
    130c125,126
    < [XMP]           Creator Tool                    : Adobe Photoshop Lightroom 3.4
    > [XMP]           Creator Tool                    : Adobe Photoshop Lightroom 3.3
    > [XMP]           Custom Rendered                 : Normal
    131a128,129
    > [XMP]           Date/Time Digitized             : 2011:04:09 13:03:22.00-04:00
    > [XMP]           Date/Time Original              : 2011:04:09 13:03:22.00
    132a131,133
    > [XMP]           Exif Image Height               : 800
    > [XMP]           Exif Image Width                : 1200
    > [XMP]           Exif Version                    : 0221
    133a135,139
    > [XMP]           Exposure Compensation           : -1
    > [XMP]           Exposure Mode                   : Auto
    > [XMP]           Exposure Program                : Aperture-priority AE
    > [XMP]           Exposure Time                   : 2
    > [XMP]           F Number                        : 16.0
    136a143,151
    > [XMP]           Flash Fired                     : False
    > [XMP]           Flash Function                  : False
    > [XMP]           Flash Mode                      : Unknown
    > [XMP]           Flash Red Eye Mode              : False
    > [XMP]           Flash Return                    : No return detection
    > [XMP]           Focal Length                    : 21.0 mm
    > [XMP]           Focal Plane Resolution Unit     : inches
    > [XMP]           Focal Plane X Resolution        : 3957.71670190275
    > [XMP]           Focal Plane Y Resolution        : 3961.90476190476
    150a166,167
    > [XMP]           ISO                             : 100
    > [XMP]           Image Height                    : 800
    151a169
    > [XMP]           Image Width                     : 1200
    152a171
    > [XMP]           Legacy IPTC Digest              : C620BC8BC4F36F55110EC1C719189BF7
    167a187
    > [XMP]           Make                            : Canon
    169,170c189,192
    < [XMP]           Metadata Date                   : 2011:04:25 20:34:48-04:00
    < [XMP]           Modify Date                     : 2011:04:25 20:34:48-04:00
    > [XMP]           Max Aperture Value              : 2.8
    > [XMP]           Metadata Date                   : 2011:04:25 20:34:19.329+04:00
    > [XMP]           Metering Mode                   : Spot
    > [XMP]           Modify Date                     : 2011:04:25 20:38:26-04:00
    185a208
    > [XMP]           Resolution Unit                 : inches
    196a220
    > [XMP]           Scene Capture Type              : Standard
    203a228
    > [XMP]           Shutter Speed Value             : 2
    213c238
    < [XMP]           Version                         : 6.4
    > [XMP]           Version                         : 6.3
    217c242,245
    < [XMP]           XMP Toolkit                     : Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
    > [XMP]           White Balance                   : Manual
    > [XMP]           X Resolution                    : 240
    > [XMP]           XMP Toolkit                     : Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40
    > [XMP]           Y Resolution                    : 240

  • Add To iPhoto in Mail fails for iPhone photos sent in multiple emails

    Someone takes six photos with an iPhone and emails them to you.
    You get 6 emails. Each one has a photo.jpg image attached.
    You click the SAVE pop-down menu in the Mail message and choose Save To iPhoto. The photo is imported into iPhoto. You delete that email and do the same thing with the second email with the second photo...
    BUT, somewhere the Mail-iPhoto smartness turns dumb, as the rest of the photos will not show up in iPhoto. (This may have something to do with the fact that the iPhone sends each photo with the attachment name of photo.jpg and somehow Mail or iPhoto think that photo has already been added to iPhoto).
    I was having this problem with photos emailed to me by iPhone users and tested it myself.
    Sure enough, after the first photo.jpg attachment is imported all subsequent Add To iPhoto operations of iPhone sent images fail... even if the photos have been sent from separate iPhones from separate email addresses.
    All the attachments are kept by Mail in uniquely numbered folders in the attachments folder of my receiving email account in Library/Mail but since each attachments is named photo.jpg that seems to throw off iPhoto OR Mail (because even the quick progress update of "Adding photo to iPhoto" does not show up on these attempts).
    I checked if quitting and restarting Mail fixed allowed the second photo to be added to iPhoto but it did not. Quitting iPhoto after EACH import/Add To iPhoto operation allowed each photo to be added into iPhoto.
    This may have to do with the iPhoto bugs handling large libraries (I have 19000 images in it) like the spinning wheel of Names window after imports, etc.
    Just sharing if others have the same experience sending 3 iPhone photos by email to themselves and seeing if all can be added to iPhoto from Mail. Thanks.
    Imran

    Yes it is a bug
    Report to apple. iPhoto menu ==> provide iPhoto feedback
    You can work around BR saving to the desktop and importing or opening in quick view, expanding to full screen and saving to iPhoto
    LN

Maybe you are looking for

  • Full EFI reset

    Hello, I have a late 2009 iMac (hardware model "iMac11,1"). I set up an EFI password with the Apple-provided utility about one year ago (or more, I was still under Snow Leopard). A few weeks later, I decided to change it, but the utility does not req

  • HT1386 iphone 4S will not update due to error 3194, need help

    went to update phone to 7 and get a 3194 error and it will not update, currently stuck with usb icon and itunes icon on main screen

  • Prefer-web-inf-classes Problem

    Hi , I have an web application war file which has some jsp's and jar files in the lib directory of the war file . Also one of the jar files which is of different version is present in the classpath of WLS . My prb is that the my web application does

  • Object Imported from Illustrator Changes When Rendering

    I am creating a page that can be seen here: http://www.jalc.org/springswing2010/ The problem is, when I import the lightning bolt from Illustrator into Flash, the two pointed corners in the lightning bolt are sharp and pointed.  However, after render

  • How to setup or review the Oracle Enterprise Manager  in 11GR2 under OEL5.4

    The Enterprise Manager is running very slowly, it fails to attempt to connect to the database by time out, and after starting the database and listener these are not accessible externally from another host. Thank... Edited by: Elix545 on Feb 2, 2010