- Thread starter
- #21
Ben Smallbone
Member
After a week of trying to recover the footage. I've finally given up. I also had a very experienced RED DIT take a look at all the files and he came up with the following:
"After a battery of tests on the footage....there were a few conclusions:
The frame rate mis-match resulted in the camera locking up in a 3 frame loop on the primary footage (this should have not let you roll if the camera wasn't in a proper configuration)
The drive was throwing dropped frames in the clips during the recording of the takes. (This would have been visible on the LCD/Viewfinder)
The file copy from the RED Drive corrupted (Least likely because of the 3 outside clips all being affected)
Overall, the clips are unrecoverable having run them through several apps to test the content with the same result of a 3-frame loop. I haven't seen anything like this happen before, but some warning should have shown on the camera's display when these clips were rolled, such as error in recording, or dropped-frames.
My only guess now would be to contact RED to see if there is a way to deconstruct the R3D file and get past the bad frames. Maybe Redline has some command options for this, but they would know better than I would."
Thanks for all your help guys and if you have any further ideas, please let me know.
"After a battery of tests on the footage....there were a few conclusions:
The frame rate mis-match resulted in the camera locking up in a 3 frame loop on the primary footage (this should have not let you roll if the camera wasn't in a proper configuration)
The drive was throwing dropped frames in the clips during the recording of the takes. (This would have been visible on the LCD/Viewfinder)
The file copy from the RED Drive corrupted (Least likely because of the 3 outside clips all being affected)
Overall, the clips are unrecoverable having run them through several apps to test the content with the same result of a 3-frame loop. I haven't seen anything like this happen before, but some warning should have shown on the camera's display when these clips were rolled, such as error in recording, or dropped-frames.
My only guess now would be to contact RED to see if there is a way to deconstruct the R3D file and get past the bad frames. Maybe Redline has some command options for this, but they would know better than I would."
Thanks for all your help guys and if you have any further ideas, please let me know.