LR 4 Gradiation & Spot tool adjustments

LR 4 Gradiation & Spot tool adjustments are the same as in LR 3. In other words, no WB adjustment available. Only the same adjustments that were available in LR 3.

WB in GradFilter and AdjBrush are only available when you select Process Version (PV) 2012 by clicking on the exclamation mark at the bottom right corner of the image frame in the Develop Module.
Or, in the Develop Module go to >Settings >Update to current Process.

Similar Messages

  • Using new LR5 healing Spot tool on a cropped photo

    Hi all,
    I haven't seen much mention of this, but it drives me nuts -- wondering if I'm alone...
    When I use the LR5 healing Spot tool on an already-cropped photo, it often picks a healing spot from outside the croped region.
    That's fine, but there is no simple way to then adjust it -- it seems I have to: 1) copy the crop, 2) reset the crop, 3) make the adjustment, and 4) paste the crop.
    It seems there needs to be a way to "view the full canvas" from within the Spot too (I'd also like to be able to "view the full canvas" from within the new straigten crop tool).

    Hello
    You can us the '/' key to force a resample and if you are lucky it will bring the sample area into view.
    Mike Engles

  • Retouch tool adjustments not saving

    Had this problem in previous version of Aperture (after it worked it just stopped working!).
    Changes I make using the repair tool to Repair or Clone are not showing.  When I make a repair, there is a long delay with "Loading" showing and when that operations is complete, there is no change to the image. 

    I am having this exact same problem since updating Aperture, iPhoto, and Mountain Lion in the past week.  I notice this problem was originally posted two years ago, however.  HELP????

  • When I use the spotting tool on a very dirty image it bogs down. Can I collapse the work?

    What is the best way to save or collapse the work I have done on an image so I can get back to working at a good speed? I am guessing if I saved the image as a JPEG and reimported it that would add noise. There is probably a simple way to solve this.  Any answers?
    Thanks

    Robert,
    There is still a known bug where LR (including 3.3RC) bogs down when large number of spots are utilized.  Every system is different and most systems appear to not have this problem.  Personally, on my system, cleaning up a BW scan will bog down when I add around 50 spots and become unbearable by 100 - sometimes even hanging for 30 seconds or more.
    Some improvement was provided with the 3.3RC in that the hanging is less likely; however, the slowdown is still experienced and adding more spots once it gets to this phase is not an option.
    If 3.3RC doesn't solve your problem, and space is not an issue, you might consider exporting (and automatically re-importing) in TIFF format.  You will probably lose the least amount of detail and introduce the least amount of noise that way as opposed to a JPEG file.  You can then continue working on the re-imported TIFF file as your original and you should be fine for a few more spots.  I would probably delete the file you exported from so you don't get confused about which file is your image file (just my personal preference not to have two files of the same image unless they are VCs).
    Also, I find that exiting and re-starting LR every 5 or so images while in Develop module can help but that is huge pain.
    Best of luck.  I am patiently awaiting updates to fix this issues once and for all.
    Jeff

  • Restrict warp tool adjustments to horizontal only?

    When using the edit-> transform -> warp tool, is there a way to restrict the adjustment of the handles to either vertical or horizontal only?
    I tried holding down shift/alt/ctrl keys but doesn't work.
    This is for photoshop cs4.

    You can double click on the tool to get the options.
    I find more usage for the tool reducing intensity and increasing simplify.  Otherwise the warp tool acts too much like a melting tool.

  • LR 3.5 'crashing' when using spot correction tool

    I recently upgraded to Windows 7 (from XPx64) and have had to restart LR several times after using the spot correction tool. The circle verifying the correction doesn't appear, and my mouse cursor disappears anytime it is over the LR program window. Task manager indicates the program is running, but I can't operate the program. It also will not close from the start bar, and only closes from the task manager. Any other experience this?

    Spot Tool slowness and lock up can be caused when the 'Lens Corrections' tool is used (i.e. Enable Profile Corrections or Manual tab settings applied). Try temporarily disabling the 'Lens Corrections' tools by turning OFF the small switch to the left of the 'Lens Correction' tab. This will disable all lens correction settings. Try using the Spot Tool again and see if that fixes the problem. If so this is the best solution for now, and once finished with the 'Spot Removal' tool you can flip the Lens Corrections' swicth back ON.

  • Adobe Lightroom 5.4 - Enhanced Spot Removal Tool

    Since upgrading to Lightroom 5.4 I am unable to effect the Enhanced Spot Removal Tool. Having selected the area to be corrected, the sampled area appears. I am unable to transfer the sampled area to the area to be corrected. What is it I'm missing?

    First step would be to make sure you opacity slider on the Spot Tool is set sufficiently high.

  • Spot heal/clone tool problem

    Hello, I thought when I upgraded to LR4 that my problems with the spot tool would be a thing of the past.  Unfortunately they are just as bad if not worse.  I run on a Windows 7, 64 bit, 2.6 GHz, 6 GB RAM.  Using the spot tool to clone or heal slows things down considerably (though I do notice a little slowing in general with version 4).  The longer I use the tool, the worse it is.  I start to get strange partial square shapes under the spot when I try to modify it in any way (e.g. move it a bit or change from heal to clone).  I then need to delete the spot and start over to get rid of it.  Results get uneven, and eventually the program freezes, with a clenched fist for the cursor, and I can't move any spots, or even click anything in the program (though the cursor does move).  Any ideas what the problem could be?  I do not want to use the tool at all now, which given how important it is, begs the question why am I even using this program to edit photos?

    Not many, maybe 8-10 or so.  But it depends on how much I've been doing two things at once, how fast I'm moving, how long I've been working (longer I'm on it, more chance of it happening).  Seems like my computer can only deal with Lightroom when I use it at a certain, measured pace.  And I thought I was comfortably over the minimum requirements regarding speed.  Plenty of room on my hard drive (catalog on a different drive than program).  My antivirus isn't doing anything at the time, no other programs working at the time, just LR.  One thing, the fan is working OT when it happens, but I have the laptop on a cooling pad.  Seems to be getting behind and/or running out of RAM when it happens.

  • 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

  • Follow up on hot spots

    To follow-up on previous hot spot question-a response that I received indicated that you couldn't put a hot spot on a background image. Is there any other way for this to be accomplished.
    I try to the following to Hot Spot the following items:
    Search for home listings here, and
    Search for land listings here.
    Please look at the following website.  You will see what areas that I am trying to Hot Spot.
    http://www.grutkowski.com/index5.html
    Thank you for your responses.

    Simply take your header image out of the body background CSS. 
    Insert image directly into the HTML document.  Insert > Image...
    Once you do that, you'll have no trouble using the hot spot tools.
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

  • Spot Removal and slow system after a few clicks

    Hello All,
    I just wanted to bring attention to a very annoying issue. If you use spot removal function a few times in a lightroom session, you end up with the impossibility to use it anymore if you do not exit lightroom and start again from zero.
    What I mean is that after a few clicks on spot removal on 2-3 pictures, when you need to use it again on picture number 4, for example, the function is almost unusable (very slow movements that make impossible to put the spot tool in the right place).
    If you then exit lightroom and start again everythimg is fine for a while. It seems it is allocating memory each time you use it....anybody having the same problem? Any idea how to solve it? I have been dealing with this since previous versions and it has never ben solved (if it is indeed a bug!).
    Thanks all!
    Cristiano

    Hi Hans,
    yes, I guess we'll have to wait...
    I have worked with lightroom in the past and then moved to NX2 for a couple of months because I was loving the picture control correspondance with my raw files....then I was so desperate that I moved back to LR. NX2 was too slow and a very bad piece of software for me...altough I will keep an eye to future releases.
    I am on a Mac.
    Thanks!
    Cristiano

  • Can't Make a Hot Spot!

    Hi there,
    I'm using Dreamweaver 8 to make a new website.
    For some reason I can't make a hot spot. I've only made one
    website before and just checked on those pages and was able to
    click on the hot spot tools and draw a hot spot.
    Then I go to my new website and click on an image and then
    click on the hot spot tools and try to draw a hot spot on the
    picture- what happens is the picture tries to "drag and drop". That
    is the command that dreamweaver says is happening when I try to try
    to draw the hot spot. ???????
    What went wrong???
    Here is the Html code behind the photo I'm trying to draw the
    hot spot on:
    <tr>
    <td colspan="3"><img
    src="graphics-headers/skyfooter.jpg" alt="Sky Footer" width="800"
    height="45" /></td>
    </tr>
    <tr>
    Any help at all would be greatly appreciated as I don't know
    what I did in the code that's preventing me from drawing them.
    As I'm just starting making all my pages off my template-
    found another problem:
    Template won't update all the changes. For instance: Made a
    change to the copyright footer - capitilized first letter- this
    change won't update. Made changes to the page properties with a
    link color change, also changed editable region- these changes
    updated.
    Weird!!! So the pages made from the template will be updated
    only part ways from the original Template!
    What did I do wrong? My first website went very well.
    www.zoodoc-stories.com

    When you create a polygonal hotspot, you don't click and
    drag. You click at
    the vertex of each side. Is that what you are doing?
    Here are seven common mistakes that will result in changes
    not propagating
    from Template to child -
    1. Rename the Templates folder
    2. Move the Templates folder to some other folder level in
    the site other
    than root level
    3. Move a template out of the Templates folder.
    4. Make changes to an editable region of the template (which
    will not
    propagate)
    5. Assume that template changes can be uploaded to the server
    without also
    uploading the changed local files
    6. Corrupt the site cache so that the link between template
    and child page
    is broken
    7, Improperly create your child pages by simply opening the
    template,
    adding page specific content, and resaving the template with
    an *.html
    extension rather that its *.dwt extension. (you can tell if
    this is the case
    by looking at the code on a child page - if you see anything
    like <!--
    TemplateBeginEditable... then this is what you have done)
    The 6th problem can be repaired by using SITE | Advanced >
    Recreate Site
    Cache, and the six others can be fixed by just not doing
    them. Have you
    done any of those?
    Or, read this -
    http://www.adobe.com/go/dd83ba8b
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "sculpturedolls" <[email protected]> wrote
    in message
    news:[email protected]...
    > Hi there,
    >
    > I'm using Dreamweaver 8 to make a new website.
    >
    > For some reason I can't make a hot spot. I've only made
    one website before
    > and
    > just checked on those pages and was able to click on the
    hot spot tools
    > and
    > draw a hot spot.
    >
    > Then I go to my new website and click on an image and
    then click on the
    > hot
    > spot tools and try to draw a hot spot on the picture-
    what happens is the
    > picture tries to "drag and drop". That is the command
    that dreamweaver
    > says is
    > happening when I try to try to draw the hot spot.
    >
    > What went wrong???
    >
    > Here is the Html code behind the photo I'm trying to
    draw the hot spot on:
    >
    > <tr>
    > <td colspan="3"><img
    src="graphics-headers/skyfooter.jpg" alt="Sky Footer"
    > width="800" height="45" /></td>
    > </tr>
    > <tr>
    >
    > Any help at all would be greatly appreciated as I don't
    know what I did in
    > the
    > code that's preventing me from drawing them.
    >
    > ----------------------------
    >
    > As I'm just starting making all my pages off my
    template- found another
    > problem:
    >
    > Template won't update all the changes. For instance:
    Made a change to the
    > copyright footer - capitilized first letter- this change
    won't update.
    > Made
    > changes to the page properties with a link color change,
    also changed
    > editable
    > region- these changes updated.
    >
    > Weird!!! So the pages made from the template will be
    updated only part
    > ways
    > from the original Template!
    >
    > What did I do wrong? My first website went very well.
    > www.zoodoc-stories.com
    >
    >

  • Who is happy with Spot and Patch?

    First let me say that I'm thrilled almost completely with Aperture in general. It pretty much solidified my transition to digital from film. I have a long workflow history with scanned slides and photoshop so I am quite used to and adept at spotting and patching my shots with their wonderful healing brush, clone tool, etc. I was excited about the prospects of using aperture for all the minute details that go into a workflow but the one glaring shortcoming is the spot and patch tool. I find the spot tool does a very bad job of using surrounding details to fill in a spot. You get a circular blur that might be accurate color wise but retains no detail. This is very apparent on skin. It's pretty much unusable. And the patch tool is a poor substitute for cloning. No matter what I do I cannot get it to blend in, I always see the circle.
    I know what you all are going to say, just shoot it over to photoshop. This is what I've been doing but it really causes the size of your library to grow since you don't get the advantages of the smaller RAW file size.
    Maybe in Aperture 2.0? Any one have any thoughts.

    I've had very good success with the Spot and Patch tool, but you have to be very careful about the areas you work with. Chad's advice is very good---read the PDF. Note that the PDF says at the very outset under "Spotting Your Images"--"When the area around the blemish is continuous (such as a solid color) and doesn’t contain a distinct texture, you can use the spotting method to obscure the blemish by integrating the pixels that surround it."
    In my experience, that advice is critical. Spotting and patching replace pixels with other pixels. Ideally, what you want to do is have Aperture take out an anomolous set of pixels (they don't match their surrounding pixels, hence they create a spot) and replace these pixels with ones that have the same characteristics of the surrounding pixels. So, for example, if the spot is in the middle of a very varied area, Aperture has trouble determining what you want as a replacement for the offending area.
    The PDF tells us a lot about how to adjust the spotting and patching when the conditions for the operation are not ideal.

  • Lightroom 5 Spot Removal

    My June purchased version of Lightroom 5 has what I think is a bug. I cannot export as DNG file either clone or heal "shaped" spot removals. It will export simple circular removals as DNG. Both types of removal can be exported as TIFF and JPG files. When I reopen spot-removed as shapes DNG files in Lightroom, even then the spot removal does not appear. Oddly, when I Import such DNG files back into Lightroom, the spot removal does appear in the thumbnail of the photo, but not in the actual file when re-imported. What gives? Is there a fix?

    It doesn't even have to be an older version of Photoshop.  Remember that Photoshop CS6 can utilize camera raw 8, and by so doing would be able to read those DNG files.  But it was mentioned that they are using camera raw 7.1.  And that version isn't going to be able to read those spot removal adjustments.  If you are using Photoshop CS6 then you really need to be using camera raw 8.  Then you will be able to read all the adjustments made in your exported DNG files.

  • Spot removal pins disappear after photoshop install

    Yesterday I installed Photoshop CC. Since the install, the spot removal pins in Lightroom don't show up. This is the case both for spots that were removed prior to installing photoshop, and for new spot removals. The spot is removed, but I cannot see where the spot was (due to no in) nor where the data to remove the spot is coming from, so I can't move the target area either. This makes quite a dent in the functionality of spot removal in Lightroom, so if anyone knows how to fix this, please let me know. I assume that this is somehow related to the photoshop install - there have been no other software updates, installs or removals on the computer at all during this period.

    Hit the "H" key while using the spot tool to get the circles back.

Maybe you are looking for