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 have owned the entire range of Panasonic PL lenses plus Sigma 56 Olympus 60 and 75The Laowa 10/2 is a favourite lens. Similar character as the Loxia 21/2.8, but smaller and cheaper. IQ isn’t as good as the Loxia.You both have a point here - to a degree. I feel you're still missing something:Well, that gets back to the FF size dilemma. Even with smaller bodies, once you get up into a little bit longer lens, you get big and clunky. For wides? Yeah, you are good, but not for the long FLs....
The FE lens catalogue is larger than the MFT one, although on average the lenses are larger and more expensive. You do get something for the added cost and weight though. There are more normal to WA options in FE mount, including some that compare well on size.
If you've never tried lenses such as Laowa's 6mm and 7.5mm f/2 ones, check these out. They are ridiculously small, solidly built and VERY good, with next to no rectilinear distortion.
Ok, those are weird ones, as they combine manual focus with camera-controlled aperture, but they underline the MFT value proposition with options FF struggles to cope with. The 6mm lens weighs 199g, the 7.5mm 170g. How's your equivalent FF lens compare? ;-)
Laowa do a lot more E mount lenses than MFT. The 15/4 macro is closest to your 7.5/2, but there is a 15/2, which is obviously heavier than your 7.5/2 because of the larger aperture. The macro has close focus of course.
I count 28 FE prime lenses in the FL range 12-21mm. The star is the Sony 20/1.8 G at 373g. The Laowa 14/4 is 228g and the CV 15/4.5 is 298g.
I’m moderately familiar with both lens catalogues. I chose the 10/2 over the 9/1.7 for my own reasons, for example. If you look back at the full post you part quoted, it seems to match the specific lenses just mentioned.
Until Canon and Sony started making small FF bodies, there was less incentive to make smaller lenses. I’m sure we will see at least a few more in future. Sony are concentrating on making smaller versions of big, expensive and high IQ lenses, not very small lenses per se. They are moving to excellent f4 zooms and some f2.5 primes. The 50/2.5 G is 174g. The older ZA 35/2.8 is less good optically but only 120g.
Andrew
PS my FE primes are mostly MF, apart from the 35mm, 55mm and 90mm macro. My MFT primes are more AF, apart from the Samyang 7.5mm and Laowa 10/2.
When it comes to primes there is not much reason to favour MFT for two reasons
1. Unless your MFT lens is really tiny for example 9/1.7 15/1.7 or 25/1.4 you can easily match an expensive MFT prime with an inexpensive Sony E-Mount prime that technically is perhaps a simpler product but does the job effectively better and it is not big at all. personally a really tiny lens was never a deciding factor but this is subjective
2. In addition due to the larger format you have access to constant f/2.8 zooms while you do not have f/1.4 zoooms in MFT. Some of those lenses are not too bulky nor expensive see Tamron 17-28 28-75 70-180 2.8. Those replace a bunch of MFT primes or match MFT lenses that are great but expensive like the PL 10-25 25-50
I don't have a simple answerFor those with a FF and m4/3 system,
What do you use your m4/3 system for and what do you use your FF system for?
I would be interested in this too Ken. Specifically how the built in stacking methods (LiveND, HR, HHHR) impact this type of noise as well as the impact of the fancy AI noise reduction/sharpening programs (if any). Thanks!Could you please share more info about mid tones noise level, or of you have any real comparison FF with M43? I am wondering if I would able to see it as wellthank you
Artistic CaveatI would be interested in this too Ken. Specifically how the built in stacking methods (LiveND, HR, HHHR) impact this type of noise as well as the impact of the fancy AI noise reduction/sharpening programs (if any). Thanks!Could you please share more info about mid tones noise level, or of you have any real comparison FF with M43? I am wondering if I would able to see it as wellthank you










Ah, interesting! Do you mean fooled by the overall groups or fooled by which group the last example fit into?I’ll admit I was fooled by the grouping, I had them flipped.
I do realize now I didn't answer your question about noise reduction...You have answered my question regarding the in camera stacking impact. A lot of good stuff in there, maybe we should have started a separate thread![]()
No worries, the least I can do in return for all your excellent posts on HR modes!Thanks for doing this. I really appreciate it.
I'll try to answer that with an analogy first: I have an excellent and quite large Japanese kitchen knife and an also excellent Swiss Army pocket knife. Both cost about the same and are excellent tools. I can cut with both, and sometimes both do indeed cut the same, e.g. apples. What I do most often with them depends on different factors, like sharpness, length of the blade, object to cut, transportability, compactness etc. pp.For those with a FF and m4/3 system,
What do you use your m4/3 system for and what do you use your FF system for?
DeepPrime XD does a nice job on baby’s eyelashes in available light when you need more DoF. That’s on FF.Noise reduction applies equally to all formats and therefore is irrelevant to a comparison
in addition in most cases on full frame you don’t need it saving time in post processing
You may need to make up your mind on which arguments to use. In the first statement, you imply that both systems benefit from NR the same way. In the second one, you argue that FF won't even need it, which is a direct contradiction to the first one.Noise reduction applies equally to all formats and therefore is irrelevant to a comparison
in addition in most cases on full frame you don’t need it saving time in post processing
I thought the final image was shot with FF. I was looking at it on an iPad which allows you to open the image into viewer mode without the auto pop up EXIF window that you get on a computer. I would have never imagined that came from a GM1! Then it made sense with the frame stacking. In the end, I now see why you began you post with the "content matters" pretext. That is an excellent image from a composition and lighting perspective. Well done sir!Ah, interesting! Do you mean fooled by the overall groups or fooled by which group the last example fit into?I’ll admit I was fooled by the grouping, I had them flipped.
No harm, I ask a lot of questionsI do realize now I didn't answer your question about noise reduction...You have answered my question regarding the in camera stacking impact. A lot of good stuff in there, maybe we should have started a separate thread![]()
The answer is I haven't really played with the more recent AI stuff enough to have an up to date opinion. What I will say, admitting it is out-dated, is:
So based on the last few times I checked in on fancy NR packages I wasn't impressed enough to bother using them on my base ISO landscapes (though they clearly work very nicely on a whole host of common images). I should try again, especially since Adobe recently integrated their version into LR.
- The pre-AI fancy NR stuff never really seemed to work well on base ISO mid-tone noise. I think this is because those algorithms were working best on structured pattern noise in high ISO shadows. Photon shot noise of course has no pattern or structure to it, it is truly random, so there is only so much you can do.
- The early AI NR seemed to work best on more obvious structures it was trained on such as feathers, fur, hair, material textures and larger scale structures like buildings. Seemed to do well on larger natural things like leaves when they were large enough to be identifiable. But a lot of landscapes down at the pixel level are almost fractal in nature (especially deserts without trees) and that seemed to not work so well.
Now you've got me thinking about capturing some examples to look at the impact of mid-tone noise and tonality. Something like...No worries, the least I can do in return for all your excellent posts on HR modes!Thanks for doing this. I really appreciate it.
Good point, and I'd say depending on the context it is either an important factor or an irrelevant factor. But of course still one worth discussing!What puzzles me in many of the endless "MFT vs FF" discussions is that the aspect of noise reduction (NR) is often omitted, as it is in your post. In my view and experience having used both systems extensively, it is an important factor to take into account.
Agree, in the past the side effects of NR were substantial enough that one could for almost all purposes dismiss it entirely in the comparison between sensor sizes.Up until a few years ago, NR engines used to be rather mediocre and, when used aggressively, came at a price most of us weren't prepared to pay, namely a reduction in image sharpness and/or the introduction of artifacts. That is probably why many shied away from using more than a hint of NR, which still left substantial and clearly visible noise differences between MFT and FF images.
Agree, right now the better NR solutions are right around the two stops of improvement that is equivalent to the jump between FF and m43 (at least for the base ISO stuff I work with, the improvements might be even more at higher ISO). But again, you can apply that same NR to the FF image. So this improvement in NR performance is most meaningful if one's threshold for acceptability happens to be right at the point where FF without NR is acceptable while m43 without NR is not acceptable.Fast-forward to today: the introduction and further development of AI-based NR engines has been a game changer, as it brought giant improvements in this field. If you've never used DxO's DeepPRIME XD for noise reduction, you may not know what I am talking about: used carefully, this technology almost levels the field between systems as the noise is largely gone without affecting sharpness or detail of the image. Lightroom is not quite there but also received substantial improvements in its latest versions.
Thanks for the excellent comparison images of the various AI NR engines!Only when using extreme pixel peeping, going to 100 percent or more, will you be able to detect any differences once such NR has been applied, and those differences are small and difficult to see. Looking at the whole image, which I hope we can all agree is the most important aspect anyway, good NR leaves no differences between FF and MFT shots. Similarly, ISO levels that used to be unacceptably high have become usable with this technology. (Examples at https://thisbeautifulplanet.de/denoising-software-comparison.)
Here I'm going to disagree fairly strongly with the terminology and theoretical assertion. DR and noise are exactly the same thing. Dynamic Range is in fact defined by noise. It is the clipping level divided by the level at which the SNR drops to some arbitrarily chosen threshold. If NR software is improving noise in the shadows then it is increasing DR at the very same time - it is part of the definition of DR.As I see it, this whole discussion needs a different direction. Noise no longer is the main distinguishing factor between systems if good NR is used, which makes it no more than an inconvenience.
Where a true difference remains is in dynamic range (DR). The two-stop difference remains unchanged in spite of NR. A Z7 has about 11.6 stops of DR at base ISO, whereas an OM-1 has about 9.6. There is nothing any piece of software could do about that. When shooting MFT, I find every so often that I get to choose whether to blow my highlights or get pitch black dark areas, but I won't be able to avoid both within a single shot.
Yep, as a landscape shooter I have many options that don't work for other kinds of photography!When shooting landscapes, I can simply bracket my exposure and blend the shots later, which again (usually) makes DR a mere inconvenience. Shooting moving subjects, however, I have to live with the issue. Shooting an animal in thick underbrush, this is not much of a problem since such scenes usually do not have high DR anyway. Shooting a bird in flight against a bright sky can present a dilemma, however, that I may not be able to avoid. If all else were equal (which it isn't, but that's a different discussion), that would make FF the better choice.
Again, I'm not so sure of this because from the theoretical stand point it is provably wrong. DR and noise are the very same thing. However, from a practical standpoint in the evolution of AI based NR it is a very interesting question. If it is true that AI based NR algorithms at present don't improve base ISO DR because they fail to reduce noise in the shadows in the RAW file then that is important mark against AI based NR and an issue that should be addressed in the AI models probably via their training datasets.In short, I am of the opinion that giving the state of technology we are at, DR warrants special attention in this debate, whereas sensor noise does not/no more.

Thanks! And yes, a little GM1 can do amazing things with exposure averaging. It is all just about collecting enough photons.I thought the final image was shot with FF. I was looking at it on an iPad which allows you to open the image into viewer mode without the auto pop up EXIF window that you get on a computer. I would have never imagined that came from a GM1! Then it made sense with the frame stacking. In the end, I now see why you began you post with the "content matters" pretext. That is an excellent image from a composition and lighting perspective. Well done sir!Ah, interesting! Do you mean fooled by the overall groups or fooled by which group the last example fit into?I’ll admit I was fooled by the grouping, I had them flipped.
Well, I just now just tried the ridiculously expedient if lazy technique of simply clicking the new Adobe AI "Denoise..." button in the Detail panel and letting it do its default thing with zero further changes to the processing:No harm, I ask a lot of questions. Perhaps I should not have called them NR packages - that might be the wrong term. I am thinking along the lines of opening an image in DxO PureRaw first which does the conversion from RAW to TIFF but with specific modules tuned to each camera and lens. Even with base ISO images it appears to have some effect on sky tones and shadow noise, sharpening, CA, colors, etc. The end result is an image that looks really good in terms of IQ.
For example, your beautiful rainbow photo above with the EM5II...I wonder if letting PureRaw do the demosaicing would bring about a clean, color rich sky as a starting point for editing.


Yes that would be an excellent thing to do, and to have it in a dedicated thread rather than hidden in our side discussion here!Now you've got me thinking about capturing some examples to look at the impact of mid-tone noise and tonality. Something like...
The R5 can only pixel shift into a JPG so I think I'll carry the SL2. The DR at ISO 50 is pretty good, just have to watch the highlights. It creates DNG in camera from the pixel shift which is convenient.
- M43 single shot, let camera meter
- M43 single shot, ETTR
- M43 LiveND
- M43 12 shot median stack
- M43 HHHR (should be similar to above)
- M43 HR (pixel shift)
- FF single shot, let camera meter
- FF single shot ETTR
- FF 12 shot median stack
- FF pixel shift
I will try down at the coast - we have some nice bluffs at the ocean which tend to have some nice shadows in the morning. Will have to work quickly though as the shadows shift. Anyway, will be fun to compare and discuss results!
I think that is an accurate and succinct summary!I think the last 3 posts have addressed a question that was forming in my mind on NR - do the modern NR tools help close the gap between M43 & FF sensors? The answer seems to be yes (completely?) when the NR software can reduce the noise either to a practical zero or to the point where it no longer causes offence in the final image.
I think that is a "it depends" and one I certainly don't have enough experience to address. I will comment that AI algorithms tend to be non-linear, which is to say they usually have their own internal thresholds. With that in mind it is certainly possible that the magnitude of their benefits differ on how bad/good the starting point is.If that point is not reached, the answer may be “somewhat” if the NR SW can reduce noise more at higher levels than at lower starting points - is this true?
I think this goes both ways, and especially for something like BIF you probably need to figure in the AF tracking performance. I'm thinking along these lines:with BIF, I think I understand that the situation is more complicated - the longer reach of M43 may lead to wider apertures (depending on the lenses used of course - let’s base the discussion on OMS 300mm f4 or BWL) and therefore lower ISOs than FF, reducing the noise delta between the initially captured images - at least for longer focal lengths?
Nothing has changesYou may need to make up your mind on which arguments to use. In the first statement, you imply that both systems benefit from NR the same way. In the second one, you argue that FF won't even need it, which is a direct contradiction to the first one.Noise reduction applies equally to all formats and therefore is irrelevant to a comparison
in addition in most cases on full frame you don’t need it saving time in post processing
Taking both together, I observe that you seem in full agreement with my main points:
1. MFT benefits from NR as it needs it much more than FF does.
2. Noise is an inconvenience on MFT because it often requires NR, but that's all there is to it. Once you've done proper NR, things are the same on both systems.
Glad we agree.![]()
Modern NR (DxO, Topaz and LR) are really changing the playing field. But I think your two points actually demonstrate that its benefits are not equally distributed. If FF in most cases doesn't need NR, then there must be other formats that do need it. The quality of today's NR now gives those other formats the ability to (almost?) match FF.Noise reduction applies equally to all formats and therefore is irrelevant to a comparison
in addition in most cases on full frame you don’t need it saving time in post processing