Skip navigation

PsF clip "converted" to Progressive in Inspector needs rendering in Progressive Project?

2010 Views 31 Replies Latest reply: Apr 30, 2012 2:13 PM by Ian R. Brown RSS
1 2 3 Previous Next
Ian R. Brown Level 6 Level 6 (17,505 points)
Currently Being Moderated
Apr 8, 2012 3:54 AM

My Panasonic SD800, likeall AVCHD cams, shoots  Progressive as PsF.


FCP X incorrectly recognises it as 1080i  so I opened the Settings View and selectedField Dominance Override: Progressive.


The Basic and Extended Views still had it listed as 1080i until I quit and rlaunched FCP X.


I then created a Progressive project and put the clip in whereupon a brown rendering line appeared above and took over twice the time of the clip to render. (A new Mac would do it in less time than the length of the clip).


The same thing occurred when I created a new project and set its Video Properties to be based on the first video clip.


So why does a progressive clip need rendering when placed in a progressive project? (I am using the clip natively as AVCHD/H.264)


Incidentally, I am no more impressed with progressive than I was 4 years ago.


I cannot see any quality benefits but do notice an irritating jitter on motion.


Probably if I stuck to making videos of stills it would be satifactory but video cameras are made for filming movement!

iMac, Mac OS X (10.6.8), FCE 4 + FCS 3 . . . Little Knowledge, Many Opinions.
  • salty777 Level 3 Level 3 (540 points)

    Ian, those are the instructions from that link you posted the other day. I followed them too and at my end the end result looks worse than just leaving it as "auto", which is a bit disappointing! I'm doing something wrong somewhere.... I've binned this whole "PF" thing and am using either 60i or 24P (true P!) now.


    It does render, and the only thing I can think that it is doing is re-combining the two fields, because they've been "segmented".... how this is different to de-interlacing is beyone me!


    I'm still experimenting, and getting more confused with HD by the day.....

  • salty777 Level 3 Level 3 (540 points)

    I thought de-interlacing combine two fields (odd lines and even lines) into one frame?


    Nice picture by the way.... you must be pleased with your camera!

  • Harmonica_Lessons Calculating status...



    This is not a new issue, but it usually doesn't get answered correctly. There is a definite problem with PsF files coming from Canon, Panasonic, and some other camcorders. It doesn't seem to be an issue with DSLRs.


    Take a look at this post from some months back. If you read the provideocoalition(dot)com links you will uncover the full story much better than I could ever explain it-


    As I said in that previous post, I broke down and bought ClipWrap and now the 1080 PF30 files are read correctly by FCPX.


    Good luck,


  • Harmonica_Lessons Level 1 Level 1 (15 points)


    Ian R. Brown wrote:


    Incidentally I notice in your thread that Tom considers the problem of incorrect recognition to be Canon related. As it affects my SD800 which has Panasonic's most advanced consumer technology, I think we can assume it is a universal problem.


    Regarding my concerns over jitter, page 61 of the Panasonic manual, when describing the operation of Digital Cinema mode adds the following footnote but not in bold type:-


    * The images may not appear smooth.


    That's a real drag about the jitter. But, I hope the ClipWrap solution helps you out with the PsF bug. Colin at Divergent Media seems to be a great guy and has been very helpful to me. Aside from the bug issue, I'm happy now with ClipWrap that I can re-name all my MTS files before I get to FCPX and also delete the junk files I will never use without worry of destroying the file structure.


    I don't get by these Apple forums too much any more (I've moved over to the Creative Cow and forums), but I know you've been a great resource for the posters here for quite some time. I do check in every month or two to see if someone specifically has the PsF problem. Hopefully now, there's a couple of people that can help with this particular issue.


    "Incidentally I notice in your thread that Tom considers the problem of incorrect recognition to be Canon related."

    Yes, Tom does not seem to be a big fan of Canon, but I have had decent luck with Canon and started with the GL1 and FCP 4.5 many years back. As a non-pro, I've been very happy with my HF S100 Vixia HD camcorder. For what I paid for it, it's worked out nicely (especially since this PsF silliness has been straightened out).



  • Harmonica_Lessons Level 1 Level 1 (15 points)

    Well that *****. Ian, go to the ClipWrap website and email Colin and tell him exactly what you wrote here. If you send him example files, he will likely come up with a fix.


    By the way, it's not just an issue with FCP X. From the original article, the same issue shows up in FC Studio (legacy) and also Adobe Premiere Pro 5.5.


    Good luck with this, I'll be curious to see how it turns out.




    (By the way, just for grins, did you happen to try the Method 1 notated in my original post with the double import?)

  • Harmonica_Lessons Level 1 Level 1 (15 points)

    Ian R. Brown wrote:


    Fearing I may have done something wrong I re-read the ClipWrap/PsF article again and noted that it was recommended to rewrap the AVCHD folder.



    I've always just wrapped the files myself. It's possible that you might lose some metadata that way, but I don't really know (or care to much for my workflow). You may want to ask Colin this as well.



  • Colin Mcfadden Calculating status...

    Hey All - There isn't a standard for PSF in AVCHD, so we need to reverse engineer and add support to ClipWrap for individual models (or potentially brands/lines).  If you drop us a line at, we can usually help out.  What's super awesome is if you can supply a PSF and a non-PSF sample MTS from the same camera.


    Hope that helps.  Oh also, if anyone is coming to NAB next week, come say hi!  We're in SL14010.



    divergent media, inc

1 2 3 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • 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.