-
Render in high-precision YUV” problems with CC 3-way
I’ve always done my D1 projects in either 8-bit or 10-bit Uncompressed, but this time I decided to try out ProRes HQ to see what it’s made of. I captured with “AJA Kona LH: 525 29.97 Apple ProRes 422 (HQ).” I have the sequence set to render all YUV in high-precision YUV, and two problems have come up:
1. Using Color Corrector (not 3-way) to pull colors back into legal levels works fine, until I render. After rendering, the effected area (“keyed” area) is changed to the complimentary color that can only be brought into view on my vectorscope by cutting the gain on the scope to around 60%. Render in 8-bit (or RGB) does not do this.
2. Using CC 3-way (on top of another CC 3-way), the image is fine until I render. It then changes back to almost how the pre-filtered image looked. Render in 8-bit (or RGB) does not do this.
Anybody know what’s going on?
Thanks,
TimMac Pro 8-core
Mac OS X (10.5.8)
10 GB
FCP 6.0.6
Quicktime 7.6.2
AJA Kona LHe
Ciprico MV4210 5TB -
10 Replies
-
I know that rendering in 32-bit was problematic for me as well.
why not render it in 10-bit? that should work perfectly fine.
And why not use the 3-way cc to adjust your luma?
-
[Chris Borjis] “why not render it in 10-bit? that should work perfectly fine.”
Are you talking about “Render 10-bit material in high precision YUV?” That exhibits the same problem. Any high-precision YUV renders come out bad.
[Chris Borjis] “And why not use the 3-way cc to adjust your luma?”
I do. I was using the old CC to legalize the color on some clips (I guess I was thinking it’d be easier on the computer?). After the render problems popped up, I replaced it with the CC 3-way, but got the same results.
-
oh, thats odd. not sure why thats a problem.
32-bit has never worked for me but 10-bit always works.
-
[Chris Borjis] “32-bit has never worked for me but 10-bit always works.”
Both “10-bit” and “All” settings render in 32-bit float. Curious you’ve had different outcomes. Perhaps it’s codec-related?
I just copied the entire sequence into a 10-bit sequence with 32-bit render settings and got the same problem (#1) with the old CC. Using 2 3-way CCs stacked did not exhibit problem #2 and worked fine. And now that I started really digging into it, it’s getting more and more weird.
I’m not going to post anymore while this web is still untangling. For example: I’m getting an orange bar on one clip with only one 3-way CC and one 3-way CC w/limit. Yet, I have another clip with the same (1 3-way, 1 w/limit), add a motion effect (P&S this 16:9 clip into 4:3), speed it up, and stack 3 more 3-way CCs w/limit on it before it turns orange–both D1 ProRes HQ in D1 ProRes HQ sequence!
I will just render in 8-bit and call it a day.
-
Hi Tim,
I don’t understand all that messing around with the render setting.
You are using 10b stuff in a 10 sequence, by default should be processed at 32b (10b, High precision) .
You can not render in 8b YUV or RGB, neither use filters like the CC (no 3W) that renders in 8b only.
If you are monitoring in a computer screen, you are lost because you have only 8b.
rafael -
[Rafael Amador] “I don’t understand all that messing around with the render setting.
You are using 10b stuff in a 10 sequence, by default should be processed at 32b (10b, High precision) .”It does not render correctly when set to render 10-bit in high-precision with 2 3-way CCs stacked on D1 ProRes HQ.
“You can not render in 8b YUV or RGB, neither use filters like the CC (no 3W) that renders in 8b only.”
I’m not sure if it actually renders it in 8-bit or not, but there are no problems with it set to 8-bit.
“If you are monitoring in a computer screen, you are lost because you have only 8b.”
Broadcast monitor with scopes.
-
Hi tim,
By any chance do you have the monitoring set to 8b instead of 10B?
Really I can not think of other reason.
I haven’t experienced that.
rafael -
[Rafael Amador] “By any chance do you have the monitoring set to 8b instead of 10B?”
It’s 10-bit. Plus, the problem is reflected in the Canvas and video out. I’m puzzled. 8-bit works, and looks okay, so I’m going with that. I may just go back to using Uncompressed D1 instead. Thanks for your thoughts. And it’s good to know the old CC is only 8-bit!
-
If you don’t have the solution yet, go to the sequense setting and change the video processing to ” always render in RGB” and your problem is gone
-
Reply to this Discussion! Login or Sign Up