Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Aspect Ratio on Exported MOV

  • Aspect Ratio on Exported MOV

    Posted by Tony Sarafoski on February 18, 2010 at 9:45 pm

    I’m working on a 720×576 Anamorphic timeline

    Image Hosted by ImageShack.us

    And am exporting my final as a ProRes422 file.

    When I try opening the exported file in Quicktime, it shows it as 4×3 rather than 16×9

    Image Hosted by ImageShack.us

    Have I missed something in the settings?

    Tony Sarafoski replied 16 years, 3 months ago 2 Members · 6 Replies
  • 6 Replies
  • Michael Gissing

    February 18, 2010 at 10:02 pm

    I can see a few things. Firstly you have PAL pixels but your frame rate is set to 29.97?? It should be 25fps for PAL codecs.

    Secondly quicktime isn’t displaying 16:9 correctly with anamorphic flagged files. That is a quicktime setting. However, if this is intended for the web, you final file should be made with square pixel settings not anamorphic. The final file should be 1024 x 576. This will correctly display on all media players as 16:9 regardless of how people have setup their quicktime or other players.

  • Tony Sarafoski

    February 18, 2010 at 10:42 pm

    [Michael Gissing] “I can see a few things. Firstly you have PAL pixels but your frame rate is set to 29.97?? It should be 25fps for PAL codecs.”

    Michael, I originally started cutting this project on a 720×576 25fps timeline, however I struck some technical issues with the original rushes, being 1920×1080 30P from a Canon 5D Mark II. I son realised the jerkiness and changed my sequence setting to 29.97 to mach the 5D frame rate. In the process I forgot to change the frame size too… ooPPss..!!! Anyway not to worry, this edit was only intended for the web for now so I guess frame size and frame rate isn’t that important.

    [Michael Gissing] “Secondly quicktime isn’t displaying 16:9 correctly with anamorphic flagged files. That is a quicktime setting. However, if this is intended for the web, you final file should be made with square pixel settings not anamorphic. The final file should be 1024 x 576. This will correctly display on all media players as 16:9 regardless of how people have setup their quicktime or other players.

    So do I just set square pixel in my sequence setting?

  • Michael Gissing

    February 18, 2010 at 10:58 pm

    If the material is all 1920 x 1080 then use that as the timeline as it is square pixel 16:9. Don’t use anamorphic SD timelines with HD material.

    Copy >paste the timeline into a new sequence with the easy setup for ProRes 422, 1920 x 1080 29.97.

  • Tony Sarafoski

    February 18, 2010 at 11:10 pm

    Michael,

    I actually down converted the 19020×1080 H.264 rushes to 720×576 ProRes 422. The reason for this was that my machine was too slow in handle a 1920×1080 ProRes 422 workflow, so I thought I’d just downconvert them instead.

    To understand you previous post, do I set my timeline sequence settings to:

    FRAME RATE: CSSIR 601 PAL Sq. (4:3)
    PIXCEL ASPECT RATIO: Square

    Then export FILE> EXPORT> QUICKTIME MOVE or FILE> EXPORT> USING QUICKTIME CONVERSION?

  • Michael Gissing

    February 19, 2010 at 12:19 am

    [Tony Sarafoski] “do I set my timeline sequence settings to:

    FRAME RATE: CSSIR 601 PAL Sq. (4:3)
    PIXCEL ASPECT RATIO: Square”

    No you need to leave the sequence anamorphic to match the footage. Otherwise everything will be stretched.

    To make the final file, you can use either quicktime conversion or Compressor. Most people here recommend Compressor. Either way, both offer the capability of making your final file in a square pixel 16:9 ratio (ie 1024 x 576 or multiples thereof).

  • Tony Sarafoski

    February 19, 2010 at 2:48 am

    Sorry Michael, I’m not sure I’ve understanding this correctly. The only setting I need to change is the Pixel Aspect Ratio?

    Image Hosted by ImageShack.us

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