-
Bug? “Range check” creates 10 unit dif between play and parked image
Has anyone noticed this?
On our “on-line” systems, if you are using “range check”, then the luminance level is approximately 10 units HIGHER when playing compared to when parked in still mode.
Since coloring is done on a still frame, this causes your levels to be almost 10-12 points TOO HIGH. We had a couple of masters kicked back from the network because of this. When I first saw it, I knew our on-line teams couldn’t be THAT far off. After some experimenting we discovered that enabling “range check” was totally altering the reading on our external scopes. While we primarily work in 8 bit uncompressed timeline, but we’ve observed the same issue using a DVCPRO or IMX timeline.Solution is to NOT use range check.
I’d be curious to hear if anyone else has encountered this.
Mark
Latest software with BM cards.
-
3 Replies
-
Hi Mark
I’ve seen this for quite a while. Don’t know if it’s just related to Blackmagic or not. I have both Kona and Blackmagic cards at work, but I’m not at work today, so I can’t check the Kona. I seem to recall that I used to see this problem on my old Cinewave system, so I think this bug has been around awhile. My solution as well was to turn off range check. I used to colour correct with external scopes and then add a broadcast safe filter for good measure (I say used to, because I have recently switched to Final Touch for colour correction)
Cheers
John Christie
-
john,
We too are starting to use Final Touch, but there’s still some projects in the pipeline that we’re using the good ole FCP 3 way.
Today I dug a little deeper into this issue and discovered that rendering seemed to make a difference too. Here’s what happens. Zero out your levels using the 3 way. Everything’s fine except now you need to render. Render. Whoops! Everything is now at least 10 points over 100. Strangely, the black levels stay put. Only the high end seems to get extended. Our on-line editors have been throwing a broadcast safe filter on it and calling it a day, but I want to know why this is happening. Any info/comments/ suggestions would be appreciated. Thanks.
mark Raudonis
-
Hi,
I’m still experiencing this with FCP 6.0.5 and MacOS 10.5.6 on a Mac Pro with DVCProHD footage.
Nasty.
– Graham
Reply to this Discussion! Login or Sign Up