.r3d file analisis tool?

[Steve Shaw]

We have a bunch of Red .r3d files that are in some way corrupt, and cause playback problems, crashing, etc.

The problem is the Red driver (SDK) tries to read the corrupt file and make the best of it. This sometimes works, sometimes doesn't.

We need to analyse all the .r3d files and isolate those that are in some way corrupt to they can be dealt with separately.

Any ideas?

 

[Gunleik Groven]

Are these from R1 oe Epic?
How plentyfull?
How long takes?

This can be done, but may need some manual handywork. A lot if there are many takes and long files...

 

[Steve Shaw]

Files from R1, and there are a lot of corrupt ones, but we need to check all - and there are a LOT of clips in total - so manual is a non-starter...

 

[Gunleik Groven]

OK...

Sounds like a massive bad coopyjob!
No chance to go back to original media?

I would have contacted Deanan directly to hear if he has a trick up his sleeve...

 

[Steve Shaw]

Not sure is was a copy issue, or duff CF cards, or what. I had no involvement with the production so have no idea...

Original material long gone.

Most of the corrupt clips can be played once, and then either crash of freeze when the clip end is reached - in Redcine-X as well as other systems. So, the idea is to render them down to dpx files to get around the problem.

But, to do this we need a way to mass collate the corrupt clips from all the rushes...

Not looking good!

 

[RivaiC]

Hi steve

We develop our own tools exactly for this type of stuff. We can detect exactly the position of the corrupt frames thru out the whole shots.

Send me one R3D files I will see if I can help. My DIT will come back on monday, if everything goes fine. We can tell u exactly the frame where it gets corrupted and amount of corrupted frames thru out the whole clips

Rivai