-
FCP output varies btw “pause” and “play”
FCP 5.0.4/ Tiger 10.4.8/G5 PPC Tower/Decklink SP Component I/O
This has always, thru several OS and FCP versions, done this:
1) any image on the CANVAS and OUTPUT (ie video monitor/Waveform scope)
in “pause” (ie parked on Timeline) image is about -5 DIV of luminance LOWER than when you hit “play”.
It is a mid-range (30-80 DIV on waveform) shift, the peaks (100) don’t change…2) CANVAS display always much darker than actual output to video/recorder/monitor.
I have attempted to boost cpu screen brightness to compensate, but whole screen needs to be cranked WAY up to start matching actual video output. Doesn’t seem right. Vid monitors/scope correctly set for levels with color bars generated THRU FCP output. Been an issue with several cpu monitors.Both issues make color correction, etc a real pain since you can’t depend on the “parked” image to be an accurate guide of what final output will be, forcing me to render the clip to view at “proper” levels.
Thoughts?
Stu Aull -
21 Replies
-
I have seen this when my hard drives weren’t fast enough to play back the footage at full quality. I was using G-Raids, which worked fine for 8-bit uncompressed, but as soon as I went 10-bit, I saw this.
Getting a SATA Raid solved this. Where is your media stored?
Shane
Littlefrog Post
http://www.lfhd.net -
Hit control-z and turn off the excess luma range check.
Or if keyboard shortcuts don’t do it for you, go to View > Range Check > Off.
Jeremy
-
The scopes are much better since 5.1.2 I am on 5.1.4 and in the scopes are showing a much more accurate display and also are real time for SD. I only grade on an external monitor and refer to the canvas window only to see the excess luma tick.
-
Hi Stu,
I’ve got a similar issue when I work with the Sheer codec. When the video is in plays is much more lighter that when is stoped. I guess this can be because Sheer is a “Gamma independent codec” so it doesn’t change the gamma to be displayed. This have make me wander few times if was any bug but I made few test comparing some clips exported with Sheer and exported with the Apple codecs (8/19b Unc). When you play the Sheers in FC or QT they look lighter than the Apples, but when I brouth them to AE or shake, where I could compare the clips better than in FC, I couldn’t find any difference.
Cheers,
rafael -
Thanks for sharing the Pain Rafael 🙂
So I’m not the only one with this problem? Is this someting ALL FCP set-ups do and everyone just shrugs it off?
Stu Aull -
Quicktime makes HUGE assumptions on gamma and attempts to correct them upon play out.
Did you try turning off the range check yet????
Jeremy
-
Also, in another forum, Gary Adcock helpfully posted a link to an Apple article.
Read and wonder:
https://docs.info.apple.com/article.html?artnum=93794
Jeremy
-
Hi Jeremy-
thanks for the reply
Yes, as I reposted: Range Check has ALWAYS been OFF-
I will look at the Link you provided.
Would be curious to know why QT needs to make ANY gamma corrections, at least on uncompressed video. And it certainly the Gamma that is being “futzed” with here!!
regards
Stu Aull -
[stu aull] “Would be curious to know why QT needs to make ANY gamma corrections”
Like I said, read and wonder…
Sorry I didn’t see that range check was off…are you Michael G too?
-
Hi Jeremy-
Read the article – interesting! Since Apple seems to recognize this output “shift” between the Canvas and TV monitors, I am surprised they haven’t addressed it – or at least provide a menu-selectable output option based on the gamma settings of the has cpu monitor??OK – I’ll bite: who is Michael G??
😀
Stu Aull
Reply to this Discussion! Login or Sign Up