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.

Similar Messages

CS5 doesn't open/process ProPhoto RGB correctly...

I'm new to Photoshop, so I apologize if the answer is obvious!
When opening RAW images from LR 3.3 to edit in CS5, it does not seem able to support the ProPhoto RGB color profile, even after switching the working space to ProPhoto RGB in CS5. It always ends up looking like this:
I'm only able to open up the photo in CS5 when I change the color space in LR's "External Editing" preferences to sRGB. I guess I could live with that, but I don't understand why my photos won't open in ProPhoto RGB as this is the profile I'd like to use. It shouldn't be this complicated, they're both by Adobe, right? Ahhhh!
Anyone have any insight?

Voilà. As you can see, the image looks normal in the layers tab... not sure what the problem could be...

Images opened in Photoshop CS5 has a blue-tinted grayscale

I was using Photoshop CS5 (64-bit) fine yesterday but today each image I open shows a loss of colour, everything looks like a blue tinted grayscale.
The same with RAW files oipened in ACR and all files opened in Bridge.
When I open a JPEG version in Microsoft Image Viewer the colour is fine.
In Windows, the thumbnails look fine with full colour in the folders.
The loss of colour only happens when the image files are opened in Photoshop, Bridge and ACR.
Anyone out there who can help?
Many thanks.

Many thanks to Silkrooster, Alec Molloy & Chris Cox, for all your help and time.
Just for info - the Huey Pro calibrator has worked well with this monitor (Dell U2410) for at least a couple of years now.
I tried old profiles created previously using the HueyPRO but they did not work, so I deleted them from the System32/spool/drivers/color folder.
Then a new HueyPRO-created monitor profile did not work, so I deleted that as well.
Then at start up, the HueyPRO seemed to auto-create its own monitor profile which it named: "hueyPRO Dell U2410 F525MOA70DKL.icc"
But that gave the same loss of colour when opening files in Photoshop
So I think Chris is exactly right - the problem must be with the HueyPRO "cigar" hardware, or with its software, so I may well have been bothering you all unnecessarily.
I'll try getting a new hueyPRO - but not too common in the shops here in central Africa.
In the meantime, I've uninstalled HueyPRO and I'm using a reference image to calibrate using the NVIDEA Control Panel (I'm working on a commission for two photo calendars at the moment and so have to keep it going....).
Any recommendations on a better calibrator (but a non-too technical one!)??
Stephen at WILDFOTO

Images opened in CS2, Bridge or Lightroom have bands of different colors

RAW images opened in CS2, Bridge or Lightroom have bands of different colors depending on the image and are unusable. Running Windows Vista 32 on Dell Desktop 531 w/2g of ram. Have been searching but haven't found a solution. I have not called Adobe yet.
Lightroom stopped running on Vista 32 windows error message says "Lightroom has stopped running windows is searching for a solution to the problem". At the same time Lightroom works fine on my laptop running Vista 32.

Are you looking at the images at 100% resolution? Banding can appear in other enlargements due to rounding errors.

Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
Michael

Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings..

Swatches go funny in ProPhoto RGB mode

I am running CS4 on XP 32 bit, in case that is relevant.
For years my working RGB has been AdobeRGB 98. Life has been fine. Recently I have changed my preferences in LR to use ProPhoto RGB as my destination color space when opening images in Photoshop.
I have logo colors which I have used for years which are in my swatches.
I have noticed that whenever I open a file in ProPhoto RGB, the logo colors are wildly skewed. The color of the image from LR is fine, but the swatches go wacky, so if I use my logo brush with the logo colors from the swatches, they are way off.
I would have thought that the color of a swatch was maintained if it remained in the gamut of the color space of any given image. It appears that this is not the case. If I had to guess, I would say that it is maintaining the numerical values of the colors, and since ProPhoto is so much larger that AdobeRGB that it is skewing the colors madly.
Is there a solution to this? Do I need to regenerate my swatches by opening a ProPhoto image and then opening my logo file, dragging the logo into the ProPhoto image and then adding the relevant colors to the swatches?

Anyone?

PROPHOTO RGB versus ADOBE RGB-should they look the same?

satisfied with editing an image in LR, I then opened it into CS5 and converted it's profile to adobe rgb, the are marj=kedly different in color,tone,brightness, etc.
i use imac,8GB ram 27" display, os 10.6.6 and I use eye one to calibrate my monitor once per month. LR 3,3 and Photoshop CS5.
searched forums and found nothing i could clearly understand. The prophoto rgb version of image is bright and cheerful but adobe rgb version is dull but probably more accurate.
am prepared for humility so how about some advice

Bob_Peters,
you are absolutely correct.
i just read about the uses if the "assign" and "convert" variations. i will read them again.
a little humility is a fair price to unscramble thoughts.
thanks, again,
vince

Camera set to sRGB, Opens as Adobe RGB

I have a Canon 5D, color space set to sRGB. When opening RAW file in Camera Raw 5.0, it opens as Adobe RGB. How can I fix this?
Thanks!

> Wouldn't that be true only if you were targeting a smaller space, like sRGB?
Factual clipping, i.e. pixel saturation on the raw level has nothing to do with the intention regarding the processing of the raw image. If pixel saturation is reached, then the raw pixel value is invalid.
The issue is, how one can achieve an in-camera conversion, which resembles the closest the raw data, in order to be able to tell how the actual exposure was. There are several steps, which can not be neutralized for the in-camera conversion, one of them being the color space conversion. Furthermore, the spectral characteristics of the color filters play a huge role in this question, so my suggestion is camera model related.
For example re the Nikon D300 I suggest using Adobe RGB in-camera. This is, because Nikon changed the color filters for the D300 sensors from the previous models very much. They are almost always changed from one model to another, but this change was extraordinarily big: the transmissity of the red range is much larger in all three filters than with other sensors. This has lead lots of photographers believe that the "red channel overexposes" (which occurs very seldom, practically nie before green saturation). Thus my (unproven!) suggestion is, that the in-camera histogram and clipping indication of the D300 gets closer to reflecting the raw data with Adobe RGB than with sRGB.

Photoshop-When opening image without tab view, image opens with only a portion in view

I having an issue with CC.
When electing in the preferences to not open image in Tabs. The images open with only about 25% of the image area showing. Forcing me to (command) 0 for full to screen preview or (command) +/- to see the image.
I am not talking about seeing the image at 100% resolution just the entire image within the floating window without having to command before view.
Sidenote: Adobe Customer Service is all based in India. I spent 4 hours on the phone only to hear that this is that way photoshop works.
There would be no logical explanation for this. Since the first version of Photoshop this has not been the case.
I think this should be called view porn with wife in the room mode. Other than that I see no point.
Can anyone help?
Lv
Chadwick Tyler

Moving discussion to Photoshop forum.

Why does paintbrush not work on images opened from Bridge?

This problem may be due to another cause but the most common occurance is when an image is opened from Bridge so I've posted it here. Here are the details.
I have had tons of problems with CS4 on my desktop PC but seem to have most of them resolved with a new video card, updated driver and help from an earlier thread. In fact, I thought all problems solved but this one has persisted. If it matters I'm running Windows XP service pack 3, 4gb of RAM of which 3.4 is available. It has an 2.67 GHz Intel Core2Duo cpu.
If I open CS4 and open an image, all paintbrush tools (paintbrush itself, clone tool, healing tools, etc) work fine. Sometimes I can work for hours with no problems. Other times these tools simply stop working. When this happens seems random. For example, the other day as long as I did not send anything to print, all worked fine but after printing a few images the tools stopped. Other times I've printed and the tools still worked. Sometimes if I open images direct in Photoshop using file -> open, all is well but as soon as I launch an image from Bridge, tools don't work. Other times launching from Bridge works fine, BUT more often than not, it seems to occur after launching from Bridge, hence the post here as I already noted. I've tried to trace down a common set of circumstances but it is too erratic.
What is interesting also is that the use of the tool shows up in the history panel as a step taken. There just is no visible effect on the image. This problem has been present since CS4 was originally installed along with several other problems. In the course of attempting to solve them all, I have deleted preferences and allowed them to rebuild, I have actually uninstalled and reinstalled Photoshop multiple times.
More confounding is that CS4 works fine on a clunky old laptop with less RAM and a much, much older video card. I also, as a test, ran the 30 day trial on the computer I'm using here. It too is older and less RAM and that worked fine too. So it seems to be saying there is something wrong with the computer used for photo editing or the video card. Don't think it's the card. I bought a new one. It didn't solve any problems so I bought another and it corrected many of the other issues I was having. Indeed after installing the latest drivers for this card, absolutely everything worked perfectly for almost two days but now this paintbrush tool issue is back.
So what the heck can be going on that is cumulative or is there a hardware component that is erratic or have I missed something in CS4? Man I love the power of the program and the improvements since CS3 but if I have to shut it down and restart it every single image, clearly that is not feasible.
Many thanks for any help.

Well, now I'm an idiot. I fired up without the tablet plugged in and
paintbrush worked fine on all files. I then left the image open I had just
painted on, plugged in the tablet with pc still running, no paintbrush
function using tablet mouse. Without unplugging the tablet I again tried
the regular mouse and paintbrush worked fine. So it's not a matter of any
sort of conflict with the tablet being active, it sure looks like a tablet
malfunction. It still mystifies my how this tablet is so smart it can tell
the difference between psd and jpg but there it is...can't argue with
results. Still, one last thing confounds me and that is the tablet works
fine on all file types in CS3 and every other app I have. If there was a
malfunction with the tablet, wouldn't you think it would misbehave on all
apps? Could it be that the tablet needs a new driver? You must've had a
clue to recommend this course of action. Now that we're here, what do you
suggest or should that be another thread?
By the way, if it matters I had already upgraded vc drivers and CS to 11.0.1
before this started.

Converting RGB images (sRGB or Adobe RGB) to 709 color space.

I'm trying to determine the correct way to convert RGB images (sRGB or Adobe RGB) to 709 color space. I can't just use the "covert to profile" function to do this because it does not produce results that fall within the 16 to 235 range that 709 dictates. I've read that you can simply use the "Levels" adjustment and change the output levels to 16 to 235. While this would clearly compress the luminance to the correct range, I'm not entirely clear if the end result would be a proper conversion (i.e. if color and gamma, for example, would be technically correct.)
I noticed that converting the profile to "HDTV (Rec. 709)" does alter the image, so I'm wondering what the result would be if I did both this AND used the levels control to compress the output range to 16 to 235.
Thanks for any feedback on this.

(1)
http://en.wikipedia.org/wiki/Rec._709
(2)
http://en.wikipedia.org/wiki/Rec._601
The transfer functions for Rec.709 (1) refer to the range [0..1] or for 8 bits per pixel [0...255].
It seems that the clipping, black=16 and white=235 has to happen after the application of the
transfer function. If this should be true, then we don't have a level compression but a level
clipping at both ends, as already for Rec.601 (2), like here:
The ICC-Profile HDTV(Rec.709) in Photoshop contains the primaries and the white point
(both like that in sRGB) and the transfer functions for [0..1], coded by a LUT with high resolution,
as found by Profile Inspector. There is no clipping.
By the way, that`s the internal profile name, I don't know the file name of the profile.
Softproofing, source in sRGB, target HDTV(Rec.709), without clipping:
With numbers not preserved: no change of the appearance, as expected.
With numbers preserved: shows the effect of different effective gammas.
Your questions are very clear and I'm not sure whether my comments help. The information
in the internet is not convincing.
Best regards --Gernot Hoffmann

Why won't large images open in full screen on first click?

I go to open an image (jpg, png) that has a byte size of 2000 x 3096. What ends up happening, is that it will initially open a full screen window, and after a second or so, that full screen window will shrink to a half screen window. Now I'm required to click the max window size button in the upper right corner to expand the window to full size, right click on the image, select View Image from the drop down menu, and then finally click in the image to get it to display in its full size.
Is there a plug-in, or a config. parameter that I can use, so that the image opens up in full screen mode from the start?

Is this with opening an image link from a web page or with viewing images that you already have stored on the computer?
You can check for problems caused by a corrupted localstore.rdf file.
*http://kb.mozillazine.org/Corrupt_localstore.rdf
See also:
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can try to rename or delete the prefs.js file and possible numbered prefs-##.js and user.js files to reset all prefs to the default value.
*http://kb.mozillazine.org/Preferences_not_saved
*http://kb.mozillazine.org/Resetting_preferences

In "Preview" 2 issues: clear last images opened & zoom not working

Any images opened in "Preview" from the past, all open up when I select other or new images to view. Basically anything I've opened in Preview since the install of Lion all opens when I select new images or items to view in Preview. Just now, 15 separate windows opened after I selected 3 images from the same folder. The other windows all contain items and images I've opened in the past few weeks. This is crazy annoying. I've never seen this before. I looked in preferences and I can't find anything to clear last opened or something to that effect. Please advise.
Secondly, in Lion, on both my Macbook Pro & iMac, I can no longer use my smart mouse, trackpad...to expand the items/images in my folders prior to opening them. Usually I could open a folder, see there are numerous images and use my fingers to zoom in & out on all the items of that folder w/my trackpad. Since Lion, no more.

In case anyone else has noticed this issue, I found the answer. It's a Lion issue, so delete the following plist:
~/Library/Containers/com.apple.Preview/

Why doesn't my image open up in the filter pop up adjustment windows?

I'm new to CS4, I just installed it and picked an image to try a few things with. When I open up any of the filter windows (for sharpening and others etc) my image does not open up in the adjustment window. Any idea why that is happening? Did I miss something when I installed the program? Is there a setting that should be set and isn't? I have Vista on my lap top, and XP-SP3 on my desktop, and it is the same in both. Thanks for any help you can give me.

Is the image an 8-bit RGB Jpeg?
(Check in Image > Mode.)
Are you on the right layer?

'open new tab' function has stopped working, even after reinstall

The 'open new tab' function has stopped working. I even uninstalled Firefox and reinstalled and no help.

-> Tap '''ALT''' key or press '''F10''' to show the Menu Bar
-> go to Help Menu -> select '''Restart with Add-ons Disabled'''
Firefox will close then it will open up with just basic Firefox. Now do this:
-> Update Firefox to the latest version by going to Help Menu -> About Firefox -> click '''Check for Updates''' -> if an updated version is found then download the latest version and install it. After that follow these steps:
-> Update ALL your Firefox Plug-ins https://www.mozilla.com/en-US/plugincheck/
-> go to View Menu -> Toolbars -> unselect All Unwanted/Incompatible Toolbars
-> go to Tools Menu -> Clear Recent History -> '''Time range to clear: select "EVERYTHING"''' -> click Details (small arrow) button -> place Checkmarks on '''Cookies, Cache''' -> click '''Clear Now'''
-> go to Tools Menu -> Options -> General -> in Startup section click '''Reset to Default''' button
-> go to Tools Menu -> Options -> Content -> place Checkmarks on:
1) Block Pop-up windows 2) Load images automatically 3) Enable JavaScript
-> go to Tools Menu -> Options -> Security -> place Checkmarks on:
1) Warn me when sites try to install add-ons 2) Block reported attack sites 3) Block reported web forgeries 4) Remember Passwords for sites
-> go to Tools Menu -> Options -> Advanced -> Network -> Offline Storage (Cache): click '''Clear Now''' button
-> Click OK on Options window
-> click the Favicon on SearchBar -> click '''Manage Search Engines''' -> select all Unwanted Search Engines and click '''Remove''' -> click OK
-> go to Tools Menu -> Add-ons -> Extensions section -> REMOVE All Unwanted/Suspicious/Incompatible Extensions (Add-ons) -> Restart Firefox
-> go to Tools Menu -> Add-ons -> Appearance section -> REMOVE All Unwanted/Suspicious/Incompatible Themes (Persona) -> Restart Firefox
You can enable your Known & Trustworthy Add-ons and Themes later. Check and tell if its working.

Images opened in ProPhoto RGB has heavy banding

Similar Messages

Maybe you are looking for