Corrupt R3D-Files - How to fix?

[damian_zylka]

Hey everyone,

got a problem with corrupted R3D-Files. Movie was shot with a RED MX - 4,5K 25fps.
I'm not from US - sorry for bad english.

A couple of files are corrupt. Some Frames are bad - don't know why.
All the damaged files were shot on CF-Cards - then copied to 2 external drives (no checksum at the end, i know you shouldn't do that)
And the 2 drives have exactly the same corrupt files. We've shot 9 CF-Cards full of material, the first 3 were fine, but the last 6 are corrupt somehow. Material on the CF-Cards is long gone of course..
I'm wondering if there was a problem with the CF-Cards or with the copying. But 6-times copying and everytime went wrong? And the first 3 times worked? ...

I'm editing with PProCS5 5.0.3. Everytime i play such a file i get "ImporterREDServer.exe doesn't work anymore" and after that I have to restart PPro.
Importing it to Redcine-X doesn't help. Also crashes when i get to the corrupt frame.

At the moment i'm trying to find the corrupt frames, cut them out and use only the rest of the R3D-file - but i don't know, if it will work fine afterwards with rendering etc.
It's really frustrating because PPro crashes everytime i find the frame, then restart, cut that frame, - move to the next corrupt frame.

Is there any possibility to find the wrong frames automatically? (or without a crash ^^)
Will the file work at the end or am i just waisting my time?
Is there a possibility to repair the files? or to transcode them, so the wrong frames are just "black" and the system don't crashes anymore.
transcoding isn't the best way anyway because of losing RAW adjustments..

Would be great if someone can help!
Thanks,

Damian

 

[Gunleik Groven]

Hey everyone,

got a problem with corrupted R3D-Files. Movie was shot with a RED MX - 4,5K 25fps.
I'm not from US - sorry for bad english.

You're doing fine...

A couple of files are corrupt. Some Frames are bad - don't know why.
All the damaged files were shot on CF-Cards - then copied to 2 external drives (no checksum at the end, i know you shouldn't do that)
And the 2 drives have exactly the same corrupt files. We've shot 9 CF-Cards full of material, the first 3 were fine, but the last 6 are corrupt somehow. Material on the CF-Cards is long gone of course..
I'm wondering if there was a problem with the CF-Cards or with the copying. But 6-times copying and everytime went wrong? And the first 3 times worked? ...

This is actually quite typical for bad CF copies. Another CF reader may have helped, but from the sound of it, this sounds like a typical worst-case result when one don't verify copy in a solid way before erasing mags.

Checksums doesn't neccesarily pick this up. Realtime playthrough or transcoding does.

I'm editing with PProCS5 5.0.3. Everytime i play such a file i get "ImporterREDServer.exe doesn't work anymore" and after that I have to restart PPro.
Importing it to Redcine-X doesn't help. Also crashes when i get to the corrupt frame.

At the moment i'm trying to find the corrupt frames, cut them out and use only the rest of the R3D-file - but i don't know, if it will work fine afterwards with rendering etc.
It's really frustrating because PPro crashes everytime i find the frame, then restart, cut that frame, - move to the next corrupt frame.

You could try using RCX, transkoding to a image-sequence format, to figure out which frames are bad, and make r3d "media managed files" from the good part of the files.

Deanan has a more exact prescription as I fortunately have not had to do this.

Rocketcine-X was going on transcoding and giving a report on the bad frames. Unfortunately I don't think that feature is available in RCX yet.

Is there any possibility to find the wrong frames automatically? (or without a crash ^^)
Will the file work at the end or am i just waisting my time?
Is there a possibility to repair the files? or to transcode them, so the wrong frames are just "black" and the system don't crashes anymore.
transcoding isn't the best way anyway because of losing RAW adjustments..

Would be great if someone can help!
Thanks,

Damian

best of luck!

Cheers!

Gunleik

 

[Benjamin Bailey]

You could try using RCX, transkoding to a image-sequence format, to figure out which frames are bad, and make r3d "media managed files" from the good part of the files.

Deanan has a more exact prescription as I fortunately have not had to do this

Is there anyway you can point me in the direction of your referral? I have a similar situation that I am trying to figure out what exactly happened. We shot on both RED drives and CF cards. My situation very well could have happen using a CF card. As the DIT, I used R3D Data Manager and never had saw problems. Now that the film is in post, we have found one clip that seems to be corrupted. Any additional comments or suggestions?

 

[Seth Zwiebel]

I have one bad R3d file - any ideas how to fix it

I have one bad R3d file - any ideas how to fix it

I recently had someone borrow my camera for a shoot. They had one bad R3d file. They used the Red 640gb drive to record. I took a look at the file on the drive after they noticed the bad clip. It was also bad on the Red drive. The clip plays fine as a quicktime proxy. It pops up with a green frame at first but as soon as I hit play it plays smoothly. In RedcineX it shows up without a thumbnail and won't play. I checked the metadata and everything is blank. Anyone else experience similar problems? Is there a way to recover this footage? I tried using redundead, but it created another non-working copy of the clip.

 

[Tim Sutherland]

I recently had someone borrow my camera for a shoot. They had one bad R3d file. They used the Red 640gb drive to record. I took a look at the file on the drive after they noticed the bad clip. It was also bad on the Red drive. The clip plays fine as a quicktime proxy. It pops up with a green frame at first but as soon as I hit play it plays smoothly. In RedcineX it shows up without a thumbnail and won't play. I checked the metadata and everything is blank. Anyone else experience similar problems? Is there a way to recover this footage? I tried using redundead, but it created another non-working copy of the clip.

The easiest way is to export a quicktime from the proxy. Other than that, it sounds like your header file may be corrupt, and I believe RED may be able to try to repair it if you contact them, but if you can render off of the proxy for that one clip in clipfinder or something similar, it may be the easiest route.

Tim

 

[Cache Daniel Blanco]

Corrupted R3D files turned Green!

Corrupted R3D files turned Green!

I have the same problem, my r3d doesnt work and the proxys plays smothly and turn completly green, anyone have any suggestion? i need to save those clips are very important and were very expensive too, please help me with orientation please, the redundead utility doesnt work with this eather, thanks

 

[Feyco Feenders]

Hello,
@damian_zylka
two questions,
can you play the file in redcine?
do you have an example of one corruped frame?

Somehow there have been often problems with corruped frames after the transcoding process, for example if the red file was fine in redcine and transcoded it with metafuse for editing, there where suddenly some glitches or have frames shown up.

If you can play them in redcine and don't see any corruped file, the redfile structure normaly is fine at all, but if it's not possible to play the file in redcine, try redalert, if there is no succsess ether, its a bad sign then...

it will be hart/immpossible to get the material back from those cf cards, if have already been used again.

best
feyco