10bit renders are adding RED COLOR?

[Aaron Neitz]

What are you doing to the footage that requires render? Can you replicate the process using SMTP bars? What are your render settings (all YUV render w/ high precision?)

I know that if I have footage and do a 3 Way CC – when I render it always shifts a little from what the RT engine pumped out.

[Mike J.]

Right, 3-way color corrector is added. Render. Boom pops up illegal on the scope when it was prevously legal.

It does it in both 10bit and YUV BEST RENDERING. 8bit it works fine. The footage can be 8bit or 10bit or HD..whatever..still does it when rendering 10bit.

It seems to be APPLE/Final Cut Pro/QUicktime issue at this point.

Anyone with a good scope. Could someone else try this out in 10bit renders to see if it dupicates?

[Steve Covello]

Had this same problem. Switch your sequence to 8-bit, keep its processing to 8-bit YUV in the Sequence settings. FCP promotes everything to 4:4:4 before rendering, so it’s not too terrible to go 8-bit unless you have serious luma values getting clipped.

Here is my original post on the subject referring to 5.1.2.

https://forums.creativecow.net/readpost/8/917354?univpostid=917269&pview=t

I have found that even with Color Finesse, the correction does not stick either from CF’s Preview mode to regular Canvas view — extra saturation or something. Very frustrating. I am running 5.1.4, 10.4.8.

Anyone have a solution for this?

steve covello
double wide post

[Jeremy Garchow]

I have had some other 10 bit problems and the trick I learned form AJA was to put a desaturate filter on the footage (from the image control filter set) with a value of 0. It should render correctly then. Is your footage scaled by any chance?

Jeremy

[Aaron Neitz]

Anyhing I render in 10bit is going to pop. HD and SD.

Lets all hope Apple solves this nonsense for FCP 6. Things like this are what cause me daily grief using FCP as an online finishing station.

[Mike J.]

See I’ve tried other things to make it render correctly…but you’re just saying add the desaturate filter and basically…don’t desaturate – leave at zero – and the processing doesn’t do that bump.

I’ve been using Colorista..it clips everything into Broadcast Safe…but render it in 10 bit and it’s back up there again. I will try the DESATURATE filter Before Colorista and after in the filter list and see.

Not a solution…a quick fix…. APPLE where are you????

[Jeremy Garchow]

[mike] “Not a solution…a quick fix”

Definitely not a solution. They way I understood it, is that the desaturate filter will force another render and correct the problem. It was a stop gap to my 10 bit woes.

What version of QT are you on?

[Mike J.]

7.1.3 is what is on that system…. I was waiting to up it until project finished….

[Jeremy Garchow]

Yeah, that’s where I am too. Too nervous to go to 7.1.5 and see if it’s fixed.

[Joe Murray]

For 10 bit finishing, I’ve all but given up on Final Cut Pro as a color correction solution, or for anything that requires renders before output in 10 bit sequences, because of ongoing problems with 10 bit renders in FCP. I export these types of projects using Automatic Duck, use After Effects or Combustion for color correction and effects, render as 10 bit and just use FCP for realtime playback. Fortunately the only projects I finish in 10 bit are commercials that originate on 35mm film; 8 bit is sufficient for everything else.

Let’s hope this is fixed soon, but it’s been a problem for quite a while so I’m not counting on it.

Joe Murray