bad frame

[John Brennick]

Hey all, I've been shooting random shots just getting a feel for the Scarlet and I've noticed a bad frame. I wasnt sure if anyone had any insight into this or not. Thanks again in advance. It was shot 2K. 60 fps. The clip was pretty long so Im not sure if that had anything to do with it but I'm just throwing it out there. It's been handling great otherwise.

Best,
-J

 

[Benoît-Joan Clariana-Roig]

Wow, looks like you shot in an untextured 3D world.

 

[Matt Ryan]

Hey all, I've been shooting random shots just getting a feel for the Scarlet and I've noticed a bad frame. I wasnt sure if anyone had any insight into this or not. Thanks again in advance. It was shot 2K. 60 fps. The clip was pretty long so Im not sure if that had anything to do with it but I'm just throwing it out there. It's been handling great otherwise.

Best,
-J

Is this from a transcoded file or does this appear in the viewer in RedcineX Pro as well?

 

[John Brennick]

Hey Matt, it appears in RedcineX Pro, Nuke, and Premiere. This is just a jpg render from the r3d file.

 

[Steve Sherrick]

Looks like a corrupted frame from a bad data transfer.

 

[Marc Wielage]

If this is just one bad frame in an important take, it can be fixed, given enough time and money. Talk to me in email if you want some suggestions for companies that fix this sort of thing. I know of a recent feature that had hundreds of corrupted frames, and as far as I know, all of them have been resolved and repaired to the point where no one will ever notice the problems.

This is not a Red issue, BTW. There were significant digital problems on Superman Returns (to name one major film), and I believe the digital fixes there went to hundreds of thousands of dollars. Crap happens. Looked fine in the theater, and that's all that mattered.