Stephen Burch's Birding & Dragonfly Website |
||
Home | Trip Reports | Gallery | UK index | Oxon pics | UK pics | Dragonflies | Other Nature | Links |
Introduction Simply looking at digital camera pictures and trying to make valid assessments and comparisons of noise levels may have its place, but the results can be very subjective and depend hugely on the subject matter of the picture, as well as the camera used and all the settings involved in getting the image out of the camera onto the screen. The size the image is viewed at can also makes a big difference. An image at 20% magnification can appear virtually noise free, but show it at 1:1 and up comes the noise. Hence, I have taken a different approach and developed a reasonably simple method for quantitatively measuring pixel to pixel noise levels on digital camera pictures, effectively analysed at 1:1 magnification. I've then applied this method to images taken with different Canon digital cameras at different ISO settings. In general, the main factors that affect the noise level on an digital camera image are as follows:
Method Introduction
Having done this, all the raw images should be close to what is coming off the sensor, with minimal processing. In other words a like for like comparison between the cameras, or 'level playing field'. Note however that with all these user selectable parameters turned off, either on the camera or in the raw converter, the measurements made show significant differences between the noise levels on images obtained with different raw converters. Hence there are some hidden processes going on in different raw converters, that the user has no control over. Grey-scale (or "step wedge") test chart
The purpose of this chart was to allow measurements of noise to be made for different image brightnesses (grey levels) from black through to white, to understand how the noise varied. The test chart was designed to have steps with different brightnesses, but each step was an even grey so that any variations in image brightness (or grey level) within the step would be due to noise and not the target. Image acquisition To reduce any variations in image brightness due to printing imperfections in the test chart, I always made sure that all the images were slightly out of focus. For each camera, I then typically took a series of images at different ISO settings, with the exposure time and/or aperture changing between them. I generally used the Av setting and about +1 EV exposure compensation with evaluative metering to get the white surrounding area at a high grey level in the image, but not saturated or "blown-out". Raw conversion of the images For my recent (late 2022, early 2023) results, I reprocessed all the image files using ACR in Photoshop 2023, using the Adobe camera standard profile in all cases (for uniformity between cameras). I made sure all noise reduction and sharpening parameters were off. In addition, I have used Canon's own raw converters, initially Digital Photo Professional version 3 (DPP3) and more recently version 4 (DPP4). For all the more recent measurements, I made sure the output files were 16-bit tiff files, not 8-bit to avoid anY loss of dynamic range. However when showing the results, I scaled the results back down to 8-bits (i.e. 0-255). Also, at the raw conversion stage, for the most recent measurements, I set the white balance using the dropper tool - on the white surround to the grey scale. This was to avoid any significant colour cast to the image. It probably did not make much difference on the final measured noise values but seemed a sensible thing to do. Note earlier results probably didn't include this stage. As stated above, in doing the conversion, the output files were always tiff files (which are lossless, unlike jpegs), I made sure any processing parameters that might increase or decrease noise were off (e.g. sharpening, noise reduction). Measurement of the images However, as I discovered in early 2023, other free packages are also available to do this analysis. ImageJ for example works well and importantly allows the results of the analysis to be saved for pasting into a spreadsheet. This saves a huge amount of time compared with writing down and then typing in all the numbers! With this software, it does not appear possible to set a specified area size but there is an interactive read-out of the area size as it is dragged out across the image. So it is quite easy to check its size. The example below shows the analysis of an image using ImageJ in progress. The procedure for the analysis is as follows:
Using the above procedure on different images, it is possible to build up a series of measurements that can be plotted and compared to study the variations in noise with various parameters, the main ones being image brightness or grey level, ISO setting, and of course camera type. Handling of colour information in images Although the grey scale image shown above had no colour in it, the RGB images generated by any camera do. Firstly, the colour balance can be off, so that the whole image has a colour tint to it. This can be avoided by setting the white balance to white on the background around the grey scale. But secondly, the image noise affects each of the RGB colour channels differently, so how the RGB channel information is handled can have a significant effect on the measured noise level. As an example, if a linear average of the RGB values is taken, and all 3 channels had the same individual noise levels, then the resultant noise level would be reduced by approximately sqrt(3) = 1.7 (almost 5dB), assuming the noise was uncorrelated between the channels. Generally, the camera noise will generate a luminance component and a chrominance (colour) component. All my measurements are intended to be of luminance, not chrominance. But there are different ways of defining luminance from separate RGB channels. For the Isee! software, a simple linear average of the RGB values is used to create the image analysed. With ImageJ, its documentation suggests this is the default option, with a more complex weighting available as a user specified option. However, while this appears to be true for 8-bit images, it most certainly isn't the case for 16-bit files! For these, I currently (late Jan 2023) have no idea what ImageJ is doing - it gives much higher values than a linear average would do! To ensure consistency between Isee and ImageJ, I have found it necessary to first convert all the camera images to "black and white", using the Photoshop 2023 option of Image ---> Adjustments ---> Black & White. This brings up a formidable menu like this, in which I leave the defaults well alone:
Photoshop 2023 menu for converting an RGB image to Black and White Exactly what this option does to the RGB values is currently unclear to me but I assume it combines the RGB values with a suitable weighting to get something which I take to be a reasonable measure of luminance. Whatever it does, the resulting RGB channels then all have equal values, and the means and standard deviations for 16-bit images derived using Isee! and ImageJ are then equal, as desired!
|
Home | Trip Reports | Gallery | UK index | Oxon pics | UK pics | Dragonflies | Other Nature | Links |