|
|
| Author |
Message |
MBAustin
Joined: 18 Mar 2011
Posts: 2
|
 Posted: Fri Mar 18, 2011 9:34 pm Post subject: 16-and-32-bit Gradient Banding Problem |
 |
|
Hi,
I have been encountering a problem in trying to create black-grey and grey-grey gradients in 16 bit and 32 bit color mode. These gradients consistently wind up with a high degree of color banding, making them look horrible! This does not happen with colored gradients, only in going between different shades of grey of similar brightness. The problem does not occur in 8-bit color mode. I have tested the program on two different monitors, one of them brand-new and very good quality, and the problem persists on both of them. I have attached a sample image of the problem. Any help would be much appreciated. |
|
|
|
|
 |
thehermit
Joined: 05 Mar 2003
Posts: 3987
Location: Cheltenham, UK
|
| Posted: Sat Mar 19, 2011 11:42 am Post subject: |
|
|
It's normally accepted that 16bit should result in less banding than 8bit editing so it's odd that you see the reverse. The accepted wisdom on banding is the age old "add noise" and it is in truth a pretty acceptable way to go about it. There are other methods that are a little more complicated, but no need to go to town if that works.
You don't mention if it's a screen or a printing banding that you see, so I assume it's a screen issue. The problem with banding is that it's more of a maths problem than an image issue, you could try higher bits, Gaussian blur and noise to counteract. I know of some other solutions like a gradient fill adjustment/layer but unless you want a diatribe of why it bands then I would save me the breath and try noise first 
Don't forget unless your image is only destined for screen then I would print out a test image, banding may not be so obvious under print conditions.
Oh and welcome to the forums MBAustin
_________________
If life serves you lemons, make lemonade! |
|
|
|
|
|
MBAustin
Joined: 18 Mar 2011
Posts: 2
|
| Posted: Sat Mar 19, 2011 2:03 pm Post subject: |
|
|
Thanks! Adding noise solved the problem, but I still don't know why it happens in the first place. It is a screen rather than a print issue, by the way (unfortunately I don't have a printer available to test right now). |
|
|
|
|
|
|
