What Is This?

Shooters on My Squad wrote:

John Gellings wrote:

I guess this is dpreview’s version of a code to crack? Too little info from a bad crop and a hesitant OP to provide anything makes this ridiculous to try to answer.

This is a false statement. Neither am I trying people to "crack a code", nor hiding information that I can share. So far I answered every question as thoroughly as possible.

If you find this ridiculous to answer, why do you even answer, and not just ignore?

I am just trying to get better photos, and I thought that many visitors here have a similar goal in mind. It looks like I might be wrong.

There were already some people in this thread that pointed me to the right direction and were helpful. I will investigate further, and hopefully find an answer.

I just see no point in your comment Mr. John Gellings.

I’m sorry you feel that way, but you have no idea what this looks like from our perspective. I can’t imagine why you’d focus on this one detail. Is the entire photo that great or are you just getting caught up in pixel peeping. Sometimes out of focus areas just do weird things depending on shapes and light, how you expose, the aperture used etc. Unless this is happening over and over in all photos you are taking, forget about it and move on.

a_c_skinner wrote:

The 27/2.8 is not mediocre, mine is optically more or less the same as my 16-55. Whatever the cause I doubt it is that. I look forward to seeing more images which can be posted complete that show the effect. I'd factory reset before taking more to be sure it isn't the in camera processing.

I am not sure if my posts are getting ignored, or if this is a joke.

If the issue is already present in the RAW files, how would a factory reset help, or how could camera processing (on RAW files?) manipulate the result?

There are some manufacturers that apply e. g. noise reduction or anti-aliasing to RAW files which you cannot turn off, but I am not aware of any other, heavier processing that would apply here.

So why do you still think this might be “camera processing” or some settings gone rogue?

Shooters on My Squad wrote:

a_c_skinner wrote:

The 27/2.8 is not mediocre, mine is optically more or less the same as my 16-55. Whatever the cause I doubt it is that. I look forward to seeing more images which can be posted complete that show the effect. I'd factory reset before taking more to be sure it isn't the in camera processing.

I am not sure if my posts are getting ignored, or if this is a joke.

If the issue is already present in the RAW files, how would a factory reset help, or how could camera processing (on RAW files?) manipulate the result?

There are some manufacturers that apply e. g. noise reduction or anti-aliasing to RAW files which you cannot turn off, but I am not aware of any other, heavier processing that would apply here.

So why do you still think this might be “camera processing” or some settings gone rogue?

If this is the only instance of this happening, don't worry about it. If it's an ongoing problem, post a full-size image you can share (preferably the RAW). You aren't giving us much to go on here. It could be a lens rendering issue, a motion artifact. a RAW demosaicing artifact, an alignment artifact (if it's an HDR etc.), it could be an electronic shutter artifact too. Do you have a RAW and a Jpeg to compare?  You aren't making it easy.

78_Anthony wrote:

https://youtu.be/4ex72Ssdd1o

Watch the above and scroll to around 6 minutes.

Is this what you are seeing?

Anthony

Thanks for sharing the link! At first I thought that my photo may be just the worst case of the issue presented there, but then I checked the photos from that particular day again, and I do not see these issues at all.

The rendering & IQ of this lens is generally good in my subjective opinion. It seems like I can isolate this to be the rendering between the two OOF planes (and I hope this is not about “X-Trans”, which is my fear, but why should it when both bodies are very similar except their user interface, and I haven’t seen this issue on the X-T4).

Erik Baumgartner wrote:

If this is the only instance of this happening, don't worry about it.

This seems to be indeed a rare issue. What I have shown in the crop here was the worst case, and similar but less visible issues are present in about a handful of shots (out of about 50). This happens mostly on photos with OOF foliage, and my assumption (thanks to the helpful feedback in this thread so far) is that this happens when something else in front of the focused subject is in the image. I will check that!

I wouldn’t worry so much, if a viewer wouldn’t have pointed this out to me. This was quite embarrassing.

If it's an ongoing problem, post a full-size image you can share (preferably the RAW). You aren't giving us much to go on here. It could be a lens rendering issue, a motion artifact. a RAW demosaicing artifact, an alignment artifact (if it's an HDR etc.), it could be an electronic shutter artifact too. Do you have a RAW and a Jpeg to compare? You aren't making it easy.

I realize it is not much to work with, but I currently gave every information I could without violating laws. I will try to isolate this issue with some specific test shots. I now also realize how RAW demosaicing could play a role here. Thanks.

a_c_skinner wrote:

The 27/2.8 is not mediocre, mine is optically more or less the same as my 16-55. Whatever the cause I doubt it is that. I look forward to seeing more images which can be posted complete that show the effect. I'd factory reset before taking more to be sure it isn't the in camera processing.

Haha, I hope it's not mediocre, I just bought one. Mine seems fine on my XE3 and XT30-II.

Shooters on My Squad wrote:

Erik Baumgartner wrote:

If this is the only instance of this happening, don't worry about it.

This seems to be indeed a rare issue. What I have shown in the crop here was the worst case, and similar but less visible issues are present in about a handful of shots (out of about 50). This happens mostly on photos with OOF foliage, and my assumption (thanks to the helpful feedback in this thread so far) is that this happens when something else in front of the focused subject is in the image. I will check that!

I wouldn’t worry so much, if a viewer wouldn’t have pointed this out to me. This was quite embarrassing.

If it's an ongoing problem, post a full-size image you can share (preferably the RAW). You aren't giving us much to go on here. It could be a lens rendering issue, a motion artifact. a RAW demosaicing artifact, an alignment artifact (if it's an HDR etc.), it could be an electronic shutter artifact too. Do you have a RAW and a Jpeg to compare? You aren't making it easy.

I realize it is not much to work with, but I currently gave every information I could without violating laws. I will try to isolate this issue with some specific test shots. I now also realize how RAW demosaicing could play a role here. Thanks.

Blur the face man...Done and done.

Sorry, yes.

It is excellent.

RustyRus wrote:

I realize it is not much to work with, but I currently gave every information I could without violating laws. I will try to isolate this issue with some specific test shots. I now also realize how RAW demosaicing could play a role here. Thanks.

Blur the face man...Done and done.

You realize I cannot win this one. When I edit the image I will have to upload a JPEG file, then everybody will want to see the RAW file again, because of “processing” issues, although the problem is already present in unprocessed RAW files with the history stack at the very bottom in Darktable where exposure, color balance, and other things look like crap, because absolutely no processing was applied, but the smeary, wormy pattern is still present. Then I will be in the same position again.

I want to make test shots with this lens on the X-Pro3 & X-T4 as my current assumption is that this is just how the OOF rendering of different planes looks like on this lens where planes cross on the Z-axis. I did buy this lens primarily for its size & focal length, and accepted that I already have other lenses with better optical parameters. I can accept this specific mediocre behavior of the lens, if my assumption is correct, because otherwise it is pretty fine. I am excited about some photos I took with this lens. In the end I just want to know in order to avoid problematic compositions (which aren’t that many to begin with), and have more keepers.

FujiShooterCY wrote:

Looks like

• there was a RAF processed with some Adobe product at default (actually, destructive) settings,
• also it was over-sharpened with the dumb USM algorithm,
• and crop was made afterwards from an OOF area somewhere around the border/corner of the image.

To avoid this kind of discrepancies I'd suggest shooting in "RAW + JPEG Fine" mode, so that in case Adobe destroys the IQ after processing the RAF again, at least you still have the reference OOC JPEG to compare your post-processing results to.

The raw has an embedded 13MP jpeg which should be plenty detailed enough for the comparison