Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Adobe Premiere Pro › What are the best sequence settings to use for HD footage coming from a Sony FS7?

  • What are the best sequence settings to use for HD footage coming from a Sony FS7?

    Posted by Adam Leonard on July 11, 2016 at 7:15 pm

    So I’m in the early stages of switching from Avid 6 to Adobe Premiere Pro CC, and while I’ve managed to find a set of settings that work, I’m now starting to wonder if it’s the best one to use for this particular camera (Sony FS7). I just talked to the videographer, and he shoots in 1080i. The things I’m making are for HD broadcast TV in the US. A typical “Properties” menu of our footage looks like:

    Type: MXF
    File Size: 147.3 MB
    Image Size: 1920 x 1080
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz – 24 bit – 8 channels
    Project Audio Format: 48000 Hz – 32 bit floating point – 8 channels
    Total Duration: 00;00;20;10
    Pixel Aspect Ratio: 1.0 (1.0)

    MXF File details:
    Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)
    File generated by: Sony, Mem
    MPEG-2 422 Long-GOP

    Any suggestions?

    Annie Eastman replied 4 years, 4 months ago 3 Members · 3 Replies
  • 3 Replies
  • Ann Bens

    July 11, 2016 at 10:48 pm

    Right click on a clip in the Project Panel and select New Sequence from Clip. This will give you a matching sequence for your footage.

    ———————————————–
    Adobe Certified Expert Premiere Pro CS6/CC
    Adobe Community Professional

  • Annie Eastman

    May 25, 2022 at 4:36 pm

    When I right click on a click it creates a sequence that I then have to size down the clip in, plus it’s too rectangular. What gives? Also, people reference using the XAVC preset, but I don’t see that in my list of presets (I’m in Premiere V22.1)

  • Annie Eastman

    May 25, 2022 at 4:44 pm

    Nevermind! ! I had the “select zoom level” set to 100% not “fit” and that was causing the problem.

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