DaveEP Posted February 12, 2007 Share #1 Posted February 12, 2007 Advertisement (gone after registration) I was shooting in London over the weekend, and 3 or 4 times I would hit the shutter button but nothing would happen, then a few seconds later the shutter would fire, just about the time I had dropped the camera from my eye to see what was wrong. The switch was on normal shooting and not self timer mode. The next shot was fine, and no delays. It's almost as if the camera had gone to sleep, yet the shutter speed was showing in the viewer, and everthing else appeared normal. Has any one else had this problem? Link to post Share on other sites More sharing options...
reven Posted February 12, 2007 Share #2 Posted February 12, 2007 Could it be that the camera was sleeping ? Because after some time it goes into sleep mode and from there it takes some time to wake up and be ready. Link to post Share on other sites More sharing options...
DaveEP Posted February 12, 2007 Author Share #3 Posted February 12, 2007 I though of this too... but I had only turned it on a few moments ago (allowing for the usual startup time). When it happened the second time, I turn sleep mode to off. In addition, it happened once almost immediately after taking another shot, then the next shot was fine again. So, there was no way the camera had gone to sleep, and I know the camera was already awake because of the previous shot. The delay was just long enough to make you think you must have turned the camera off, and as you move it away from your eye it fires! Weird! Link to post Share on other sites More sharing options...
chetccox Posted February 12, 2007 Share #4 Posted February 12, 2007 Even if the camera goes to sleep, you can press the shutter and take a picture immediately. However, you will get the rainbow vertical stripes in the picture if you do not wait a few seconds for it to do whatever it does to fully awaken. Link to post Share on other sites More sharing options...
sps Posted February 12, 2007 Share #5 Posted February 12, 2007 This sounds like a slow memory card. Are you writing DNG+JPEG Fine and taking several exposures within a minute? Next time it happens, see if the red light is blinking on the back. Link to post Share on other sites More sharing options...
DaveEP Posted February 12, 2007 Author Share #6 Posted February 12, 2007 No, I really don't think it's a memory card issue. DNG only, and using Transcend 150x cards. I have taken several shots like this in a row before and not had a problem. At least two of the problems we 'not' after just taking a shot - so that discounts that too. Link to post Share on other sites More sharing options...
sps Posted February 12, 2007 Share #7 Posted February 12, 2007 Advertisement (gone after registration) Sorry to hear it. I'm using the 150 Transcend 4GB card without any such problems. I hope it works out for you. Link to post Share on other sites More sharing options...
Hans Roggen Posted February 12, 2007 Share #8 Posted February 12, 2007 Could it be that the camera was applying noise reduction? Happened to me a couple of times. Hans Link to post Share on other sites More sharing options...
wlaidlaw Posted February 12, 2007 Share #9 Posted February 12, 2007 This sounds like a slow memory card. Are you writing DNG+JPEG Fine and taking several exposures within a minute? Next time it happens, see if the red light is blinking on the back. I am not getting this problem but I am getting a slow response when I press Play, sometimes very slow. I am using a 4GB MyMemory 133x card. I have ordered a 2GB SanDisk Extreme III on the grounds that you usually get what you pay for and one has to say the MyMemory card is VERY CHEAP. It also seems quite slow when taking in DNG + JPEG fine mode. I wonder how reliable various manufacturers' speed claims are in real life. Wilson Link to post Share on other sites More sharing options...
rpierce Posted February 12, 2007 Share #10 Posted February 12, 2007 I believe I had something similar happen yesterday. For me, it happened once and the shutter did not close as if on the timer; it went when I pushed it again. The M8 was on, went to take photo and nothing happened; went to take another shot and it worked. I'm using SanDisk Ultra II 2GB, raw only. The previous shot was several minutes earlier. Since it only happened once, I put it down to a mistake on my part and if it happens again, I'll look for more info about the circumstances. My M8 is first batch, just back from The Fix. Bob Pierce Link to post Share on other sites More sharing options...
DaveEP Posted February 12, 2007 Author Share #11 Posted February 12, 2007 Could it be that the camera was applying noise reduction?Happened to me a couple of times. Hans This is an interesting theory, but can of course only apply to the times when I just took another shot. However, those shots were testing my new 75 cron @ f2 with fairly high shutter speeds, so I don't think N/R would be applied. Still, it is a possibility... Link to post Share on other sites More sharing options...
knipse_olivia Posted February 12, 2007 Share #12 Posted February 12, 2007 is it possible that you switched the "release selector" instead of "C" or "S" into the selftimer position? That happened to me one time... Link to post Share on other sites More sharing options...
Guest WPalank Posted February 12, 2007 Share #13 Posted February 12, 2007 so I don't think N/R would be applied. Still, it is a possibility... Dave, At least the few times my camera applied noise reduction it was very obvious. The LCD screen goes black, a message says something to the effect of "excuse me, noise reduction is now being applied", then you get a countdown timer in seconds. Link to post Share on other sites More sharing options...
DaveEP Posted February 12, 2007 Author Share #14 Posted February 12, 2007 Dave,At least the few times my camera applied noise reduction it was very obvious. The LCD screen goes black, a message says something to the effect of "excuse me, noise reduction is now being applied", then you get a countdown timer in seconds. This is my experience also, which is why I am pretty sure this was not the cause.... Link to post Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.