corrupt file

[axel ebermann]

Hey guys,

Here is my issue:

We shot on a Red Drive on one of those ultra low/no- budget shorts where
you work as AC/DIT.

I copied the files overnight on my Raid and spot checked them
with clipfinder. All looked happy.

When I did try to ingest it in to FCP via the FCP importer one file was only partially transferred.
The R3D file (599MB) opens in clipfinder and Red Alert, but then inevitably crashes the entire system.

I cannot copy the file to a different harddrive and it also crashes my Raid whenever I try to copy it.

Naturally it turns out this is exactly the take that is needed for the film...

Any ideas ?

Thanks

Axel

 

[Ido Karilla]

Can you get the original magazine? even if it was reused there is a chance you can recover that file using redundead.

 

[Marc Berger]

Hi Axel,
don´t forget to check the raid. I had exactly the same problem with some clips and I finally found out that one of the 5 hard disks was nearly dead (this one disk only affected some of the clips on the raid). Changing the disk and restoring the raid (level 5) solved the problem.

Marc

 

[Kim Frank]

Sounds like a bunch of corrupt frames. You can try to transcode around those frames

 

[Mark Andersen]

I recently had some corrupt files and when Rocketcine got hold of them it crashed the app. Mine were shot at 3k 16:9 and 50FPS (which is right at the limit of frame rate) I am thinking that I had a write problem wiht the raid, or the Redraid wasn't keeping up and I had some bad frames. I never have this problem at lower frame rates.

 

[axel ebermann]

mark,

just trying a bunch of stuff. The footage was shot at 24fps, RC 42, 4k HD.
There is some data stream headroom. So that should actually not be the problem.