Here's what worked for me:
Been running across the issue of pink/flashing frames when trying to convert my spanned RAW files to DNGs. I've been recording to FAT32 cards, so file size was limited and files spanned to multiple RAW files (RAW, R00, R01, etc)
All of my problem files have been at the end of the card, when the card filled up and the camera rolled out, before it had a chance to write the footer.
None of the converters even recognized these files, labeling them with crazy resolutions (23453x51246) and Framerates (-69.345).
I looked around and found this forum, which was a godsend.
Shield's Hex fix worked flawlessly for the files that did not span across multiple 4GB files - Thank you!
Those that did span, however, still provided a corrupted image.
I cross-checked similar takes from the card, and noticed that the footer for spanned files is actually longer than the one posted by Shield, so I grabbed the longer length of the footer, making sure to choose a take that was similar length, but slightly longer to compensate for the extra frames, and pasted it at the end of the corrupted spanned file.
Then, I used RAWanizer to open the file and convert to DNG+Cineform Proxy.
Been checking out the proxies, and the problem has been resolved!
And the converter actually truncates the file automatically, so there are no extra frames to worry about at the end.
Here are the steps again:
1. Open the last spanned file of the corrupted clip in HxD or another Hex editor (the ones with extension .R04, .R05, etc. Not the .RAW file)
2. Open the last spanned file of a non-corrupted clip in HxD. Preferably one of the same extension and slightly larger file size (ie. if you opened M16-1700.R05 in Step 1 with a size of 1GB, then this file would ideally be something like M16-1646.R05 with a size of 1.1GB or larger.)
3. Copy the footer from the non-corrupted file to the end of the corrupted file. For me it was the last 28 lines, starting with the tags A5 A5 A5 A5... - see image below.
4. Open the file in the converter, and it should recognize it and be able to process it. RAWanizer was the only one I have tried so far, but I'm sure it would work with any of them after this point.
If you're in doubt, I suggest repeating Step 2 for several non-corrupted files and checking for similarities in the footer.
Hope this helps!
Been running across the issue of pink/flashing frames when trying to convert my spanned RAW files to DNGs. I've been recording to FAT32 cards, so file size was limited and files spanned to multiple RAW files (RAW, R00, R01, etc)
All of my problem files have been at the end of the card, when the card filled up and the camera rolled out, before it had a chance to write the footer.
None of the converters even recognized these files, labeling them with crazy resolutions (23453x51246) and Framerates (-69.345).
I looked around and found this forum, which was a godsend.
Shield's Hex fix worked flawlessly for the files that did not span across multiple 4GB files - Thank you!
Those that did span, however, still provided a corrupted image.
I cross-checked similar takes from the card, and noticed that the footer for spanned files is actually longer than the one posted by Shield, so I grabbed the longer length of the footer, making sure to choose a take that was similar length, but slightly longer to compensate for the extra frames, and pasted it at the end of the corrupted spanned file.
Then, I used RAWanizer to open the file and convert to DNG+Cineform Proxy.
Been checking out the proxies, and the problem has been resolved!
And the converter actually truncates the file automatically, so there are no extra frames to worry about at the end.
Here are the steps again:
1. Open the last spanned file of the corrupted clip in HxD or another Hex editor (the ones with extension .R04, .R05, etc. Not the .RAW file)
2. Open the last spanned file of a non-corrupted clip in HxD. Preferably one of the same extension and slightly larger file size (ie. if you opened M16-1700.R05 in Step 1 with a size of 1GB, then this file would ideally be something like M16-1646.R05 with a size of 1.1GB or larger.)
3. Copy the footer from the non-corrupted file to the end of the corrupted file. For me it was the last 28 lines, starting with the tags A5 A5 A5 A5... - see image below.
4. Open the file in the converter, and it should recognize it and be able to process it. RAWanizer was the only one I have tried so far, but I'm sure it would work with any of them after this point.
If you're in doubt, I suggest repeating Step 2 for several non-corrupted files and checking for similarities in the footer.
Hope this helps!
Code Select
A5 A5 A5 A5 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
55 55 AA AA 55 55 AA AA 55 55 55 55 AA AA AA AA
52 41 57 4D 80 07 38 04 00 60 37 00 87 1F 00 00
01 00 00 00 A8 5D 00 00 48 48 04 00 00 00 00 00
01 00 00 00 00 20 15 0B 26 05 00 00 20 08 00 00
38 0E 00 00 50 34 49 00 0E 00 00 00 FE 07 00 00
98 3A 00 00 00 00 00 00 00 00 00 00 88 07 00 00
08 05 00 00 1E 00 00 00 92 00 00 00 26 05 00 00
1A 08 00 00 00 00 00 00 00 00 00 00 00 01 01 02
01 00 00 00 42 1A 00 00 10 27 00 00 85 FD FF FF
10 27 00 00 3D FC FF FF 10 27 00 00 41 EF FF FF
10 27 00 00 AC 30 00 00 10 27 00 00 EC 07 00 00
10 27 00 00 74 FC FF FF 10 27 00 00 72 08 00 00
10 27 00 00 24 16 00 00 10 27 00 00 EF 03 00 00