k-hawinkler Posted July 22, 2011 Share #461 Posted July 22, 2011 Advertisement (gone after registration) Hi there, BTW, it's K-H for Karl-Heinz. I agree. Without the issues, the M9 is absolutely wonderful. No doubt about it. Everybody has to be mindful that we are interested only in the intermittent problem. This has to be very carefully separated from everyday malfunctions, like hardware parts or memory cards really going bad. Best, K-H. Link to post Share on other sites More sharing options...
Advertisement Posted July 22, 2011 Posted July 22, 2011 Hi k-hawinkler, Take a look here My M9 is eating SD cards [MERGED}. I'm sure you'll find what you were looking for!
wlaidlaw Posted July 22, 2011 Share #462 Posted July 22, 2011 I am reasonably confident that this issue has been produced or at the very least, exacerbated by FW1.162. I use burst mode for 5 shot bracketing quite a bit. Since I am a bit deaf, I never use discrete mode, as the noise never worries me. Whereas I have had the odd lock up on my M9 over nearly 2 years now, it is only since 1.162 that I have had the missing/null images and long buffer clear times. Is anyone visiting Solms soon and if so, perhaps they could ask Leica how we could set up a reporting system for this issue. There is little point setting up a reporting system, which nobody at Leica is going to read. Null/missing images is really quite serious. Wilson Link to post Share on other sites More sharing options...
jaapv Posted July 22, 2011 Share #463 Posted July 22, 2011 I have been asked to make a FAQ entry on this. As soon as there is some kind of clariy about the cause and extent of the problem and reliable workarounds I will do soz Link to post Share on other sites More sharing options...
jaapv Posted July 22, 2011 Share #464 Posted July 22, 2011 It may be there in all cases but not uncovered because the specific conditions haven't occurred yet. IOW, the fact that it can't be duplicated immediately by a certain sequence of button presses doesn't mean that there isn't a problem. It's hard to prove a negative. The fact that a particular M9 hasn't turned into a frog doesn't mean it won't. I would suggest that the position: "your camera has no problem but mine has so yours has it as well but just hasn't broken down yet" is in the same league as " your camera has a problem and mine doesn't so it must be user error". Equally unproductive, I would say. Link to post Share on other sites More sharing options...
k-hawinkler Posted July 22, 2011 Share #465 Posted July 22, 2011 I am reasonably confident that this issue has been produced or at the very least, exacerbated by FW1.162. I use burst mode for 5 shot bracketing quite a bit. Since I am a bit deaf, I never use discrete mode, as the noise never worries me. Whereas I have had the odd lock up on my M9 over nearly 2 years now, it is only since 1.162 that I have had the missing/null images and long buffer clear times. Is anyone visiting Solms soon and if so, perhaps they could ask Leica how we could set up a reporting system for this issue. There is little point setting up a reporting system, which nobody at Leica is going to read. Null/missing images is really quite serious. Wilson Hi Wilson, I agree with you that something changed significantly with FW 1.162. However, I have encountered the problem also with the previous FW version when fiddling with the controls in the back of the M9. The symptoms just vary a bit. But that's it. Best, K-H. Link to post Share on other sites More sharing options...
jaapv Posted July 22, 2011 Share #466 Posted July 22, 2011 I am reasonably confident that this issue has been produced or at the very least, exacerbated by FW1.162. I use burst mode for 5 shot bracketing quite a bit. Since I am a bit deaf, I never use discrete mode, as the noise never worries me. Whereas I have had the odd lock up on my M9 over nearly 2 years now, it is only since 1.162 that I have had the missing/null images and long buffer clear times. Is anyone visiting Solms soon and if so, perhaps they could ask Leica how we could set up a reporting system for this issue. There is little point setting up a reporting system, which nobody at Leica is going to read. Null/missing images is really quite serious. Wilson I fully agree Leica should be alerted but I happen to know that this forum is being read carefully in Solms. However, I find it telling that there was not one report of this during the extensive beta testing of this firmware by a large group of forum members looking for glitches. Link to post Share on other sites More sharing options...
dwbell Posted July 22, 2011 Share #467 Posted July 22, 2011 Advertisement (gone after registration) Telling in what way? Link to post Share on other sites More sharing options...
k-hawinkler Posted July 22, 2011 Share #468 Posted July 22, 2011 Telling in what way? Here are a couple interesting and relevant posts on this subject: http://www.l-camera-forum.com/leica-forum/1742376-post45.html Quote:"Late to this thread, but I had this problem happen twice (when saving DNG+JPG fine), once recently after the firmware update ("lost"/never recorded about 20 photos); also occurred during the beta test of the firmware. Included a couple freezes that required a battery pull / power recycle. Using a 16GB Sandisk Extreme (current version)." http://www.l-camera-forum.com/leica-forum/1743681-post71.html http://www.l-camera-forum.com/leica-forum/1743801-post73.html Best, K-H. Link to post Share on other sites More sharing options...
wlaidlaw Posted July 22, 2011 Share #469 Posted July 22, 2011 It may well have been there during the Beta FW test phase. As far as I can recall, I don't think I ever used continuous (burst) mode during the Beta FW testing, as I was changing settings with each shot and writing down the settings. The main things I was looking for were symmetric and asymmetric vignetting, Auto White Balance and Italian flag correction with various lenses, not things that were not an issue before the Beta FW. I have never had the missing images on DNG but only when taking DNG and JPEG Fine, which I do when I want to have a quick look at the images on my iPad, as I don't have a laptop with me. I have once had the lock up and long buffer clear time on DNG only but no missing images in that case. I use nothing but 16GB Sandisk Ultra cards and quick format each time in camera after downloading the images. Wilson Link to post Share on other sites More sharing options...
nodrog Posted July 22, 2011 Share #470 Posted July 22, 2011 It may well have been there during the Beta FW test phase. As far as I can recall, I don't think I ever used continuous (burst) mode during the Beta FW testing, as I was changing settings with each shot and writing down the settings. The main things I was looking for were symmetric and asymmetric vignetting, Auto White Balance and Italian flag correction with various lenses, not things that were not an issue before the Beta FW. I have never had the missing images on DNG but only when taking DNG and JPEG Fine, which I do when I want to have a quick look at the images on my iPad, as I don't have a laptop with me. I have once had the lock up and long buffer clear time on DNG only but no missing images in that case. I use nothing but 16GB Sandisk Ultra cards and quick format each time in camera after downloading the images. Wilson >_< This post makes my head ache. Link to post Share on other sites More sharing options...
nodrog Posted July 22, 2011 Share #471 Posted July 22, 2011 I thought that this thread should be included in the merged thread currently bubbling. Something needs to be done. Come on, gnomes of Sölms, pull your fingers out! Link to post Share on other sites More sharing options...
k-hawinkler Posted July 22, 2011 Share #472 Posted July 22, 2011 Another merger makes perfect sense. K-H. Link to post Share on other sites More sharing options...
Robert_M Posted July 22, 2011 Share #473 Posted July 22, 2011 I now have a completely unscientific and unverified feeling it's to do with soft / descreet mode. I'm also wondering, if my auto-off is set to 1min, which it is, and I get one of the "slow write" occassions as described above then it could well be that the camera auto off's during the writing of several files from the buffer. This is then replicating Jaapv's experience where he physically turned off the camera. All speculation - but until Solms come back with anything that's all I have. dwbell, I find this a very interesting idea. I have been wrapping my mind around some of the same thoughts in the last few days and going over the manual as to what may be different in these shutter modes. Thank you for bringing it up - you beat me to the punch. I have almost always been using discrete mode and also have auto-off set to 1 min. I still can't figure why different SD cards come into the mix (at least for me) but that may have to do with write speeds and buffer interaction/handling. K-H, Yes, excellent list. I will go through the list for my experience and answer soon. Another parameter I'd like to throw into the mix: What is the battery level when the "failure" occurs? The battery level reading is a fairly complex function in the camera. If there is a slight error in this analysis (even momentarily) it is conceivable that it causes some pausing in the SD card write to preserve power. Just another random thought.... I am encouraged that the tone of this thread has now turned to pinning down facts and symptoms. That is a step forward in itself. RM Link to post Share on other sites More sharing options...
k-hawinkler Posted July 22, 2011 Share #474 Posted July 22, 2011 Hi RM, Many thanks. The battery stuff needs to be in there, of course. I didn't think of it as that has never been an issue for me. But of course, it has been for others. The tone has certainly changed. Now we need to get good participation once we have finalized our procedure. I believe, folks who suffered, are eager to get this problem under control. So I would think participation is the best way for those folks to help themselves and every M9 user as well. Best, K-H. Link to post Share on other sites More sharing options...
wlaidlaw Posted July 22, 2011 Share #475 Posted July 22, 2011 >_< This post makes my head ache. This is a helpful comment - have you anything useful to add? Wilson Link to post Share on other sites More sharing options...
steelduck Posted July 22, 2011 Share #476 Posted July 22, 2011 I cannot go into the details as Leica has not given me a OK to copy paste the email here. I just say that I was informed that Leica has acknowledged the issue and are working hard to figure it out. Link to post Share on other sites More sharing options...
jaapv Posted July 22, 2011 Share #477 Posted July 22, 2011 Another merger makes perfect sense. K-H. Done Link to post Share on other sites More sharing options...
dwbell Posted July 22, 2011 Share #478 Posted July 22, 2011 This is a helpful comment - have you anything useful to add? Wilson I read it as meant in a light hearted way Wilson. Might be best to question the tone before assuming a negative one? Link to post Share on other sites More sharing options...
dwbell Posted July 22, 2011 Share #479 Posted July 22, 2011 I cannot go into the details as Leica has not given me a OK to copy paste the email here. I just say that I was informed that Leica has acknowledged the issue and are working hard to figure it out. Well wonderful, that sounds very encouraging. Maybe I wasn't imagining it after all..... Link to post Share on other sites More sharing options...
LBX Posted July 22, 2011 Share #480 Posted July 22, 2011 Ok. Don't know if this will help everybody but. I just got Brand New M9. I'm a working pro so I bought 24 cards all the same Sandisk Extreme 8gb. I was shooting on self timer. Then forgot it was on and hit shutter release and realized it was in self timer mode, so I powered it off to "cancel" before the shutter fired. Then poof. It would not come back on. All my previous shots were gone I shot 30 minutes prior. camera was completely dead, so I powered down, and pulled card and battery, then back in, and nothing. Did the same with new card, everything back to normal. SO I quarantined card and figured no prob, I can dump the card and I'll get what is on it later (I know they are on there, I saw the previews when I was shooting earlier. Not so. Card would not mount etc. like the other posts. Anyway, I scheduled re-shoot (corporate portraits) but thought in the meantime I will do damage control and try to salvage images. Here is what I did in a big hurry, BUT IT WORKED: buy a Hyperdrive Colorspace UDMA. Don't try the recover mode, it did not work for me. DO the usual backup (dumping the card to the device) WATCH the files as they are written to device. It will stop at the bad (corrupted file) and nothing will be saved to device. THen note the file that it "hung up" on. Then Reboot the device as it will have locked up. Then insert card again and "browse" to the file that is bad in File Manager of the colorspace device. DELETE THE BAD FILE PLUS ALL THE FILES BEHIND IT. via the colorspace file manager THEN go back and do the usual card dump. It worked for me. I am not positive that you have to delete all files behind the corrupted one, but I did it for safe measure. SO within receiving my brand new hyperdrive to recovered files, less than one hour of trial and error and I'm back in business. Got my Original DNG files all intact except for a few (7 files) before the camera crashed. I wanted to share this asap to any that might need this tip. I'm sorry if any of this is old news or redundant, as I did not spend time reading all the posts as I had to figure out how to salvage this job in a short amount of time. Hopefully this will help others. any details needed.... Better use a PM than a telephone number - Jaapv Link to post Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.