Okay, it's not desaturated - but it's not my image. Whatever it is, it's meaningless because the true image resolution has been massively nuked, resulting in complete misrepresentation of the actual pixel values.
I guess you just want to forget about the fact that you can see the haloing in the original image posted?
Yes, because that's from Nigel's embedded JPEG that only has a resolution of 1660 by 1080 pixels. We also don't know how that was generated. Only Nigel knows. Was it sharpened or otherwise manipulated? Regardless of the answers, the resolution shrinkage has invalidated the pixel data.
mfinley, post: 68229080, member: 1727339"]
.... It's just imported into lightroom and nothing more.
Jeez, just look at the images in that post to which you replied.
What madness does Lightroom do that would cause my image crop, which is this ...
I asked you how LIghtroom could turn my image into that unrelated thing you posted.
Since you don't have access to LR to see the problem, you keep trying to blame it on something else,
Right. I blame it on your mistake by calling it my image. I also blame the original mistake you made by trying to use a crop from a 1660 x 1080 image to analyze something that you need to crop from a 24MP image to actually analyze.
when one of the phantom causes doesn't remove it, you come up with another one. If I'm correct you're up to 6 at last count: chromatic aberration, aliasing, lossy compression, lens corrections, luminosity masks, and the latest one - sensor bloom...
You have corrected nothing whatsoever. You have utterly failed to disprove my contention that CA, aliasing, and luminosity masking should be considered as factors,
as I first said.
I, on the other hand, have been pointing out your repeated mistakes.
Let us know how it turns out after you correct for all of those. If you need any help let me know.
Everything you've posted is mired in misinformation, so your conclusions are misinformation.
