Canon EOS-1D X Firmware 1.0.6

Status
Not open for further replies.
Thanks for the help. Just a little over cautious I guess.


neuroanatomist said:
Virgil Quick said:
Sorry to keep asking questions but I really would hate to mess this up.

If Canon says the file is 33.04 MB then that should calculate to 33,812,480 bytes (33.04 X 1024). The extracted FIR file that I have downloaded is 32,988,060 bytes according to the "properties" function.

I confess I am not a computer person but it sounds like my file is not complete. Any help appreciated.

Mine says 33 MB on disk (32,988,060 bytes). You're fine, just go for it.

BTW, your math is wrong, you need two factors of 1024: bytes to kilobytes then kilobytes to megabytes (meaning 32,988,060 bytes = 31.46 MB), but also hard drives have a minimum block size that means files take up more room than their actual size, and that minimum block size increases with larger drives, and is dependent on the OS.
 
Upvote 0
Ah good catch on the two factor. I think most of his error is related to the extra bytes from the large block sizes.

I would also hope that Canon provides internal CRC checking to make sure the FIR is intact and not corrupted.

neuroanatomist said:
Virgil Quick said:
Sorry to keep asking questions but I really would hate to mess this up.

If Canon says the file is 33.04 MB then that should calculate to 33,812,480 bytes (33.04 X 1024). The extracted FIR file that I have downloaded is 32,988,060 bytes according to the "properties" function.

I confess I am not a computer person but it sounds like my file is not complete. Any help appreciated.

Mine says 33 MB on disk (32,988,060 bytes). You're fine, just go for it.

BTW, your math is wrong, you need two factors of 1024: bytes to kilobytes then kilobytes to megabytes (meaning 32,988,060 bytes = 31.46 MB), but also hard drives have a minimum block size that means files take up more room than their actual size, and that minimum block size increases with larger drives, and is dependent on the OS.
 
Upvote 0
bkorcel said:
Ah good catch on the two factor. I think most of his error is related to the extra bytes from the large block sizes.

I would also hope that Canon provides internal CRC checking to make sure the FIR is intact and not corrupted.

neuroanatomist said:
Virgil Quick said:
Sorry to keep asking questions but I really would hate to mess this up.

If Canon says the file is 33.04 MB then that should calculate to 33,812,480 bytes (33.04 X 1024). The extracted FIR file that I have downloaded is 32,988,060 bytes according to the "properties" function.

I confess I am not a computer person but it sounds like my file is not complete. Any help appreciated.

Mine says 33 MB on disk (32,988,060 bytes). You're fine, just go for it.

BTW, your math is wrong, you need two factors of 1024: bytes to kilobytes then kilobytes to megabytes (meaning 32,988,060 bytes = 31.46 MB), but also hard drives have a minimum block size that means files take up more room than their actual size, and that minimum block size increases with larger drives, and is dependent on the OS.

From wikipedia:
The megabyte (abbreviated as Mbyte or MB) is a multiple of the unit byte for digital information storage or transmission with three different values depending on context: 1048576 bytes (220) generally for computer memory; and one million bytes (106, see prefix mega-) generally for computer storage.[1][3] In rare cases, it is used to mean 1000×1024 (1024000) bytes. The IEEE Standards Board has confirmed that mega- means 1000000, with exceptions allowed for the base-two meaning.

So it kinda depends, huh?
 
Upvote 0
For some reason. AF auto adjustment isn't working for me. Neither is saving the serial number!.. I manually input my 85 1.2 serial and gave it an AF Microadjustment setting. Turned off the camera, did the same for the 50 1.4.. Turned off, put back the 85 and it's not recognized (now it appears as[01]EF85mm f/1.2L II USM.

arrghhh~!
 
Upvote 0
So here is the thing. I'm not sure this is related or not but if the lens doesn't report the serial number to the camera, entering it into the AFMA setting doesn't help. The camera will still revert back to the what is read from the lens. If the serial number isn't readable, it will still save the AFMA value for the lens (identified as serial 00000000) you just cant save AFMA values for multiple copies of the same lens. You can only do that for lenses that actually report back their serial number to the camera.

Is it that the lenses are not reporting their SN or is it the camera not saving it once it's detected and read from the lens?

JEAraman said:
For some reason. AF auto adjustment isn't working for me. Neither is saving the serial number!.. I manually input my 85 1.2 serial and gave it an AF Microadjustment setting. Turned off the camera, did the same for the 50 1.4.. Turned off, put back the 85 and it's not recognized (now it appears as[01]EF85mm f/1.2L II USM.

arrghhh~!
 
Upvote 0
bkorcel said:
So here is the thing. I'm not sure this is related or not but if the lens doesn't report the serial number to the camera, entering it into the AFMA setting doesn't help. The camera will still revert back to the what is read from the lens. If the serial number isn't readable, it will still save the AFMA value for the lens (identified as serial 00000000) you just cant save AFMA values for multiple copies of the same lens. You can only do that for lenses that actually report back their serial number to the camera.

Is it that the lenses are not reporting their SN or is it the camera not saving it once it's detected and read from the lens?

JEAraman said:
I "thought" it wasn't saving it once detected. After further testing, I can safely say that if you manually input a serial number (it's being SAVED); same goes for the AFMA setting.
For some reason. AF auto adjustment isn't working for me. Neither is saving the serial number!.. I manually input my 85 1.2 serial and gave it an AF Microadjustment setting. Turned off the camera, did the same for the 50 1.4.. Turned off, put back the 85 and it's not recognized (now it appears as[01]EF85mm f/1.2L II USM.

arrghhh~!
 
Upvote 0
bkorcel said:
So here is the thing. I'm not sure this is related or not but if the lens doesn't report the serial number to the camera, entering it into the AFMA setting doesn't help. The camera will still revert back to the what is read from the lens. If the serial number isn't readable, it will still save the AFMA value for the lens (identified as serial 00000000) you just cant save AFMA values for multiple copies of the same lens. You can only do that for lenses that actually report back their serial number to the camera.

Is it that the lenses are not reporting their SN or is it the camera not saving it once it's detected and read from the lens?

There are three situations that I've encountered with various lenses, before this firmware update (which I haven't yet applied, but with Orientation Linked AF Point disabled, AFMA seems to behave normally):

[list type=decimal]
[*]Serial number reported automatically by lens, AFMA values can be stored for multiple copies of the same lens. This applies to the newest lenses, like the 40mm f/2.8.
[*]Serial number not reported automatically by lens, can be entered manually, AFMA values can be stored for multiple copies of the same lens. This is the case for most of my lenses.
[*]Serial number not reported automatically by lens, can be entered manually, AFMA values cannot be stored for multiple copies of the same lens. This is the case for relatively old lenses, including the 135L and the 100-400mm. For these lenses, on the screen where you manually enter the serial number, there is a asterisk to the left of the row of boxes.
[/list]
 
Upvote 0
Hi, just upgraded to 1.0.6.
I noticed that after formatting a Lexar 32 GB the number of shots (R+jpgL10)is now 665, and it used to be around 800 shots for that card.
I loaded an empty "old" card which gave me a free shot count of 807. I took one shot and the free count went down to 664
Did anybody notice same?

I noticed the back focus problem before, but I tought it was my own stupidity. I will try later this week
 
Upvote 0
Did anyone have the AFMA problem that the camera suddenly applied an "to all" setting of +8?

I had to go in and check that it wasn't applied every now and then (when I rememebered) and turn it back to "pr lens" it kept the settings when I switched back it just applied for all.
 
Upvote 0
wopbv4 said:
Hi, just upgraded to 1.0.6.
I noticed that after formatting a Lexar 32 GB the number of shots (R+jpgL10)is now 665, and it used to be around 800 shots for that card.
I loaded an empty "old" card which gave me a free shot count of 807. I took one shot and the free count went down to 664
Did anybody notice same?

I noticed the back focus problem before, but I tought it was my own stupidity. I will try later this week
I also upgraded to 1.0.6. I formatted both my Sandisk and Lexar 32GB cards after seeing your post above. Shooting raw only, I get an available count of 925 photos when using them in the 1DX.
 
Upvote 0
wopbv4 said:
Hi, just upgraded to 1.0.6.
I noticed that after formatting a Lexar 32 GB the number of shots (R+jpgL10)is now 665, and it used to be around 800 shots for that card.
I loaded an empty "old" card which gave me a free shot count of 807. I took one shot and the free count went down to 664
Did anybody notice same?

I noticed the back focus problem before, but I tought it was my own stupidity. I will try later this week

RAW files are losslessly compressed (that's why each RAW file has a slightly different file size). Generally speaking, higher ISO shots and those from lenses with noticeable distortion (fisheye lenses) compress less, and have larger file sizes. The larger the file size, the less you can fit on a card. :)

Try this: put your lens cap on, and dial in an exposure of ISO 100, 1/400th second shutter speed, any aperture. Fire off a burst like that and see what the camera reports back as the number of shots the card can hold. I bet the number will be bigger.
 
Upvote 0
Status
Not open for further replies.