Highlights and Shadows develop settings are not functions

While implementing an image-processing plugin, I learned something very interesting (to me) about the Shadows and Highlights develop settings.  The other basic tone settings (exposure, contrast, saturation, etc.) always map any one color to another single color uniformly throughout the image.  But the Shadows and Highlights may map a given color to multiple colors in a single image, depending on the location of the pixels.
For example, in a test image I made with Shadows = +100, pixel (824,286) had its original 16-bit color value (0, 0, 0) transformed to (1724,1387,852).  Pixel (861,287) also had original color (0,0,0), but it was transformed to a much different color (3093,2688,1316).
Abstractly, the other basic tone settings are functions (any input color always has the same output color), while Shadows and Highlights are many-to-many mappings (any input color may have multiple output colors). I knew that Clarity was not a function -- the transformed value of a pixel would depend on neighboring pixels.  But it never occurred to me that Shadows and Highlights weren't functions either.  
Is this property of Shadows and Highlights well-known by expert users of LR?  (I.e. Rob, I assume you knew of this?)

Yup - @Lr4 (PV2012) there are 3 adjustments using Adobe's new "magic" algorithm:
* Clarity
* Highlights
* Shadows
I really don't know enough to fill in much in the way of details, except to say that when you use -highlights or +shadows, it "clarifies" the highlights and/or shadows a little bit, by way of the laplace-transform based algorithm Adobe developed. Jeff Schewe has pointed us to a white-paper about it in the past, but I dunno the link.. To me, it's akin to Topaz Detail and/or Topaz Adjust's "adaptive" enhancements - two Photoshop plugins I used regularly until Lr4 came out (Adobe's algorithm is very well done - in my opinion, better than Topaz labs, or any of the others doing similar things, e.g. PhaseOne, DxO, Nikon, ..).
FWIW - this is one of the reasons some people were raising heck when Lr4 first came out - no way to brighten shadows using the basic sliders without getting the clarification effect.. That said, Eric Chan also has informed us that Lr3's fill light had a similar mathematical algorithm backing it, and so Lr4 was not new in that regard, just improved..
Rob

Similar Messages

  • With 'Mail v8' and 'Yosemite' accounts settings are not saved and I keep having to check the "SSL" box

    With 'Mail v8' and 'Yosemite' 'mail' "account settings" are not saved and I keep having to check the "SSL" box. This has only occurred since upgrade to Yosemite?
    Any help would be appreciated as this is so frustrating!!

    Update to 3.6.16 has fixed this problem.

  • Develop settings are not saved

    Hello,
    I'm working mainly with jpeg and psd files and trying to save all settings and metadata automatically to be able to use it from other applications (e.g.Bridge). The two catalog options "Include develop settings in metadata..." and "Automatically write changes to XMP" are activated.
    However, Lightroom does not save the modifications that I made in the Develop module. All other metadata changes (ratings, title, IPTC, etc...) are saved and available in other applications. I'm using version 3.3 on 64bit Windows. I'm not 100% sure but as I recall I didn't have this problem with previous versions.
    Is there any solution?
    Thanks!

    It's not clear what you actually expected. Outside of Lr or Camera Raw the only way that an image will be rendered as per your edits is if they had been exported (i.e. newly fully rendered version of JPEG or PSD). Simply saving the setting does nothing other than embed a bunch of metadata.

  • Develop settings are not carring back to the Library

    I downloaded LR4 the first morning, and it has been pretty impressive. Until last night. I did the editing I wanted to do in the develop module, and when I went back to the Library to export, not everything came along. Most notible was the noise reduction from the details pannel, and the work from the brush didn't come along either. Also when I right clicked and selected edit in PS, whatever I had done with the brush was black in PS.

    PS, I should also ad that I'm running on a 64bit windows 7

  • When Firefox is closed, all previous search page and home page settings are not saved. Must reset firefox and reset homepage url everytime.

    All previous search engines on "Manage Search Engines" are gone and cant access the "get more search engines"...all grayed out.

    Session Manager and Save session are the ad-ons which can solve your problem of saving previous search pages and url.
    To set up home page and its related error You have to read this :
    http://mzl.la/Mt91fd

  • Are highlight and shadow clipping must be avoided in any image?

    Are highlight and shadow clipping must be avoided in any image?
    Because in some cases, let's say, night scene, usually has many black pixels in the sky. Which perform nice contrast against the colorful signs.
    Please check the attached image for reference(01.tif).
    I know there's nothing in the sky, so I would like to keep all the pixels to be clipped. Is this right?
    Some of my students says that other instructors told them to keep all the pixels in the histogram.
    But I tell them it depands on how would you like your images to show. Am I correct?
    As the attached image, it's impossible to pull the black pixels back to the histogram and I think it's acceptable in this case.
    Let's see the 2nd case(02.tif), this image has highlight clipping in the clouds.
    I like the way this image looks, which looks like a watercolor painting.
    If I pull the white pixels back, the image will change a lot and I will get a very dark overall.
    My question is, is it that important to keep your images without having highlight or shadow clipping?
    This is not apply to any image, right???
    THANK YOU

    For a more in depth discussion of clipping, it should be noted that clipping can occur in either the raw file or the rendered white balanced file. In the latter, it can take the form of luminosity clipping or saturation clipping. Saturation clipping occurs when the chosen color space is too small to accommodate saturated colors at a high luminance. In ACR, saturation clipping is indicated by a colored line or shoulder at the right of the histogram. The remedy is to use a larger color space. Luminosity clipping in ACR is indicated by a white line or shoulder at the right of the histogram and the remedy is to adjust exposure or use highlight recovery.
    Examination of the OP's histogram shows a yellow line at the right, indicative of saturation clipping of the red and green channels. The OP could try a wider space such as ProPhotoRGB.
    Here is an image of a a flower rendered into sRGB using the ACR defaults and the Adobe Standard camera profile. It appears overexposed and the yellows (actually reds and greens) are clipped as indicated by the yellow line at the right of the histogram.
    The raw histogram (produced by Rawnalize) shows that the image is well exposed. The red and green channels are just short of clipping. The image appears overexposed with ACR, since ACR uses a baseline exposure offset for the Nikon D3.
    However, when white balance is applied for this daylight exposure, the red channel is multiplied by approximately 2.21, and this should result in clipping of the red channel. This did not work exactly as expected with ACR, so I used Iris (a freeware astronomical program which allows extensive control of the conversion process) and examined the histogram of the resulting image in Photoshop. Note that the green channel is just short of clipping, as expected and that the red channel is clipped.
    To avoid clipping with the white balance in ACR, it is necessary to use negative exposure to offset the red white balance multiplier. I chose to use a bit of highlight recovery as well to tone down the highlights while maintaining a pleasing value for the midtones. Here is the resulting preview with rendering into ProPhotoRGB.
    In this case, I was able to avoid clipping. However, when the image is printed or viewed on a display with a limited gamut, some clipping would undoubtedly occur.

  • The u, j, m and 7 keys on the keyboard are not functioning properly on my macbook air. Please Help!

    The u, j, m and 7 keys on the keyboard are not functioning properly on my macbook air. In its place are a random assortment of keys (Ex - u = "eqrw" or "IOUY"). This randomly happened when logging back in after sleep mode. No liquid damage at all. Please help!

    OK, I fixed the problem by doing a SMC (System Management Controller) reset as follows:
    1. Powered off my MacBook and removed everything connected except for the power chord.
    2. When powered off, I held "Shift" + "ctrl" + "Option" + "Power button" for 5 seconds or so until the little light on the front started to blink rapidly.
    3. Powered up my Mac, which took a little longer than usual to start and tested the "missing" keys which now works perfectly again.
    Just added another couple of years usage with my aging mac :-)

  • Clock and date settings are not saved

    clock and date settings are not saved in lion

    I'd give AppleCare a call.
    AppleCare Support Phone Number: 1-800-275-2273
    open 6am to 6pm Pacific Time
    International Technical Support Numbers
    http://www.apple.com/support/contact/phone_contacts.html
    You may want to look under date & time and set the clock from the internet.  At least you will have the correct time after a while.
    RObert

  • I have a macbook pro with OSX Mavericks 10.9.5 and some keys that are not working. Specifically, the enter/return button, the "p", "0", ";", and all the function keys.  What's really weird is that happens randomly.  I've never spilled anything on it

    I have a macbook pro with OSX Mavericks 10.9.5 and some keys randomly are not working. Specifically, the enter/return button, the "p", "0", ";", and all the function keys.  What's really weird is that happens randomly.  I've never spilled anything on it, and I can't for the life of me figure out how to fix this.  Can anyone help?  of course this happened after my warranty expired.

    **update**
    I don't know if this will help someone but I am posting this for that purpose.  In the past when I first had this problem, I'd read a post somewhere (sorry, long ago, don't have the link) where an individual was having the same problem and they stated that when the MBP got heated, that's when the keys would stop working, and they went into the MBP and jiggle some stuff around (a specific wire, I'm not electronically inclined so I know NOT of what they spake!).  Well I didn't want to do that but it always stuck in the back of my mind.  I had given up, really, and was planning to take my MBP to the apple store.  But by chance one night I left my MBP on the floor where it's cool, and when I turned it on, the problem went - poof! It seems there was some validity to the post that spoke about heat, because my problems started when I would stream foreign dramas on my MBP for hours at night, and I would hear the fan going off all the time, and in the mornings, my "p", "enter", "0", ";", and all the function keys would stop working. 
    So, maybe try keeping the MBP in a cool place when it's off.  Since I've started doing this overnight every night (keeping it on the cool floor, out of reach of any big feet), I have not had a single problem with my keyboard.
    Hopefully this might help someone.

  • TS3048 I have just purchased a new apple cordless keyboard.  The numeric line of keys along the top are not functioning as they should.  For example I am unable to get a question mark or a forward slash.  I have tried holding down both shift and alt keys.

    I have just purchased a new apple cordless keyboard.  The numeric line of keys along the top are not functioning as they should.  For example I am unable to get a question mark or a forward slash.  I have tried holding down both shift and alt keys.

    Thanks for prompt response - I tried what you suggested but I'm afraid it has not helped.  It seems as though the line of number keys along the top aren't actually doing what is printed on them.  Some are OK, but the further towards the right hand side of the keyboard you go, the less predicatable it becomes.  So whilst the second key from the left gives me 1 and ! when holding the shift key, by the time I get to the 6 when I press and hold shift I get ^ rather than & symbol which is what is actually printed on the key.  The & symbol is actually on the next key along - and when I hit the key with 8 I get * rather than the ( which is printed on they key but actually located on the next key along.  Things get even more muddled by the time I am over on the right hand side as rather than a question mark (I have had to type the word as I cannot find the symbol anywhere!) I get this _ and the other symbol marked on the key is a comma, but I get - instead.  It is going to drive me mad if every time I want to type something it is a guessing game....!  What do you suggest - question mark

  • Phone will not vibrate and all my settings are correct.

    Phone will not vibrate and all my settings are correct.

    If you're sure Settings are correct then do a reset (Hold Sleep/Wake and Home buttons about 10 secs or more till Apple logo appears)
    Note: You will not lose any data.

  • I just downloaded lightroom 5.6. Why do I have fill light and recovery but not highlights and shadows?

    I just downloaded lightroom 5.6. Why do I have fill light and recovery but not highlights and shadows?

    Your photo is using legacy processing version (2003 or 2010). Click the lightning bolt up near histogram, or use process drop-down at bottom in dev module (right panel, camera cal section) to use current processing version (2012).

  • Hi I'm new to Mac. I have a macbook air and for some reason the top keys, ec, f1 etc etc are not functioning and emitt the non function noise when pressed. Also the volume keys don't adjust the volume. Have I done something to disable them?

    Hi I'm new to Mac. I have a macbook air and for some reason the top keys, ec, f1 etc etc are not functioning and emitt the non function noise when pressed. Also the volume keys don't adjust the volume. Have I done something to disable them?

    I don't have the same version of OS X here but try System Preferences>Keyboard. Is there an option similar to "Use the F1, etc, keys as standard function keys"?
    If so, and it has a checkmark, uncheck it & see if that does the trick.
    ~Lyssa

  • My iPad was changed to Suomi language and I can't set it back to English the settings are not the same so that does not help

    iPad changed to Suomi language can't set it back to English. The settings are not the same as the advice given by support???

    Just follow this:
    http://support.apple.com/kb/ht2371

  • Highlight and Shadow Recovery in Aperture?

    Hey folks,
    I am still pretty new at using Aperture 3, but I was very curious to know if it has a similar feature as Lightroom 4 does with its highlight and shadow recovery feature. I am really impressed with how this works in Lightroom 4 and would be curious to see if this would work in Aperture. Thanks!

    DiploStrat wrote:
    Andy, you owe us an advanced tutorial on shadow recovery.
    I find it interesting that 3.5's "Auto Fix" always seems to include a healthy dose of shadow lift.
    LOL. I haven't forgotten Frederick, honest. But a few things have been happening that put it down the priority list.
    And, I've become increasingly frustrated at the way things are being run over at DPR, in particular the way the so called moderators in some of the forums are deleting content, not only for alleged rule breaches but based on their personal opinions and friendships it seems. Complaints either go unanswered, or given the generic 'moderators actions can't be discussed'. Gee - 'Can't be discussed', hardly surprising some of them feel they have the power to do what they like! If it can't be discussed, my only real power is to take my clicks and content somewhere else.
    So I'm in two minds if I want to publish it on DPR or just leave it until my new site is ready.
    But it's actually a partially related subject that has really side-tracked me. I've beed in touch with the developer of the old Enfuse Edit Plug-in for Aperture to find out if there were any plans to make it compatible with Aperture 3.
    He explained he doesn't have the resources to work on it at the moment, so I offered to take the Plug-In and make it compatible.
    I've now done that and have it working on my system, and I'm just putting the finishing touches to an installation script to work around some gatekeeper/quarantine issues. The first version is going to be a little rough as it's essentially just a recompile of the old beta, with a couple of inelegant work arounds for the issues encountered. If there's any interest in it, I'll start finessing it a little.
    If you're unfamiliar with Enfuse, it's a command line program that takes multiple images with different exposures a blends them together using the best exposure from each (base on some settings).
    enfuseEdit is an Edit plug-in for Aperture where you can select the images to be blended and have the result returned directly to Aperture.
    Here's a small example I made with the plugin:
    The two exposures (actually 2 versions of the same raw with different exposure adjustments):
    And the 'enfused' output:
    Andy

Maybe you are looking for