P: Rings/Vignetting with Tamron 17-70 Lens on Fuji XT-4

[RubenKempter]

Hey there,

I hope you can help me with this, it's driving me insane.

I noticed the problem first when shooting into a blue sky with clouds at a wedding, then I saw the problem on a table the next shoot as well. Now I checked with a white wall and found that Lightroom actually does this to my newly picked up Tamron 17-70 2.8 (on a Fuji XT-4)

I'm having crazy rings and vignetting with the Tamron lens, first thought it's the lens, but it's Lightroom adding the crazy rings. Since when I'm importing there's nothing, but when i hover over the image and select it, it takes a second and then Lightroom adds them to the picture, as if it where implementing a lens correction, but horribly wrong. Turning off Lens Profile / Correction doesn't do anything, once it's there it's there. Also the JPEG looks fine, it's only the raw file. 

Attached are the two images, it's easy to tell which one is the JPEG sooc and which is the RAW file out of Lightroom with the "vignette" 

Can you please tell me how to fix this, and what is going on there?

[curious_fashion1549]

Eight months after detecting the problem, I turn on my Mac and Camera Raw is updated to version 15.3. I open Lightroom with hope and... nothing. Adobe still hasn't fixed the double rings problem. How long will it take to fix it?

[curious_fashion1549]

Hi. They still haven't fixed the double vignetting problem, with the Tamron 17-70mm f2.8 for Fuji, when editing with Adobe software.

how long to wait?

[theshukans]

@curious_fashion1549 Completely agree with you!
That's so dumb to have that issue with such a cool lens.
I think about it a very day 😞

[curious_fashion1549]

Hello community.

This defect, which only occurs when shooting at 17mm and at a large aperture (f2.8...) Does it occur only with the X-T4 or has anyone also observed it with the X-H2s, for example? Thanks

[curious_fashion1549]

Nine months after reporting the bug, Adobe still hasn't fixed it, but if you don't pay a month's fee, Adobe does "fix" the subscription. 

[curious_fashion1549]

It is possible that the problem disappears in Adobe Photoshop, selecting the image and typing in the artificial intelligence “fix the double exposure ring bug” (irony mode)

[curious_fashion1549]

Foro en español donde se habla del problema.

https://fujistas.com/foro/threads/problema-tamron-17-70mm-vs-lightroom.66363/

[curious_fashion1549]

@Rikk Flohr: Photography ¿hay noticias?

Gracias !!!

[curious_fashion1549]

Do you remember in your childhood, the night you waited for Santa Claus with gifts?  I have the same feeling with Adobe, every time I turn on the computer and check if there is an update and when there is, I wonder, will this be the one that solves the double exposure/vignetting rings that occur in the combination Fuji x-t4 +  Tamron 17-70mm + Adobe? The same joy that Christmas day will produce me when that update arrives.

[curious_fashion1549]

There was an ACR update today, 15.4. It's like opening a surprise envelope, waiting for the gift I want to come out: no double vignetting rings on photos taken with the Fuji X-T4 + Tamron 17-70mm f2.8 . All my illusion went away when verifying that the error continues here. Waiting for the next update...

[curious_fashion1549]

No Tamron lens for Fujifilm X mount in the list of lenses compatible with Adobe software.

https://helpx.adobe.com/camera-raw/kb/supported-lenses.html

[curious_fashion1549]

Poll on the future of error:

a.- I hope that Adobe solves the error in a short time. 

b.- Adobe does not fix the error. I change the X-T4 for the X-HS2.
c.- Adobe does not solve the error. I trade the Tamron 17-70 for the Fujifilm 16-55mm.
d.- Adobe does not fix the error. Change Adobe for Capture One.

[Jakub30911411p62m]

Hi Fernando,

I wish I had found out about this prior to purchasing Tamron 17-70. I do love the lens though. Apparently it is up to Adobe to do something about it. It strikes me Adobe has not been able fix it over the period of 10 months. That sucks as I have been subscribed to Ps + Lr package for years. I do eperience the same weird phenomenon even on PC so I do not think this is a Mac issue only. 

I am downloading Capture One right now. Shame on Adobe for not fixing it over such a long period of time. I will make sure this gets plenty of attention on Fuji forums. 

Take care

[RubenKempter]

It's really a shame. Also have been subscribed to Adobe for so many years and just nothing on this (easily fixable) bug. 😞

@curious_fashion1549 

Thanks for throwing in the XH2S argument, i own that one now for video work, and have just tried the lens on that one. The problem seems to be gone in combination with the XH2S. That is a workaround for me right now, but certainly not even close to a good solution from adobe to anybody else. 

I was also close to selling the lens after not having used it for all those months because of this bug. But selling it now would mean loosing 400$ for a lens i used ONCE, on a job where I had to paint out the bug by hand in order to deliver.

@Rikk Flohr / Adobe 

Thanks for updating the bug status to "noted, don't care." 

[knowledgeable_Rose6C2C]

Adobe needs to fix this terrible bug!

[curious_fashion1549]

¿Cuánto tiempo falta para que corrijan el error?

¿Después de "CONFIRMADO" va "INVESTIGANDO" o "CORREGIDO"?

__

How long does it take for them to correct the error?

After "CONFIRMED" do you go "INVESTIGATING" or "CORRECTED"?

[RubenKempter]

Let's be real: Adobe won't fix this error, there's probably not enough Users with that Lens/Body Combination, so they do the math and it's not economical for them to do anything about it.

After 10+ Years with Adobe I'll now look into Davinci Resolve for Video Work.

I'll first cancel my Premiere Subscription and then I'll check out CaptureOne for Photography Work.

I've been putting up with all of Adobes Bugs for long enough, and the 50 bucks every month are not at all justified with the service they provide these days - at least on the applications I use. 

I'm sure losing me as a customer won't bring Adobe down, but from what I've been hearing from many colleagues I'm not alone with my decission. 

[Rikk Flohr: Photography]

Update:

Greetings all,

Updates for the Adobe Photography Products have been released.  The August 2023 updates contain a fix for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

Thank you for your patience.

[curious_fashion1549]

Hello. I have updated Adobe Camera Raw to today's version. If I open a RAW file in Adobe Photoshop the effect is fixed, but in LR CC I still get the error. I deleted the LR CC catalog previews file, rebooted the Mac and when I regenerated the previews in LR CC I got the double vignetting error. 

[FSt0p]

That's because Lightroom (Classic and Cloud) does not use ACR plugin.

They have ACR built-in, and we'll have to wait for updates to Lightroom with updated ACR to get this fix.

Hopefully it will be released soon enough.

[curious_fashion1549]

Thank you very much for the reply.

I didn't know. We will wait. The important thing is that Adobe has fixed it.

[curious_fashion1549]

When are you going to update Camera Raw for LR CC from 15.4 to 15.5 to fix this bug?

[MarcoRosado]

Hi everyone.

I'm using a Tamron 17-70mm f/2.8 Di III-A VC RXD for Sony E-Mount since february.

Recently, when i'm processing some RAW files, i found some weird artifacts (kind of an halo/vignette) when i push a little bit the exposure. I've tried the same file on another RAW editor (Capture One), and i don't ger the same issue, so i'm thinking is something that Lightroom "creates".... Does anyone else having the same issue, or has someone found a fix?

Here's an example. Just overpushed the exposure so the issue could be more visible. No other adjustments were made.

[theshukans]

hello! 
Could you share some daylight examples?
We had similar problem with his lens, but paired with Fujifilm X-T4, but it was fixed a while ago. at least I don't experience this issue anymore.

[MarcoRosado]

Oddly enough, after a quick review of some daylight images, the issue didn't seem to happen...

It's not an opticall flaw, so it must be something within the software.

Tomorrow i'll try some stuff during daylight time to check if i can replicate the issue