Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Corrupt Frames

N

negativespaces

Banned
Joined
May 14, 2008
Messages
12
Reaction score
0
Points
0
Location
NYC
Website
www.negativespaces.com
Hey there

I found some corrupt frames in the R3D's from a recent stereo shoot.

2x RED One Mysterium-X cameras running Build 30.6
Genlocked with a Denecke SB-T
Shooting to 16GB RED Compact Flash

I found only a handful of these frames intermittently throughout the footage and the problem was only with one camera.

See frames below. It doesn't look like any sync error I've ever seen but that would be my first guess.

If anyone can shed some light on this mystery, it would be very much appreciated.

A%20-%20woman%20lying%20med%203%20__corrupt%20frames__%2005322723.jpeg


A%20-%20woman%20lying%20med%203%20__corrupt%20frames__%2005322800.jpeg


Thanks
 
  • Thread starter
  • Banned
  • #4
These frames are from the original media. This error only showed up now and again and I'm trying to get more info from the production so I can determine if the problem was unique to a single compact flash card. So you've seen this sort of copy fault before?

Thanks
 
Yes,I meant the original cards.

I have seen this several times on copies, but it has never been a media/recording fault the ones I have been able to verify.

Others claims to have had them on the original.

I do go through a couple of hours of RED footy a year, though, and have ended up trusting my own experience on this...

By never sending a card/disk back before I have had a verified transcode, I have not lost a frame on any of the productions I have been handling or supervising...
 
Transfer errors!

Transfer errors!

I had this problem on hot CF cards from cam, to immediate transfer...if I let the cards sit for a while (30 min or so) the transfers were error free...? The only way I found out about the error, the transcodes were crashing RCX. Luckily I had plenty of cards, so I had the original media to transfer again...
 
Watch every second of every copy every time BEFORE reformatting cards, drives, or RAM.
Rinse and repeat.
The only time I have seen these errors have been from bad copies. The original media is invariably fine.
Cheers,
Harry
 
Harry Clark said:
Watch every second of every copy every time BEFORE reformatting cards, drives, or RAM.
Rinse and repeat.
The only time I have seen these errors have been from bad copies. The original media is invariably fine.
Cheers,
Harry
Click to expand...

Me2
 
Next time someone verifies they have a good file on CF media and a bad copy file I would be interested in them making an MD5 of each file. The MD5 hash should be different for each file. It only takes a second to do, in Terminal just type md5 /path/to/file for each file, then compare the numbers it gives you.


Dusty
 
"The Woodstock Effect"

"The Woodstock Effect"

This is something that we have coined the term "The Woodstock Effect" (for obvious reasons). It could be several things (1) Transfer error: The pins in the CF card reader may not all be straight, i.e. one or two may be bent or there may be dust in the reader (2) Another thing we have seen is that the pins in the actual camera body may be bent so when the camera was rolling, the footage was not properly captured (3) corrupt card: cards do get worn down and need replacement. Whatever the case, the best thing to do is to trouble shoot the first 2 things I mentioned, which are both rather simple fixes. And another safety net we make sure to do when offloading on set, is to slowly scrub through each clip from each card in Red Cine, trying to find any drop frames or any other funny business, before handing it back to the AC.

Hope this helps!

J. Michael Vargas
 
You must log in or register to reply here.
Back
Top