Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy De-interlacing Issues

  • David Roth weiss

    April 12, 2011 at 7:49 pm

    Call me Amber, you can find my phone number on my website. I’ve seen and fixed this issue before.

    David

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.

  • David Roth weiss

    April 12, 2011 at 7:55 pm

    Unfortunately Vimeo has blocked your embed of the video file.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.

  • Rafael Amador

    April 12, 2011 at 9:01 pm

    [Amber Navarrete] “The fps is 29.97, the codec h264 and the field dominance being lower.”
    This would be the first case of HD Lower-first I see.
    All the HD standard are Upper.
    Double check this and try checking the stuff as Upper.
    rafael

    http://www.nagavideo.com

  • David Roth weiss

    April 12, 2011 at 9:06 pm

    [Rafael Amador] “All the HD standard are Upper.

    Echo!!! Echoooo!!!!! Echoooooooo!!!!!!!!

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.

  • Amber Navarrete

    April 12, 2011 at 9:24 pm

    David – you are a genius! The process in compressor fixed the issue. Thanks again for your help – people like like you are priceless. Keep up the good work.

    Thx,

    Amber

  • David Roth weiss

    April 12, 2011 at 11:03 pm

    [Amber Navarrete] “David – you are a genius! The process in compressor fixed the issue. Thanks again for your help – people like like you are priceless. Keep up the good work.”

    Even a broken clock is right twice a day Amber, but thanks for the feedback, it’s always good to hear when things work.

    For the record, Amber’s problem stemmed from h.264 video without the proper field designation. The issue happens because certain cameras (Canon and Sony) that record interlaced HD with upper fields first, fail to write an entry in metadata line #21 on the files. The missing entry is thus misinterpreted in all QT enabled apps as progressive footage.

    The solution is to use Compressor to transcode the h.264 files to ProRes and force to upper field dominant by turning Frame Controls on, and setting fields to upper from the default, which is normally set at “same as source.”

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.

  • Alan Okey

    April 13, 2011 at 3:12 pm

    The part that I don’t understand is that Amber said the original footage was 1280×720 which implies that it should be progressive (720p). It was then transcoded to 1280×720 ProRes. Was that a typo, and was this indeed originally 1080i footage? Or were fields incorrectly introduced during the Compressor transcode to produce a 1280×720 ProRes file with interlacing? I didn’t even know that was even possible… Please advise, thanks.

  • Amber Navarrete

    April 13, 2011 at 3:45 pm

    Alan, I think you are right. 1280×720 should always be progressive. The clip says it is progressive but looks interlaced when there is a lot of action – frustrating. I thought I had solved the issue using a short clip to test. I converted all my clips last night and when I got in today I realized the ugly (interlace looking) lines are still there. Sucky. I think I’m screwed as I’ve tried about every combo possible in compressor.

    Any other suggestions are welcomed but I think it is what it is.

    – Amber

  • David Roth weiss

    April 13, 2011 at 4:15 pm

    [Alan Okey] “The part that I don’t understand is that Amber said the original footage was 1280×720 which implies that it should be progressive (720p).”

    Good question Alan. I suspect that camera is one of those that shoots (720Psf) i.e. progressive segmented frames that are in reality interlaced video, but with two identical fields. And, that is misinterpreted both by machines and their human operators.

    Does this make sense?

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.

  • Rafael Amador

    April 13, 2011 at 9:53 pm

    [David Roth Weiss] “I suspect that camera is one of those that shoots (720Psf) i.e. progressive segmented frames”
    Psf its doesn’t exist in 1280×720.
    rafael

    http://www.nagavideo.com

Page 2 of 2

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