visoflex Posted September 23, 2018 Share #1 Posted September 23, 2018 Advertisement (gone after registration) Using firmware 2.4.5.0. Looking at some photos uploaded, I notice that the metadata indicates that one photo has been taken with a Tri-Elmar 16-18-21 ASPH lens. But I don't and never have owned a Tri-Elmar 16-18-21 lens. Curious! Additionally, the camera is set for Multifield exposure metering, but the metadata says that it is centre weighted. Anyone else noticed this or anything similar? Welcome, dear visitor! As registered member you'd see an image here… Simply register for free here – We are always happy to welcome new members! Link to post Share on other sites Simply register for free here – We are always happy to welcome new members! ' data-webShareUrl='https://www.l-camera-forum.com/topic/289748-m10-unusual-metadata/?do=findComment&comment=3598165'>More sharing options...
Advertisement Posted September 23, 2018 Posted September 23, 2018 Hi visoflex, Take a look here M10 Unusual Metadata. I'm sure you'll find what you were looking for!
TomB_tx Posted September 23, 2018 Share #2 Posted September 23, 2018 Mutifield metering only works when using live view. With live view off, it only uses center weighted regardless of setting. Link to post Share on other sites More sharing options...
visoflex Posted September 23, 2018 Author Share #3 Posted September 23, 2018 Thanks - that's one question answered. Link to post Share on other sites More sharing options...
adan Posted September 23, 2018 Share #4 Posted September 23, 2018 (edited) 1) What lens DID you use? 2) was that lens 6-bit coded? And was it official "factory" or "Leica service upgrade" coding? 3) How is you M10 set for "lens detection" - "Auto"? or "M Lens" manual? The lens detection for M lenses is, of course, purely optical/mechanical. No electrical contacts. Just infra-red light LEDs/sensors, that bounce IR light off the back face of the lens to detect the painted B&W "bar code" of 6 black or white dots on the lens. Combined with a micro-switch that reads the position of the frameline selector (28/90, 35/135, 50/75). As such, it is - sensitive - to things like: poor coding marks (hand-made, or otherwise insufficiently black and white), dirt blocking the white spots (or the camera IR sensors), the lens not being exactly "clicked in" to the locked mounting position, or a mismatch between the 6-bit code and the frameline position ("sees" coding pattern for a "50mm f/2", but "senses" framelines set to 35/135 or 28/90.) The M10 in particular will revert to the current manual lens choice in the menu, if it senses "garbage" or confused data from the auto-detect system. An intentional, useful feature - since if one has three factory-coded lenses, and one uncoded lens, the M10 can automatically ID all four lenses (three from their coding, and the fourth by reverting to the menu setting, which can be permanently set to ID the fourth uncoded lens). To make that work, the M10 is far more sensitive to "ratty" data from the auto-detect system, espcially hand-painted 6-bit markings that worked on previous (M8/9/240) cameras. I had a 90 Summicron, hand-coded, that my M10 insisted was a 35 f/1.4 ASPH. Try putting your "suspect" lens on the camera, turn the camera on, and press the "info" button. The camera will show you a lot of info, including the lens it thinks is currently mounted. Which is what will be recorded in the metadata. Edited September 23, 2018 by adan 2 Link to post Share on other sites More sharing options...
visoflex Posted September 23, 2018 Author Share #5 Posted September 23, 2018 Thanks for that. I've checked all 3 lenses and they register correctly. I'll put it down to a temporary aberration and lose no further sleep over it. 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