Lightroom 4 - Banding/Posterization in shadows

Hi,
Ever since I upgraded to LR4, I've noticed severe banding/posterization in the shadow areas when using the graduated filter with reduced exposure or using the vignette to on Amount -100.
I previously used these tools in LR3 to create fade to black areas in my shots, but have noticed that now, instead of a nice smooth gradient, I get a hard black edge, with a green band stippled into the black before returning to (in this particular case) a grey backdrop rather than a smooth transition from black (like I used to get with LR3).
Initially I thought it was my GFX card as my main one died and I temporarily replaced it with an older card. However, I recently purchased an Nvidia GEForce 630 as a replacement and it's still an issue. I also exported a file and viewed it on my partner's HP latop and the issue was still there.
I googled LR4 shadow banding to try and find answers but didn't have much luck. Is any one else experiencing this issue, or do I just have some sort anomoly?
Tech info::
Windows 7 64bit
Lightroom 4.1
Dell 2408 WFP monitor
GeForce GT630
Spyder 3 Calibration
Any help would be appreciated as at this point I'm not sure whether it's something with my system or LR4.
Thanks in advance.

There is an issue with the 'local tools' in that they are applied before the global tools, which can reduce dynamic range in the highlight and shadow areas. This may also be the case for the Post-Crop Vignetting tool, but I haven't tested it.
http://forums.adobe.com/message/4612100#4612100
Why it only shows up with certain cameras is probably due to the available dynamic range in the individual raw image files.
Another possible issue that could be contributing to the "banding" artifacts is your Dell 2408WFP wide gamut monitor. Using a wide gamut monitor with 24 bit display data stretches the available gradations (16,777,216 colors) over a wider range, and provides less smoothness (i.e. banding). Many wide gamut monitor users will argue that this is NOT the case for them and that may be true. But anytime you use "extreme settings" in LR (100% settings, two graduated filters/spot tools) you're setting up a situation where banding may become visible. Try exporting an image with banding using TIFF, ProPhoto RGB profile, and 16 bit data, and then view it on another system equipped with a standard gamut display. You can also download this Ramp test file from AMD's site, import it into LR, and see if you have visible banding:
http://www.amd.com/us/Documents/ramp.psd
Photoshop supports a full 30 bit display data path when using a 30 bit graphics card, but Lightroom only supports 24 bit display data.
In short you have multiple things in LR that may be causing the artifacts you are seeing. My best advice is to use the global controls more heavily (Highlights, Shadows)  and lighten up on the locals, since they can reduce the dynamic range in your image.

Similar Messages

  • Severe banding issue in shadow areas

    Short Version: Having severe banding issues in shadow areas in Lightroom. Need to know how/what to set my color profile to to fix this issue. Lengthier description and images below.
    I have read several posts here in the Lightroom forums about others who are experiencing the same type of banding issues, but I haven't seen any definitive answers on how to solve the problem.
    I was able to take a couple screenshots of the issue that I am seeing. The image looks very different in Photoshop, Lightroom, Windows Photo Gallery, and also rendered in IE7. Screenshots of the image in Lightroom and the image in Photoshop are posted below at a 100% crop of the affected area. The first image is how it appears in Lightroom and the second image is how it appears in Photoshop.
    From what I have read elsewhere the problem has to do with how Lightroom uses color profiles. I do not have much experience with color profiles, so I'd like to get everyone's recommendation on what color profile I should be using, and maybe a link to some information on setting color profiles and how to fix this issue. The image looks so much different in Lightroom than it does elsewhere, that I can't see myself being able to trust Lightroom to process my images.
    Some info on my setup. Shoot RAW with Canon Rebel XT. Use a Dell with Pentium D running Windows Vista. Monitor is a Dell 2007FP, and currently I am using the Dell 2007FP color profile as far as I can tell.
    Screenshot of image with banding in Lightroom
    Screenshot of image as displayed in Photoshop

    Don, Bob!
    I think it is quite obvious that the Eric's problem is not banding per se (and the related cure by fiddling with black setting), but rather about the mismatch between how the file looks in LR's Develop 100% view and how the same file (or an exported file) looks in Photoshop.
    Eric!
    I am afraid there is no definite answer to this problem. Indeed there are a number of Windows users that have reported this problem. A very exhaustive and inconclusive thread is this:
    http://www.adobeforums.com/cgi-bin/webx?128@@.3bc3578d
    The bottom line so far seems to be this:
    LR on Windows uses Windows ICM to generate how the image looks on the screen, while PS uses Adobe own engine to generate this. Somehow this set-up appears not to work reliably with LR - the on-screen image in LR 100% develop differs from the same file's appearance in PS or other color managed applications. The mystery here is that other applications that seem to use Windows ICM still manage to show image correctly, but not LR. But anyway, the Windows ICM appears to be the culprit here.
    The amount of difference people see depends on the complexity of the monitor profile used. LUT based Version 4.0 profiles will be affected worst - not only shadow detail, but the overall tonality and colors may be off. The best match is achieved with simple matrix based version 2.0 profiles - on my machine the mismatch occurs only in deep shadows were I see banding/splotchiness in LR and only under certain Develop settings.
    (Incidentallly, on Windows XP (and older) machines one should ALWAYS use ver 2.0 profiles, as Windows ICM does not support ver 4.0 profiles. I also think that Windows ICM cannot handle LUT based profiles correctly. My own experiments showed that using LUT based monitor profile resulted in mismatch between PS CS2 and other applications (like Canon DPP), not only LR. BTW - as you are using generic monitor profile, I can almost bet that it is a matrix ver 2.0 profile (good thing).)
    I am curious about the Vista thing though. I had certain hopes that this image appearance problem in LR would be eliminated on Vista, as it uses the Microsoft's new Windows Color System which incororates an updated ICM that now supports ver 4.0 profiles and reportedly has many bugs of the previous ICM fixed. However, if your report is true and the image mismatch is not due to some other factors, then it seems that Vista does not solve this.

  • Raw Conversions - Posterization and shadows EXACTLY like H.264 ??

    I was playing with my lil brother's new 17" iSight iMac this weekend (nice xmas present!). Anyway, I've always noticed weird things happening in the shadows of H.264 movie trailers and such.
    It occured to me that the noise and "posterization"? looks identical in Aperture as H.264 ..
    Can anyone else comment on this? Perhaps Apple is using the same routines from H.264 and applying them to the images?
    Curiously,
    Aaron

    okay.. maybe it's just pure noise, then?
    It had nothing to do with his iMac.. it's on my machine.
    ~Aaron

  • Banding/Posterization Artifacts in Premiere Timeline & Export

    I am having an issue with Premiere CS6. Just for some details...I am on a 2013 27" iMac. 32gb ram, NVidia GeForceGTX 680MX.
    I am editing 5D Mark iii footage. I am experiencing bad compression when editing and exporting the footage. I have tested all forms of export settings (VBR 2, higher bit depth, maximum bit depth, uncompressed Animation, etc)...all looking the same as the timeline does. Which is leaving me to believe it has something to do with the timeline. I am NOT using previews to export...however, under Sequence Settings, I have tried to use Maximum Bit Depth & Maximum Render Quality.
    All getting the same results. The actually footage does not have bad compression, and I am testing my exports without doing any color correction or anything to them. Just testing how the export out of the timeline.
    Within the preview monitor, the footage looks fine, within the sequence monitor...it looks terrible. Please look closely at the gradient in the sky to see the artifacts. I have attached an screenshot.
    Your help would be greatly appreciate. I do understand that I will get some compression when exporting for the web using .h264... as I am quite familiar with compression. However, in this situation...it seems to be in my timeline before I even do any edits.

    I would like to add some things. I have been struggling with this all day...and am noticing a coorilation between using plugins that are creating this effect. One is WARP STABILIZIER, and the other is TWIXTOR. In both situations...you can see that this banding is being created when enabling them. Here are examples. Look at the gradient in the sky.
    This is Warp Stabilizer Off -
    This is Warp Stabilizer On -
    This is Twixtor Off -
    This is Twixtor On -
    Note the banding going on in the sky. There are no other effects applied to the clip at this time. Just so you can compare side by side...here is a picture with twixtor on with the source footage beside it -
    I could REALLY use some help here. I have 5 projects I gotta get done, and I am totally stuck here. I have tried everything! Thanks!

  • Different color issue in Windows Lightroom? Banding?

    I can't tell if I'm running into the same color issue other users are seeing, or if I've got my own issue going.
    I see what looks like color "banding" in Lightroom when I'm looking at the preview of a raw image. It happens most often in the shadows, where the fine gradations between shades are lost and the entire shadow area becomes one "blob" of the same color. (It looks like what happens when you look at in image in 8-bit display, after booting in Safe Mode.)
    I see this effect for RAW files from a Canon D60 (.crw) and Canon 30D (.cr2). I have a dual display setup, with a 24" external monitor (a BenQ WP241Z) and a laptop display. I'm using the color profile for the 24" monitor I obtained from Adobe Gamma until I get access to a colorimeter. Under the Color Management tab in the control panel, it shows the correct profile associated with my monitor.
    Opening the preview of the same image in Lightroom and Faststone on the 24" monitor shows a stark contrast -- I don't see the "banding" at all in Faststone. Instead, I see a gradual transition between shadow tones.
    Any idea what I'm doing wrong? It seems odd for Lightroom to look so *ugly*.
    Thanks!

    Hi, I think you might be seeing the same thing I experienced with my night shots. I imported them with the "none" preset, which actually means using Lightroom default settings.
    There was banding in the shadows, exactly as you describe, whereas Digital Photo Pro (canon's s/ware) showed it fine. I started playing around and found out the default setting of "Blacks" to "5" was the problem. Setting it to "0" took care of the banding. Hope that works for you.
    If so, and if you do import a lot of pics which require "Blacks" at "0", a good way to do this is to set "Blacks" to "0" and save your own preset, for use with those pictures that you know will show banding.
    Hope this helps,
    Kai

  • Shadows differ in Photoshop vs Lightroom

    SUMMARY: Photos saved in Adobe RGB (1998) from Photoshop has much better shadow performance than the same unmodified image in Lightroom. Artifacts pop up deep down in the shadows, despite the rest of the image is rendered almost identical in the two programs. I can not find a way around the issue, and I wonder what it is?
    DESCRIPTION:
    I have scanned photos at high resolution (profiled by inCamera), which are treated and optimized in Photoshop CS3 and then saved as JPEG quality 12 in Adobe RGB to be imported into Lightroom 1.3.1 on a MacBook Pro. (I don't want to use TIFF since those are more than 100 MB each, whereas the JPGs are just under 10MB.)
    In Lightroom, I make sure there are no develop settings being applied by using the preset called Zeroed. But since Lightroom has touched the image, metadata is changed and written to the file, and when I reopen the image in Photoshop, it invokes CameraRaw! A bit strange, but I guess it is because LR has written some metadata to it, although all the develop settings are zero(?)
    Except for those deep shadows, the image look identically in Photoshop and Lightroom, so profiles appear ok. My monitor is a good one: SpectraView 2690 profiled by Gretag eye-one and SpectraView Profiler 4.1.7 (same as basiccolor).
    Shadows are deep, and have been lifted in photoshop, so they are a bit noisy and grainy, and it is really critical to get those right without artifacts. When zooming to 1:1, and just looking at a deep shadow section, it is obvious that the carefully balanced noise and black point settings are being mangled by Lightroom, creating blotchy artifacts and color casts.
    To make sure it was not a cache issue, I deleted all previews, thereby forcing LR to rebuild them, and I also restarted the machine. It is also pretty strange that the shadows look different in the Library module from the Develop module!?
    The following are links to screen captures of that dark section (PNG images, between 600 and 800 kB each):
    (These are dark, so close everything brighter than mid gray on your screen, otherwise you won't see much. The images are in Adobe RGB, but it doesn't really matter if you see them with the correct profile or not, since the important and strange thing is that they are different. The best is of course if you download and view them in Photoshop.)
    In Photoshop: http://photo.bragit.com/pics/Shadow_LR_PS/PS.png
    In Lightroom, Library module: http://photo.bragit.com/pics/Shadow_LR_PS/LR_L.png
    In Lightroom, Develop module: http://photo.bragit.com/pics/Shadow_LR_PS/LR_D.png
    Lightroom uses Perceptual rendering intent, and claims to be using ProPhoto internally.
    To see if I could change settings in Photoshop to make it look like Lightroom (just for testing purposes), I changed the color settings in Photoshop to perceptual and also tried the Apple CMM instead of Adobe (ACE). But that didn't make any difference.
    To see if the reason Lightroom makes it bad is caused by a roundtrip to ProPhoto, I converted the image in Photoshop into ProPhoto, and then to my monitor profile; but also in this case it didn't make any difference.
    QUESTION:
    So, there must be something else causing this.
    What is it?
    I want Photoshop to be the norm, and don't like Lightroom inventing shadow casts of its own. But I want to make slide shows and prints from Lightroom...
    Regards, Harald

    >In Lightroom, I make sure there are no develop settings being applied by using the preset called Zeroed. But since Lightroom has touched the image, metadata is changed and written to the file, and when I reopen the image in Photoshop, it invokes CameraRaw! A bit strange, but I guess it is because LR has written some metadata to it, although all the develop settings are zero(?)
    The way to prevent this is to NOT use a preset. Lightroom will not apply any settings to non-RAW files. Second, you should NOT enable "automatically write metadata to xmp" as you appear to have done in Catalog Settings. This will ensure that Lightroom will not touch your originals and will make Lightroom much faster.
    >Shadows are deep, and have been lifted in photoshop, so they are a bit noisy and grainy, and it is really critical to get those right without artifacts. When zooming to 1:1, and just looking at a deep shadow section, it is obvious that the carefully balanced noise and black point settings are being mangled by Lightroom, creating blotchy artifacts and color casts.
    Probably a rendering intent issue (see below)
    >It is also pretty strange that the shadows look different in the Library module from the Develop module!?
    This is due to the fact that Library uses a preview jpeg that is generated from your file in adobeRGB. You do NOT see the actual data in Library. In develop, Lightroom renders the file into prophotoRGB. Perceptual rendering into the monitor profile from prophotoRGB will give different results than perceptual from adobeRGB, even if you have the same absolute color data. This is why you want to have no perceptual rendering intent defined in your monitor profile (see below)
    >Lightroom uses Perceptual rendering intent
    Indeed, and this is how it differs from Photoshop. You cannot setup Photoshop to use perceptual rendering for the screen profile. If your monitor profile has both intents, your display will differ between Photoshop and Lightroom. To get rid of this recalibrate using your profiler, making sure you only create a relative colorimetric intent, forcing Lightroom to go through that.
    >To see if the reason Lightroom makes it bad is caused by a roundtrip to ProPhoto, I converted the image in Photoshop into ProPhoto, and then to my monitor profile; but also in this case it didn't make any difference.
    Apart from the fact that Lightroom doesn't use prophotoRGB but uses a linear version of prophoto (i.e. a color space with prophotoRGB primaries and a linear gamma instead of 1.8), you should get similar results if you use perceptual rendering when you convert into your monitor profile. Lightroom uses the exact same color engine as Photoshop, so if you set it up correctly, you should get almost identical results.
    Lastly, many of these differences seen between photoshop and Lightroom are caused by corrupt monitor profiles. Many of these are canned profiles from the monitor manufacturer. Trash them and never touch them again. Only use profiles from a hardware calibrator. Also, make sure your graphics card driver is up-to-date. Lots of these problems are caused by outdated graphics drivers.

  • Shadow slider banding artifacts in PV2012

    I've been pixel peeping the same images I have uploaded in this post (it is still available for download) and found some artiafcts. Note the banding in the shadow under the ski tip:
                            Click the image to view at 100%.
    I've been dragging a lot of sliders back and forth and found that the Shadow seem to be the root cause. Though, resampling caused by Lens Corrections seems to make matters worse. Also, high Noise Reduction seems to exaggerate the issue, wiping the noise that naturally interferes with the banding artifacts.

    FYI, it's been fixed in the final release.

  • Current Lightroom / Camera Raw Camera Profile for Sony ILCE-6000 inaccurate: green cast in shadows! Capture one better! Please fix it!

    Hi folks from Adobe!
    Please take note that the current Lightroom / Adobe Camera Raw Camera Profile for the Sony ILCE-6000 is very inaccurate: There is a serious green cast in the shadows!
    Capture One Express for Sony (which is free by the way) renders a lot more correctly!
    Please correct this, since I'd rather buy the coming LR6 because of keeping my established workflow instead of going the Capture One route.
    A good example can be found in the dpreview forum "LR5 A6K shadow pulling, a mess! Adobe LR is broken? "
    Or search for Philp Reeves 3 weeks with the Sony A6000 review "3 Wochen mit der a6000", where he compares it to the Sony A7, using both times Lightroom to push the shadows.
    The Sony A7 is fine where earth looks like brown earth, the A6000 picture looks like grass instead.
    Please fix this! This is a high volume camera frequently bought by enthusiast or as second body for FF photographers. That would be really great!

    I am talking about the two raw files linked in the very last post of page 6 of the Reeves comparison thread, not JPGs or screenshots of unknown manipulation.  In LR they both say f/11 and ISO 100 and have a similar tone, but one is shot at twice the shutter speed as the other.  This side-by-side is using Adobe Factory Defaults for each image where the profile is Adobe Standard, the toning sliders are all 0, tone-curve linear, and the Sharpening and Color NR are 25:
    However, when I look at the camera-embedded JPGs, side-by-side, the 1/80th image on the left is darker than the 1/40th image on the right, as expected given the reported shutter-speed difference:
    And it is indeed the darker image that has more shadow problems, also as expected.
    When I do manipulate the darker (a6000) raw file in LR, I do see that the shadows are greenish when brightened unlike most other cameras which usually show magenta, which is the combination of the blue and red sensors showing more noise because there are half-as-many photosites as compared to the green, so I am seeing what people are complaining about and would expect shadow noise to be purple not green, I'm more concerned that these two example raws aren't actually comparable due to apparent differences in exposure.  It is also odd that the lens listed in LR is different than the lens listed in the filename, so either someone has mistakenly or deliberately renamed the file wrong or someone or something has changed the EXIF parameters that LR is reporting to be the same when they're really not.

  • Images opened in ProPhoto RGB has heavy banding

    HI,
    I am a photographer, and I shoot Canon 5D and 1Dmk3, shooting RAW and in AdobeRGB.
    If I open a correctly exposed CR2 file in Camera Raw, applying no changes at all to the photo, open it as ProPhotoRGB 16-bit, I get heavy banding in the shadows and gradients when the image opens in PS.
    If I then try to use a brush (normal soft tip), I also get heavy banding and posterization on the transitions between the different shades of that brush.
    I have double checked that my image, when open in PS, is indeed 16 bit ProPhoto RGB.
    If I open the same image in Camera Raw, but change the color space to Adobe RGB, these issues are gone!
    Late 2013 27" iMac with 24GB RAM, 750GTX with 2GB VRAM.
    RUnning OS X Yosemite 10.10 and latest PS CC 2014.
    DIsplay is calibrated, and these issues does not show when opening the same CR2 in Aperture.
    ANy ideas.

    I Should add, that if I create a new empty document with the same settings (ProPhotoRGB/16bit/300dpi), the same brush works fine.
    I recently did a shoot where I used a dark grey seamless background, and any given image looks great in Lightroom and ACR (imported as DNG), but when editing the same image in PS with the settings above, I get banding, pixelation, and posterization in the shadows, and in the light falloff on the grey background.
    Using raw files directly makes no difference from a DNG version...
    Again, change just the color space from ProPhoto to AdobeRGB, issue goes away most of the time.

  • Color checker profile (in lightroom) only work for JPEG file?

    I followed all tutorials for color checker-lightroom and succeeded to sync my JPEG images into the camera profile I want.
    However, these are JPEG images from the camera. I want to work with raw file or at least PSD file.
    So my retouch pipeline was:
    - opened my raw file
    - save it as PSD
    - back to lightroom and open it there
    - and intended to sync this PSD file image with the camera profile
    But this is impossible to do, because suddenly all the camera profile  options (the ones we generated via color checker passport and the  default adobe profile) are dissapeared. The only option of camera  profile now is "embeded".
    That's it. So does it mean that I have to convert my raw file into JPEG first ?
    If yes, it's very unpractical and I can loose a lot of data bcause I  thought saving it to PSD or TIF keep the image data better than into  JPEG.
    Confused..
    Thanks for your point of views.

    In LR Preferences / External Editing you can control things about the LR-to-PS transfer:  the file format (PSD/TIFF), the color profile (sRGB, AdobeRGB, ProPhotoRGB), and the bit-depth (8 vs 16). 
    My Edit-in-Photoshop is set to use PSD, ProPhotoRGB, 16-bit.  I have chosen this because it gives me a large colorspace, with millions of distinct colors and a file-format that can contain smart-layers and other Photoshop-specific things.  LR, itself, is using a color-sapce as large as ProPhotoRGB and I don’t want to lose colors just because I’m editing in Photoshop, at least not until I’ve finished my adjustments in PS.
    A large colorspace with millions of colors gives more freedom for extreme adjustments before color banding (posterization) or color-shifting (channel clipping) at the bright end of the histogram.  The downside is that before I can save my photo as JPG for general viewing is that I need to set PS / Edit / Convert Profile to sRGB and PS / Image / Mode to 8-bit.
    It sounds like you are saving your photos as 8-bit ProProtoRGB not realizing you also need to convert to sRGB as your color profile.  For browsers and operating-systems that don’t do color-management correctly, which is most browsers and Windows-halfway, your ProPhotoRGB color numbers in the JPG are being interpreted as sRGB which makes them much duller and less saturated.   It may be that you have your External Editing set to 8-bits, which is not a good idea if you are using ProPhotoRGB as your colorspace, so set it to 16-bit.

  • Editing timelapses in Lightroom- looks very different if there´s a small change within the frame

    Hi
    We´re having some serious issues with editing timelapses in Lightroom (5.6). What seems to happen over and over again, is that if there´s a small change within the frame (such as a bird flying past, people walking), the editing result varies greatly compared to the previoius frame. It´s easiest to understand what I mean by viewing the examples below.
    Here there´s one picture without a boat in the frame, and a few seconds later there´s a boat in a small part of the frame. The camera is set to full manual, and the two JPGs which show the unedited pictures shows that the background and sky in both pictures look exactly the same. However, after pasting the same editing setting on both pictures, the picture with the boat looks vastly different (shadow areas are much darker). It´s the same result weather it is a white boat, a black bird or a person walking in/out of the frame. The picture gets much darker, and leads to some serious flicker in the timelapse which can be impossible to get rid of.
    I assume that as there´s a small change in the histogram when the boat enters the frame, this change affects what Lightroom thinks of as shadows/highlights on so on? The example below has some heavy editing applied (shadows up, highlights down, clarity). You can see the settings that have been adjusted in the screenshots below. Does LR change what it considers shadows/highlights based on the histogram, or are there standard settings? If this is the case, it would be much better for timelapsers if Lightroom had standard values for what is considered shadows/highlights, so that two pictures where the only difference is a person walking on the street or not, would look the same with the same editing settings applied. What I find strange if LR works like I´m asking here, why does the picture get darker whether it is a white boat or a black bird changing the histogram slightly. Shouldn´t they then have the opposite effect of each other?
    Any ideas what is causing the difference, and what I can do about it? Thanks!

    In these forums you are only talking to other users like yourself, not Apple. Be sure to repost your info in the channel Apple has set up for it:
    http://www.apple.com/feedback/imovie_iOS.html

  • Posterization exporting the project

    Hi all,
    I have a problem with iMovie '11 when exporting my project.
    I have many projects containing photos and movies taken with an AVCD camera. The problem is that when I try to export the projects, the photos and the video footage have a great amount of posterization: black shadows and also dark colors look very bad, with very visible pixels, making the whole video look very grained.
    Can someone help me with this? Do you know any solution to this problem?
    Thanks for helping!

    Does someone know if in FCP X is there some posterization issue like in iMovie? If this will solve the problem, I'm going to move from the latter to the former.
    Thanks

  • Does duplicating layers from an 8-bit PSD reduce the color depth of a new 16-bit edit?

    I have been using several versions of Photoshop over the years starting with CS3, then CS6, and finally CC. Through 2012, all my RAW files were converted using 16-bit color depth in ACR. However, in examining my files recently, I noticed all were in 8-bit color-depth, which likely happened once I upgraded to CS6 and ACR left 8-bit as the default. As such, I now have hundreds of images that I wanted to edit in 16-bits that have been converted to 8-bit starting with my ACR export. The files are all RAWs from cameras like the Canon 5D, 5D Mark III, Olympus OMD EM5, and Sony RX100.
    I have 8-bit PSDs of my edits of these files which contains multiple layers. I use features from the Nik and Topaz collections for noise reduction, contrast enhancement, black and white conversion, and sharpening. I also use layered Photoshop features like Selective Color. I want to know if I can simply duplicate the layers from the 8-bit PSD files onto a new 16-bit RAW converted background layer rather than re-edit each and every file. There would be no change in the crop of other reasons why the layers would not match up, but I am concerned that duplicating those layers might throw away the benefit of moving to 16-bit since they were created in an 8-bit color-depth.
    As a test, I looked at a few files where I had pushed the shadows and colors to an extent and duplicated the layers from an 8-bit conversion to a 16-bit conversion and could see no difference. I am not sure if this is because Photoshop has become very good at reducing color-depth without a perceptible difference or if I am throwing away information in moving the layers.
    I work off of a fairly modern computer and a top-end Eizo CG276 self-calibrating monitor and good video card. I am extremely sensitive to color and shade changes as well.
    Thanks for any help, I am a bit stressed at the thought of re-editing hundreds of files from step 1, but it is important to me that I not throw away color information and it is better I start re-editing now rather than years from now.
    Ketan

    While raw file contain a 8Bit jpeg previews image in some color space. The RAW sensor data is not a color image and has no color space and the bit dept of pixels depend on the manufacturing.  Most sensor produce one value for each pixel  10 to 14 bit seems to be common.   Sensors only measure the light intensity not color.  If front of each pixel sensor is a color filter which lets Red or Green or Blue light be measured for intensity.
    A RAW converter can convert your sensors RAW data into a color RGB image in any color work-space in 8 or 16 bit color depth.    No Adobe update went around and scanning your computer looking for 16bit color depth images and convert all of them to 8bit color.  Your ACR workflow settings may have been change from 16 bit color to 8 bit color by you or set to 8bit by some update or script used.  So you current ACR work-flow setting may be converint tou raw datya into 8bit RGB images. As long as you have you raw files you can reprocess these  to produce 16Bit color RGB Image by makinf the proper ACR work-flow settings.   You can also change your 8bit image to 16 bit image mode.  However this will not recover any color quality lost or posterization that has set in..  It will give you a bit more latitude using Photoshop filters which may help you not get banding posterization.

  • Slideshow image quality/color rendering

    I´m quite frustrated after discovering that some of my images look quite poor displayed by the slideshow module. My situation ist as follows:
    LR 5.2 running on Mac OS X 10.8.5, 1:1 previews are rendered, preview quality is set to high, and I´m using a sample image showing a dark cloudy sky with some fine gradients; my slideshow preset doesn´t use any borders as I read this often causes quality issues.
    When I´m in the Develop module, there is no problem at all, even in fullscreen display mode on my 1920x1200 display the gradients are perfectly rendered.
    In Library module, when displaying fullscreen, quality is okay, but I can see some slight difference compared to the Develop module - which I understand after reading that in Develop the output is based on the actual raw data, and in all the other modules on rendered previews.
    Now, when in Slideshow module, the image quality is significantly lower than in Library and I see some quite obvious banding in the gradients. I don´t have problems with blocking artifacts but the banding/posterization is considerably worse compared to a JPEG export with a quality setting of, for example, 75.
    I can´t imagine LR´s slideshow tool would be working with a lower color depth than the 8 bit as in standard JPEGs, right? Did I miss any of LR´s parameters that influence the image quality of Lightroom slideshows or of the previews used therefore? Otherwise do you have some other explanations or hints for me in order to get this fixed? We do everything to capture our images in the best possible quality so we should also be able to present them properly after all...
    Thanks a lot for any advice!
    Toby

    In-Lr slideshow images look like crap on my system too (dull contrast and de-saturated shifted color).
    My guess is some issue with icc-profile/monitor-profile or something, but I'm not qualified for assessing.. - could just be a bug in Lr that only bites some, dunno...
    I use ShowBiz instead, which works well on my Windows box, and it should also work on your Mac box.
    Rob

  • InDesign black actually 91%K

    Hi all,
    I've seen this discussed in many forums, but I have yet to come across a satisfying solution, so I thought I'd try to find an answer.
    The problem seems simple:
    For the sake of discussion let's imagine a single page in inDesign with one word or graphic shape in the middle, set in black, using the default indesign 'black' swatch. This is a greyscale document, and will be sent to an off-set press for printing with no colour signatures. Just a black plate.
    I export this page as a PDF and view it on screen: the text doesn't show black, but more of a grey. I thought no problem, it's just showing me an approximation or a proof black that shows how it will be on paper (if it is set in RGB, it comes out nice and black).
    So to test, I open the PDF in photoshop to check the levels. Lo and behold, the black is not 100%, but 91%K.
    Why is the black not black? And should I worry about this? (Images with a 100 seem to come out black just fine).
    Anyone any thoughts?
    Thanks in advance.
    eu.

    In my opinion it's more important to render a solid black and keep the relationships between the shadows and the midtones than it is to preserve absolute percentage values.
    But that doesn't happen if you export from SWOP to 20% Dot Gain and the appearance of black set to rich. You do preserve 100% black, but you don't preserve all the other relative values—the shadows get lighter and the highlights get darker than the original.
    Look at these PDFs and you'll see the problem—the swatch labels are the starting CMYK black values.
    This is a Photoshop5 to 20% dot gain conversion:
    http://www.zenodesign.com/forum/PS5-20.pdf
    Here's SWOP to 20% with rich black turned on:
    http://www.zenodesign.com/forum/SWOP-20-RichBlack.pdf
    Here's a capture from Acrobat. The SWOP conversion is on the right—the image tonal range is flattened and the blend bands in th shadow end

Maybe you are looking for