UPDATE: I figured out how to get back the rest of the footage
I decided to start back from square one and recover the files from the CF card, but this time using a different file recovery software than I had before. What I used was FTK Imager, and when I scanned the CF card, it found a new folder that I had not seen before called "unallocated space". In it was about 60GB worth of files without extensions and with numerical names such as 0000010, 0003210, 0006410, and so on. I looked at the hex preview and sure enough, they had VIDF blocks. I exported a random file towards the end of the folder, brought it into MLVApp, and saw footage that I had not been seeing previously. Finally! The footage I was looking for was there all along, as I had thought. The funny thing though is that each of these files were 100MB (and there were hundreds of them). So in order to reconstruct the video, I had to open one file in a hex editor, copy all of the code, append it to the end of the very first file in the sequence (0000010), then rinse and repeat about a hundred times. It is a painstaking process to rebuild a 19GB clip 100MB at a time, but it was worth it. Grateful for the ML forum for providing me the information to help me recover this file; I otherwise would not have known how to manually edit the files using a hex editor, let alone think to do it. Hopefully this helps anyone in the future who finds them self in the same situation.
I decided to start back from square one and recover the files from the CF card, but this time using a different file recovery software than I had before. What I used was FTK Imager, and when I scanned the CF card, it found a new folder that I had not seen before called "unallocated space". In it was about 60GB worth of files without extensions and with numerical names such as 0000010, 0003210, 0006410, and so on. I looked at the hex preview and sure enough, they had VIDF blocks. I exported a random file towards the end of the folder, brought it into MLVApp, and saw footage that I had not been seeing previously. Finally! The footage I was looking for was there all along, as I had thought. The funny thing though is that each of these files were 100MB (and there were hundreds of them). So in order to reconstruct the video, I had to open one file in a hex editor, copy all of the code, append it to the end of the very first file in the sequence (0000010), then rinse and repeat about a hundred times. It is a painstaking process to rebuild a 19GB clip 100MB at a time, but it was worth it. Grateful for the ML forum for providing me the information to help me recover this file; I otherwise would not have known how to manually edit the files using a hex editor, let alone think to do it. Hopefully this helps anyone in the future who finds them self in the same situation.