[Jeff Coleman]

The venerable Mr. Jordan has provided the following answer to the question regarding how to turn RT Extreme Off.

“You turn off RTExtreme by going to the top left corner of the Timeline and setting the RT Menu to “Safe” and make sure the top setting says “Dynamic” and the bottom setting says “Full” or “All.”

This is how I’ve had my settings:

So I think RT Extreme has been off this whole time. While this has been an enlightening discussion, I don’t think it’s shed any light on this particular issue.

[Jeff Coleman]

Thanks for that clarification.

How do you turn RT Extreme off then (see previous post)?

[gary adcock] “you are moving from a 10bit PR image + an RGB graphic into an 8 bit transition (due to RTX processing) and then back to 10bit video content -“

I’m not. I’m just dissolving from a 10bit ProRes to a 10bit ProRes, perhaps at times dissolving from a 10bit ProRes to a 10bit ProRes(HQ). Color correction is applied to the clips.

Why does FCP and Compressor play that movie back with no gamma shifts, while QT Player 7 does show gamma shifts?

[Jeff Coleman]

Let me see if I have that point correct regarding RT Extreme in FCP.

If I create a 10bit timeline (ProRes, Uncompressed, etc.),
BUT I have RT Extreme turned on, then my movie output will be rendered as a 10bit movie from 8bit renders within it? The clip is 10bit, but that effect between them is rendered as 8bit. When QT Player sees a 10bit clip against an 8bit render the gamma jumps. When Compressor or FCP see it, they’re happy as clams. In other words, it doesn’t matter what the timeline codec is (in terms of bits), or what you’ve set the video processing tab to be (again in terms of bits) as long as RT Extreme was turned on when you rendered any effects. So RT Extreme trumps Video Processing settings?

Have I summarized accurately?

How do you turn off RT Extreme? My selections are “Safe RT” or “Unlimited RT”. I don’t seem to have an OFF selection.

[Jeff Coleman]

notice Fredy’s similar problem in this post:
https://forums.creativecow.net/thread/8/1094526

[Jeff Coleman]

Thank you.

I think this is a FCP ProRes bug of some sort. I didn’t think it happened in FCP 7.0.2 though.

See this recent post for very similar problem.
https://forums.creativecow.net/thread/8/1094366

The workaround seems to change the sequence codec prior to output to ProRes HQ.

[Jeff Coleman]

If you put that movie in Compressor and play it in the preview window, is it okay or does it do wacky stuff?

What if you reimport that movie back into FCP and play it, is it okay or wacky?

In QT 7 Player Preferences, is the box checked “Enable Final Cut Studio Color Compatibility”? If it is, uncheck it and tell me how it plays.

If you go back to your original sequence and change the sequence codec from ProRes to ProRes HQ and then output a movie, do you get the same results in QT X or is everything okay?

Interested to hear your results.

[Jeff Coleman]

Neil,
Thanks for the post.
Good to hear a confirmation.
I too haven’t noticed this in FCP 7.0.2.
Thanks again.

[Jeff Coleman]

I’m missing the relevance of RT Extreme in this case.

Original acquisition is a mix of ProResHQ and ProRes footage.

[Jeff Coleman]

ProRes is a 10bit codec and should yield better results, especially when processing, than an 8bit codec. The Uncompressed 10bit yields the highest quality, but takes a lot of headroom and storage space.

[Jeff Coleman]

Your FCP 10-bit Uncompressed movie file may be just fine, you just won’t be able to confirm that with your hardware.
So as David suggests, go ahead and send them what you can confirm is good (i.e., the Apple ProRes movie file exported from your timeline) IN ADDITION TO the 10-bit Uncompressed file they’ve requested.
Perhaps you can call the dub house and find out if your 10-bit file was good. (Even though as David indicated, it won’t be any better than the ProRes file)