Clips in Color are Frozen, sent from an M Proxy Timeline

[Ian Andolina]

Hi,

I'm using M proxies in FCS3 with all updates to Apple and Red software (QT codec 3.9, Color plugin 2.8, Color 1.5.1, FCP 7.01). A number of clips end up being frozen on the *last* frame when the timeline is imported into Color, making it close to impossible to grade. None of my footage was recorded across the 00:00 midnight boundary. Things I've tried:

1) Clipfinder fix apple color loop bug - NO SOLUTION
2) Turn off new color science and resave the QT proxy - NO SOLUTION
3) Context menu in Color > Relink - NO SOLUTION
4) Strip out everything (sound, fades) and all clips except the offending clip (one simple M proxy clip on the timeline) before export to Color - NO SOLUTION

Does anyone have any other ideas how to solve this?

 

[Ian Andolina]

The highlighted R3D file is one which causes the last frame bug (you can check timecode etc.):



I also tried using media manager to export some clips into a new project. The timeline claims that the clips are REDCODE proxies, however although this new project timeline exported to color doesn't freeze on the last frame, the Red tab in the primary in is not enabled...

 

[Ben Brainerd]

You can't media-manage REDCODE. It will say it is, but it will really just transcode to ProRes or something. The only way to MM REDCODE is to re-L&T your footage.

As far as the clip freezing issue, I'm totally baffled. There have been a few issues where it would freeze on the *first* frame of the clip (The looping bug, and the midnight rollover issue) but it doesn't look like either of those apply to you. That screenshot is very low-res, but the clip beneath it seems to be created/shot at 14:59. So you're not hitting the midnight issue. I would try recapturing it, if you're using wrapped R3Ds, or rebuilding the proxies using clipfinder/RedAlert.

 

[Ian Andolina]

Thanks Ben.

I did have problems with the camera proxies saved with the R3Ds - they cause Color to crash when at least the 2GB limit is reached and thus multiple R3Ds are generated, along with some other triggering factor. So I went through and regenerated all the camera proxies with the current version of clipfinder. For the problem clips I've tried Redalert and clipfinder in case there was a bug in either (though I assume they both use the same SDK functions, but just on an off chance).

And in clipfinder, I tried turning off the "new" (now older!) color science and resaving the camera proxies just in case that was an issue (with only one clip on the timeline). And that didn't solve this.

I really need to finalise the project before Sunday - it is only waiting the color correction. Does anyone have suggestions on where they'd take this. I could try importing some XML into Premiere Pro > After Effects but I've never color corrected there (or really used Premiere) so don't know what to expect. Any other usable route from Final Cut for final color correction and output to DPX (going to 35mm)? Not really much money left on this project so no chance for post-house etc. This R3D color plugin bug is hugely frustrating for use.

If we can't use the RAW data (the reason we shot Red in the first place) then what is the best way to generate ProRes clips to process through color? Most of the R3Ds have a first-light correction done via Redalert/clipfinder - how can that be used as a starting point on an M_Proxy timeline project?

If I conform to the R3D files themselves via clipfinder, will color read that?

Thanks again for any and all suggestions!

 

[Ben Brainerd]

Yikes. Sunday's definitely a tight deadline.

Not having seen your issue before, and having no clue what would cause it, I would say your best workaround might be to render the problem clips out of Clipfinder/RedAlert using ProRes and add it to your sequence. It's a less than ideal solution, I know, but it would get you past the current speedbump.

Hopefully the problem clips aren't major shots, since it might cause headaches trying to grade them to match everything else. You could always render out the whole project, but that seems overkill.

If you do go with this workaround, I would suggest that you use Clipfinder and turn *off* the new color science. Since the Color plugin is still old CS, you'll probably get a better match that way.

 

[Charles Angus]

You can always render out Quicktimes of the whole project, or just offending shots from Clipfinder using the existing RSX data. You can then re-link to the new footage in FCP. Not sure how happy Color would be with mixing and matching RED and QT footage, never tried it.

You can even use the "Import clips from FCP XML" function in Clipfinder, for easy locating of the shots you use.

NB: I have only used the newest beta Clipfinder, YMMV if using the older one.

 

[Ian Andolina]

Thanks for your help guys, looks like I've got a looooong weekend ahead of me...

Currently trying to use FCS uninstaller and reinstall on a virgin Snow Leopard image just in case there is a system issue.

 

[nickcolombini]

Was there ever a solution to this issue? I am having the same problem...

 

[Sarah C.]

I have only one frozen clip myself. Going to do some hoops just to get that one done so project can be done.

~s

 

[Tobias Roediger]

Isn't this part of the Color Looping Bug issue that Clipfinder fixes?

 

[Kaku Ito]

Some situations, Clipfinder's color loop but fix does not solve it. That is when you have sent proxies from Clipfinder with TC not being Edgecode. Make sure you select a clip in Clipfinder then edit look to set the timecode to the edgecode, apoly that to all clips, the do a make quicktime to all of the footage.

 

[Gunleik Groven]

Are you saying that if one consistently uses edgecode throughout the workflow, this issue does not happen?

I had a project bombing due to mistakingly setting edgecode on the proxies, but then that was edited with TOD TC proxies, so it makes sense. Still had issues with one clip, though....

 

[Kaku Ito]

Gunleik,

Is the one clip crossing over 0:00am? If that is the case, may be replace that with R3D wrapped QT? If the problem is persistent then that is what I do.

 

[Brandon Boulay]

hmmmm

hmmmm

Hey Guys,
I am experiencing the same problem and confused as to wether or not a fix has been found.

I am editing M proxies created in Camera and numerous shots play has still frames in COLOR and when rendered out in COLOr as well. They play fine in Final Cut.

If the fix has been found can someone walk me through what I need to do?

 

[Uli Plank]

Get Clipfinder, go to the tools menu and choose "Fix looping bug".