Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro FCPX internal filters.

  • Craig Seeman

    September 11, 2011 at 6:27 pm

    Of course Apple reveals none of this.

    I think people will need to do some comparative studies.

    De-interlace alone has many methods such as:
    Duplication
    Interpolation
    Blending
    Edge Detection
    Motion Compensation

    Superficially there’s no way to know which or what combination of the above is at work in FCPX. One might have to test the same clip using the above methods and compare the results to what FCPX is doing.

    Interesting though is that FCPX offers fairly sophisticated frame rate conform.
    It offers:
    Floor
    Nearest Neighbor
    Frame Blending
    Optical Flow

    You can create a Deinterlace filter in Motion. I wonder why that isn’t included though unless FCPX is somehow already doing some kind of analysis resulting in something more that might include edge detection or motion compensation?

    Note Brendan Gibbons has done this.
    https://f1.creativecow.net/2662/fcp-x-effect-bg-you-into-lace-deinterlace-filter

  • Rafael Amador

    September 11, 2011 at 10:22 pm

    [Craig Seeman] “Of course Apple reveals none of this.”
    Why?
    Pro re-scaing filters are almost public domain.
    Avisynth loads similar filters than SHAKE (https://avisynth.org/mediawiki/Internal_filters).
    Rescaling has been one of the FCPs weak points.
    Would be great that FCPX had a set of filter for the different tasks on different kind of footage.
    Curiously MOTION has a downscaling filter also present in SHAKE (Lanczos). Comes in the “Image Units”, so is integrated in MacOsX.

    [Craig Seeman] “Interesting though is that FCPX offers fairly sophisticated frame rate conform.
    It offers:
    Floor
    Nearest Neighbor
    Frame Blending
    Optical Flow”

    That’s the very retiming engine of Compressor, expect by the “Nearest Neighbor”, option, which, BTW, is not very clear at all how it works.

    “Nearest Neighbor: Final Cut Pro rounds to the nearest integer during its calculation to match the clip’s frame rate to the project’s frame rate. Rendering is required”.
    I really don’t catch it.
    raffff

    http://www.nagavideo.com

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