Lightroom Journal

Lightroom 3.5 and Camera Raw 6.5 are now available as final releases on Adobe.com and through the update mechanisms available in Photoshop CS5 and Lightroom 3.  These updates include bug fixes, new camera support and new lens profiles.

New Camera Support

• Fuji FinePix F600EXR
• Hasselblad H4D-60
• Leaf Aptus II 12
• Leaf Aptus II 12R
• Nikon Coolpix P7100
• Olympus E-P3
• Olympus E-PL3
• Olympus E-PM1
• Panasonic DMC-FZ150
• Panasonic DMC-G3
• Panasonic DMC-GF3
• Pentax Q
• Phase One  IQ140
• Phase One  IQ160
• Phase One  IQ180
• Phase One  P40+
• Phase One  P65+
• Ricoh GXR MOUNT A12
• Sony Alpha NEX-C3
• Sony Alpha NEX-5N
• Sony SLT-A35
• Sony SLT-A65
• Sony SLT-A77
• Hasselblad “FFF” files created by the Hasselblad Phocus software for currently supported models are also now supported. (FFF files created using the FlexColor software are not supported)*

New Lens Profile Support

Lightroom 3.5 Bugs – Fixed

• Using the arrow keys to modify image adjustment settings lacked responsiveness
• A Publish Collection targeting a hard drive on Windows would not behave properly if the designated folder was deleted from hard drive
• After editing the capture time in Lightroom, “Date Time Digitized” was incorrectly changed. (Only “Date Time Original” should be modified)
• On Windows computers, Lightroom would interpret the wrong time zone per the following customer report: http://feedback.photoshop.com/photoshop_family/topics/xmp_metadatadate_has_wrong_time_zone
• Changing Lightroom’s date created field to a date prior to 1933 resulted in unexpected values
• Lightroom 3.2 introduced preview cache inefficiencies
• GPS Altitude metadata was incorrectly excluded from files converted to DNG or exported as DNG files from Lightroom 3.4.1
• For non-English language operating systems, folder names in the import dialog may not have been translating properly
• When exporting images with the “Write Keywords as Lightroom Hierarchy” enabled, keywords with “Include on Export” deselected would still have been included on export
• Saving metadata to a JPEG file in Lightroom 3.4 could have caused Lightroom to quit unexpectedly
• A Publish Collection in Lightroom 3.4 set to publish original files would fail to include XMP files for proprietary raw formats.
• RECONYX images did not open properly in Lightroom 3.4
• When applying automatic lens profile correction, Lightroom 3.4 did not automatically recognize the following lens:  “Nikon AF-S NIKKOR 24mm f/1.4G ED”
• Using the plus or minus key to increment Develop Module parameters did not work properly on the Mac
• The Limit File Size export option was incorrectly including EXIF metadata on export when the Minimize Embedded Metadata option was selected
• On Mac OS X 10.7, the Lightroom import dialog did not properly display network volumes
• On Windows computers, using Shift + Scroll wheel to adjust the Adjustment Brush feather size, the expected result of the scroll wheel movement was reversed per the following feedback post
• Lightroom would not provide the correct error message when attempting to delete photos published to Facebook
• Lightroom would experience tether capture failures on computers utilizing OS X 10.6.8 and 10.7
• Develop load time performance was inconsistent

Camera Raw 6.5 Release Notes
These items have been FIXED in Camera Raw 6.5:

• Camera Raw did not allow write-back capability for the EXIF GPS properties.
• The DNG File format did not support XMP Media Management.
• A JPEG file with a specific characteristic was found to have a pink cast.
• The undo command (Command+z) was failing to undo crop adjustments.
• Single images marked for deletion were not moved to the trash.
• A magenta color cast could have appeared on Nikon D7000 or Pentax K-5 images if the multi-exposure feature was used with raw capture.
• Applying Sigma 10-20mm Lens Profile to Nikon D7000 raw files could have produced dark or black corners
• Some EXIF fields of Panasonic raw files appeared to be blank in Bridge Metadata panel
• Applying the exposure adjustment brush to a high ISO image could have caused excessive noise reduction correction to the entire image