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

PLEASE HELP! BIG ISSUE!

D

Dominick Sivilli

Active member
Joined
Dec 23, 2009
Messages
35
Reaction score
0
Points
0
Location
New York City
Website
www.codebreakerproductions.com
Hey RedUsers,

Seems Like I have a problem, Here Goes:

I shot something about a week ago and doing the grading for this client, after I render to pro-Res(sq) some of the clips just give me a black Screen or Some clips play half-way threw and than go black!
What I noticed from these clips is that there is more than one R3D file in them maybe its because that, I also heard its a metadata problem, Many people say reset meta in RedAlert and make new quicktime proxies, Which has worked for one file but not all. Does this sound like a folder of bad clips or is there something I can do to fix it?

Help is much appreciated ,
Thanks,
Dom
 
Dominick Sivilli said:
Hey RedUsers,

Seems Like I have a problem, Here Goes:

I shot something about a week ago and doing the grading for this client, after I render to pro-Res(sq) some of the clips just give me a black Screen or Some clips play half-way threw and than go black!
What I noticed from these clips is that there is more than one R3D file in them maybe its because that, I also heard its a metadata problem, Many people say reset meta in RedAlert and make new quicktime proxies, Which has worked for one file but not all. Does this sound like a folder of bad clips or is there something I can do to fix it?

Help is much appreciated ,
Thanks,
Dom
Click to expand...

I'm no expert, but I was under the impression that RedAlert was obsolete and deprecated, and didn't support camera firmware past Build 21? RedCine-X is the up to date application.

Mike
 
So that sounds like a bad frame from copy in there.

Out of curiosity, was this shot to cards or to drives?

Is the error occuring at the same frame in RCX and RA?

If you know that framenumber, try setting in- point for the export at a couple of frames after the error occurs and try a new export.

Keep us updated.

Cheers

Gunleik
 
Some thoughts:

Dropped frames - due to heat, HD vibration, etc.
Bad data copy from Compact Flash - this can happen with a bad cable or chip reader.

Do the clips play correctly in proxy? Have you ever ripped the footage cleanly? Have you tried it on a different system yet?

The multiple r3d files might just be the 2 gig sectioning.

I think we need more information...
 
Gunleik Groven said:
So that sounds like a bad frame from copy in there.

Out of curiosity, was this shot to cards or to drives?

Is the error occuring at the same frame in RCX and RA?

If you know that framenumber, try setting in- point for the export at a couple of frames after the error occurs and try a new export.

Keep us updated.

Cheers

Gunleik
Click to expand...

It was shot on cards!

RedCine-x exports all the way threw without crashing but red Alert Crashes!!

What should I try? Setting in point to export?

Thanks Gunleik, you might be my hero on this,lol!
 
Mark Wilkinson said:
Some thoughts:

Dropped frames - due to heat, HD vibration, etc.
Bad data copy from Compact Flash - this can happen with a bad cable or chip reader.

Do the clips play correctly in proxy? Have you ever ripped the footage cleanly? Have you tried it on a different system yet?

The multiple r3d files might just be the 2 gig sectioning.

I think we need more information...
Click to expand...

The clips run trew the proxies fine! we downloaded it on a 800 firewire card reader! and were grading from the original footage! and I have not tried it on a different system yet?
Thanks Mark
 
Well proxies working is a good sign. I think you should download an older version of redcine and try that. And try on another system - ghost in the machine?

It really sounds like you've got a data glitch. If you have another backup of the data, I'd try ripping one of them.
 
Definitely more information please. What system, OS, camera Version, and like the others said, do you have another copy to look at.
Do the Proxies work fine on every clip? or only that one clip you created new proxies for?
When your clip goes black, does it come back to the footage at any point? ie. Bad frames in the middle of the clip?
Quite interested.
Also, are you using a Rocket to transcode to prores?
 
Jonathan Carbonaro said:
Definitely more information please. What system, OS, camera Version, and like the others said, do you have another copy to look at.
Do the Proxies work fine on every clip? or only that one clip you created new proxies for?
When your clip goes black, does it come back to the footage at any point? ie. Bad frames in the middle of the clip?
Quite interested.
Also, are you using a Rocket to transcode to prores?
Click to expand...

Mac osx 3.06 ghz core i3/ 12gb ram
Newest camera Build Version 30.7 I believe
I don't have any other copies to look at ;(!
Proxies play perfectly, some one told me it was a metadata problem?
and no rocket, still doing testing tried everything!
-Dom
 
Dom,

When you look at the Clip in RCX BEFORE you transcode to PROres SQ, does it play through the entire clip? Or does it go black then as well?
Have you tried transcoding to ProRES out of Clipfinder, just to rule out a RCX problem?
I've seen this occur before, but it was a glitch between a 1st Gen MacPro, and the RR card using OS 10.6.

Has the file structure been tampered with at all? If those "multiple" .R3D files get shifted around, RCX is unable to link them together and it would go black like that.
Another thing to try, would be to give the "Log and Transfer" a shot in FCP just to see if you get a different result.

The since the Proxy files rely completely on the .R3D files, its safe to say that the footage is there and in tact.
Good luck
 
I had just the same problem as you : there were corrupted r3D frame wich could not be developped byt Redline or the RedRocket. The problem was that when Redline or the rocket found one of these bad frames, it corrupted all the images that were after this bad frame (all the clip was black but the proxy worked). It was a big pain to try to find this image with "in" and "out" point because, I had to develop all to see if the decoding image process was corrupted or not.
So, my friend Mikael Lubtchansky helped me by writing a little script wich was able to developp each frame individually with Redline. And when there where a corrupted frame it was traced in a log file. I took a long time but at the end, only a few numbers of bad frames was such corrupted and we saved the day of shooting. You should ask Mikael to help you with his script.


Olivier
 
RCX will always insert a black frame for a frame when it fails to decode. It also reports the frame number in the "details" column of the batch window.

There is an option in RCX which attempts to export every frame in a clip separately with redline to help with finding which frames are corrupt. "Export Preset Dialog" -> "Options tab" -> "Use Redline (software only)" & "Frame Only Mode".
 
You must log in or register to reply here.
Back
Top