FCP output varies btw “pause” and “play”

[Jeremy Garchow]

not only do they recognize it, they desinged it. It’s so that when you are working with FCP wihtout a monitor, the canvas will approximate what the video will look like on tv. I have a better idea, how about just hooking up FCP to a tv and then we won’t have to deal with all the crazy gamma slammas…

It’s nuts and drives us all crazy, ok, maybe just me crazy.

[stu aull] “or at least provide a menu-selectable output option based on the gamma settings of the has cpu monitor??”

Well, that’s going to cost you…hopefully the rumored FCP Extreme or whatever will take this into account, but it’s going to be a $10,000 option along with the fastest baddest computer…so $15,000 for proper gamma handling, as long as FCP Extreme handles gamma correctly. I’m so sick of the, “hey, this software is only $1,000!” argument. It’s over and time to put the Pro in Final Cut Pro…or design pro codecs…or something…know what I mean?

Jeremy

[Stu Aull]

HA! 😀
for $10K I’ll figure it out myself – maybe while on the trip to the Caribbean with the $$ I save! “Extreme”? Yikes! $10K IS certainly that! Kind of a step backwards after basically GIVING away Shake…

Feelin’ the Pain here-
Stu Aull
Alaska

[Paul Escandon]

Hi everyone

I just wanted to throw in my 2 cents. I found this thread because I was having a similar problem to the original poster’s first problem. I just hooked up a set of high-def hardware scopes to my video output and that’s when I noticed that the parked image was noticably darker in some areas and it was very noticable when reading the hardware vectorscope (FCP’s vectorscope didn’t pick up on this). I’m using 5.1.2, with a G5 and Kona 2 setup..

And in my situation, TURNING OFF the excess range check solved the problem, as one poster has suggested.

Just wanted to let people know that that worked for me.

[Johnny Ung]

Hello,
We are having the same problem. We have a kona 3 card. Everytime we pause in FCP it gets darker. Then when we play it lightens back to normal.

The range check has always been turned off. I can play old files just fine, and pause them with no darkening.

Can this occur from rendering? or is there some other setting?

thanks,
johnny

[Jeremy Garchow]

What codec are you captured to? And what codec are your ‘old files’?

[Johnny Ung]

Both animation files. Editor says it nothing that we have ditched.

[Jeremy Garchow]

[johnny ung] “Editor says it nothing that we have ditched.”

Huh?

Animation files are RGB. If you render those after you put them in the timeline, you will see that FCP can convert them to YUV quite nicely.

Jeremy

[Johnny Ung]

These are not files that are digitized from tapes.
Files are animation files at full resolution.
We have figured out how to drop the files on to a time line with out rendering to get real time playback.
The issue is: some files have the drop in brightness when you push pause or stop. the brightness drops on both the video playback monitor and viewer in the program. The codec resolution, data rate, doesnt change from file to file, just that some files work and some don’t.

[Johnny Ung]

One more thing. We think it may be related to the workstation. One workstation can render out perfect, the other renders out the files with errors. Could it be that the after effects cs3 they are using, which are different versions be the problem. or quicktimes, which is also different versions, be the problem. The one that works has quicktimes 7.3 and the one that has the problems is quicktimes 7.4.

thanks, hope i havent confused you.

[Jeremy Garchow]

[johnny ung] “These are not files that are digitized from tapes. “

Obviously.

[johnny ung] “We have figured out how to drop the files on to a time line with out rendering to get real time playback. “

If you are using the Animation codec as a sequence codec, make sure you choose to render in RGB from FCP.