[Mike J.]

Actually, use YALE FILM AND VIDEO for better rates and turnover. I’ve always ended up going to them over PRO8mm because of the PRO8 upsell this and thats.

https://www.yalefilmandvideo.com/

CHECK OUT: Two Guys Drinking At A Bar (the series) on Itunes and Youtube
https://www.twoguysdrinkingatabar.com
Itunes Subscribe: itpc://www.avmypodcast.com/file/kidgalaxy/95.xml

HERE’S EPISODE ONE:

[Mike J.]

By the way..you’re adding the deasaturate filter doesn’t work for me in any position of the render tree.

[Mike J.]

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

[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????

[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?

[Mike J.]

Yes… I have found that to be the case….

Unfortunately, they go to 3rd part QC BEFORE delivery and they scrutinize it. I mean… really scrutinize it.

Thanks, Bob for your help and wit.

[Mike J.]

What was your though Jeremy?

[Mike J.]

Same.

[Mike J.]

Actually… if I color correct based on using the scope itself…. the I have a really ugly image heavy in RED OR BLUE in the dark areas but not NORMAL on the LEader scope. And Final Cut Black color values become brigher with the color in the WHOLE image not just the black. That’s it flaw.

So it does appear something is weird. The SDI is run through it and coming back to HD monitor normal. But honestly, I can’t color correct it back into safe at all unless I ignore the image and use the scope only…. Then the image looks hideous.

It’s like a phasing issue type thing. I’ve done all the dust blowing, preference trashing, reload the driver what nots… it appears to be the scope somehow.

Thanks Bob…

[Mike J.]

Bob,

Everything is reading out of gamut . Even with the saturation all the way down. Leader thinks there may be a problem with it. Composit gamut is not out though during this error..just gamut. The point is, not matter what I try short of making things black and white, gamut error is always on…unless I convert the YUV clip to RGB and back (output a quicktime and reimporting basically)

Basically, just trying to distinguish between over 100 on the RGB parade and maxing out the color in the whites and blacks using the error warning. Even the Broadcast Safe in FINAL CUT doesn’t remove the error either.

Does that make sense?

Forgive my ignorance… I know you excel in this area.