Lightroom 3.2

Was it really necessary to issue yet another version of Lightroom, Version 3.2, less than 3 months after version 3 was issued? Do we really need all these updates, except for including new cameras in the ACR?

If you own the camera that is now in the update, yes. -- Tom When my bones turn to dust, and if my CD's didn't rust, future generations will see my photos and think that I was nuts.

5 minute download. At no cost. Yes, its ever so tiresome -- Larrys Wife/alter ego/best friend.

roy5051 wrote: Was it really necessary to issue yet another version of Lightroom, Version 3.2, less than 3 months after version 3 was issued? Do we really need all these updates, except for including new cameras in the ACR?
Well, LR 3.2 basically contains nothing else but the support for new cameras. Essentially you are still at LR 3.0 CSU2 (camera support update 2), or maybe 3.0.2.

roy5051 wrote: Was it really necessary to issue yet another version of Lightroom, Version 3.2, less than 3 months after version 3 was issued? Do we really need all these updates, except for including new cameras in the ACR?
It also includes Lens Correction profiles for an additional 150 lenses. Upgrade was free & only took a few minutes.

New in Lightroom 3.2 The goal of this release is to provide additional publish functionality, camera raw support, lens profile support and address bugs that were introduced in previous releases of Lightroom 3. (A comprehensive list of issues fixed in this release is included below.) Lightroom 3.2 New Features • Publish functionality has been added for Facebook and SmugMug • Numerous lens profiles have been added. Please visit http://blogs.adobe.com/lightroomjournal/ for the complete list. Lightroom 3.2 Known Issues • A mixture of Japanese and English strings appear in the Japanese language SmugMug interface • A Japanese language file name is not properly preserved when uploading images to SmugMug Lightroom 3 Bugs - Fixed • Develop: A custom aspect ratios get rounded to nearest standard ratio when adjusting crop overlay • Develop: A history state is incorrectly added after creating a preset that includes a graduated filter or lens profile correction • Develop: In the crop mode the X key sets a photo to reject instead of rotating the crop (Windows only) • Develop: Lens profile corrections were synced even when they were not selected in the sync dialog. • Develop: The escape key incorrectly applies a crop after a CTRL/CMD right arrow with the crop tool enabled • Develop: The local adjustment brush could have a very slow first stroke when exposure is the selected adjustment • Develop: The Live Loupe view on a second monitor could become unresponsive when switching images in the Develop module • General: Certain menu items were missing from the Windows version of Lightroom • Help Documentation: Inaccuracies and translation errors were corrected throughout the help documentation • Import: Copy as DNG selection not remembered for subsequent imports • Import: For some devices the import dialog did not allow directory browsing • Import: Import image number sequence is not incrementing properly • Import: Panels in the import window fail to scroll via the mouse wheel in some multiple monitor configurations • Import: The EXIF renaming token was not available • Import: Windows could crash when attempting to import video files • Library: Sub-optimal preview rendering performance could impact application performance • Library: If a directory tree is collapsed prior to closing Lightroom it will appear expanded after re-launching the application • Library: 1:1 preview generation could appear to repeat itself for DNG files • Library: Importing keywords causes a catalog to hang when imported keywords already exist in the catalog • Library: Attempting to drag and drop a folder when multiple folders are selected removes a folder • Library: Cancelling a catalog backup can require an excessive wait time before the cancellation is complete • Library: Cancelling a catalog export process could require an excessive wait time • Library: An internal error could occur when published smart collection conditions are updated

• Library: Choosing to apply recent keywords in a keyword set would cause the recent keywords to reorder • Library: Clicking the metadata flag on an image in the filstrip acts incorrectly on the selected image in the grid view • Library: Failed publish comments remain in the comment box across different images • Library: Flickr Publish Collection publishes to a Photostream in the reverse of the expected order • Library: Grid scrolling in a publish collection with the hand tool could fail (Windows only) • Library: Importing from a catalog fails when both catalogs contain images from the same folder • Library: In Smart Collections a hyphen ("-") Is now treated as a word delimiter for "contains words" • Library: In the IPTC Date Created field the seconds could be incorrectly removed on writing to XMP • Library: Lightroom 2 search criteria "+abc" meant "starts with abc" and "abc+" meant "ends with abc". This was reversed in Lightroom 3 • Library: Moving a stack to another folder only moves the top image and unstacks the remaining images • Library: Panning an image at 1:1 while the image is still loading can cause Lightroom to crash (Windows only) • Library: Ratings and Labels were not propogated to a TIFF or PSD file created for an Edit in External Application workflow • Library: Saving metadata on a folder is inccorectly labeled as "undoable" • Library: Scrolling or louping through many photos can cause Lightroom to start paging aggressively • Library: Setting "Caption is Empty" in a smart collection failes for some images • Library: Setting "Rating is Zero" incorrectly includes all images in a catalog • Library: Setting rating "is not" in a smart collection fails to include unrated photos • Library: Smart collection exposure time incorrectly limited to 1,000 seconds instead of 100,000 seconds. • Library: The "metadata for this photo has changed" dialog box lacks clarity • Library: The keyword list will fail to display properly if there are database integrity problems • Library: The save metadata command was incorrectly available when a video file was selected • Library: There is no warning when incorrect data types are entered into IPTC fields • Library: Updating DNG Previews and Metadata is incorrectly labled as "undoable" • Library: Upgrading a Lightroom 2 catalog via the import catalog function will fail if duplicate files are present • Library: Using an exclamation point in search criteria fails to work properly • Print: A faulty or corrupt print template could cause a "nil" error message when changing templates • Print: Image loses "pan" position when placed in cells that are not big enough • Print: Lightroom could crash while preparing a print • Print: The Print to JPEG save dialog box resets for every save • SDK: A URL could fail to open properly in a web browser (Mac only) • SDK: Calling info.publishedCollection:getName() from within updateCollectionSettings() causes "can only wait within a task" exception. • SDK: copyrightState was not documented (Will be corrected when documentation is posted with the final release) • SDK: Errors during collection or collection set update callbacks are not recognized when a collection or collection set is created • SDK: Function "withPrivateWriteAccessDo" lacks clear behavior documentation (Will be corrected when documentation is posted with the final release) • SDK: Lightroom does not respect the default system web browser (Windows only) • SDK: Per comment URLs were incorrectly included in the documentation (Will be corrected when documentation is posted with the final release) • SDK: Plug-in error reports "nil" instead of proper filename • SDK: Renaming a publish collection dissasociates it from collectionSettings • SDK: setEditedFlag does not work as intended • SDK: The publish icon size was incorrectly documented as 26 pixels instead of 24 pixels wide • Slideshow: Exporting a video that will overwrite an existing video that is currently being played will cause Lightroom to crash (Windows only) • Tethered Capture: The develop settings text was misaligned (Windows only) • Web: In-line editing of Site Info stops working if a number is entered • Web: Setting "sequence" as the title or caption fails to work properly Web: Certain galleries do not handle accented characters properly -- Dave http://www.rosser.pwp.blueyonder.co.uk http://www.pbase.com/dgrosser

On my 'old Mac' (iMac 24" coreduo with 3 GB RAM), it runs way faster and is about on par performance wise as LR 2.6 was, so yes I feel it was necessary...

This is to stay in sync with Camera Raw as new cameras are added.

Yeah, Lr is expensive and version upgrades aren't exactly cheap. So I think regularly scheduled mod upgrades and bug fixes should be expected and at no cost. You should hear how users of other programs complain when THEIR software of choice won't release a mod upgrade for their camera of choice. This is one of the reasons I bought Lr and not something else. And upgrading to the new mod releases IS voluntary, you know.

Exactly. So many users of other products complain "When is the update? When are you going to fix this bug? When are you going to support my camera?" At least with Lightroom you can hope that it's actually going to happen soon. VueScan is another app that's updated even more frequently, sometimes several times a week. People actually complain about that! If you think an app is updated too frequently, just skip the update. After all, if you don't care about it, please don't stop them from issuing a fix for MY bug or support for MY camera. One day, you're going to be the one whose workflow is held up waiting for an update of some kind...

Did you check the list of fixes? Some of the items being fixed affect most users. Besides adding lots of lenses for correction, the following bugs were fixed. I'm glad they did it. There are too many to list here: See http://www.adobe.com/support/downloads/detail.jsp?ftpID=4789

I'm happy with updates! I want fixes! I remember back in the day when you had to wait for them to mail you an update on a CD once a year. I'll take a new update as soon and as often they can push them out the door. Ok, so when is 3.3 due.... can't wait....

Scales USA wrote: Did you check the list of fixes? Some of the items being fixed affect most users. Besides adding lots of lenses for correction, the following bugs were fixed. I'm glad they did it. There are too many to list here: See http://www.adobe.com/support/downloads/detail.jsp?ftpID=4789
and reproduced here http://forums.dpzen.com/forums/read.asp?forum=1000&message=36202605 and continued here http://forums.dpzen.com/forums/read.asp?forum=1000&message=36202658 -- Dave http://www.rosser.pwp.blueyonder.co.uk http://www.pbase.com/dgrosser

If you review the 'fixes' & additions listed for a particular update and don't feel like they offer you anything you want/need, just skip the update and spare your blood pressure. -- 'There is no limit to what a man can do so long as he does not care who gets the credit.' -Philip Hyde (1922-2006)

As a regular daily user of Lightroom (and BR and PS) for my workflow for quite a few years now, I happily receive the news of new updates! I hope Adobe keep spoiling us with their little improvements and also making it easy to find, download and install. It actually is a privelege rather than with some other software producers, esp. those from the major camera manufacturers, that are painstaking slow on upgrading their software. If however you are happy with a particular version and it works well with your camera and pictures, then relax and enjoy it.

I've installed the 3.2 update, but under Lens Correction, it still only has the Tamron 28-75mm f/2.8 available. I shoot a 17-50mm f/2.8 and would really like to have the profile available.

DirkBelig wrote: I've installed the 3.2 update, but under Lens Correction, it still only has the Tamron 28-75mm f/2.8 available. I shoot a 17-50mm f/2.8 and would really like to have the profile available.
http://www.dpzen.com/news/1009/10090207tamronphotoshoplensprofiles.asp Two versions of the 17-50 are included. Like the Sigma profiles, they are only for raw files.

ljfinger wrote: Two versions of the 17-50 are included. Like the Sigma profiles, they are only for raw files.
Ah, there's the problem. I was looking with JPEGs. Switching to some RAW shots gets me the whole list. Thank you kindly for the assist.

G Davidson wrote: Thanks, I was wondering why it couldn't be changed on jpegs. As a matter of fact, I'm still wondering- if they can make one profile for jpeg, why can't they offer them all?
For example, all the Sigma profiles were created from lens design data. Obviously, such data cannot include the particulars of the processing of the JPEG engine of any particular camera. So, those profiles are raw only. They can be converted for use on non-raw images, but with somewhat degraded performance depending on the particular camera and in-camera settings. For example, if you apply the vignetting correction needed for a raw file to a JPEG file that's already had vignetting correction applied in-camera, you are applying it twice which will obviously result in a massive overcorrection.

Add new comment

Attachment
More information
  • Files must be less than 2 MB.
  • Allowed file types: txt.
By submitting this form, you accept the Mollom privacy policy.