Help With Recording Problem

[Frank Di Bugnara]

Here's the situation: We recorded three clips on the same camera, one right after the other.

First: About 3 Mins
Second: About an hour and a half
Third: About 30 Mins

The problem is the second clip appears to have no audio associated with it--the video looks fine. We made two copies of all the footage from the Red drives--both through R3D Manager.

We have opened the problematic second clip in Final Cut and Clip Finder and there is no sound in either place.

Any help or suggestions would be greatly appreciated.

Thanks.

 

[Frank Di Bugnara]

Here's an update:

I did not mention before that the proxies did not contain audio. We just tried bringing the R3D's into the Log and Capture window in FCP and when playing in that window, we could hear the audio. So we are going to try an export tonight and see if we can get extract the sound that way.

Has anyone run into this before? Essentially, the sound not being part of the proxies.

 

[Brian Ferguson]

What build of firmeware are you using?
In some early builds the meters went a bit far down on the green side enough that you could see the meters move but not enough volume for Quicktime. But your other clips were ok so I don't think that is your case.

 

[Frank Di Bugnara]

Thanks, Brian, I don't think that was the problem. I was running two cameras and they both had the same build.

I think what happened is the camera simply did not make proper proxies for that clip (It was actually about 2 Hours long). We ended up running the R3D through Log and Capture in FCP and got the sound that way.

On another note, I have never heard of problems with very long clips in Red, but maybe they are not a good idea. We did not want to stop the cameras during the interview because it was with a high-profile person. We did not want to break the flow of the interview and wait for the camera to post long clips.

We did notice something else very interesting: At regular intervals (about 6 evenly spaced incidents throughout the 2-Hour clip) there are clusters of bad frames. These dropped or corrupted frames view as green in FCP and sometimes cause FCP to crash if you stay parked on them for more than a few seconds. Does anyone know what this is about?

 

[Brian Ferguson]

I personally don't like long clips like that, you can't break up the R3D file later. I try to cut and resart during the question portions of the interview if you aren't using the voice of the person asking the questions.

Did you try making a new proxy in RED Alert?
You may have had some dropped frames.

 

[Nook Kim]

Having the same corrupted data issue

Having the same corrupted data issue

Hi guys,

I'm having the exact same corrupted (not dropped since it's about 25 sec long) data within a 24 minute clip. The shooters were using Build 21 with audio going into the channel 1, 4K 16:9, 23.98fps, etc.. It was an interior interview shoot on a tri-pod. The audio was brought into the camera wirelessly with the 48V off since the mic was powered.

The Red Drive was 320GB one, which I believe was purchased in April 2008. I'm not sure it has been updated for the infamous "SATA_TRANS_ERROR"

Anyhow, what is too long for a clip to be safe?

Thanks,