[Jonathan Hensley]

I guess I just don’t understand why .R3D files crash programs when they are scrubbed over and there is no RED support on the problem. I mean, it is one thing to have a green dropped frame or a portion of footage lost. At least then, however, you can edit around it.

What frustrates me is why it is so hard for RED to release something that keeps Final Cut and Red Cine-X from CRASHING when it encounters a dropped frame. When something that big can ruin an ENTIRE shot, that is a huge problem that needs to be fixed.

[Jonathan Hensley]

Same goes for me Josh. We took a break over Christmas from the project and I decided to go ahead and edit the unaffected scenes, but now I need to move on and there are two key scenes, both of which have corrupted footage.

I presently don’t have Clipfinder, but before I spend $100 on it, I would like to know if it can solve this problem or not.

Thanks!

[Jonathan Hensley]

I’m glad you found a possible solution. My only concern is how this will effect relinking the R3D files back to the converted footage in Color. Is it even possible when you split the clip in two?

[Jonathan Hensley]

UPDATE:

Sorry to double post in this thread, but after getting frustrated with Final Cut Pro, I decided to run the clips through RedCine-X. It actually worked fine for a minute, but when I looked through the clips, I noticed THE SAME PROBLEM! (though the clips were black this time instead of green).

Video Below.

https://www.youtube.com/watch?v=PHPLpvr-xxA

This leads me to believe that there has to be something wrong with the way the Red folder are set up, though not the clips, because the Quicktime files work fine and play well.

[Jonathan Hensley]

Hey guys. Thanks for the advice.

A few weeks into this now, and I’m still running into the same problems on THREE different computers (all with the same specs). Software has been updated correctly on all three, and I trashed the waveforms and thumbnails on all three.

Sometimes I get a green screen like before, and sometimes Final Cut Pro quits unexpectedly and blames the RedCode QT Plugin.

Any ideas? I’m desparate.

[Jonathan Hensley]

Possible. But I don’t know if that would explain why it worked for the first 75% of the footage but not the last half.

[Jonathan Hensley]

Honestly, I don’t think you can tell a color grade is bad based on what project you used it in. As the old adage goes, it’s not the tools you have, it’s how you use them.

However, there are certain advanced tools in Color that you simply don’t get with Final Cut. Final Cut’s 3 way Color Corrector is meant to be basic for quick, on the fly color correction.

If you have the time, then I would say go ahead and learn Color. Go ahead and take a few weeks to learn the program and how to round trip back to Final Cut. If time is not an option, and you want the most options for your film, there is no really reason not too.

[Jonathan Hensley]

If anything, you can convert the HDV footage down in Compressor and simply re-link the FCP file to the newly downconverted video files. Everything should still be edited, you’re just telling Final Cut to look at the new lower-quality files as opposed to the original HDV ones.

[Jonathan Hensley]

I would say it mostly depends on what you’re hoping to do with the final product.

If it it a narrative film, for example, shot on the RED and you’re hoping to go into festivals with it, take the time to go to Color or some other professional color grading program and back to Final Cut.

If it’s a short video interview and you need a small color grade done in two hours or so, stay in Final Cut. Final Cut’s color corrector is good for quick yet effective color grading that needs to be done fast. Color is for more in depth projects that need a lot of work, or where you can devote the time needed to make an effective grade.

Hope that helps.