back alley
IMAGES
for those of us not in the know but still curious...
JohnM
Well-known
It's a digital imaging artifact - patterns of lines in the image. (Like digital 'noise', but in a repeated line pattern instead of a random display.) Can be vertical or horizontal, long or short. I don't know which affects the M8 sensor as I do not have one.
But, I have to think Leica will be able to fix it fairly easily.
But, I have to think Leica will be able to fix it fairly easily.
ywenz
Veteran
http://www.rangefinderforum.com/forums/showthread.php?t=30775
It is quite obvious here why banding is a bad thing.
It is quite obvious here why banding is a bad thing.
back alley
IMAGES
ywenz said:http://www.rangefinderforum.com/forums/showthread.php?t=30775
It is quite obvious here why banding is a bad thing.
it's obvious just from the titles and number of threads about it.
i just wanted a nice simple description of what is is.
thanks, johnm!
joe
waphoto
Newbie
banding seems to be an issue on the first generation canon 1d, even though this is a rangefinder forum... 
ywenz
Veteran
The 1D suffered banding when extreme level tweak is applied to the image.
Pulled from fred miranda's site:
http://www.fredmiranda.com/1D_review/
Pulled from fred miranda's site:
http://www.fredmiranda.com/1D_review/


waphoto
Newbie
ah, ok, ive only used one about 5 times...and i wasnt really shooting anything that required a massive contrast bump...thanks for the clarification though 
ClayH
Diana camera, coffee
rvaubel
Well-known
ClayH said:Shoot the moon, for instance. Not art by any stretch of the imagination, but I think this nicely illustrates the issue. ISO 1250
Clay
Your moon picture shows all the artifacts. Notice the biaxial symmetry and the negative moon.
This is something that can probably be fixed pretty easily in firmware. In any case, for most of us it doesn't affect a lot of pictures. However, when you know about it, it drives you crazy. I find myself looking for it in every M8 file I see. Its turned into a sort of "where is Waldo" game for me.
Rex
AndyPiper
Established
Back Alley: banding, in a general sense, is, as already mentioned, any digital artifacting that reveals the underlying bands, or rows, or columns, of pixels on a digital sensor. As opposed to the random speckle artifacts one gets from noise or grain.
There have been several instances of banding issues with new cameras, each slightly different in form and (as it turned out) often with different causes.
The 1Ds - as already demonstrated. Also the Nikon D200 (cause was some kind of readout imbalance between alternating rows of pixels). Also the Canon 5D (cause was determined to be EM interference when the AF drive motor was running in "continuous" mode when the exposure was made).
In the case of the M8, the proximate cause is a bright light source against a dark background that spills brightness into surrounding dark pixels in a band across the frame. Several theories as to the technical reason this happens have been bounced around, but none is confirmed.
Best I've seen so far is: a timing issue that leaves some of the silicon "gates" between pixels open at the wrong times in the process of reading the individual pixels' brightness in the instant after exposure. Sort of like a canal with all the lock doors left open - instead of each lock having a discrete level of water in it, all one sees is a continuous rushing river through all the locks downstream.
There have been several instances of banding issues with new cameras, each slightly different in form and (as it turned out) often with different causes.
The 1Ds - as already demonstrated. Also the Nikon D200 (cause was some kind of readout imbalance between alternating rows of pixels). Also the Canon 5D (cause was determined to be EM interference when the AF drive motor was running in "continuous" mode when the exposure was made).
In the case of the M8, the proximate cause is a bright light source against a dark background that spills brightness into surrounding dark pixels in a band across the frame. Several theories as to the technical reason this happens have been bounced around, but none is confirmed.
Best I've seen so far is: a timing issue that leaves some of the silicon "gates" between pixels open at the wrong times in the process of reading the individual pixels' brightness in the instant after exposure. Sort of like a canal with all the lock doors left open - instead of each lock having a discrete level of water in it, all one sees is a continuous rushing river through all the locks downstream.
Share:
-
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.