Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy synchronizing formats for canon xlh1 and panasonic hvx200

  • synchronizing formats for canon xlh1 and panasonic hvx200

    Posted by Paul Typaldos on November 29, 2007 at 7:22 pm

    we are preparing to edit a trailer. there were two cameras used. the canon xlh1 and the panasonic hvx200. the settings for the cameras were as follows:

    canon: 720 x 480 @ 24 fps
    panasonic (a): 1280 x 1080 @ 29.97 fps
    panasonic (b): 960 x 720 @ 23.98 fps

    the canon and the panasonic (a) were the principal cameras and so most of the footage is in that format. the footage for the canon was captured via dv/dvcpro-ntsc and the resulting frame rate is 29.97. the panasonic (a) compressor is the dvcpro had 1080i60. the panasonic (b) compressor is the dvcpro hd 720p60.

    the question(s) i have are as follows:

    1. is it better to match the canon frame rate to the panasonic frame rate (29.97) or match the panasonic to the canon (24 fps)? what are the possible benefits/drawbacks to up or down converting?

    2. if i did want to match the canon to the panasonic, would i have to re-capture the canon material again? if so, which compressor should i use?

    3. if i want to match the panasonic to the canon, what’s the best way to do that? during the shoot, we dumped the p2 card to our external hard drive, but i’m not too familiar with how to change the import P2 settings. i.e. in the p2 window, there are no options for changing compressors, frame rates, etc.

    4. is there a way to verify the original format of the panasonic material? the shooter INSISTS that he shot at 24 fps, but as i mentioned, in fcp, the clips indicate that they are 29.97 fps.

    hopefully this makes sense. i’m a bit new to these formats, so i’d appreciate any and all insight.

    thanks.

    paul

    Paul Typaldos replied 18 years, 9 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