Durr3
Established
How do I check for the total shots taken on a M8? thanks
Benjamin
Registered Snoozer
Count how many till the shutter busts and work backwards..
rya
Established
I don't own an M8, but...
Depending on your computer operating system there are different programs to download (free) that will be able to tell by looking at a file from the camera. Search for "EXIF" reader programs and feed a file from the camera to one, it should tell you.
Depending on your computer operating system there are different programs to download (free) that will be able to tell by looking at a file from the camera. Search for "EXIF" reader programs and feed a file from the camera to one, it should tell you.
gshybrid
Well-known
actuations
actuations
When viewing the latest image from the camera in question in Bridge you can search the metadata for the "Image Unique ID" This number is a long string of zeros followed by some whole numbers and letters. You can enter these numbers(you don't have to include the preceding zeros) into an online hexadecimal converter to get the decimal equivalent which is the actuation number for that shot. It might sound a bit complicated but it actually quite easy.
actuations
When viewing the latest image from the camera in question in Bridge you can search the metadata for the "Image Unique ID" This number is a long string of zeros followed by some whole numbers and letters. You can enter these numbers(you don't have to include the preceding zeros) into an online hexadecimal converter to get the decimal equivalent which is the actuation number for that shot. It might sound a bit complicated but it actually quite easy.
chief
Newbie
Total shots taken are in the EXIF data and described as Unique Image ID.
It's in hex so need to convert it to decimal to get the number
of actuations. Only use the digits after all zeros.
You can use converter below:
http://www.easycalculation.com/hex-converter.php
It's in hex so need to convert it to decimal to get the number
of actuations. Only use the digits after all zeros.
You can use converter below:
http://www.easycalculation.com/hex-converter.php
ampguy
Veteran
This Unique Image ID # only equals the # of activations if your current directory is 100Leica.
If your folders are 10xLeica, where x > 0, you would multiply x by 10,000, then add the above for a total.
If your folders are 10xLeica, where x > 0, you would multiply x by 10,000, then add the above for a total.
Jeicob
Amateur
Huh?This Unique Image ID # only equals the # of activations if your current directory is 100Leica.
I got an used M8.2 witch were a couple of activations into the 101-folder. My first 4 jpeg-tests were picture 74-77 and the Unique Image ID gave 6a0-6a3 (1696-1699) witch means that the 100-folder must have had 1622 activations before being reset.
After resetting the camera myself the current folder is the 102-folder and now the Unique Image ID equals the sum of the 1622 activations in the 100-folder plus the number activations I actually did in the 101-folder plus the number in the file name of the picture in question.
Last edited:
popeye
Established
Off topic, but I wonder if this works for most any brand camera...
fbf
Well-known
Huh?
I got an used M8.2 witch were a couple of activations into the 101-folder. My first 4 jpeg-tests were picture 74-77 and the Unique Image ID gave 6a0-6a3 (1696-1699) witch means that the 100-folder must have had 1622 activations before being reset.
After resetting the camera myself the current folder is the 102-folder and now the Unique Image ID equals the sum of the 1622 activations in the 100-folder plus the number activations I actually did in the 101-folder plus the number in the file name of the picture in question.
So you are saying the unique ID # equals to your total acuations regardless what the folder # is? Did I read it wrong?
Just want to make sure since I'm a little confused.
ampguy
Veteran
interesting
interesting
So you're saying that after unique image 1699 in folder 101, you did a user menu reset and immediately went to folder 102? and unique image id from exif info did not start at one? (which exif tool are you using?)
Since you got the camera at folder 101, how do you know if/where it was reset or if it went through 9999 images for the 100 folder?
BTW, if you use this tool: http://regex.info/exif.cgi the authors released a new version yesterday that fixes 2 M8 issues, one is exposure comp, the other is unique image formatting (# it shows is same as previous, and same as every other exif tool I've used on M8 DNG/JPGs).
fyi -
***
The DCIM standard that governs the file/folder structure on modern cameras defines that images are named along the lines of
DCIM/###?????/????####.???
where the final #### is an image number that cycles from 0000 through 9999, and the first ### is a folder number that starts at 100 and bumps up once every time the #### number cycles past 9999 to 0000 again. Thus, if your images are in a folder "102leica", you add 20,000 to the four-digit number in the image file.
***
interesting
So you're saying that after unique image 1699 in folder 101, you did a user menu reset and immediately went to folder 102? and unique image id from exif info did not start at one? (which exif tool are you using?)
Since you got the camera at folder 101, how do you know if/where it was reset or if it went through 9999 images for the 100 folder?
BTW, if you use this tool: http://regex.info/exif.cgi the authors released a new version yesterday that fixes 2 M8 issues, one is exposure comp, the other is unique image formatting (# it shows is same as previous, and same as every other exif tool I've used on M8 DNG/JPGs).
fyi -
***
The DCIM standard that governs the file/folder structure on modern cameras defines that images are named along the lines of
DCIM/###?????/????####.???
where the final #### is an image number that cycles from 0000 through 9999, and the first ### is a folder number that starts at 100 and bumps up once every time the #### number cycles past 9999 to 0000 again. Thus, if your images are in a folder "102leica", you add 20,000 to the four-digit number in the image file.
***
Huh?
I got an used M8.2 witch were a couple of activations into the 101-folder. My first 4 jpeg-tests were picture 74-77 and the Unique Image ID gave 6a0-6a3 (1696-1699) witch means that the 100-folder must have had 1622 activations before being reset.
After resetting the camera myself the current folder is the 102-folder and now the Unique Image ID equals the sum of the 1622 activations in the 100-folder plus the number activations I actually did in the 101-folder plus the number in the file name of the picture in question.
popeye
Established
The DCIM standard that governs the file/folder structure on modern cameras defines that images are named along the lines of
DCIM/###?????/????####.???
where the final #### is an image number that cycles from 0000 through 9999, and the first ### is a folder number that starts at 100 and bumps up once every time the #### number cycles past 9999 to 0000 again. Thus, if your images are in a folder "102leica", you add 20,000 to the four-digit number in the image file.
***
Independent of the card used right?
ampguy
Veteran
yes, but may be camera/vendor/firmware dependent
yes, but may be camera/vendor/firmware dependent
In my M8, with latest M8/8.2 firmware, it behaves per the DCIM standard. I have not tested or do not know how the M8 with original firmware or M8.2 with latest firmware behaves.
Especially when exceptions occur like popping card out and another card in from similar camera but different image count. I would presume the camera would ensure to not overwrite an image, but there are several ways it could do this.
Also, not sure how the M8/8.2 handles swapping between FAT16 and FAT32 formatted cards.
Have seen other cameras write 10xvendor folders within common DCIM folder on card, but also cameras write a whole new tree structure on an identified new card (e.g. \DCIM\DCIM\10xcamera2\...
yes, but may be camera/vendor/firmware dependent
In my M8, with latest M8/8.2 firmware, it behaves per the DCIM standard. I have not tested or do not know how the M8 with original firmware or M8.2 with latest firmware behaves.
Especially when exceptions occur like popping card out and another card in from similar camera but different image count. I would presume the camera would ensure to not overwrite an image, but there are several ways it could do this.
Also, not sure how the M8/8.2 handles swapping between FAT16 and FAT32 formatted cards.
Have seen other cameras write 10xvendor folders within common DCIM folder on card, but also cameras write a whole new tree structure on an identified new card (e.g. \DCIM\DCIM\10xcamera2\...
Independent of the card used right?
Jeicob
Amateur
I didn't reset until a little later, say 1775 or so, but when I did the camera switched to the 102-folder but the unique ID went on as nothing had happened. I used this exif tool (which don't work on the DNG's).So you're saying that after unique image 1699 in folder 101, you did a user menu reset and immediately went to folder 102? and unique image id from exif info did not start at one? (which exif tool are you using?)
If the unique ID were starting from scratch in each new folder I would have had no way to tell. But now that the unique ID just seams to continue, this is the only explanation I can come up with.Since you got the camera at folder 101, how do you know if/where it was reset or if it went through 9999 images for the 100 folder?
Exactly!So you are saying the unique ID # equals to your total acuations regardless what the folder # is?
Maybe the unique ID goes up to 9999 and starts all over again regardless of the current folder-number
user237428934
User deletion pending
Maybe the unique ID goes up to 9999 and starts all over again regardless of the current folder-number![]()
Are you mixing up the unique ID in the EXIF-Information of the file and the numbering of the file name?
Independently of the file name the unique ID contains the number of actuations in Hex-Format.
Fujitsu
Well-known
Simply take a jpg image, upload to flickr and see meta data.
user237428934
User deletion pending
Simply take a jpg image, upload to flickr and see meta data.
Sorry. This EXIF-attribute is not displayed in flickr.
Jeicob
Amateur
Nope!Are you mixing up the unique ID in the EXIF-Information of the file and the numbering of the file name?
Yes but the problem is which number of actuations, the number of actuations in current folder or the number of actuations since the day the camera left the factory?Independently of the file name the unique ID contains the number of actuations in Hex-Format.
user237428934
User deletion pending
Nope!
Yes but the problem is which number of actuations, the number of actuations in current folder or the number of actuations since the day the camera left the factory?
I think it's the latter.
ampguy
Veteran
Thanks Jeicob
Thanks Jeicob
This is very interesting. Appears the 8.2 and 8 may behave differently here.
My M8 original, without any factory or user resets that I am aware of, but with latest M8/8.2 firmware, increments Unique image exif info. for current folder only.
Thanks Jeicob
This is very interesting. Appears the 8.2 and 8 may behave differently here.
My M8 original, without any factory or user resets that I am aware of, but with latest M8/8.2 firmware, increments Unique image exif info. for current folder only.
I didn't reset until a little later, say 1775 or so, but when I did the camera switched to the 102-folder but the unique ID went on as nothing had happened. I used this exif tool (which don't work on the DNG's).
If the unique ID were starting from scratch in each new folder I would have had no way to tell. But now that the unique ID just seams to continue, this is the only explanation I can come up with.
Exactly!
Maybe the unique ID goes up to 9999 and starts all over again regardless of the current folder-number![]()
wintoid
Back to film
Sorry. This EXIF-attribute is not displayed in flickr.
Works for me
Share:
-
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.