Can't transcode EPIC footage... HELP!

[Matthew Mann]

Hey all, posted this on Redcine thread, but still need help!
I have a project that is completely transcoded to 1080p ProRes 4444 except for the last 3 files. The footage was shot on Epic, mix of 5k 2:1 and 2k 2.4 @300fps. All shot onto the same SSD. The files that aren't working are 5k 2:1 96fps on 23.98 time base RC 13:1.

Essentially the transcode takes FOREVER (12+hours per clip!), and when it completes the .mov file is corrupt, and has a tiny file size of a few MBs at the most. I tried using multiple versions of Red Cine X, Red Cine X Pro, and Premiere Pro CS5.5 (w/ epic plugin). In all programs, the playback of the files in question works without a hitch and looks great. I tried chopping the clips down but the same issue still occurs... Drive I'm rendering to has plenty of space, and I've tried multiple drives. Other clips that worked in the project are even longer at same specs and transcoded fine.

Running on 8-core Mac Pro, no Red Rocket. Mac OS 10.6.8


HELP PLEASE!

 

[Nook Kim]

Try to update the driver and firmware on RR, and use the latest RC-X Pro. It solved it for me.

 

[Matthew Mann]

Don't have a Red Rocket. Running latest version of RCX Pro, but also tried on multiple older versions with no luck. :scared:

 

[Rob Lohman]

Can you describe HOW it's not working? R3D files not loading, image corruption on playback/export, rendered QuickTime file not opening, etc.

 

[Matthew Mann]

Hey Rob. The R3D loads in RCX Pro as well as Premiere Pro CS5.5. It's an issue when I transcode to QT PR 4444. The .mov files are coming out corrupt. Like I said, it's only happening with the last 3 R3Ds on the mag.

I appreciate any help you can give me.

 

[Rob Lohman]

When you say corrupt, do the .mov files not open AT ALL or do you see image corruption?

If the former then it's likely:

1) your destination drive is full when it hits those clips

or

2) you're exporting long clips that are over 2 or 4GB in *output* size and you're outputting to a volume that does not support such big files (such as FAT volumes or certain network systems)

If it's image corruption then please email me a screenshot of the corruption (rob at red dot com)

 

[Joel Barnett]

If all else fails....

You could try transcoding to a tiff sequence.

Then convert to a prores file using QT Pro (You could add reel name and TC in QTChange if you need)

This way if there is only 1 frame which is causing an issue, you should have all the other frames.

 

[David Collard]

If the last three clips are really long, try exporting those with quicktime that handles clips longer than 2GB.

 

[Matthew Mann]

When you say corrupt, do the .mov files not open AT ALL or do you see image corruption?

If the former then it's likely:

1) your destination drive is full when it hits those clips

or

2) you're exporting long clips that are over 2 or 4GB in *output* size and you're outputting to a volume that does not support such big files (such as FAT volumes or certain network systems)

If it's image corruption then please email me a screenshot of the corruption (rob at red dot com)

Not image corruption. They're going on Mac formatted drives with over a terabyte of space. I've also tried transcoding to other drives but had the same issue.

I'll try exporting a TIFF sequence and turning that to Pro Res. Hoping that works!