Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP Capture Issue

  • FCP Capture Issue

    Posted by Martin Tupperheim on October 7, 2008 at 4:05 am

    Hey all,

    I am new to FCP and am working on some recent projects so please be kind.

    I am running into issues where I capture from an AJA IO from a UVW-1800 and a Kona LHe from a Panasonic AJ-SD93. REGARDLESS of what I capture I am finding that I am getting blockiness/artifacting whenever I apply the de-interlace filter.

    Now I should mention that sometimes I capture Beta SP, DVCPro 50, 24p and 60i. I know that about 24p being progressive and I should incorporate the pulldown info from Cinema Tools. I do that.

    The problem I am running into is that regardless of what I am capturing and working with I get this blockiness/artifacting around the faces, heads, shoulders of people. Obviously I don’t apply the de-interlace filter on progressive footage but when I apply it on ALL other footage I get this. I have my settings within FCP (depending on what I capture) typically with fields set to none within the sequence. When the footage is captured it comes is as lower field first. I then de-interlace and get this artfacting.

    My question is… Do I need to set the sequence to “None” when it comes to fields or do I set it to lower field first? Also, do I make sure the footage is set to lower field first? What is the right combination for footage that needs de-interlaced? I will work on the problems I am having with progressive footage at a later date as I am getting this artifacting regardless of the footage – that’s what makes me believe it is a capture/sequence issue.

    I hope I am being clear and any help would be greatly appreciated.

    Thanks,
    MT

    Follow your dreams. You can achieve your goals; I’m living proof… BEEFCAKE!

    Martin Tupperheim replied 17 years, 7 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

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