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

Any idea what would cause this...?

P

precinct13

Member
Joined
Oct 24, 2007
Messages
7
Reaction score
0
Points
0
I was synching up the day's footage when I ran into this:

A106_C007.jpg


A109_C001.jpg


They appear randomly over several shots. Also, some clips shut down QT and FCP when played...

Any ideas?

Thanks in advance!
 
I've had that happen to me and was not able to identify the problem. ( tried many many variables too ) Seek Help. If you figure out what it was let us know. What camera # are you using ?

Matt Uhry
www.mattuhry.com
 
Triple check your FW cables, and your CF card reader. It's a data problem, not a sensor problem.

If the issue persists, call it in. They should get you up and running pretty quickly, once you've made sure that the problem exists on the card itself, and it's on the card itself.
 
For everyone who has had this problem lets start with the exact model and brand of card reader used.
 
Sorry to hear others have had the same problem...

It's Red #15. I'm not sure what firmware build. I'm just the assistant editor. I get handed a drive with all the material on it at the end of the shoot day. I'll try to find out build # and CF reader type.

This has happened over a couple of nights now. The only thing I can find that these shots have in common is that they are night time exteriors and its been very cold here in Ohio. But I'll keep digging...
 
Is it getting worse with each new card shot?
 
I wouldn't say it gets progressively worse...it's pretty random. But it definitely happens most in the last third of the shoot day. Which, lately, has been midnight to 4am in 30 degree weather.
 
With all the metadata encoded in the R3D file, maybe firmware version should be included too?
 
Matt Uhry said:
Why do you think that ? What in particular about the problem makes you think, "It might be a bad cable or CF card" ?

Matt Uhry
www.mattuhry.com
Click to expand...

Sorry, I meant card reader. I have seen the 'crashing fcp' thing show up when copied with a bad cable, I replaced the cable in a dummy check and the second copy when fine.

But do contact red tech support asap, because if those aren't a bad copy, it means that that stuff is actually on the R3D file.

It is NOT a cold issue...
 
I found a similar problem with a sample clip in REDCODE. Some areas of certain frames show a weird pattern. On one frame it's there, on the next frame it's gone.

anomalyfd8.jpg


Note that I was working in "Full res. High".

Can anybody reproduce this?
 
I saw this too. But if you go to the same frame in Red Alert it's not there. Reassuring that it seems to be a function of the decoding rather than the encoding of the footage.

I emailed Graeme about it and he's on the case.
 
Well, if it still matters, I found out it is build 6 on the camera.

Also, I still see the patterns when I load the .r3d file in Red Alert.
 
You must log in or register to reply here.
Back
Top