Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Pro Res and odd Frame Rates

  • Pro Res and odd Frame Rates

    Posted by Richard Boghosian on February 23, 2010 at 6:22 pm

    Digitizing with the Kona LHe: from a Panny 1200 deck thru the Kona card as DVCPROHD 1080i60 the resulting image file is “1280×1080 @ 29.97” as reported in FCP 6.06 and when the file info is viewed in QT player. Same footage digitized in ProRes is reported in FCP as 1920 x 1080 @ 29.97, BUT in QT player it is reported as 29.73 fps or sometimes 29.71 fps. When I shared this footage with an Edius editor, he reported this strange frame rate to me (and noted a lack of audio sync). We resorted to DVCPROHD codec and all was fine. But what’s up with the weird frame rates from a ProRes injest?

    Richard Boghosian
    Bogh AV Productions

    FCP 6.03 Intel 2.8 8 Core Apple X-Raid and Atto SCSI UL5D Kona LHe

    John Pale replied 16 years, 2 months ago 2 Members · 3 Replies
  • 3 Replies
  • John Pale

    February 23, 2010 at 7:37 pm

    Open the files in Cinema Tools and use the conform function. Conform the files to the correct frame rate (even if Cinema Tools reports the correct frame rate initially). The change is instantaneous and there is no transcoding or quality loss. You can batch conform or do individual files. This will fix any bad frame rate metadata in Quicktime.

  • Richard Boghosian

    February 23, 2010 at 9:08 pm

    Thank you John, that was the fix. But why is ProRes writing files like this?

    Richard Boghosian
    Bogh AV Productions

    FCP 6.06 Intel 2.8 8 Core Kona LHe Apple X-Raid and G-Tech G Speed es RAID

  • John Pale

    February 23, 2010 at 9:22 pm

    [Richard Boghosian] “Thank you John, that was the fix. But why is ProRes writing files like this? “

    That is a question for Apple. Use the feedback link in FCP to report it as a bug.

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