tinternaut
Veteran Member
The GR's lens goes toe to toe with a camera/lens I seriously lust after, and it does pretty well in the comparison.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I don't really have any experience with the film GR cameras (though I would probably pick one up if I happened across a used one). All my GR lenses have been on digital cameras, but I find them to be very impressive and are some of my favourite lenses.I might be missing something here, but the GR1 produced distortion free pictures on 35mm, which is considerably larger than an aps-c sensor. Is there any reason why this would be harder to achieve on a smaller, digital sensor?i have no doubt it's a great lens, I love my GR lenses. But so close to perfect from such a small lens covering an APS-C sensor in such a compact body would be a truly remarkable achievement, even for Ricoh.The Ricoh GR lens is based on the original GR1 lens, that was a revolutionary design for a 28mm lens. It was so good Ricoh even made a Leica M version. Its only limitation was the maximum aperture of f/2.8.
photographylife.com
Indeed, the post was written and intended as a good news story, hence the closing paragraphThe GR's lens goes toe to toe with a camera/lens I seriously lust after, and it does pretty well in the comparison.
I can see a couple of people have their twickers in a knist over it, but I don't really follow why. The post is simply saying; Ricoh did a great job, I wonder how they did it, and looking for clues.Of course, this is all speculation, well except for that end part, because as you all know, they do in fact deliver a 16MP near distortion-free raw file, and I think the most appropriate words for that are, however you did it, well done Ricoh.
Why are you getting so nasty about this? Why all this negative spin using words like troll, clueless and (from your previous post) worthless?Are you just trolling, or are you really clueless about digital cameras, optics, and image processing, and have never heard of Google?Sorry, i missed the requested link(s) to the tests you claimed had been done. Could you point it out or were these tests just another thought experiment?
J.
Your response ignored the request and started down the nasty path with the "worthless" remarks.Tested how? Was the camera disassembled and mounted on some kind of test equipment? Do you have a source for that please?It has been tested by various places and has negligible distortion - around 0.3%. Some processing software such as DxO Optics Pro corrects that minor distortion, but the raw files from the GR do not.
If tested from the camera raw file (which is how DXO do most of their testing) and pre-raw correction is occurring, then the test is on already corrected data, which would also explain the extremely low distortion.
One of the charts commonly used for testing is the 1951 USAF chart, so I think the chart-based methods pre-date digital photography.[snip]
I haven't seen any 'optical testing' results for the film GR, but I suspect the majority of testing/review was done by taking real world photos and looking at them, rather than the chart and numbers testing we have become ensconced in today. But I guess I could be wrong about that.
[snip]
Oh dear, it's never a good idea to examine evidence with a bias, as it introduces the risk of not being balanced and unbiased in the examination.So let's examine your evidence for distortion correction of the raw data, and show with a few minutes of thought that it is worthless.
But I never mentioned what I considered the "circumstantial" evidence to be. Instead the remainder of the OP was about how, IF it was being done, the possibility of utilising the total sensor photo detectors over the full sensor area could perhaps lead to a superior result than the defacto standard method of storing the raw uncorrected data, and correcting it later with a reduced data set.Let me start of by saying my position is that I do think there is some circumstantial evidence that the GR maybe applying software corrections to the raw files for lens distortion.
In fact, most of this "evidence" is being introduced by you and Ron, seemingly for the purpose of attributing to someone else (me) so it can then be criticised.Of course, this is all speculation, well except for that end part, because as you all know, they do in fact deliver a 16MP near distortion-free raw file, and I think the most appropriate words for that are, however you did it, well done Ricoh.
It may be something different. One of the links bill provided was an introduction to FT in which there are various graphs, including what is expected from a well behaved sensor and from various types of processing. The GR files Rondom supplied showed deviation from this, hence bills assessment that there was evidence of signal processing. The link is here (I know you know how to use google, I include it just for your convenience ;-) )Bill (for who I have great respect) has produced a 2D Fourier transform from part of a GR raw file (it is only 256x256 pixels), or maybe many blocks stacked together. The FT shows a correlation indicating nearest neighbour image processing. Is that something different from the usual de-mosaicing? Without more information, I can't say.
I made no such claim. Show me where I made such a claim and I will donate £10 to your favourite charity.You claim that this shows evidence for distortion correction. Distortion correction is not nearest-neighbour processing. It is an interpolation and re-mapping process from a curvilinear to a rectilinear grid that varies across the image. What would the frequency-domain signature of such a transformation look like? Do you know? I find it very hard to guess - some sort of slight bias in the spectrum that would increase as you looked at blocks closer to the corners, I suppose - not what you have shown, anyway.
It's not my evidence, it's Rons and Bills, and it is what it is, evidence of some signal processing.So let's discount your 2D FT "evidence" for what it is - blowing smoke -
Just to point out, you are introducing this, not me. So when you and Ron are having a chuckle about it in in those other posts, you are laughing at yourselves.and look at something a bit more obvious. If Ricoh is going to all the effort of manipulating the raw data to correct lens distortion digitally, why did they reduce it to 0.3%, leaving a residual distortion that can be corrected to practically zero by programs such as DxO Optics Pro? It doesn't make any sense, does it, unless that 0.3% is the actual optical distortion of the lens?
Again, this is "evidence" being introduced by you, not me, but again I'm happy to offer my thoughts.The signature of the Ricoh GR series was originally a highly-compact 28 mm lens covering the full 35 mm frame, with exceptional optical performance but relatively modest aperture. Your idea that in the current version Ricoh for some inexplicable reason replaced it with an under-corrected lens relying on software correction of distortion is, literally, nonsense, in that it doesn't make any sense logically.
Indeed, that is how they choose do it. And it has merit, especially for an interchangeable lens camera. But it has the downside that a distorted image is saved in the raw which may need correcting before use and will lead to some information loss.Other cameras that use this approach to distortion correction such as µ4/3, Leica Q, etc. do it by including the corrections as meta-data in the raw file, so it is easy to detect and measure the uncorrected distortion.
Unsurpringly I see a different summary.So, to summarise: your idea is not supported by any evidence, it fails when tested against measurement, and it doesn't make sense logically.
Ok, I posted a link on the S&T thread to this discussion and invited Bill and Jack to have a browse, seeing as how we keep mentioning them.Great! Sounds good. I suggest that you share it in S&T forum.Ron - I said I will perform my own test and report back.
Ok, the vignetting once againAs we are aware of about half of the lens vignetting in ORIG - at what point does it demonstrate that the usable portion of a lens is less than the intended focal length?
A lie? You need some distortion correction as wellThe vignette correction is degrading the image, can not be turned off. The GR lens in this sense is a lie.
Ok. I will let this statement speak for itself. Considering your strong opinion, I'm not sure if your distortion correction test will be impartial, though! Can't wait!
Could Leica sell the Q "summilux" without correction? That's a clear No.Could Ricoh sell this GR lens as a 28mm equiv without the vignette correction?
Ok maybe this is worth discussing: Is vignette correction as critical as distortion correction. I don't know the answer to that. I didn't notice my DNG files breaking apart during post processing. I'm sure Leica files are perfectly fine as well. I guess I have a soft spot for distortion free glass (I assume yours is vignette free glass)
I personally like vignetting. I even add some!
I would say It's important to see the TRUE ORIGINAL before making such gross claims about the lens being useless for the intended FOV,
Could there be a test that would simulate the pre-correction look?
I would love to see that. But I would be embarrassed to go back to S&T and ask the question! I already took a lot of their time- and my own time too![]()
Here's a raw image from the GR II taken from imaging resources:... This was the image posted in the other subthread as an example from the Leica Q.
The barrel distortion of the lens is obvious and if this was a film camera, likely unacceptable for most. In the analog world, the distortion is the monster
...
Of course, but I think the open question was whether Ricoh corrects the raw data; I don't believe they do.I'm careful as to whether or not I correct the distortion. Sometimes it gives the image a certain presence that is hard for me to describe. The exception is close up photos of people, where the correction really helps.
I'm careful as to whether or not I correct the distortion. Sometimes it gives the image a certain presence that is hard for me to describe. The exception is close up photos of people, where the correction really helps.
Thank you for adding some words of good sense to this thread. It will be interesting to see if the OP listens to you, as he seems unwilling to listen to anyone else!Here's a raw image from the GR II taken from imaging resources:
Looks clear to me that the raw file has not been corrected for distortion.
Regards,
--
Bill ( Your trusted source for independent sensor data at http://www.photonstophotos.net )
Looks clear in what way please?Here's a raw image from the GR II taken from imaging resources:... This was the image posted in the other subthread as an example from the Leica Q.
The barrel distortion of the lens is obvious and if this was a film camera, likely unacceptable for most. In the analog world, the distortion is the monster
...
Looks clear to me that the raw file has not been corrected for distortion.
Excellent. Thanks for taking the time to join us, much appreciated.Here's a run down of the various sensor areas using the Leica M9 which has a Kodak KAF-18500 sensor as an example.
(I chose this simply because I have the spec sheet handy.)
5212x3468
This is the final image size.
5216x3472
This is the raw image size.
The 2 pixel border is required for demosaicing.
5270x3516
This is the Active Area according to the spec sheet.
These pixels have the Color Filter Array (CFA).
55 columns and 44 rows of pixels were not used.
5310x3556
This is the Effective Area according to the spec sheet.
There is a 20 pixel border of buffer pixels.
5422x3610
This is the Total Area according to the spec sheet.
The pixels are electrically active but have no CFA.
Some are purposely shielded from light ("optical black").
Note that with 6.8 micron pixels the image is 35.44mmx23.63mm; not quite 36mmx24mm
The sensor array occupies 36.87mmx24.55mm
The total package size, according to the spec sheet, is 37.8mmx26.4mm
I point this out because we're often not given pixel size (pitch) and frequently overestimate pitch with careless math.
35.8mmx23.9mm is commonly listed as the sensor size; but this is the Active Area not the image area.
So carelessly we might say 35.8mm/5216pixels = 6.86 microns; but that's about 1% too large.
For some sensors, especially small ones, the difference is more extreme and leads to errors in computing Quantum Efficiency (QE).
Looks distorted, although not so much as the Leica Q.Looks clear in what way please?Here's a raw image from the GR II taken from imaging resources:... This was the image posted in the other subthread as an example from the Leica Q.
The barrel distortion of the lens is obvious and if this was a film camera, likely unacceptable for most. In the analog world, the distortion is the monster
...
Looks clear to me that the raw file has not been corrected for distortion.
Not unused, just not part of the final image; this is an important distinction.Excellent. Thanks for taking the time to join us, much appreciated.Here's a run down of the various sensor areas using the Leica M9 which has a Kodak KAF-18500 sensor as an example.
(I chose this simply because I have the spec sheet handy.)
5212x3468
This is the final image size.
5216x3472
This is the raw image size.
The 2 pixel border is required for demosaicing.
5270x3516
This is the Active Area according to the spec sheet.
These pixels have the Color Filter Array (CFA).
55 columns and 44 rows of pixels were not used.
5310x3556
This is the Effective Area according to the spec sheet.
There is a 20 pixel border of buffer pixels.
5422x3610
This is the Total Area according to the spec sheet.
The pixels are electrically active but have no CFA.
Some are purposely shielded from light ("optical black").
Note that with 6.8 micron pixels the image is 35.44mmx23.63mm; not quite 36mmx24mm
The sensor array occupies 36.87mmx24.55mm
The total package size, according to the spec sheet, is 37.8mmx26.4mm
I point this out because we're often not given pixel size (pitch) and frequently overestimate pitch with careless math.
35.8mmx23.9mm is commonly listed as the sensor size; but this is the Active Area not the image area.
So carelessly we might say 35.8mm/5216pixels = 6.86 microns; but that's about 1% too large.
For some sensors, especially small ones, the difference is more extreme and leads to errors in computing Quantum Efficiency (QE).
This seems to confirm that there is indeed a border of unused data around the final used area, although at around 1.5% (for this sensor) perhaps not as much as anticipated, I guess it will vary from sensor to sensor.
As I said, some of it is definitely "used".Do you have any insights into why they elect not to use this data, or indeed of any scenarios where it does get used for something?
No. This is an annoying aspect of the industry as it has matured.Is getting hold of the sensor spec sheet something that is relatively easy for the layman?
Manufacturers often don't identify the exact sensor used.And what about identifying which sensor is being used. This is an area that has caused numerous debates over the years, for example in the M43 forum there was a debate over which sensor was used in the first OM-Ds. It raged for months and eventually led to one member buying a camera just to dissassemble it to try to identify the sensor, which ultimately led to the conclusion it was built by Sony. Do you think it is a case of some manufacturers being very open about it and some concealing it, or more a case of being fairly easy if you know the right places to look.
You are welcome.Once again, thanks for joining us.
DxO and DPR report that their copy of GR had a distortion of 0.6% at short edge and 0.01% at long edge. The measured focal length was 18.4mm (as opposed to the declared 18.3mm). Compare that to the measured 18.1mm focal length of Coolpix A (which is declared as 18.5) and this might explain why DPR's studio scene test shows sharper extreme corners for the GR than the Nikon A. Also, something is correcting the CA better in the GR (glass or software?).[...]. Obviously GR's 0.3% barrel distortion is hardly an issue