molto1 Posted July 25, 2013 Share #21 Posted July 25, 2013 Advertisement (gone after registration) Thank you very much !! I will try molto1 Link to post Share on other sites More sharing options...
Advertisement Posted July 25, 2013 Posted July 25, 2013 Hi molto1, Take a look here M9 shutter taking 5 seconds to comlete it's click!. I'm sure you'll find what you were looking for!
nggalai Posted July 25, 2013 Share #22 Posted July 25, 2013 same issue here.I found a trick that helps when the shutter is stuck and the finger has already left: half press the release again and the shutter will start to reload immediately. hope it helps, for me it works 100% G Works here, too. It’s sort of automatic for me by now; if I don’t feel the rewind I just tab the release. There’s little reason for me to stick with the current firmware, though – I don’t own any of the lenses which the “new” firmware supports via lens profiles. So I might downgrade to 1.176 again, just for the heck of it. Link to post Share on other sites More sharing options...
AceVentura1986 Posted July 25, 2013 Share #23 Posted July 25, 2013 Anyone know if you can load 1.176 on an ME? In theory, they're just rebadged M9s. Link to post Share on other sites More sharing options...
adan Posted July 25, 2013 Share #24 Posted July 25, 2013 On the question of batteries shutting down much sooner (50%) using firmware 1.196. That is the whole idea of the firmware! You risk other problems if you are using older batteries without the new firmware. It isn't a bug - it is an intentional improvement. From Leica's list of revisions for 1.196: "Improved power management. The camera is now measuring battery stability internally. In case of weak battery stability, the camera switches off automatically. Using old batteries could have lead to camera crashes and banding stripes under certain conditions with the previous firmware versions. Especially the usage of nearly 6 years old M8 batteries proved to be critical. It is the nature of Li-ion batteries that the capacity weakens after a certain time. We recommend replacing the batteries for the M8 and the M9 after 3 years at the latest. Heavy usage can even accelerate the aging process, and then batteries should be replaced earlier. In case that the total amount of pictures, that can be taken with a certain battery, is significantly lower than before with Firmware 1.196, we recommend replacing this battery." I had multiple banding and camera-lock-up problems last winter (and yes, one of my batteries dates to the M8 era). Now those problems have gone away, thanks to upgrading to 1.196. Link to post Share on other sites More sharing options...
jplomley Posted July 25, 2013 Share #25 Posted July 25, 2013 This is a known bug in FW1.196 together with inoperative highlight clipping. Leica have known about this for almost a year but have still shipped every M-E with these bugs. Shocking given that they upgraded the MM firmware. Link to post Share on other sites More sharing options...
pico Posted July 25, 2013 Share #26 Posted July 25, 2013 I worked in IT for over thirty years, and if we had a firmware as screwed up as Leica's for the M9 we would be ashamed. Leica should be, too. WTF are they doing, besides nothing? . Link to post Share on other sites More sharing options...
MarkP Posted July 26, 2013 Share #27 Posted July 26, 2013 Advertisement (gone after registration) Has anyone gone back to 1.176 and resolved ths issue? Link to post Share on other sites More sharing options...
elgenper Posted July 26, 2013 Share #28 Posted July 26, 2013 On the question of batteries shutting down much sooner (50%) using firmware 1.196. That is the whole idea of the firmware! You risk other problems if you are using older batteries without the new firmware. It isn't a bug - it is an intentional improvement. ..... Has anyone gone back to 1.176 and resolved ths issue? Mark, yes I did just that, and have had zero problems after that. Andy, you´re right on that point, of course; I do recall Leica saying so when the 1.196 was released. So, even if it hurts a bit, I would accept this part of it. What I CANNOT and WILL NOT accept is the intermittent recocking delay: I want to use discreet mode, and when I do shoot, I want to concentrate on the subject, not on various ways to coax the camera into actually doing its part.... It is really up to Leica to fix this ridiculous bug with a new update; if they feel the need to retain the ´battery sales protection feature´, then so be it. And, until they do, I stay with 1.176. Link to post Share on other sites More sharing options...
GLAUMAX Posted July 26, 2013 Share #29 Posted July 26, 2013 I am happy I found this thread. I have the same issue since day one with my new M-E. I was prepared to send it to Solms. I will downgrade the firmware. Thanks to all. Link to post Share on other sites More sharing options...
GLAUMAX Posted July 26, 2013 Share #30 Posted July 26, 2013 Just tried to downgrade to 1.176 and I have a message : this firmware doesn't work on your camera. I tought that the hardware of the M-E was 100% similar to the M9. I was apparently wrong. Link to post Share on other sites More sharing options...
swamiji Posted July 27, 2013 Share #31 Posted July 27, 2013 Just tried to downgrade to 1.176 and I have a message : this firmware doesn't work on your camera.I tought that the hardware of the M-E was 100% similar to the M9. I was apparently wrong. The M-E has a different camera ID code. The firmware was coded to read the code. The firmware is not backward compatible, even if the hardware is identical else wise. Link to post Share on other sites More sharing options...
MarkP Posted July 27, 2013 Share #32 Posted July 27, 2013 Well I've had two problems with the M9 since the upgrade to 1.196. First, the problem described here of delayed re-cocking of the shutter after exposure when on discrete mode. Second, an intermittent delay between depressing the shutter release button and the actual shutter release. Both now fixed upon reverting to 1.176. Thanks for the advice Link to post Share on other sites More sharing options...
leicanet Posted July 27, 2013 Share #33 Posted July 27, 2013 Just received my Monochrome with the "upgraded" 1.02 firmware. And I too am having problems with the shutter intermittently completing its rewinding cycle only after a few seconds after the shot is taken. Shall I too reverse the firmware to the previous version...? Link to post Share on other sites More sharing options...
Guido Posted July 27, 2013 Share #34 Posted July 27, 2013 The M-E has a different camera ID code. The firmware was coded to read the code. The firmware is not backward compatible' date=' even if the hardware is identical else wise.[/quote'] Since there is an USB/PTP menu option in the M9 and the USB port is missing in the M-E, it seems plausible that firmware versions before 1.196 were not made M-E aware yet and thus won't be allowed to load. The hardware may be only 99% identical after all. Link to post Share on other sites More sharing options...
brill64 Posted July 29, 2013 Share #35 Posted July 29, 2013 a couple of little taps on the shutter button, as if to wake the camera from sleep mode, usually releases it. Link to post Share on other sites More sharing options...
D&A Posted July 29, 2013 Share #36 Posted July 29, 2013 I thought I had read a few posts here and or in another forum that some with specifically the Leica M-E body, we're able to revert back to 1.176 fiirmware from the current latest one. Can anyone with a Leica M-E body confirm that they've been successful in doing this? The other question is some with M-9 or M-E bodies and the latest firmware 1.196 say they don't have the report ed issues with descrete mode as others do. If this is true, maybe electronics or circuitry is slightly different in early vs. late model production and that only Ate model produced m9 bodies as well as M9-P and m-E bodies are affected when loaded with 1.196? Dave (D&A) Link to post Share on other sites More sharing options...
jaapv Posted July 29, 2013 Share #37 Posted July 29, 2013 Afaik it is impossible to load M9 firmware in the ME. My M9 (one of the very first ones) has no problems, except possibly for the discreet bug which doesn't bother me as I never use the combo - so I never experienced it. Any other problem is avoided by using certain cards like Panasonic. Link to post Share on other sites More sharing options...
pico Posted July 29, 2013 Share #38 Posted July 29, 2013 [...] If this is true, maybe electronics or circuitry is slightly different in early vs. late model production[...] That question has occurred to me often. It is a software engineer's nightmare when components are changed during production of the product for which he coded, especially in embed systems. I will write once again that it would most helpful to have a 'configuration dump + ' option to facilitate debugging and communication between users and Leica. Link to post Share on other sites More sharing options...
pfhrased Posted July 30, 2013 Share #39 Posted July 30, 2013 I'm not sure if this is the same for others, but the recocking delay is perfectly aligned with card-write on my M9-P. As soon as the red light stops blinking, it recocks. Link to post Share on other sites More sharing options...
pico Posted July 30, 2013 Share #40 Posted July 30, 2013 I'm not sure if this is the same for others, but the recocking delay is perfectly aligned with card-write on my M9-P. As soon as the red light stops blinking, it recocks. The camera should not wait. The buffer is there to accommodate the next activation (shutter release). Leica's firmware, and possibly their manufacturing and acquisitions protocols are broken. Link to post Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.