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.
Lightroom 3.x (Camera RAW 6.x) has excellent Color NR, only so-so Sharpening tools.bob-one wrote:
Is there a good all in one photo processing software out there for the lx5 and the fz150 ? Or is one of the major draw backs to Panasonic cameras is no software supports their ever changing raw formats?
I'm not quite sure I understand you. If you load the RAW file into Lightroom are you saying you cannot improve on the default settings or that the RAW looks worse than a camera jpeg?I'm not a detail expert like Detail Man (but who is?) but basically the converted FZ150 files are less sharp, almost smeared in appearance, by comparison.
I just sent it (the FZ150) back to B&H for replacement. I'll keep you all posted!
Yes, I see the differences that you report. It seems that the de-mosaicing algorithm used by FastStone surely works better than the particular ("secret-sauce") de-mosaicing algorithm that LR-3.x/CR-6.x selects in the case of FZ150 RW2s.canuck dave wrote:
... when viewed in FastStone, for example, they look as expected, that is pretty good, but possibly could edit better. And that has been my experience with other RAWs in general. But the FZ150 RAWs soften up when even the defaults in Lightroom, RT etc are applied. Never seen anything like it!
Not sure if these two will show it, but the first is 'just' using FastStone to convert to a TIF. The second is the default TIF from LR.
Have you perhaps tried the various de-mosaicing option of RAW Therapee 4.052 ? Any differences. The fact that FastStone looks pretty good seems to mean that there may well be hope here ?Again, I have a lot of experience with RAW editing. With the FZ150 RAWs, working in any of four editors does not achieve the results I have come to expect from any other RAW files.
Ditto here. S-IPS, sRGB-calibrated.(I have a calibrated IPS monitor!)
I did not include the Tone-Curve (having already covered a lot of controls). However, when adjusted in "parametric" mode, it can be used in a workable and repeatable manner. I usually set the bottom two control-sliders (in descending order) to -5 and -10 (or -6 and -12), in order to impose a very mild "S-Curve" in the lowest shadow-tones (that is similar, but a bit more reserved than the Lightroom 3.x "Medium-contrast" Tone-Curve Tool setting. This gets me close to what I want (without affecting the top-end of the tone-curve), then I use (some) LAB color-space Contrast in addition to that.Gerry Pasternack wrote:
"Yes" to all of your suggestions (but did not try the tone-curve).
That the camera was hand-held makes the fine-details of the far-field (small) foliage less definitive. They are a bit "fuzzy" - and I was wondering if this was possibly the result of some camera-motion (which it may in this case be).Camera was handheld and sky was overcast - just starting to rain.
There have been various anecdotes published on the internet with specific examples of the DNG converter chucking-out certain manufacturer meta-data in certain cases. The up-shot of these (and your reported) experiences just add stronger evidence to not convert to DNG (at all, if possible), or to convert to DNG only if the processing will be accomplished in Adobe applications.Of interest: I also converted the image to DNG (so that I could process in LR2). When I processed this negative with RT there were black-dot artifacts in the resulting jpeg output at the clipped-and-restored top of the waterfall. No such anomally when processed with LR (but not as good highlight recovery as with RT).
(Perhaps) it is the other way around ?Does RT play well with DNG?
Such things should not matter (if all was well) ...Perhaps my highlight recovery with this negative was too aggressive?
I hope so (for her sake). But, the numbers seem a bit stacked against that. Your first unit, the Imaging Resource unit, and Cole's unit seem to have similar characteristics.canuck dave wrote:
Thanks DM for your input. Yes, I'll be curious as to whether another version of FZ150 works better for me. Ooops; I mean for my wife, as it's her Xmas ...
The "chickens will come home to roost in the end", eh ? ...... gift.......LOL.....but I wind up doing most of her RAW editing!
Kevin C has indeed been posting some nice material. However, he himself points out that it utilizes flash in order to be able to shoot at base ISO=100 (over which he has reported that he finds even the RW2-level output to be noisy).I should hasten to add that I'm not one of the 'my images look bad, must be bad equipment at fault'. The superb work from the likes of Kevin Coppalotti should be an inspiration for all of us!
Any specific examples in mind ? I am always interested in what in-camera JPG "engines" in what camera models people perceive as doing a good job. Do you personally like the FZ150's JPGs ?canuck dave wrote:
I only 'converted' or evolved to RAW a couple of years ago after I saw (for myself) that there were distinct advantages to be gained. I think many onboard JPG processors are far underated.
The fact that the FZ150 JPGs look nice to a viewer(s) does not imply that the FZ150 RW2s should appear to be so marginal on image-detail (particularly in the case of a number of RAW processors):It may be that the FZ150 has somewhat hit a wall with their RAWs, and that the near-optimum is achieved (without any fuss, and little or any loss) with the great results Panasonic engineers have tweaked from their onboard computers!