willeica Posted April 18, 2018 Share #21 Posted April 18, 2018 Advertisement (gone after registration) The net problem in my case is a stuck lens release which is leading to over-rotation, six bit recognition and focus issues. Those M mounts a lot more intolerant to misalignment than you might think. William Link to post Share on other sites More sharing options...
Advertisement Posted April 18, 2018 Posted April 18, 2018 Hi willeica, Take a look here Auto lens detection not working.. I'm sure you'll find what you were looking for!
colorflow Posted April 19, 2018 Share #22 Posted April 19, 2018 In my case my M10 does not detect my Elmarit 24 ASPH. The lens is not over-rotated on the M10, the coding is clean, it is properly detected on my Monochrom I, and was properly detected on my M240 when I had it. So my question is does anyone have the same problem, or have an M10 that properly detects the Elmarit 24 ASPH? Link to post Share on other sites More sharing options...
jaapv Posted April 19, 2018 Share #23 Posted April 19, 2018 Thank you Pico. I use LR6 for processing all of my photos and regularly apply LR's lens correction for the specific lens. I just wonder if any lens correction done in camera using the wrong profile can be overridden by the profile used by Adobe in LR. If not, then I would disable the auto detect function of the M10 for the problematic lenses, if I remember. I would have to guess this would be more important for the 24 Elmar than for the 35 Summicron.As far as I am aware, LR does not override any in-camera corrections. This is applied before the data are written to DNG. This is in contrast to the Q which carries the corrections in a separate file embedded in the DNG Link to post Share on other sites More sharing options...
mdemeyer Posted April 19, 2018 Share #24 Posted April 19, 2018 Mine detects the 24 3.8 ASPH 100% of the time. Never seen an issue with any firmware release. So it’s not firmware. In my case my M10 does not detect my Elmarit 24 ASPH. The lens is not over-rotated on the M10, the coding is clean, it is properly detected on my Monochrom I, and was properly detected on my M240 when I had it. So my question is does anyone have the same problem, or have an M10 that properly detects the Elmarit 24 ASPH? Link to post Share on other sites More sharing options...
colorflow Posted April 20, 2018 Share #25 Posted April 20, 2018 Mine detects the 24 3.8 ASPH 100% of the time. Never seen an issue with any firmware release. So it’s not firmware. Mine is the 24 2.8 Elmarit ASPH which is a different code from the 3.8. Anyone has that on the M10? Link to post Share on other sites More sharing options...
Ecar Posted April 23, 2018 Share #26 Posted April 23, 2018 Mine is the 24 2.8 Elmarit ASPH which is a different code from the 3.8. Anyone has that on the M10? Yes - just mounted and unmounted it a few times on the M10. Always immediately detected. Link to post Share on other sites More sharing options...
colorflow Posted April 24, 2018 Share #27 Posted April 24, 2018 Advertisement (gone after registration) Yes - just mounted and unmounted it a few times on the M10. Always immediately detected. Thanks. This is strange. My 24/2.8 works on the 240, Monochrom I, but not on my M10 ??? Link to post Share on other sites More sharing options...
Coolattitud Posted April 30, 2018 Share #28 Posted April 30, 2018 hello, I just bought a used noctilux that I ride on a new Leica M10, and I do not see the coupling box active lens, in auto, and in manual the noctilux is not in the list, the firmware of the device is 1.10.4.0. Thank you in advance for your advice Link to post Share on other sites More sharing options...
Gobert Posted April 30, 2018 Share #29 Posted April 30, 2018 Which noctilux? Link to post Share on other sites More sharing options...
Coolattitud Posted April 30, 2018 Share #30 Posted April 30, 2018 the 50 mm 0,95 Link to post Share on other sites More sharing options...
Gobert Posted April 30, 2018 Share #31 Posted April 30, 2018 I checked. You’re right. The 50/1.0 version although is there. Link to post Share on other sites More sharing options...
Dino G. Posted July 18, 2023 Share #32 Posted July 18, 2023 On 4/14/2018 at 10:08 PM, ymc226 said: Has anyone re-installed the current firmware or an older version (if this is possible) to see if this corrects the issue? I have the same problem ... do you thing that can be the firmware ? Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now