Jump to content

Firmware Glitch


Guest sirvine

Recommended Posts

Guest sirvine

Advertisement (gone after registration)

I turned on DNG+JPEG for the first time since the firmware upgrade so I could preview in B&W. The frame count on the top LCD shows 500+ exposures left when the camera is first turned on. This drops down to about 140 exposures when I start shooting, or when I change ISO settings, which is the correct number of exposures for a 1GB card shooting DNG+JPEG with a few shots already saved.

Link to post
Share on other sites

x
I turned on DNG+JPEG for the first time since the firmware upgrade so I could preview in B&W. The frame count on the top LCD shows 500+ exposures left when the camera is first turned on. This drops down to about 140 exposures when I start shooting, or when I change ISO settings, which is the correct number of exposures for a 1GB card shooting DNG+JPEG with a few shots already saved.

 

 

Not really, 140 is about the right amount for a 2GB card. A 1GB card would be about 68-70.

 

I just checked mine and when set to DNG+JPG, turn camera of then on I get 136.

If you were previously using JPG only that could be it. I mainly shoot DNG only.

Link to post
Share on other sites

Guest sirvine

You're right, I meant 2GB. I shoot mainly DNG, too. It's still a firmware glitch if the camera shows more exposures than are available on the card, and then adjusts itself downward for no apparent reason.

Link to post
Share on other sites

You're right, I meant 2GB. I shoot mainly DNG, too. It's still a firmware glitch if the camera shows more exposures than are available on the card, and then adjusts itself downward for no apparent reason.

 

For some reason the M8 never changes the shots left display when going to Jpg from DNG or the other way or when doing DNG+Jpg until you turn off then on or take a shot.

Bug??? Who cares. If for some reason you have only a few shots left on the card when you change this setting then change out the card for a fresh one. Are you going to shoot 136 shots before you look at the shots left LCD. Remember film, you have to remember whether you had a 24 or 36 exposure roll in the camera and then subtract the shot counter from the total to find out how many where left. I don't think I shot to many full 36 exposure rolls before I switched it with a fresh roll.

 

This is starting to sound like the Nikon forum with the D200 showing about half the remaining shots when using compressed RAW.

Link to post
Share on other sites

Guest sirvine

Alright, then. We're just going to let the display for exposures left be wrong, and shug it off? It ought to display the number of exposures left, and that's not being nit-picky. Can I work around it? Of course I can.

Link to post
Share on other sites

Guest guy_mancuso

Sol i think was is happening is the camera has to sort of need a reboot to read the card when you make this change , you have to take a shot after you make the menu change so it can read the card capacity than will make a adjustment after it knows your change . Same with turning on and off. It really is not a bug but it needs to re read the card so it knows what the new remaining count should be with the menu change you did. Sort of like a set button idea

Link to post
Share on other sites

Advertisement (gone after registration)

I had a similar experience that I noted after downloading v. 1.102 yesterday. When you turn the M8 on (and you are in DNG only with a 512MB card), the file counter starts at about 140 but AFTER teh first shot, drops to the (correct) number 45. The value 140 re-appears after you turn the camera off adn restart it. Again it drops to the correct value AFTER another shot is taken. If you lightly depress the shutter, no change happens. I call this a bug IMHO..... :rolleyes:;)

Link to post
Share on other sites

There is also a considderation to be made as to how event driven the firmware must be. The more stuff you want the camera to go check say every second or so the more power it consumes. That power is IMHO better spent allowing us to take more shoots before we have to change the battery. Sometimes engineers have to chose the lesser of serveral evils. I'm not saying this isn't a bug, just that it might be one we want to live with.

Link to post
Share on other sites

Guest sirvine

Albert -- this is the problem I have exactly.

 

Carl + Guy -- I hear you, and I don't want to add time to startup, but it's checking the card on startup anyway, otherwise where does the 500+ value come from? My theory is that it checks JPG only capacity on startup and then revises to DNG+JPG after the first button press.

Link to post
Share on other sites

Guest guy_mancuso

Yes Sol it actually maybe a glitch and hard to say but from what i see that it is doing is it wants to re read the card , so glitch or not just the way it works. I can send a note in and see if i can get some clarifaction on it. I think it is just the way the firmware is written

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...