Creative Communities of the World Forums

The peer to peer support community for media production professionals.

  • Gary Adcock

    January 4, 2008 at 10:55 pm

    [C.R. Caillouet] “These problems were verified by decoding and evaluating the video from the files, not just looking at them on monitors. So the errors that Ben is talking about could be real processing errors and not just monitoring ones. “

    Agreed, CR.

    but also note that Ben discussed first that the Gamma was darker when output directly from the Video Apps, but not as bad as it was when he used compressor or some of the other tools that are designed for compression.

    In all honesty, as you know all to well, there are many apps that just cannot understand what to do with Quicktime, especially since QT often makes its own rules when working with Non Apple applications.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows
    Inside look at the IoHD

  • Arthur Dobbe

    January 5, 2008 at 12:20 pm

    I, too, have been trying to set my monitors’ gamma to 2.2 lately. I agree that QT player uses ColorSync, no problems there.

    However as far as I could find (by trying and searching the manual), there is no way to prevent FCP from “correcting” the gamma. This is what I found in the FCP 6 manual:

    Whenever you watch your video on a computer display (such as video displayed in the Canvas, the Viewer, or via Digital Cinema Desktop Preview), Final Cut Pro applies gamma correction to the video to more closely approximate the way it would appear on a video monitor.
    Note: Gamma correction is not applied to external video outputs such as DV or third-party interfaces because this correction is inherently applied by external video monitors.

    For still images and RGB video codecs there is an option to set the source gamma, but (quote) ‘Y

Page 3 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy