Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Panasonic Cameras Camera/FCP settings

  • Camera/FCP settings

    Posted by Gerret Warner on September 13, 2006 at 10:26 pm

    Thanks to everyone who has shared their knowledge about the HVX200 and P2 workflow. I wish I could figure out some of the following questions from the help files of FCP and the HVX200 manual, but it’s not readily apparent how to proceed.

    Here’s another question before I start an especially important project using our new camera.

    We want to shoot in DVPro50/24 and some of what we shoot will be undercranked–not a lot–but some of it. I’ve tried tests in which I set the camera to DVPro50/24PA and that seemed less stuttery than 24 or 24N, but I’m not sure it’s the best choice. Then when I import, should I leave the remove pulldown option checked?

    Also, the camera gives a “squeeze” or or “letterbox” option. I want a true 16 X 9 finished product. Which is the better setting?

    Lastly (for now), what setting should I use for FCP so that my DVPro 50 footage won’t require rendering in the timeline.

    Many thanks for any advice.

    GPW

    Gerret Warner replied 19 years, 7 months ago 2 Members · 2 Replies
  • 2 Replies
  • Noah Kadner

    September 14, 2006 at 2:49 am

    Use the DVCPRO50 Easy Setups in FCP. You cannot undercrank in DVCPRO50- so shoot 720pN for those shots and downconvert. Squeeze is true 16:9. If you want to cut at 23.98- leave the pulldown option checked. Again stick with the Easy Setups and you will not have to render.

    Noah

  • Gerret Warner

    September 16, 2006 at 11:56 am

    I read in another thread that Firestore records 24p (non-native) and that the resulting files lose sync when importing into FCP? Is there any way around that problem. Sounds like a serious limitation, and makes me not want to use my new FS-100 with the maiden voyage of our HVX200.

    GPW

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