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

OK Dustin and others, thanks for your patience and feedback on this.

The only other component installed by these packages is the preference pane for REDcode QuickTime decoding. That hasn't changed since the last installer, but you could go to System Preferences and see if the decoding quality is what you expect it to be. Perhaps this is a source of playback-performance issues.

For anyone getting the "you have a later version" message, try doing a custom installation and deselect the optional components. If that works, add them one by one so we can determine which of them the installer is complaining about. Thanks!
 
Thanks for all the feedback guys. We're actively looking at the reported issues.

Please help Gavin out, he's one of the guys working on this.

Thanks everyone!
 
I have been experimenting with the new RED FCS installer build 30.
For the first time, the proxies look identical in Quicktime, FCP and REDCINE-X (246). Good.

But I can't grade the proxies in Color anymore. It's not the looping bug.
It's some timecode problem. When I send a clip to the render queue in Color, the in timecode is OK but the out timecode is wrong. Just one frame of duration for the clips.
All of them. And if I render I only get one frame. And in the timeline it will only play one frame. So at least it's consistent this bug...

Mac OS X 10.6.4
Final Cut 7.0.2
Color 1.5.2
 
I remember similar bug before. When you edit with older proxies and try to send that to Color, I'd have these still frame render issues. I had to set the timecode to match either TOD or edgecode, making them consistent and overcame the problem.

Maybe setting the metadata to one consistent timecode, then reconform in Clipfinder will fix this fast? I will try to see if that works.
 
can´t see FLUT in the color´s red tab!!, that´s not the upgrade I was waiting for.
 
Vico Martin said:
can´t see FLUT in the color´s red tab!!, that´s not the upgrade I was waiting for.
Click to expand...

It's sad but Color itself has to be updated I think.
 
Paulo's problem sounds very similar to what is happening to me, except I only get the first frame of the clip.

I tried making new proxies from Clipfinder (Redline 247) and Redcine 247. No luck.


Dusty


Paulo Américo said:
I have been experimenting with the new RED FCS installer build 30.
For the first time, the proxies look identical in Quicktime, FCP and REDCINE-X (246). Good.

But I can't grade the proxies in Color anymore. It's not the looping bug.
It's some timecode problem. When I send a clip to the render queue in Color, the in timecode is OK but the out timecode is wrong. Just one frame of duration for the clips.
All of them. And if I render I only get one frame. And in the timeline it will only play one frame. So at least it's consistent this bug...

Mac OS X 10.6.4
Final Cut 7.0.2
Color 1.5.2
Click to expand...
 
Dustin Cross said:
Paulo's problem sounds very similar to what is happening to me, except I only get the first frame of the clip.

I tried making new proxies from Clipfinder (Redline 247) and Redcine 247. No luck.


Dusty
Click to expand...

Dustin,

In Clipfinder, conform using the XML, set the timecode of the metadata for every clips to say, edgecode, then reconform to generate a new XML, then bring it in Color. It might be worth trying.
 
I had a Color project that I worked in January and opened it up with v30 installed Color but I didn't see the still frame problem at all. So, it could work, just have to nail the proxy related problem I think.
 
So I open the FCP XML in Clipfinder. used CMD-E to check "use Edgecode", made new Proxies. Conformed the XML to _H and imported into Color. Still get the same problem.

This has something to do with FCP Installer v30. I sent six reels to Color with no problems. A couple hours later I installed FCP v30, resent reel 1 that was working and now every cut is the first frame of the clip and not the frame it should be for the edit.

The other five reels seem to be working fine, but I wont know for sure until I render them out of color and send back to FCP.

I can use the arrow key to frame through the clips in Color, but when I try to play it only shows the first frame.

Come on Red, give me some idea of what to do to fix this. Until I have this fixed, I don't trust Color is working.


Dusty
 
Dustin Cross said:
Color is also not seeing the footage as Red footage. No Red tab on the footage that shows frame 1 and won't play.


Dusty
Click to expand...

That, you certainly have to fix first. Without the RED plug-in for Color, there's no way to work R3D natively.
 
I want to ask Graeme,

You said the FLUT thing is working in Color even though there's no FLUT or shadow control.

How is R3D metadata process and the Color's image processing working together? Is it like;

1. R3D is processed natively in the RED tab, processed from 12-bit raw
2. Then going into Color's image processing at whatever mode you are in (say floating point) with the primary room, the secondary room and so on.

Are process 1 and 2 independently processed so if I were to push master gamma in the primary (or is it in the primary?), then lower the master lift to emulate the effect of the FLUT and the shadow control, would I get the data passed from R3D raw as much as possible?
 
Kaku,

I have the Color plugin installed. Color just does not recognize this footage as Red footage. I think there is a problem with the proxies, but I don't know how to fix it. I have tried making new proxies several different ways with no lock.

These proxies seem to work everywhere except Color. But other proxies work just fine in Color. For some reason every proxie in reel one of six reels is boken. The other five reels seem to work fine.

The only difference is I sent reel 2-6 to Color using the old software and sent reel one to color using FCP installer v30. Now every proxie in reel one is broken to Color and I can't fix it.

What could cause this?


Dusty
 
Dustin,

You can make a new empty Color project then browse and find where your R3D files are, then place it directly to the timeline. This would show no relation to the proxy and you are placing the R3D directly in the Color. Then if it doesn't work, there must be something wrong with your Color or Color plug-in.
 
Hey others,

Do you think it's worthwhile for Dustin to install the latest REDLINE?
 
Aside from Dustine's problem, I still see quite a difference in the color temperature from the proxies and native R3D processing.

34063_398755090833_581555833_4732910_541798_n.jpg


Left top is the proxy on FCP, right top is the RCX, left bottom is the RCX output in the FCP, right bottom is the RCX output in the QT7. Only proxy is inconsistent in the color temperature.
 
SO I just opened Color, browsed to some of the clips that won't work when I send the project from FCP or import the FCP XML, imported into Color and the files work correctly.

So something about FCP sent to Color is not working.

Let me play with that some more.


Dusty
 
Good, at least we know your Color with the plug-in is working.

Maybe you have inconsistency with the footage's time code settings.
Like I said, open them up in the Clipfinder, set the timecode to the edgecode, then send the proxies from the Clipfinder (M size) to FCP, next edit, finally send to Color.
 
You must log in or register to reply here.
Back
Top