Local adjustments undo keystroke

Just wanted to mention this as an annoying behavioral bug that I'd appreciate you fixing before release.
When making local adjustments, if I'm modifying one of the sliders to an existing adjustment, then hit undo it de-selects the adjustment, so I have to go find the pin again on the photo.
So for example I have a photo where the sky is too bright. I put a gradient adjustment on the upper portion of the sky, taking down the exposure a little bit. But in addition the sky now seems flat, so I change the contrast slider to add more punch to the sky. After looking for a second, it seems too much so I hit ctrl-z to go back a step. Now I have to go back and re-select the adjustment to make changes to the sliders again, which I shouldn't have to do since I selected that several steps ago.
Thanks so much for looking at this. I love using LR, and am thrilled with the improvements coming in ver. 4.
Schlaave

That would only be possible if you remember your latest good setting.
Not much of a challenge maybe if it was just one slider. But for complex changes something like a history for the local adjustment would be useful, inside the dialog while you are still doing the adjustment.
But the OP did not even ask for that much, just for an Undo of the very latest action.

Similar Messages

Lightroom has a hard time with local adjustments:

Local adjustments: Spotting / Cloning / Healing Brush, Adjustmenst Brush, Graduated filter
I posted the piece below as a response to thaehn’s post “Lightroom freezes on Dust Spot Removal” but I thought the topic is important enough to warrant its own post.
This in advance: I'm running WIN XP SP4 with all available patches; have 4 GB of RAM; have a dual-core processor at 3 GB.
Apart from my drive C, I have two internal hard drives in Raid 0 configuration (thus they show up as one drive). I also have an external hard drive that's in Raid 1 ( "mirroring') and is connected by fire-wire 400.
Yes, LR "freezes" when using the dust spot tool and also when using the adjustment brush or - but to a lesser degree - when using the grad filter.
My observation though is that it's not a true "freezing", because if I wait long enough LR starts working again. So when using these tools, LR gets extremely busy und just doesn't have enough resources left to respond to further commands right away - but it "stores" the comands and acts on them eventually.
If I turn on my task manager I observe the following when using these tools: the CPU gets extremely busy (i.e. the green bar is at 100%) while the RAM usage is high but not to the max. The "freezes" occur when and as long the CPU works at 100%. If the CPU is below 100% LR responds sluggish and the response is normal again when eventually the CPU usage is at 0%.
Also, in my observation, this behaviour of LR is compounding, i.e. the wait-times for my CPU to get back to 0 are increasing, the longer I work with these tools or the more photos I work on. Re-starting LR does not bring change: the behaviour establishes itself when using the tools again. It is as if LR needs to do some work in the background and that this background work piles up the longer I work in LR.
I am not a software or hardware specialist, so the following observations are somewhat subjective and not really quantifiable.
In Photoshop I observed a similar behaviour (although never as bad) when working on files of 500 MB and above. It was particularly bad when working on photos residing on my external RAID 1 hard drive. I had a hunch that it might have to do with the reading and writing from a drive that a) is external and b) is in RAID 1. It is known that RAID 1 has slower writing (and also reading) speeds than RAID 0 (or no RAID at all). So in Photoshop I managed to cut down on the unresponsiveness by moving large files to my internal RAID 0 hard drive and working from there.
From this experience I come to the assumption that some of the "busy-ness" in LR (or of the CPU) is due to reading/writing to/from the hard drive.
To test this assumption for LR, I moved some photos from my external (RAID 1) to my internal (RAID 0) hard drive and did some "intensive" work: first some "fancy" lens correction, then a few grad filters, and a "final touch" with the adjustment brush. I thought that LR could handle these tasks somewhat better when the photos were on the internal drive - so some of the "sluggishness" or " freezing" is due to the reading/writing from/to the hard drive.
Acually I cannot explain why this should be so: In my naivete I thought LR writes everything only into the catalog (?), that - by the way - is on my internal RAID 0 drive.
I think it would be good if Adobe could look into this and maybe give us some recommendations, just as they do for Photoshop by saying that the scratch disk should be on a different drive than Photoshop.
But it seems also that local adjustments - spotting, adj. brush. etc - are a very high "number-crunching" business for LR - independent of where the photo is located on the drive. (Interestingly the grad filter is not as bad as the adjustment brush). The clone-tool in Photoshop hardly registers on my CPU and if at all only with a very short spike, while the clone tool in LR sends the CPU through the roof for 10 to 30 seconds- even when the photo in question is on the internal drive.
I'm sure loots of people will now tell me that this is due to the difference between pixel-based adjustment and non-pixel-based ones. OK, I acknowledge that. But still ...
It seems some guys are still in denial about this (or maybe they have two quad processors and 16 GB of RAM):
But it's a fact: LR has a hard time with localized adjustments. There must be by now 100's of complaints to that respect, and that can't be dismissed by blaming it on the hardware specs alone.
I just hope Adobe is working on that.
LR3 is a fantastic program that I would not want to work without. Often I have to work on a lot of photos with a very tight deadline. Without LR it would be impossible.
Thank you,
ErnstK

You are right Samoreen.
I posted my above message in July 2010 and this topic has been re-opened by Adobe under the thread Lightroom 3.3 Performance Feedback
I think it would be best if everybody would post their concerns only under this thread.
Otherwise we'd have two different threads for the same issue.
So let's close this one here.
WW

Local adjustments slow on Vista 64 (LR 2.1 - not a Nvidia problem)

Hi,
I am using LR 2.0/2.1 from the release of the 2.0 and recently has migrated my PC to Vista 64bit. My hardware is 2 years old but nevertheless is quite up to task - P4 dual core 3.2 Ghz CPU with 4 GB of RAM and SATA RAID with XFX GeForce 6800XT card (with 512MB of card RAM).
It is a very fast system in general but I do have some problems in LR 2.1 with a local adjustments brushes. I know it's a well discussed topic however I feel that in my case it is sufficiently different to warrant a new topic. I've done all the Nvidia driver optimisations - setting all the driver properties to max performance for LR. This did make a difference initially but as brush strokes are added the lags are getting worse and if I have about 8-10 strokes and more - it gets really unusable - very slow to catch up with delays as much as a minute or two.
I don't run any antiviruses or any other scanning utils other that bog standard Vista 64 bit services (all the potential scanning services like disk indexing, defender scanning has been disabled for the purpouse of the performance testing - nothing made a difference). What is curious though, that a few people who have the brush working fast were saying that CPU was not topping up and in my case I noticed that both cores were used quite a lot when the delays started to occur (with the number of strokes around 8 or 10 and more). The combined CPU usage went up to 90% (so both cores were used extensively). I have a relatively medium catalog - around 10000 photos.
Setting the automask on/off does not make a lot of difference - with the automsak off it only is more responsive for a couple more further strokes and then slows down again.
I am sort of exhausted my options of what to investigate further and would appreciate any constructive comments of where to look and what to look for (please no Adobe blaiming here). I will also appreciate some Adobe engineers comments on the CPU usage of the adjustment brush and possible also insights of how can I look at what's going on.
Thanks,
Alex

I've contributed elsewhere but I'll just add another voice to this thread. Same cumulative slowdown here with a very similar system. I don't know if you have noticed but it's not only the brush strokes that slow down to treacle speed. If you get fed up waiting for a response and start clicking buttons you can find them reacting sequentially for up to a minute. Its like watching a very slow recorded tutorial. It's the same for adjustment sliders once the slowdown is under way.
Also I find that if you move the brush too quickly it will abreviate the curve you create into a series of angles. I postulate that, in the case of my Intuos tablet at least, the program has a problem responding to the data rate from the tablet. An example is if I tap the pen in the image, lift and go quickly to make a menu selection. The brush will continue to draw after the pen has lifted along the line of cursor movement and I have to go back and delete the stroke.
Brian

Missing priority rules for local adjustments

It would be nice -- in the absence of layers for Lightroom -- to have a feature that lets me sort the various local adjustments in a picture (i.e. the gray points) so that some have priority over others. Currently, I found no way to achieve that: If regions which I painted with the adjustment brush slightly overlap and either has different settings, the result is not really predictible. I for my part use Photoshop to make precise adjustments, but I'd prefer to stay in Lightroom. Is there something I missed or would that be an idea for future development?
Andreas

If you have to do various local adjustments, Photoshop is your program of choice.
Lr does not so well with local adjustments, not to speak of various local adjustments.
Try to avoid overlapping areas of different Adjustment Brushes.
You most probably know that you can erase areas of an Adj. Brush where you painted by mistake by holding down the Alt/Opt key.
And, no, you can't prioritize the various Adj. Brushes.

Best Plug-in/External Editor for Aperture Local Adjustments

I've been playing with trial versions of Nik's plug-in suite, Lightzone, and I have a version of CS3.
From the standpoint of making local adjustments ( hopefully something we will see in the next version of Aperture), which do you feel is the easiest to use without compromising results.
I sorta lean towards Nik's plug-in especially Viveza but would like to hear from those of you who have had some serious usage with any of these tools as with the trial period and being busy, there's only so much time I can spend on it. Nik suite is being bundled for discount and there's also a discount on Lightzone as an external editor.
Thanks,
Larry

CS3 is a great external editor- If you want something that is really easy and quick to use the Nik software is amazing. The three tools that I use a lot from Nik (I use them directly from Aperture and in Photoshop on smart objects) are Viveza, Silver EFEX Pro, and sharpener.
RB
Ps. I have a couple of reviews on my site just look up the product name [http://photo.rwboyer.com]

Couldn't delete Local Adjustments (Dodge, Burn) from Virtual Copy/Photoshop Edit

Setup: Lightroom 2.3 on Mac with latest OSX
1. I applied some settings to an image in LR, along with some local adjustments using the LR Adjustment tools.
2. I made a virtual copy of that image to apply some further adjustments, and I wanted to remove the local adjustments from this copy, so I deleted the adjustment points from this virtual copy. I also clicked "reset" on the Local Adjustments panel.
3. I do a Command+E to open up the virtual copy image in Photoshop for further edits. Problem: in photoshop the effects of the local adjustment tool are still displaying. There are dodge and burn marks in the image per the local adjustments I made in the master image, but removed from the virtual copy.
4. I rechecked the virtual copy and could see no sign of the local adjustments still in the file.
To resolve this, I had to return to the master copy, delete the local adjustments in the master copy, and create a new virtual copy.
Is this normal... I should be able to remove a local adjustment in my virtual copy and let the master copy keep its adjustments, no?

No. You cannot be taken seriously.
1. Photoshop is not Illustrator / Fireworks / Premiere / After effects / Dreamweaver / InDesign. Thank god Adobe. It is already bloated enough.
2. Much worse: your improvement list is sometimes faulty.
These are randomly selected examples:
Anri Orlow schrieb:
When you are duplicating and coping layers the layer panel becomes a horrible mess with dozens on layers with names like "Layer 123 copy 14" and it's very hard to sort it all out. Maybe it's better to copy layer with the same name as it's original?
Rename your layer. See screenshot.
Anri Orlow schrieb:
When you try to drag n' drop a layer holding down Alt to copy it, and it's already placed on top of the layer stack you have no ability to copy it on top of original one. I think it must be fixed
False. Press first Alt and move the layer a little bit upwards until you see the light line.
Anri Orlow schrieb:
Custom shapes. I understand why they are separated buy setst, but why does dialog this stupid annoying "do you really want to replace this set with another" appears every time you change the set??? And why can't we review all the sets in the same time?
What - in your opinion - means the upmost entry in the list?
Anri Orlow schrieb:
Why we can add as many raster masks to the layer but can't do the same with vector masks? Why?
Only 1 layermask + 1 vectormask maximum per layer. Try it.
3. Some of your wishes are ok, but have in mind: different people have different wishes.
miss marple

Local adjustments - jumping between sliders

Hi.
In short - <tab> button does not work in the panels of Local Adjustment Brush and Graduated Filter.
In detail, I often adjusting images using keyboard, especially in the Basic panel.
Because it's better to use sliders from top to right, I'm using following procedure:
1. Clicking to text field of the top most slider (usually Exposure)
2. Adjusting value using Shift+Up/Down Arrows
3. Fine tuning using Up/Down Arrows
4. Pressing Tab to jump to next slider, or Shift+Tab for previous if needed
And so on.
But unfortunatly Tab and Shift+Tab does not work in the panels of Local Adjustments tools.
I think this is not a bug but rather missing feature - it does not work in previous versions too.
But it's really missing.

SistersCountry wrote:
When doing heavy highlight or exposure recovery using local adjustments on RAW files I can see a demonstrable difference many times between using automask and not using it.
The "heavy highlight or exposure recovery" is a key...Auto Mask works well when the adjustment are subtle–which is what it was designed for. If you are expecting accurate masking when making radical changes, it simply will not work. For that you really need to go into Photoshop and use really accurate selection techniques to get accurate results.

Feature Request: More Local Adjustments

Sometimes it's nessesary to correct hue/saturation locally — change face colour or something like that. And it would be good to have such brush. Together with ability to change Fill Light, Black and Vibrance in a part of image. Why the current selection of brushes is so narrow?

alex krylov wrote:
Sometimes it's nessesary to correct hue/saturation locally — change face colour or something like that. And it would be good to have such brush. Together with ability to change Fill Light, Black and Vibrance in a part of image.
+1 vote.
Although, its amazing what can be done with the current complement with some practice. For example, opposing color can be added to remove color casts... I often paint with brightness and contrast all the way down and exposure way up to bring detail out of shadows...
alex krylov wrote:
Why the current selection of brushes is so narrow?
My theory is that it is due to the limitation of the present design - limiting the brushes keeps it fast. People with inside knowlege don't much respond on the forum to these types of questions, so us outsiders may never know for sure... But if you think about how painted sharpening is implemented, its just a series of offsets that are applied to the global sharpen settings, so Lightroom doesn't have to do a bunch of different sharpening - just one pass, applying the net amount in each area.
Summary: I think the present complement of local adjustments has been carefully chosen to keep the develop module efficient in accordance with the present design, and to expand the local adjustments a great deal will require some redesigning. I hope I'm wrong and that it will be easier than I would imagine to add local white-balance & fill... If I'm right, I hope Adobe redesigns the develop module for Lr4 in order to expand the local adjustments.
Finally: My present thinking for Lightroom is that this will be too much for Lightroom 4, and that we are more likely to see incremental changes to the Develop module (maybe improved distraction removal) combined with new features like soft-proofing and photobooks... That said, I have switched my desire for Lightroom, to have better integration with external editors, so one can take it as far as possible in Lightroom, but be better able to integrate outside work done on selected photos.
Rob

5d mkII files + local adjustments = Crash

While doing some 15+ brush strokes on a file, I keep getting crashes from Lightroom, either propper crashes, or freezups. I have also managed to get freezups while exporting a file with lots of adjustments to jpg.
This started on LR 2.2, but yesterday I upgraded to 2.3 after reading on these forums, but it has not helped.
This is on XP 32bit SP3 with 2gb of Ram. GeForce 7600 GT.
I've used a 1d mkIII previously for more then a year and never had these issues, and so far only have had them with 5dmkII-files.
On a sidenote, local adjustments have always been very slow on this computer, but it had never crashed lightroom before.
/Björn

Ensure that nVidia nView is disabled - instructions at http://forums.adobe.com/thread/358030?tstart=0
If that doesn't fix the problem try deleting the preference file - instructions at http://forums.adobe.com/thread/358041?tstart=0

LR2 not scrolling in Local Adjustments menu

There is no scroll bar indicator, nor will it allow mouse wheel scrolling in the Local Adjustments functions. This is both the Brush and the Graduated Tool. Anyone else?

This is by design.

Fast switching of tools when applying local adjustments

I've recently bought LR5 and have it installed on my iMac. When using local adjustments, e.g. the adjustment brush and painting on a mask area I know the slash key can be used to switch between brushes A and B but I find I frequently also need to select Erase on the fly.
Is there a keyboard key that will select erase so I can erase then switch back to brushing the mask?

Hold down the option key and the brush will change from positive to negative enabling you to fine tune your mask.

Restore default presets in local adjustments

I think that there is a problem when restoring default presets in local adjustments. I can not restore them, both from the preferences window and from the menu in local adjustments.
By the way, I'm storing my presets with the catalog.

how to restore these presets.
By reinstalling any Adobe app that makes use of the shared PDF components. The presets themselves are stored in the pertinent program folder and also in your user data folder. In fact if you simply create a new user account they may magically show up because they were re-created/ copied with factory defaults... On the other hand that may also point to possible permissions issues with your own user account - the files may be there, but inaccessible due to insufficient privileges. Other than that really simply reinstall.
Mylenium

2.3 Cannot Edit Local Adjustments

Today, I opened up Lightroom and it told me 2.3 was available. I had been waiting for this before downloading it from Adobe Labs, in case some terrible thing happened and I would have to reinstall 2.2. (Terrible things seem to always happen to me.)
Now that I've updated, I cannot edit my local adjustments. The grey dots no longer appear on photos I edited before the update, or on new ones that I began editing after the update. The graduated filter works fine and shows its grey dots, but the adjustment brush does not. I restarted LR and it's still giving me a conniption.
Anyone else experiencing this? I couldn't find anything on the web or in the forums that related to my problem. Is there some preference setting that changed? I reported this as a bug on 2.3 in the Labs, but would love to hear if anyone else has resolved an issue like this.

Yep this got me too. H will fix it, but it sure is bizarre behavior that is hard to figure out until you know the key.

LR 5.3 bug: local adjustments not saved in XMP

Hi,
I'm seeing the following bad bug on my mac, with LR5.3
If I save metadata to disk and immediately reload, I lose some adjustments, like brushes, tone curves, etc.
I compared some old .xmp and the .xmp saved by LR5.3 and indeed there are some sections missing.
Can anyone confirm? This looks like a P0 bug to me. What's the procedure for notifying Adobe?

did you wait for LR to save all the 10000 XMPs?
yes, I waited... 24 hours. but again, time is not the issue. This happens even for a single picture, albeit it does not happen for any picture.
I open a picture, save metadata, switch to finder/terminal, look at the .xmp manually and I see all the legitimate differences (e.g. softwareAgent changed from LR4.1 to LR5.3), but also a lot of sections are missing.
If I switch back to LR and re-read metadata from the file, I lose all the local edits, etc.
are you sure the Write rights of the restored files are OK?
Have you tried the same operation on the local disk?
yes and yes.
I think I found the pattern:
this happens for pictures that have been upgraded from PV2010 to PV2012 in LR4.
If I edit one of these pics in LR, it shows "Process version 2012", and in history I see "Update to current process (2012)".
However, the .xmp file on the disk says: "crs:processVersion = 5.7" (which is 2010, IIRC).
If I select "Process Version 2010" and then again "Process Version 2012", and I re-save the xmp, then it looks good.
Do you have any clue of what's going on?

Local adjustments - can you define an area

I like the new local adjustment tools in LR4 but it would be really useful to be able to accurately define an area - say a bright window frame so I can change the white balance and pull the exposure a little in a precise area that is different from the rest of the shot.
Is there a better way than just with the crude brushes available? Perhaps something similar to the PS pen tool?
TIA
David

dhphoto2012 wrote:
Is there a better way than just with the crude brushes available? Perhaps something similar to the PS pen tool?
In Corel AfterShot Pro there is.

Local adjustments undo keystroke

Similar Messages

Maybe you are looking for