Skip to main content
F
FeedbackCommunityMember
Inspiring
May 3, 2016

P: Tamron 150-600 not recognised in developer module

  • May 3, 2016
  • 16 replies
  • 742 views

Lightroom 6.5.1: Nikon D750 with Tamron 150-600/5-6.3, nef file converted to dng upon import, library module recognises and displays correct camera and lens information but developer module is unable to identify lens automatically for correction despite having a respective profile from Adobe, Tamron 70-200/2.8 would work flawlessly, fix would be very much appreciated - Thanks, Stephan

    This topic has been closed for replies.

    16 replies

    F
    FeedbackCommunityMemberAuthor
    Inspiring
    June 9, 2016
    Hi Rikk,
    Hi Everyone,

    thanks for the support. I can confirm that it works like a charm in Lightroom 6.6!

    Brilliant.
    Best regards
    Stephan
    Rikk Flohr_Photography
    Community Manager
    Rikk Flohr_PhotographyCommunity Manager
    June 8, 2016
    This should now be fixed as of the CC2015.6/6.6 update released today. You can find more details here: http://blogs.adobe.com/lightroomjournal/2016/06/lightroom-cc-2015-6-now-available.html
    Rikk Flohr: Adobe Photography Org
    ccastleb
    Adobe Employee
    ccastleb
    Adobe Employee
    May 6, 2016
    Camera make is not as important when looking up a lens profile against a source image. Lens metadata is the main thing used for this. Each lens vendor/camera body includes/excludes lens metadata differently, so we have to use custom code in some cases in order to help the lookup routine make an intelligent guess as to which lens was actually used to make the image. The Tamron case is not unique; it's a common issue with 3rd party lenses on other camera bodies. I've just recently figured out a reasonable way to work around the limitations (mainly related to lens IDs that I mentioned previously) to make auto matching work for that lens make.
    ssprengel
    ssprengel
    Inspiring
    May 6, 2016

    E=Canon threw me off, otherwise I would have guessed. 

    Is the non-filtering of profiles by camera make Tamron-specific behavior?

    I never use the lens corrections in PS, but from your answer I assume there isn't any camera-make distinction between lens profiles, then, like there is in ACR/LR, or is this Tamron-specific behavior? 

    ccastleb
    Adobe Employee
    ccastleb
    Adobe Employee
    May 6, 2016
    Hi Stephan,

    I have confirmed that the fix I am working on to enable Tamron lenses to automatically match lens profiles works on your NEF file, because lens names are not written in EXIF for third-party lenses on Nikon, so we fill it in and that is one factor that enables the match.

    The DNG already has a generic lens name baked into (via conversion to DNG with the current implementation) it so the new code will honor that and not make the change/match the profile because we cannot reasonably disambiguate that from a Nikon lens with the same lens ID without unintentionally mixing them up. You can still work around this using custom lens profile defaults as Steve explained earlier.

    When this new fix makes it to a production build, future DNGs will have the correct lens name inserted and that will enable matching for DNGs as well.

    Hope that helps.

    - Chris
    ccastleb
    Adobe Employee
    ccastleb
    Adobe Employee
    May 6, 2016
    VC A011E (Canon EF), VC A011N (Nikon F), and A011S (Sony A). The profiles are generated by Tamron from lens design data and we (Adobe) make some minor modifications before including them in the products.
    ssprengel
    ssprengel
    Inspiring
    May 6, 2016

    There are three profiles listed:  VC A011E and VC A011N seem the same and non-VC A011S.  I am not sure why there are so many versions but maybe a specific profile isn't being used because Adobe cannot tell which of the three (or at least of the two VCs) it should be.

    If you look at my reply to Rikk's and his, earlier in the thread, you'll see how to have LR default to the right lens instead of saying None by customizing the LR Lens Setup to Default instead of Auto and also saving profile you choose after clicking Tamron as the Default profile for that lens in LR.

    F
    FeedbackCommunityMemberAuthor
    Inspiring
    May 5, 2016
    When I check the box to activate lens correction within the developer module I get the error message that it was not possible to identify a suitable profile automatically. If I choose Tamron as manufacturer the correct profile A011N is picked straight away. This indeed confirms what Chris wrote.

    Best regards
    Stephan
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    May 5, 2016
    Hi Steve,

    So sorry. I rushed and overlooked it. Please find the links attached. I used OneDrive, hope that doesn't matter, I don't have a dropbox account.

    Appologies and best regards
    Stephan

    DNG
    https://onedrive.live.com/redir?resid=C4DE3BE7AD9FDB86!1132&authkey=!APohwNjMUKd2DWU&ithint=file%2cdng

    NEF
    https://onedrive.live.com/redir?resid=C4DE3BE7AD9FDB86!1133&authkey=!AIbFetzQh-j-oI0&ithint=file%2cNEF
    ssprengel
    ssprengel
    Inspiring
    May 5, 2016
    In my previous post I say what to do.  Upload to www.dropbox.com (create an account if need be) and post a public share link to it, here.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices