UPDATE – Lightroom 5.2 is now available as a Final Release. Read the detailsis now available as a Release Candidate on Adobe Labs. The ‘release candidate’ label indicates that this update is well tested but would benefit from additional community testing before it is distributed automatically to all of our customers. The final release of Lightroom 5.2 may have additional corrections or camera support.Bugs Corrected in Lightroom 5.2 Release CandidateThe following bugs that were part the Lightroom 5 have been corrected.
The team appreciates the very detailed feedback the community has provided on Lightroom 5 and we’re excited to correct a number of issues experienced by our customers. I recently noticed with LR5 that when cycling through images I will notice that some crops and adjustments revert back to their orig. State but the sliders will stay to their adusted spots and in the image history it will remain on the last change but the physical image will look as if it did out of camera. This happens to maybe 1 out of every 20 images i cycle through after they are processed.Also when creating a black and white in a virtual copy I noticed that the brush tool settings will be applied from 2 previous images onto this virtual copy.This is a serious problem because before I deliver a wedding of 700+ images I have to scroll through each grouping before I export to make sure none of my adjustments have been reset, its embarrassing when I have to spend extra time doing something when you are using a tool to help your reduce processing time.Any improvements??? I think what you are seeing here is how lightroom renders images. It will first present the raw/preview image and then apply the adjustments and replace the image with the final render/preview.
When stepping an image at a time, you don’t notice this, but if you start to step through albums quickly, what you see may actually be the raw unprocessed image and you need to wait a little before the adjusted image is rendered. How long it takes is related to your PC/disk/memory speed.It’s a byproduct of non destructive editing that is core to lightroom – I don’t know if you could entirely eliminate it and still retain the flexibility /speed – but I won’t say that I’ve never been caught out by it. More than once, until I realised what was happening, I thought I’d lost my edits or messed them up and started editing again.
Adobe Lightroom links with some popular social networks like Instagram, Facebook and Twitter. If you have a great photo, don’t hesitate to share it with everyone. Upgrade the power with the Premium version. Adobe Lightroom is a completely free download application.
Doing this will override whatever adjustments you had made when the tool/pc/mac finally catches up.I don’t think I’ve seen it apply adjustments from the wrong image – but I would expect it’s the same problem. Don’t get me wrong, I love LR5 and I am grateful for the new features and speed optimization (basically it’s close to a perfect product as it is), but it took almost 2 months (50 days) to fix an essential export problem, which probably affected most of the users during any web sized exports (noise reduction and output sharpening not applied). That’s simply too long for such a huge issue with direct impact on the final image quality. One would hope for a different approach especially during the sensitive “mandatory CC migration period”.Also the export for smaller images still seems to have bug – some images are 1px shorter after export then specified (e.g.
Exporting 1000px width jpegs makes some as 999px wide, etc.). Have the same problem Just spent 2 days editing a studio shoot just to find out about this bug the hard way when going back to re-edit some photos already cropped.
Basically and arbitrary extra crop step is added to the history every time I go back to a cropped image. Selecting the previous step in the history reverts to the correct crop. Normally I would then add a small edit which will delete the actiosn above the selected history item, but again, when I select another photo and go back, another abitrary crop step has been added. At this stage I am pulling my hair out – deadline looming and no answer thanks to Adobe. Only solution is to do all cropping and writing tiff before going to next photo.
In LR5 I’m still having the problem that when exporting it seems that the memory is not released after each photo, resulting in Lightroom taking up too much memory and telling me various exports failed because of insufficient memory. I don’t see a fix for this in the above list, even though the problem has been extensively described three months ago I realise I’m on a 32-bit 4GB system, but as far as I know that should only slow things down due to writing to the HDD, it should not stop exporting at allAny idea when this will be fixed?
Seeing the same thing as Sven with LR 5.2RC on a Windoze 7 32 bit 4GB system. I’m selecting 40-50 images to export and setting the start image number to 1 in the panel. Exporting images with single digit sequence numbers (i.e.
Newimage-1.tif to newimage-9.tif) was erratic in that some images were deleted as soon as their export was complete. In one case only sequence 6 and 8 remained of a possible 1 thru 9. When images went to double digits (i.e.10, -11 etc) LR seemed to stabilize. At the end of the entire export I got a panel announcing memory errors on the missing images.
Releasing memory on a non-existant image could confuse memory management?? Charles, that’s just plain whining. Adobe has put out release candidates for years, and sometimes there are more bugs that get fixed because of it.
Private beta tests can only involve so many people.Would you prefer that Adobe not do public release candidates? Because then they would be more like those companies that people criticize for not giving the public any advance warning of what’s coming. At least it is possible to give feedback this way.
You could switch to Aperture where this is no advance notice of new releases and you must accept what you are given, with no opportunity to find bugs they didn’t before the final release. Is that what you want?
One of the claimed fi´xed issues is not actually fixed – at least not for me:◾Incorrect photo was selected when trying to select a photo in segmented grid in Publish Services.I think in 5.0 this happened only very often but not always (but I’m not 100% sure abou the exceptions) – in any case, now with 5.2 RC the selection issue occurs always and with all my published services – so no improvement at all at best. This bug already forced me to redo color and star rating for more than 2000 photos!
Hopefully, Adove will actually fix this before releasing 5.2. A Smoothness adjustment slider has been added to the Detail Panel under Color Noise Reduction.This is great for high ISO shots!Refinements to the Spot Healing Tool:New Feather controlAwesome! But it needs more feathering still.
Also, it’s bad painting over with solid white mask because you cant see how close to the edge of something you are, I’d like to be able to control the opacity of the mask while painting over with the healing brush.Refinements to the Local Adjustment Brush:Right Click (PC) / Control-click (Mac) on a brush adjustment pin to bring up a context menu to duplicate or deleteControl+Alt+Drag (PC) / Command+Option+Drag (Mac) on a brush adjustment pin to clone (duplicate) that adjustment1. It’s a step in the right direction, but you should just INCREASE THE MAXIMUM EFFECTIVENESS OF THE SLIDERS. For both local AND global sliders.2.
We want to be able to copy and paste local adjustment settings!3. We want to be able to move a brush pin and adjustment just like the the ND and Radial filter!
If you take 2 shots of a person, and they only moved a little in one shot, we currently have to repaint all the adjumstent over again on the second shot, it would be so much nicer to just be able to sync it and drag the brush adjument into place!4. We want to be able to make local adjustments with the tone curve, HSL/C/BW, split toning, Detail panels.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |