Banding in broad color space????  grrr

I'm on an old laptop, PS 5.5.  I have a properly exposed iso 1800 D600 jpg
captured in adobe rgb color space.
I use camera raw to open this picture in photopro space and 16 bits to
avoid banding and yet if I lift the curve a tiny bit or any other brightening trick
immediately there is banding.  What?

Steve Zeeeee wrote:
What else happens with this choice and how does it affect photo editing?
As far as I know, with Photoshop CS5.5 Standard edition you'll have all GPU-dependent features, so you might just find the screen updates a hair slower - or not, modern processors are pretty fast, even in laptops.  The primary difference is that the Adobe Color Engine is executed in the CPU, rather than the GPU, and as such it produces more accurate results.
With Photoshop Extended versions and/or CS6 I think there may be actual GPU-dependent features that are hobbled or disabled if you use Basic mode GPU operations, though to be honest I've lost track of all the permutations.
Try it and let us know whether Basic mode supports all that you do, just with more accurate color.  It's what experts do when we need to use an alternate configuration setting to work around a problem.
By the way, the issue does not present itself even in Normal or Advanced modes if you choose to make the Adobe RGB 1998 profile your working space.  Since few output devices provide gamuts larger than Adobe RGB it's a possible alternate workaround.
-Noel

Similar Messages

  • CFIMAGE error "Numbers of source Raster bands and source color space components do not match"

    I keep on getting this error when trying to upload a .JPG file. This error is not present for all jpegs, just for some of them.
    I am running CF 9 on a Windows 64-bit server.
    Any suggestions on how to modify cfimage tag or workaround this?
    Thank you!

    i have found a solution to this problem.
    first, install ImageMagick (http://www.imagemagick.org/script/index.php)
    then, detect whether or not the image is valid
    <cfset image_path = "c:\path\to\image.jpg">
    <cfif not isImageFile(image_path)>
         <cfset fixImage(image_path)>
    </cfif>
    here is the fixImage function, customize for your preferences. it essentially converts the image to a jpg format that will not throw an error with cfimage. once you run this function you can resume whatever operation you would have done with the image - IE resizing it.
    <cffunction name="fixImg" access="public" returntype="void">
            <cfargument name="image_name" type="string" required="true" />
            <cftry>
                <cfset ext = listLast(arguments.image_name,".")>
                <cfif ext eq "gif">
                    <cfset uploadedImage = ImageNew("#arguments.image_name#")>
                    <cfset uploadedImage = imageCopy(uploadedImage, 0, 0, uploadedImage.width, uploadedImage.height)>
                    <cfimage action="write" destination="#arguments.image_name#" source="#uploadedImage#" overwrite="yes">
                <cfelse>
                    <cfexecute name="C:\Program Files\ImageMagick-6.6.2-Q16\convert.exe" arguments="""#arguments.image_name#"" -strip -colorspace rgb -quality 100 ""#arguments.image_name#""" timeout="1000" />
                </cfif>
            <cfcatch type="any">
                <cfset this.err_msg = "#cfcatch.Type#:#cfcatch.detail#:#cfcatch.ExtendedInfo#">
                <cfset this.err = true>
                <cfmail to="[email protected]" from="[email protected]" subject="fix image error" type="html">
                    #arguments.image_name#<br /><br />
                    <cfdump var="#cfcatch#">
                </cfmail>
            </cfcatch>
            </cftry>
        </cffunction>

  • Why Can't Something Simple such as Setting Color Space Be Included??

    Seriously, Lightroom is really lacking in that one cannot select a particular color space to be used in Lightroom. This is in Photoshop why not in Lightroom?
    I'm sure there would be many others interested in this simple feature.
    Cheers
    Ron

    LR works in a broad color space, similar to, but not exactly Pro Photo, which, when you export to files outside of LR, you can set to a number of color spaces.
    RAW files have no color space, or temperature, so you have wide latitude in setting them when you convert a file to TIFF, PSD, JPEG.

  • Recommended color space to use with my D50

    Hi -
    I'm pretty new to Mac and I'm now finding time to work with digital photos taken with my Nikon D50. Having read up on some things, I realize Mac OS and iPhoto can match the color space of the imported photos as an attempt to keep colors consistent between camera, computer, and eventually the printer. I was wondering what is a recommended color space to use when shooting. Nikon offers 3 choices - IIIa ( sRGB with a boost to green ), Ia ( sRGB ) and II ( Adobe RGB ). I believe their IIIa is my default and I have not changed it. I've noticed, however, that when I took a picture of my daughter in her prom dress outdoors in natural sunlight, it rendered it's magenta color as more red than magenta. Would Adobe RGB be better ? I read some articles here on color and I believe somewhere in the article it said the Adobe RGB color space has a broader color gamut than sRGB.
    Any opinions ?
    Thanks in advance,
    Bill

    I don't have a Nikon (I use Sony's) and I find my cameras output matches up well with sRGB. iPhoto seems to use sRGB as well. Adobe RGB comes up very saturated, too saturated for my taste. When I use Adobe. I set Adobe to sRGB as well.
    Magenta is a tough color and many fabrics reflect infrared and/or uv band and some camera sensors can pick that up. You may find the same effect with flowers.
    Gamut depends more on where you plan to output the images. A broader gamut is not always the best thing for displays but may work well for printing. Personally I find sRGB works well for me.

  • Color space, gamma, and code value range data

    Greetings!
    I'm getting close to submitting my film for professional DCP creation.  It's a ProRes 422 4096 by 1716, 2.39 - 1 file, created as a "master file" in a Premiere Pro CC export (the sequence being an "online" of sorts, built from SpeedGrade color-corrected DPX files).
    The Guidelines for "Digital Cinema Source Delivery" require me to provide information about Color Space, Gamma, and Code Value Range Information (head vs full).  Specifically, an order form asks for TRT, Color-Space, and Full or Head. 
    This is simply all Greek to me.  I know my film looks gorgeous, and the rest of what I've told you, but that's the limit of my experience.
    Can someone help me out?  Specifics are preferred to broad strokes.  Many thanks in advance.

    This is probably too late now for you anyway but here is some extra information:
    The "Digital Source Master" is the video footage before any D-Cinema formatting or encoding has been done.
    It can be literally anything. The DCI specification did not specify this.
    They did however specify exactly what the transcoded verison has to look like. The "D-Cinema Distribution Master" (16bit TIFF, XYZ)
    So in other words, you need to tell your service provider:
    The resolution, fileformat, frame rate and especially the colourspace that you used.
    For example r709 for HD or any other RGB colourspace with applied gamma value (2.3 for example).

  • Setting up color space between Aperture, Photoshop and my Epson 3880

    Hi. I use Aperture to do quick fixes and Photoshop for more complex edits and printing. I have setup my export preference in Aperture to the external editor as 8 bit ProPhoto RGB and in Photoshop my color space as Prophoto RGB. I use mainly Nikon RAW files. (Epson suggests using ProPhoto RGB to get the most out of the ink). Does all this make sense? As a sort of related question I don't suppose there is a way to export RAW directly from Aperture to Photoshop using the mouse right click and edit with Photoshop option..

    Yes, your setup makes sense, but the fact you're asking implies that you don't know much about colormanagement. Thus although this part of your workflow makes sense, it might well be that you're making error in the printing process for example. Get yourself a copy of the 'Real world colormanagement' by Bruce Fraser, to teach yourself all about it. Furthermore, when working in ProPhoto RGB, I'd suggest working in 16-bit instead of 8-bit, to reduce possible banding in color gradients.
    By export RAW directly to Photoshop, I believe that you mean opening the RAW-file in Camera RAW? No, there is no way of doing that directly, though Aperture does have an export master option, allowing you to place a copy of the original RAW-file anywhere on your hard drive.

  • Which color space to save still images for FCP?

    When saving still images as TIFF files to be brought into FCP, what color space should the files be saved in? The Adobe color space or SRGB, or other?
    Thanks.

    sRGB/JPEG is the best because all the color information is encoded in the actual image when you create a JPEG, as JPEGs don't carry color space information with them, like .PSD and .TIFF do.
    As for sRGB, that is as close as there is to a universal color space for monitors, and you are least likely to find a surprise when you check across many monitors. The tradeoff is a reduced color gamut if you display on a well calibrated broad gamut monitor.
    The gamma matters all the way through, if you want what you see in Photoshop to match what you see on a calibrated display monitor. The newest Photoshop, and Lightroom, use a native gamma of 2.2, which matches all video displays (not computer displays). If you generate JPEGs from them, they will have a gamma of 2.2. You then need to import them into FCP with a gamma of 2.2 for the interpretation. If you go directly to DVD from there, all is fine. If you go to a Quicktime movie, you need to know what the codec you plan to use will do. ProRes maintains the existing gamma, H.264 lightens up to 1.8, as does animation. I haven't characterized the others.

  • RGB Working Color SPace ....

    I'm very confused with this stuff ...
    I read that when we setup Photoshop we should set the working color space
    rgb to Adobe RGB or ProPhoto RGB .... fine I understand this up to a point.
    However what happend if the monitor can not display the color space ?
    For example when I display the Color Picker on my external NEC monitor
    everything always looks good but on my internal laptop monitor there is
    banding in the Color Picker.
    If I set the working color space to srgb then the banding disapears.
    So just how should I set all this up ?

    Michael,
    rely on a calibrated precision monitor (not the laptop),
    define all images by AdobeRGB and improve them by Levels,
    Curves and Sharpening.
    Check occasionally by Proof Colors / Gamut Warning
    (using the monitor profile) whether the colors are out
    of gamut for the monitor.
    The monitor is probably not the final output device.
    If the output device should be e.g. offset ISOCoated,
    then check by Proof Colors / Gamut Warning whether the
    colors are out of gamut for ISOCoated. If this should
    be the case, then modify the RGB source until only small
    parts of the image are out of gamut (yellow blossoms).
    Otherwise larger parts might be affected by posterization
    (blue sky).
    Theoretically one can use 'desaturate by 20%', which should
    show larger space colors mapped to the smaller space.
    I don't use it, I'm preferring the gamut warning - recently
    for a couple of landscape photos with very blue skies,
    yellow blossoms and orange sunsets.
    Best regards --Gernot Hoffmann

  • What Color Space to Set in Nikon Camera

    Nikon cameras alllow the user to set the colorspace into the camera. There are a lot of choices. A few of them have the letters RGB included in the name.
    Which color space should an Aperture user select?
    (I mostly shoot in  ambient light. And sometimes use flashes in a softbox. Photos are seldom printed.)

    William Lloyd wrote:
    I don't know of a single camera that shows a RAW-based histogram on the LCD.
    Me too.
    William Lloyd wrote:
    It's true that histogram blinkies _may_ not indicate an area of the photo that is unrecoverable. Still, if I'm shooting and I get blinky highlights I'll re-shoot if I can, because you're so close to the edge that it's hit-or-miss.
    I use Sony FF bodies almost exclusively.  I'm learned to judge from the blinkies and their relationship to the scene what they mean for blown pixels.  The Sony FF histograms (and they seem to be equal in this regard, even for very different cameras {e.g.: a850 and RX1R}) seem to give at least 2/3 of a stop cushion in the highlights.  In practice, if there are no blinkies at the highlight end, I can increase the exposure at least 1/3 and often 2/3 of a stop without ending up with blown pixels in the converted-from-RAW file.  So I usually aim for at some blinkies -- the exception being where the highlights are broad and significantly lighter than the rest of the scene.
    In fine, on my Sony cameras, the blinkies are not actually "close to the edge".  Rather they are on the grass on the other side of the pedestrian walkway that itself is still inside the caution rope.

  • Is color space conversion destructive?

    Is a simple color space conversion from RGB to CMYK, and then back to RGB a destructive process – meaning will image data be altered in a way that makes it different that the original image? Like jpg compression? I’ve been working with multi-spectral image data in 4 bands (channels) that is not recognized by PS in it’s original form (R,G,B,NIR), hence the color space swap in order to manipulate. It is a very kludgy way to work with output from some amazing imagery. If the image is trashed by doing this, it becomes another reason for seeking out a better way to edit them. If it does not negatively effect the data I have a bit more time to find a better way. So far, it’s a tough row to hoe.
    Thanks! TLL ( long time no post )

    The experimental evidence is that the conversion is a lossy process. Take an image & duplicate it. Change one of the images from RGB to CMYK and back.Then change the blend mode to difference and you will see the resulting image is not black, but has low level colored noise - conversion errors.
    Paulo

  • Quick develop and color space ...

    Ok, I know that library module previews are in Adobe RGB.
    So, we view files which are in Adobe RGB.
    But what about editing?
    What color space we use when adjusting in quick develop in library module?

    Armut12 wrote:
    Thank you for such a clear summary.
    Do you know why does Adobe not use Melissa RGB in library mode previews?
    As far as I can see, assigning an Adobe RGB profile to a JPG file and assigning a ProPhoto RGB profile to a JPG file does not create any difference in file sizes.
    Is there a disadvantage of using Melissa RGB in library views?
    Melissa RGB isn't really a supported RGB working space. That is, it's not something you'll find anywhere outside of LR unlike say sRGB, Adobe RGB (1998), ProPhoto etc. It isn't installed or used by any other Adobe app. It's kind of a strange beast too: ProPhoto RGB with the sRGB gamma TRC. We'd have to ping the original LR architect (Mark Hamburg) to find out why he decided to use this odd space solely for RGB values and Histogram but I suspect the main reason is that viewing a linear encoded Histogram would confuse most users (it would look 'odd'). I can't say why he didn't just use the ProPhoto 1.8 TRC instead but that's water under the bridge. This space is not ProPhoto RGB due to the gamma encoding and it isn't used for processing! Only the RGB values and Histogram.
    The actual color space used for processing has no name. It IS ProPhoto RGB primaries with a 1.0 TRC.
    I suspect that using Melissa RGB or a similar huge gamut is unnecessary in any preview mode because:
    1. Being so big, you'd want high bit (16-bit) data to reduce banding and that's overkill.
    2. There isn't and never will be a display capable of previewing ProPhoto gamut.
    3. There are a few displays that get close to Adobe RGB gamut, we may see that grow in the future. So might as well use that large gamut color space for previews. IOW, ProPhoto is way, way too big, sRGB is too small considering we have wide gamut displays.
    IF you have Photoshop, you can build Melissa RGB and save that out as a profile. Only useful if you want to play around but has no practical use. In Photoshop's color settings, select ProPhoto RGB as your working space. In the same menu, now select "Custom RGB". The dialog shows you the "DNA" of ProPhoto RGB (white point, chromaticity values, gamma). Change the gamma to 2.2, save as an ICC profile. You now have Melissa RGB. You don't get the true sRGB TRC but a simplified one, but close enough.

  • Can you show slideshow within Lightroom 4.4 in Adobe RGB color space?

    Can you show slideshow within Lightroom 4.4 (not export out from LR) in Adobe RGB color space provided that you are using a wide gamut monitor which is capable and hardware calibrated & profiled to show such color space?
    If this is possible, what is required to do so in Windows 8 and i7-4770 & HD Graphics 4600 platform or does LR take care of it automatically?
    This is very basic question, however, I could not find a clear answer/info from LR documentation, so wish that someone can advice.

    Those settings are probably stored in a plist somewhere in ~/Library/Preferences. If you can locate the appropriate file, you should be able to copy it to all the network user folders.

  • Image in PDF error - Expected end of color space

    Hi friends,
    I am displaying a PDF file in an webdynpro application. The contents are coming from the output of a RFC. The pdf file contains an image. While I am running the Webdynpro application the image is not coming. An error popup <b>"Expected end of color space"</b> is generated. But the texts of pdf file is coming properly.
    Please help.
    With regards,
    Sekhar

    Hi Sekar
    We are facing the same issue.  Have you managed to resolve this issue ?
    Please advise
    Regards
    Vivek

  • Asking the Bridge Team:  Bridge "working color space" setting when one does not have the Suite?

    Common sense tells me there is really no such thing as a
    "working color space" in Bridge, because
    Bridge is not an image editor, just a browser
    Therefore, this may turn out to be a purely academic question; but that doesn't keep my curiosity from forcing me to ask it anyway. ;)
    Is there a way to set the Bridge
    "color settings" when one does not have the suite?
    The only Adobe program I keep up to date is Photoshop, so I've never had the suite. My version of Photoshop is 11 (CS4) and I run updated
    (not upgraded) versions of Adobe Acrobat 7.x, Illustrator 10.x and InDesign 2.x. Consequently, the Synchronize color settings command is not available to me.
    It seems to me that Bridge is behaving like a proper color-managed browser (e.g. Firefox with color management enabled), in that it displays tagged image files correctly and assumes sRGB for untagged image files. This normally works fine.
    But what if I wanted Bridge to assume my
    Photoshop color working space for untagged images
    so that it behaves the same as Photoshop? I'm just curious, as I deal with a minuscule, practically negligible amount of untagged files.
    My reason for bringing it up now is that I don't recall this being explicitly mentioned in forum replies when users inquire about color settings in Bridge. A recent post regarding Version Cue in the Photoshop Macintosh forum got me thinking about this. Just wanting to make sure that I'm right in my assumption that
    there is really no such thing as a
    "working color space" in Bridge, because Bridge is not an image editor, just a browser.
    Thanks in advance.

    Hi Ramón,
    Thanks for sharing the outcome of your tests. However, I may have found a bug/exception to Bridge's colour management policy!
    It appears that CMYK EPS photoshop files are not colour managed in Adobe Bridge, even if they contain an embedded ICC profile.
    I've tried every combination in the EPS 'Save As' dialogue box, so it doesn't seem to be an issue with file encoding. Also, Bridge doesn't rely on the low-res preview that is held within the EPS itself.
    My guess is that Bridge is previewing the CMYK EPS with a Bridge-generated RGB image, but it's being displayed as monitor RGB (assigned) rather than colour managed (converted to monitor RGB). For most users the difference will be barely perceptible, but the problem became very noticeable when using Bridge to preview Newsprint CMYK images on a wide-gamut monitor (images that should have appeared muted really leapt off the screen!).
    How do I report this to the Colour Police at Adobe?!?

  • Lightroom's 4 color "spaces"

    I’m working on designing an advanced photography course. This course makes use of Lightroom and Photoshop in the photographic workflow.
    I’m learning and researching myself as I go along, and I feel I have reached a ceiling on what I can work out from the sources at my disposal thus far.
    So I am turning here for help.
    I am trying to clarify how tones and colours are affected from the actual scene through to the printed page. This might seem like overkill to some. However, there is a lot of misunderstanding and confusion, not to mention heated discussions amongst photographers about these issues. I’m experimenting with metering and colour / tone targets and my calculations are only meaningful if I understand how tones and colours are affected at every stage of the workflow.
    Here’s how I understand it:
    There are 4 (sort of) Colour “spaces” in Develop where a real-time dynamic preview of an image is rendered
    1.       The “viewing space” (ProPhotoRGB Chromaticity co-ordinates, sRGB gamma)
    2.       The “computational space” (ProPhotoRGB chromaticity co-ordinates, linear gamma – “MelissaRGB”)
    (Martin Evening’s Lightroom 3 book published by Adobe press - Appendix B, section on color space page 628-632)
    Below that, things get a little fuzzy. According to Jeff Schewe (Real World Camera RAW for CS5, page 32) there is a sort of
    3.            “Native Camera Space” and of course there is the
    4.            RAW data in the file on disk.
    So to generate the dynamically rendered preview, the image goes through the four “layers” as follows (from bottom to top). This is almost certainly flawed, but one has to start somewhere when trying to work things out :-)
    1. The RAW file is read from disk. Colorimetric interpretation is performed using a camera profile (e.g. Adobe Standard for whatever camera it is you are using). This process puts the image data into “Native camera space” (“Plotted” onto CIE XYZ with D50 white point)
    2. In “Native camera space, the scene white balance (as selected by user, guessed by Lightroom or reported by camera) as well as additional camera calibration panel matrix tweaks “informs” the colorimetric conversion into Lightroom’s “computational space” e.g. Melissa RGB. The colorimetric definition of camera RGB primaries and white is re-DEFINED. The demosaicing as well as chromatic aberration corrections are performed in “native camera space”
    3. Almost all image processing calculations occur computationally in the  “MelissaRGB Lightroom computational space”
    4. What is displayed on the screen, however, has an sRGB tone curve applied. This represents the “viewing” space. The histogram is generated from this and the RGB colour percentage readouts are generated from this as well. In addition, some slider controls from user input are weighted back through the tone curve into the computational space below.
    Could someone from Adobe kindly help me to clarify the steps? Eric are you reading this? :-)
    Thanks in advance

    Sandy - Thanks for the link. The spreadsheets you posted on your site is quite helpful.
    Jao – I think what you said goes to the heart of what I am trying to achieve here: “Photograph a grey target at the exact same exposure with the exact same lighting but with different cameras and you'll end up with different values in the raw files” Which is why I encourage photographers to experiment with their cameras in order to understand exactly how the camera will respond in the heat of a real shoot. Set up a scene; take a picture, open in Lightroom. What is clipped and why? Use a reflective spot meter. Repeat. Use a hand held incident meter. Repeat. How much can you reliably recover? Are you happy with what your meter considers the mid-point (and what you set your exposure for on the camera) or do you need to compensate? Just how much latitude do you have between what your camera histogram shows as a blown out highlight and what Lightroom shows as a blown out highlight. This relates to tone. I could go on with more examples, but by now, I am (hopefully) making more sense.
    I’m merely trying to clarify that which is already public in order to form a coherent mental picture. And by mental picture I do not mean an accurate representation of the minutiae and maths involved. Think of a subway map. It represents a bird’s eye view of a transportation system in a logical fashion, yet it bears almost no resemblance to the cartographical reality of the physical topography. I really don’t care where the tunnels go, how they were dug, how they are maintained or where they twist and turn. What I AM looking for is a logical (not physical) map. This map tells me where the different lines begin and end, and where I can change from one line to the other. The most important quality of the map as a whole is that it provides context. You can tell, at a glance, how different lines interact with each other and even how it links to other entities such as bus stations or public landmarks.
    As many have rightfully pointed out, I should not have to care about the maths/secret sauce/internal calculations. And I don’t. In addition, I am a very happy Lightroom user and I am very comfortable using it. I know what a user needs to know to get his picture from A to B. There is no shortage of information on how to accomplish that.
    It might help if I illustrate what I am trying to do below:
    Please excuse the low resolution, the maximum height allowed for upload is 600 pixels. The picture below goes on the bottom left of the "layer" picture above.
    Even though there are certainly many mistakes in my diagram, this is a helpful visualisation. I derived this diagram from publicly available information. As the subway map, this is a logical (not physical) representation that provides context in a visual form. With a little help from people like Eric I am sure I can correct and expand it. The net result is an enhanced understanding of Lightroom and ACR and where it fits into the photographic process, both in terms of tone and colour.
    I am not posting the entire chart here since I am not even certain that a 4 “layered” representation is an appropriate logical representation. I posted the spine of the chart with the 4 “layers” and one part that elaborates on the colorimetric interpretation between the two bottom layers. Comments and corrections are welcomed. And I am convinced that this can be accomplished without divulging anything confidential.

Maybe you are looking for