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

NEW: RED FCS installer build 30

Does the new software fix this crazy timecode stuff? My project is perfect in FCP. FCP doesnt care what timecode the clips use. When it goes to Color though, it gets crazy. Does the new software fix timecode in Color?


Dusty
 
Hey Dustin,

Sorry to hear about your problems. Neither our QuickTime codec nor the Color plugin deals with timecode AT ALL. They simply get a frame, decode it and return the uncompressed data to the caller. This means the problem is with the generated reference files and/or the XML FCP sends to Color.

You're not using Log & Transfer, correct?

From what I know ClipFinder uses REDline and the latest REDline does have an issue (like Redcine-X) with generating proper timecode in the QuickTime reference files. As Gavin indicated we are trying to track the issue down, but it's a weird one.

Do you have any problems if you go back to the older RCX/REDline/ClipFinder and re-generate the QT reference files?

Thanks,

Rob
 
Rob,

I am using an old version of Clipfinder and Redline so that is working now. So I can create Quicktime Reference files with the either TC or EC.

The new FCS software did something. I sent this FCP project to Color and it worked perfect. I installed FCS v30 and resent to Color and everything is screwed. I downgraded back to FCS installer v20 and it is still messed up. At some point I made Quicktime reference files with Clipfinder and the new Redline.

FCP doesn't care about the timecode. Color has a huge problem with it. The Red software has to do something with timecode in Color, because I send Quicktime reference files to Color and Color uses the R3D. It seems the problem is in that process. Color is confused about the timecode between the reference and the R3D.

The six FCP projects I sent to Color before I installed FCS v30 worked great. I resent reel 1 and that is my nightmare project. The other five projects still work just fine.

I have no idea how the editor made the Prores files. I am just the Colorist on this project, but because of this problem I am spending way too many hours doing work I am not getting paid for. I have wasted more hours trouble shooting this than I should have spent coloring the entire feature. And now I need to try an d re-edit the first 20 minutes and see if that solves the problem or if FCS v30 ruined this entire project.



Dusty
 
I there a way to get L&T to just do the 61 files used in this project? All it wants to do is the entire mag that each clip comes from and that will take days and too much space. Plus I don't even know that using L&T at this point will fix this.

Dusty
 
So I just spent the last few hours using L&T to convert the clips I need for this edit and using Clipfinder to conform the edit to the L&T files. Now FCP has similar if not the same problems as Color. It seems like the timecode in the R3Ds is corrupt. Is that possible? How can I test the R3D timecode? Seemed like L&T was using EC instead of TC. Is it possible for EC and TC to get confused inside the R3D?

Any thought on this? I am really getting worried about this footage being RUINED!!!!!!!


Dusty
 
So I am finding that L&T only transcoded part of several clips. SO now I am going back and redoing those clips one at a time and they seems to be working.

I have never used L&T. Are there bugs in this I should know about?


Dusty
 
Dustin Cross said:
So I am finding that L&T only transcoded part of several clips.

I have never used L&T. Are there bugs in this I should know about
Click to expand...

I have seen a couple of past comments about intermittent behavior like this, but we've never seen it in house. Without knowing the conditions that produce it, we can't know if this is a general FCP L&T problem or something specific to our plug-in. If you note any pattern, please let us know.

Dustin Cross said:
It seems like the timecode in the R3Ds is corrupt. Is that possible?
Click to expand...

Unlikely. We don't rewrite the R3D files. We already know that the timecode in the reference movies produced by the current tools can be wrong; that's most likely the source of your problems.
 
Gavin Stokes said:
Unlikely. We don't rewrite the R3D files. We already know that the timecode in the reference movies produced by the current tools can be wrong; that's most likely the source of your problems.
Click to expand...

Gavin,

Is this still an active issue? Any progress made on the time code issues?

Thanks,

Brandon
 
After installing REDCINE-X and Redline 256 the timecode problem with new proxies is gone. Color is working just as it did before this problem surfaced.
 
Brandon Kraemer said:
Is this still an active issue? Any progress made on the time code issues?
Click to expand...

Hi Brandon. Yes, this is still a top priority. After reproducing the problem in house, we determined the likely culprit and are working to fix the code. I'll post updates when the fix is imminent.

Thanks for your patience on this one, guys.
 
I was able to fix my problem by using L&T on the project I was having problems with and then using Clipfinder to conform to the L&T files. Sent that to Color and everything is great.

I am finding random problem clips in older Color projects now though. I have a project that was finished and rendered for DVD and now that I have final approval I need to render DPX files for film out and about 9 clips in a feature are messed up now. They were working perfectly before. It will be easy to solve the problem for the bad clips, but it is weird, because the same clip is fine in some spots and bad in others.

Also these projects worked perfectly fine and were rendered out of Color three different times with no issues. None of the proxies were touched and now there are issues.

Just a heads up for you guys.


Dusty
 
You must log in or register to reply here.
Back
Top