For several years now I have noticed that there is more interest in negative articles, probably because they work like reverse psychology, or maybe because there is a form of masochism inherent in the net in looking for the negative instead of the positive, buth…
Many times I have seen and heard about the problem of braw files, especially nowadays with larger files and too much thinking … fluid in handling media and their characteristics, which is then an excuse for not following the rules 😯 .
What can give problems with Braw files?
- Recording on the wrong medium, not certified
(certification is not a simple speed test, but means that bmd or some other tests under many different conditions the reliability of the media from the first to the last byte, too many elements can break your speed chain and ruin a recovery) - Recording on fragmented media
(delete and write files from computer or other) - Recording on media not formatted by the camera
(not many people know or do not check how many hidden files are written by certain brands, because they obviously optimize their cameras) - Recording on media with the wrong cable
(not all cables are the same) - Recording on external media with insufficient battery
(this is a less considered problem, but it is the cause of 90% of corrupted files on external disk, many external battery plates have a dual 7.4v -12v power supply, be sure to connect them to the right 12v pin). - Recording to a media that is not properly attached to the camera when shooting on the go
(usb c is the weakest connector in the world, a little movement can cause a pin to disconnect, enough to ruin the shot) - Turn off the camera without waiting for it to stop working on the stand
(many people turn off the camera in play mode. they go back to recording mode and turn it off) - Record at a higher bitrate/quality than the media without warning about missing frames.
- Open media from Windows and allow chkdsk to do its job to destroy data (more common than you think, never leave external media connected to Windows during reboot, chkdsk originated for very small files, ages ago, today when it acts on large files it causes 99% only damage)
- Lowering power during recording
(disconnected or ignored battery at end of life, remember that when the battery dies, the camera starts to reduce power to the external device and then shuts down, this causes corruption of Cfast or Usb disk which closes braw files) - Support firmware upgrade
(sometimes the frantic mania to update everything forgets that the whole chain is based on the old state of the chain and updating something is never a good thing). - Copying files without control, today we have a free tool in Resolve to clone the contents of our files to another hard drive, if you don’t like Resolve there is a great free tool called QuineCopy https://www.quine.no/quinecopy.
Very often file problems are related to copies not being made properly.
And to that I’ll add one, but being superstitious I won’t call it 13
12.5 Using the ExFat filesystem on very large files.
Where it is possible, Blackmagic allows you to do so, instead of the ExFat filesystem we use the HFS , born in Apple and the counterpart of the more robust NTFS from Micorsoft. If you use Windows there is a driver costing 12 euros to read and write it as if it were native (Paragon HFS for WIndows), it will be the best money spent of your life.
The reason is very simple, ExFat was born for WindowsCE in 2006, with the limitation of a few GB maximum size (it was for pocket products), and then modified later to be able to format and handle larger media and archives, but…. unfortunately writing very large files this filesystem is much more susceptible to errors, problems in data recovery in case of damage to the disk structure etc etc etc.
So if you have a chance, avoid that FileSystem, we use NTFS under Windows and HFS and later under Mac.
In case of corruption problems, but the data is there, a method to recover the data is shown in this video :
or you can contact Aeroquartet
My experience with BMCC, BMPC4K, Ursa Mini Pro G1, p4k, 2x p6k G1 gave, following the rules, almost zero problems with corrupted files while working 😀