Skip navigation

Format mismatches: 1080pA clips into FCP timeline

611 Views 10 Replies Latest reply: Nov 19, 2012 7:53 PM by zapmeister RSS
zapmeister Calculating status...
Currently Being Moderated
Nov 9, 2012 8:22 AM

For my HVX, in FCP, I'm using the suggested preset for 1080 24pA which cites a compressor setting of DVCPRO HD 1080p30. When I try to drag the clip into the timeline it says there is a mismatch--that the clip does not match the preset and I have the option to change the sequence setting to match the clip settings or not. FCP advises that one change the sequence to match the clip property, and so if I opt to change that sequence setting, when I look at the sequence specs the one thing that has changed is that now the sequence setting is DVCPRO HD 1080i60.  That is, it appears from this that despite having checked the box in Raylight to remove the 2:3:3:2 pulldown, this has failed and clip is still interlaced over 60. And indeed when one looks at the clip properties the clip is identified as DVCPRO HD 1080i60.

 

What am I doing wrong and what do I do to get the pulldown properly removed and make my 1080pA shot footage progressive?  Or is there something fundamental I'm not correctly understanding?

Mac Pro, Mac OS X (10.6.8), FC Studio 3
  • Shane Ross Level 8 Level 8 (41,655 points)

    Does RAYLIGHT remove pulldown?

     

    The correct format for 1080pA is 1080i60...because that is how it was shot.  1080i 29.97 with pulldown.  If you want to remove pulldown, use Log and Transfer to import the footage, and in the L&T preferences, make sure the option to REMOVE PULLDOWN is checked.

     

    Raylight allows you to edit the footage natively...without converting.  So how can it remove the pulldown when it doesn't modify the footage in any way?  It just allows FCP to see it as it is...allows FCP to read the MXF files.

  • Shane Ross Level 8 Level 8 (41,655 points)

    >Whether I use L&T or Raylight, I get a clip with the same properties except the compressor setting being DVCPRO HD 1080i60. I assume that FCP identifies the mismatch because of the difference of that parameter.

     

    The COMPRESSOR doesn't matter in this case.  It should be 1080i...that's the original format you shot.  1080i 24pA.  It's pA in a 1080i stream.  So the format is 1080i.  Your RATE should be 23.98.  If your rate is 23.98, and format is 1080i60...you are fine.  Things are normal. 

     

    >3. Though the image of the 1080 footage is larger, that 1080 footage does not look as clean 720 pN (24p) footage shot with that same camera.

     

    Because the sensor on the HVX is 960x540...half the resolution of 1080.  It uses Pixel Shifting to make it the size it is.  720p on those cameras is cleaner because the blowup isn't as extreme.  I always shoot 720p 24PN with those cameras.  First off, it takes up a lot less space on the cards so I have longer shooting times.  Second, the image quality is better.  Third, I can output 1080p or 1080i fine with the Kona 3 and it upscales VERY well, and makes it look like it was shot 1080 to begin with. 

  • Shane Ross Level 8 Level 8 (41,655 points)
    Currently Being Moderated
    Nov 18, 2012 1:27 PM (in response to zapmeister)

    Safer to have FCP set the sequence up to match the footage.

  • Studio X Level 7 Level 7 (26,835 points)
    Currently Being Moderated
    Nov 19, 2012 6:01 PM (in response to zapmeister)

    Why did you give yourself the solved star and not Shane who answered the question?

     

    x

  • Shane Ross Level 8 Level 8 (41,655 points)
    Currently Being Moderated
    Nov 19, 2012 6:04 PM (in response to Studio X)

    Pssshhh...like I need it. 

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.