Canon R6 CR3 format

[davey]

Downloading.

If you could also share a few of the recovered files, that may be useful too.

Also, I hope you have the correct signature file, because I updated it one time, shortly after I uploaded first version. For completeness sake I attached it again to this message.

CR3-R6.rar

I suggest to try it, recover like 10 CR3 files and check those. What you have there sounds like my previous version and although these files are very easy to repair, it's still not what we want ..

Carved DMDE samples uploaded, new scan with updated ini in progress.

[Joep]

Yup, just a tad too large, if I truncate file at right point it's viewable and intact. Check PM sent some repaired examples.

[Joep]

Tried with disk image you shared. For me it works, I get intact CR3's.

[davey]

Yes! Scanned with Joep`s updated INI and it worked, almost all Canon R6 CR3`s are readable under Viewer / RAWDigger etc.
BUT
another thing is that they`re not opening in Lightroom (which in fact is a must for every RAW pro user), original samples (not carved) are opened without problems. I`m now looking for walk around solution (conversion to DNG or smtn).


Regards,
Davey

[fzabkar]

Could you post the first and last sectors of a good file and a carved file?

[davey]

Could you post the first and last sectors of a good file and a carved file?

Hello fzabkar ,

beggining and end of carved vs originals attached, also few samples uploaded to gdrive.

https://drive.google.com/drive/folders/ ... share_link

Best Regards,
Davey

[davey]

Tried with disk image you shared. For me it works, I get intact CR3's.

btw Joep thanks for Your massive input in this case!

Best Regards,
Davey

[lcoughey]

Joep is a beast in this arena. He is pretty much the goto guy for data recovery professionals around the world when it comes to dealing to damaged image files.

[fzabkar]

This is a working file (A55A8928.CR3):

Code: Select all

Offset(h) 00       04       08       0C

0001DDF0  00000001 6D646174 00000000 007FDE66  ....mdat......Þf

The size of the mdat atom is 0x7FDE66. This corresponds to the range from offset 0x1DDF0 to 0x81BC55.

Code: Select all

Offset(h) 00       04       08       0C

0081BBF0  00006D18 000044DF BC012067 BC414449  ..m...Dß¼. g¼ADI
0081BC00  46465241 4354494F 4E5F434F 52524543  FFRACTION_CORREC
0081BC10  54444154 4100B468 BC01C06B BC01DC02  TDATA.´h¼.Àk¼.Ü.
0081BC20  0000FF16 0000E016 0000C116 0000F468  ..ÿ...à...Á...ôh
0081BC30  BC017A02 00000000 00000000 00001069  ¼.z............i
0081BC40  BC410020 02000100 00000000 01000000  ¼A. ............
0081BC50  00000000 0100                        ......

This is a partially-working carved file (f938081352.CR3):

Code: Select all

Offset(h) 00       04       08       0C

000A35F0  00000001 6D646174 00000000 01D8F866  ....mdat.....Øøf

The size of the mdat atom is 0x1D8F866. This should correspond to the range from offset 0xA35F0 to 0x1E32E55. Instead the file ends at 0x1E32E54.

Code: Select all

Offset(h) 00       04       08       0C

01E32DF0  BE01C0E2 BD414449 46465241 4354494F  ¾.Àâ½ADIFFRACTIO
01E32E00  4E5F434F 52524543 54444154 41004CE4  N_CORRECTDATA.Lä
01E32E10  BD0158E7 BD01DC02 0000F816 0000D916  ½.Xç½.Ü...ø...Ù.
01E32E20  0000BA16 00009B16 00007D16 00008CE4  ..º...›...}...Œä
01E32E30  BD017A02 00000000 00000000 0000B0E4  ½.z...........°ä
01E32E40  BD410020 02000100 00000000 01000000  ½A. ............
01E32E50  00000000 01                          .....

Therefore ISTM that the .ini file should be tweaked to correctly calculate the size of the mdat atom, assuming that is even possible. Otherwise you could carve an additional sector, and then write a tool to truncate the carved .CR3 file to its correct size (is that in fact what you are doing?).

[fzabkar]

Joep is a beast in this arena. He is pretty much the goto guy for data recovery professionals around the world when it comes to dealing to damaged image files.

Agreed.