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 :)

Frames ruined by Blue Flashes

C

ChristopherKenworthy

Well-known member
Joined
Jan 26, 2007
Messages
277
Reaction score
0
Points
0
Website
www.christopherkenworthy.com
Shooting Build 15 2.1.7, and two frames were ruined, as shown. This one had the blue lines, the next frame just looked a bit hazy. We were using the Red Drive (Raid), 24fps, ASA 320. It was a five minute take - one of many, but the camera wasn't hot. Any ideas? Has this been seen before?

For the record, this was seen in the HD monitor at the time, and seems to be embedded in the RD3s - so it's not just a QT proxy problem. The attached file is a direct output from Red Alert, with no work done, except size reduction in Photoshop.
 
I'm certainly no expert, but it kind'a looks like an I/O timing or data buffer issue to me. Not on acquisition, but in processing. Particularly when you consider it was such a very long take (5 mins.).

This is one Graeme would love to take a look at, for sure. You ought to send it to him.

Good luck!
 
MikeHedge said:
wow that is strange.... hope you get direct answer from RED...

PS how's Sculptor going?

Mike
Click to expand...

Thanks. The Sculptor is going very, very well. We're ahead of schedule, thanks in part to Red, and the results are magical. We're doing that shoot-your-feature-on-beta-build thing that we're not supposed to do. But, until this blue flash, we've been getting away with it.
 
Tico said:
I'm certainly no expert, but it kind'a looks like an I/O timing or data buffer issue to me. Not on acquisition, but in processing. Particularly when you consider it was such a very long take (5 mins.).

This is one Graeme would love to take a look at, for sure. You ought to send it to him.

Good luck!
Click to expand...

It was seen in the monitor (HD split, and on the steadicam), so it looks like it happened in camera, rather than in post. And it gets worse. We've found more frames, whited out this time, as shown here.

As for the long take, the errors started 1 minute in, and appear throughout this take and the next one. They then appeared to stop. Still checking the footage.
 
Sorry for the misunderstanding Chris, when I suggested "processing," I was referring to a data processing component after the sensor output and before the R3D is created. In camera. Stuart and Graeme are the ones to poll on this.

The white-out frames are puzzling and disconcerting, to say the least.
 
Christopher, you must report this asap through RED support channels. That's the only way we can properly track and deal with this kind of thing.

Graeme
 
Graeme Nattress said:
Christopher, you must report this asap through RED support channels. That's the only way we can properly track and deal with this kind of thing.

Graeme
Click to expand...

Hi Graeme,

The support ticket went in as well. I just wanted to know if others had experienced this, and to share the feedback publicly. I don't want to start a panic - you'll never find a stronger Red-supporter than me - but I thought this needed airing on the forums, as that's that the Bugs/Problems/Help forum is for. It's concerning, but we're not fretting too much. A few frames after weeks of shooting isn't a big deal. The last time I used film, I lost reels and reels...

But, we'll be sad if this happens every day. We have a spare Red, and spare drives/cables and so on, so there's lots we can change. But if there are any clues as to what this might be, we'd love to know.
 
Thanks! I've not seen such an issue before, and it would be wrong of me to make blind guesses.

Graeme
 
Had the same issue with a shoot this week. Severe corruption across 5 cards shot during the same run cycle. Corruption is severe enough to cause QT proxies, REDCine, and REDAlert to crash when certain frames appear. During the visable footage there's severe artifacting every second or so in some of the clips, and less frequently in others.

Most of the clips were long performance takes in the neighborhood of 4-4.5 minutes each. Firmware was 15 v2.1.7.

We shot 70 cards (4k, 3k, 2k, 23.98 and assorted varispeed) during the 48 hour period surrounding these clips, and these are the only ones to display any corruption.

I'm filling a trouble ticket now for reference.
 
Interesting that these were also 4-4.5 minute takes. As I say, these didn't happen more than a minute or so into the take, but we were running a lot of long takes. Is there something about long takes that upsets the camera with this firmware? My ticket is in, and Red are looking at the frames.
 
ChristopherKenworthy said:
Interesting that these were also 4-4.5 minute takes. As I say, these didn't happen more than a minute or so into the take, but we were running a lot of long takes. Is there something about long takes that upsets the camera with this firmware? My ticket is in, and Red are looking at the frames.
Click to expand...

Of the 70 cards we shot, maybe a third of them were 4+ minute rolls....and only 5 had issues. Not sure what's going on, but for me that blows a pretty big hole in the problem being situated in long takes.
 
Please give tech support the first opportunity to respond to problems (esp. with beta firmware) before posting. That's what they're for.
 
I believe the bomb squad is already trading emails with you, thanks for the report.
 
ChristopherKenworthy said:
For the record, this was seen in the HD monitor at the time, .
Click to expand...

MrDorf said:
Of the 70 cards we shot, maybe a third of them were 4+ minute rolls....and only 5 had issues. .
Click to expand...

Can you confirm guys that you observe it while shooting on exteranl monitor ?
I mean it is not hidden problem (we can notice it while onset ) ?
 
BASSAM MSSALATIE said:
Can you confirm guys that you observe it while shooting on exteranl monitor ?
I mean it is not hidden problem (we can notice it while onset ) ?
Click to expand...

I wasn't shooting personally, but I'm 100% certain that if my DP saw what was actually recording on the frames through the LCD he'd have stopped cold.

In short, no, our problem did not show up on the LCD.
 
You must log in or register to reply here.
Back
Top