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

RedCine-X keep quitting unexpectedly

J

Jeremy G

Member
Joined
Nov 10, 2010
Messages
13
Reaction score
0
Points
0
Hello.

Having some issues with RedCine-X. I have tried multiple builds (356, 351, 348) which seems to indicate something with the footage.

Eventually, the application will crash while transcoding Red4k 16:9 to 1080 ProRes LT via software only (no Rocket). I have done a couple of jobs like this with no issues. For some reason, this job seems to be giving me fits. I have been working on this for 4 days now and I can't seem to get through it all. It's not an exorbitant amount of footage.

I wish I could give more info to help you you help me, but I'm not exactly sure what info to give.

OSx 10.6.4, FCS support 30.3.

Thanks for any assistance.

Jeremy
 
Small update. I just transcoding tried one clip where RCX left off and I am getting "Error Decoding Frame: 800" or whatever the frame number is. Going to try and see if another copy of the footage is OK. Any suggestions welcome.

Jeremy
 

Attachments

  • Error.jpg
    Error.jpg
    7.3 KB · Views: 0
Gunleik Groven said:
Sounds like you have a bad frame in there...

Usually these come from poor copying routines.

Do you have access to original media?
Click to expand...

Thanks for your response.

Now that I am sitting here and have time to trouble shoot a bit I am watching the footage, I noticed that the logs say corrupt frames.

By original media, you mean CF cards or whatever they shot on? No. I have three copies of the footage on three separate hard drives. I am attempting to restore the footage from a different hard drive than I used originally. I am unsure of how they footage was verified on set, but I have some sort of log here that seems to be a checksum. In each reel folder, there's a text file that is named ProjectInformation.txt. It then lists all the media and lists an MD5. Sound familiar at all?

Jeremy
 
Sounds very familiar.

Sounds like it was don with r3d manager, which is a good START for file integrity.

I have made it a rule never to erase media until all data has been transcoded without issues. as r3d manager can slip through faults. The times I have been able to verify this, the errors have been introduced in the copy process. I know others have other experience, but I go through and supervise a fair amount of r3d data over a year working with TV-episodicals and features, and all I can say is that: These errors on the original media is very rare.

This seems to happen more frequently when copying from CF cards than disks...

But in short: Sounds like your RCX is behaving. You'll have to find the bad frames and transcode before and after.

Cheers!

G
 
Gunleik Groven said:
I have made it a rule never to erase media until all data has been transcoded without issues. as r3d manager can slip through faults.
Click to expand...

Sort of beyond my control, but I guess it's good to know.

Gunleik Groven said:
But in short: Sounds like your RCX is behaving. You'll have to find the bad frames and transcode before and after.

Cheers!

G
Click to expand...

Can't wait. Thanks a lot for your response. Hopefully this new copy will solve this.

Jeremy
 
I am now trying 32bit version of 356. The good news is that it doesn't seem to so crashy on a corrupt frame, but it doesn't seem to recover after a corrupt frame. How exactly would I go about exporting after a corrupt frame?

Edit. Actually, nevermind. Wow. This data set is really effing bad.

Is there a way to restore corrupt R3ds? How does one deal with this?

I can see the corrupt frames in QT using the QT proxies. I can then scrub for a while before and after, then QT crashes.
 
Last edited:
You must log in or register to reply here.
Back
Top