|
A couple of things need to be noted here.
1. The image from the 40D is reported as 768x800 and at 100% "zoom" on the screen, it is physically not much bigger than the Neximage.
2. the image from the Neximage is reported as 640x480.
So I don't see the stretching as the main problem as all I am looking at is the resolution in pixels as reported.
In the Neximage shot, you can clearly see the "pixellating" similar to mpeg artefacts where there is a distinct blockyness. Now if I look at the 40D's reported 768x800 which ain't much larger than 640x480, there is hardly any pixellation or blockyness. This will help explain the registax artefacts after wavelet processing but the two resolutions are almost identical and hence shouldn't have this large difference.
But have a look at my Registax wavelet comparison. Its exactly the same process and exactly the same wavelet. To me this looks like a bit depth problem in that it may appear as if the Neximage is capturing only 8bit and hence the wavelet is decimating it on processing.
What do you blokes think?? In fact if it does turn out to be 8bit vs 14bit then I would be much more comfortable knowing that it's just a limit of the Neximage.
Hey Brendan, excuse my ignorance but what is binning? I have read only briefly about it.
Cheers,
Darrin...
|