Interlacing problems: iMovie Better Than FCP10?

Hi guys. New to these forums and a bit of a rookie so be gentle...
I've just moved from iMovie to FCP10. We're shooting a short film complete with cast etc. and wanted better quality editing options. Shooting at 1920x720p @ 25fps, I converted 3 scenes from MTS to .MOV. using the Apple Pro Res 422 codec. I then imported the scenes to iMovie where the footage (apart from the usual slight drop in res) looked just fine.
I then loaded the same .MOV footage into FCP10. Anything that wasn't stationary - from a moving van to blades of grass swaying in the wind - was riddled with (what I assume is) interlacing wavy lines. Not a little, but a lot. To add to this, darker areas and shadow had really bad noise issues. Basically, it was unusable.
I tried changing the fields from progressive to lower etc. That didn't work. I tried the 'Foxy' method of changing values from 'p' to 'i' - I even tried 1080. Still no joy, not even a slight improvement.
As it stands, I'm getting much better results from iMovie; no wavy lines and no noise in dark points. Can it be that iMovie will do a better job than FCP10? Or am I doing something wrong?
We go back out to the Scottish wilderness in ten days to complete filming, so I really hope to get this problem licked by then. If anyone can offer a solution I'll be eternally grateful - hell, I'll put your name on the end credits as a tech adviser! Thank you in (possible) advance!
PS. Pleased to find this site - I look forward to many more visits.

Curious how you converted the MTS files to Pro Res MOV. Did you have FCP X do that by optimizing at import? Or a third party converter? And have you tried working natively with the files?

If you shot 1080P and let FCP determine the project settings automatically, it should give you a progressive project without issues. (Although if the camera shot PSF – Progressive Segmented Frame – FCP might have some trouble.) BTW, what is the camera model you used?

Russ

Does it show up on exported files? If not, just for the heck if it, make sure the playback quality (drop down menu in upper right of the viewer) is set to "Better Quality" rather than "Better Performance"

Sorry about the delay, guys. The site wouldn't let me back in! (admin disabled public write access)

Russ
- I converted the MTS using Borosoft software. Pro Res is one of the output options. I tried working natively with the MTS file, but FCP doesn't seem to accept the file type. My camera does record progressively; I used the HA1920 option for our shoot. I had the option of 1080, but it means having to shoot at 50fps (the only available frame rate I have at full 1080i). As far as I know, shooting in 50fps can be a problem when viewing on LCD TV's via DVD/externals. Perhaps I could try shooting at 1080i/50fops then downgrade the frame rate during export? I might try that. Oh, the cam model is a Panasonic HCV700. Just a mid range consumer model. Thanks for replying.

Hi Plysat,

By showing up on exported files, do you mean when playing via FCP? Or the converted file? The converted file is perfect (at least when played through iMovie). It's only when I export the .MOV to FCP the problems start.
I'm pretty sure I choose best possible quality, but I intend to go back in and run a sample clip to try your suggestion.
Thanks for replying.

Joe90 wrote: Hi Plysat,

By showing up on exported files, do you mean when playing via FCP? Or the converted file? The converted file is perfect (at least when played through iMovie). It's only when I export the .MOV to FCP the problems start.
I'm pretty sure I choose best possible quality, but I intend to go back in and run a sample clip to try your suggestion.
Thanks for replying.

Hey, Just wondering if you see the degraded image if you export (share) the project from FCP and play it in quicktime player or something. It's probably not the case, but often people have the playback quality set to a lower resolution. So it looks like crap in the app, but it's actually fine, it's just a preference that can make playback smoother with certain codecs, lots of compositing effects etc...

Huge amount of misinformation here. Borosoft is horrible. AVCHD does not need conversion in FCP if it handled properly. The current version on FCP actually supports .mts files, but it's a crao format and should be avoided. 1080i50 is not 50fps but 25fps. There is no problem playing actual 50fps media on any monitor.

So what OS are you running? Also what Version of FCP X? I know the latest version can work with MTS files without converting.

I kind of anticipated that a third party converter might be involved. As Tom indicated, they can sometimes introduce their own range of issues.

Russ

Oh sorry, Plysat, I see what you mean. Yeah, that's definitely worth trying. A little annoying dealing with the flaws during the edit, but bearable if I know the final product will be smoother. The good playback on iMovie is still a mystery...
I'll give that a go. Tnanks.

Joe90 wrote: Oh sorry, Plysat, I see what you mean. Yeah, that's definitely worth trying. A little annoying dealing with the flaws during the edit, but bearable if I know the final product will be smoother. The good playback on iMovie is still a mystery...
I'll give that a go. Tnanks.

Hopefully it's just the playback setting, which can be changed very simply. iMovie doesn't have this option, which may be why it looks better. It is odd since, (assuming you're using these) FCP X 10.1.x and iMovie 10.0.x, are essentially the same application.

Hi Tom
I was just starting with MTS when I chose Borosoft. I've since read some bad reviews. You say FCP supports MTS. As it won't let me import them, and you don't explain the solution, perhaps you could supply a link I could try? The 1080i setting on my cam offers 50fps only. I'm not aware of any other choice. I'm confused about the 50fps statement. Apart from reading about problems with TV monitors, my own LCD TV won't play them (25fps is fine). As I said earlier, a bit of a rookie so I'll check all that out.
Thanks.

Hi Plysat,
Yeah, my fingers are crossed on that one. Not at home at the mo, but I'll be testing the minute I am. And yes, really strange with iMovie. Any more of these problems and we're looking at an iMovie production! www.fcp.co/media/kunena/topicicons/default/user/exclamation.png
Thanks.

Ah, that explains Tom's point. I'm running the older version - 10.0. The hardware's an old 2009 Macbook Pro with added RAM.
Thanks, Russ.

Your MBP will run 10.1.

It's worth upgrading for a long list of reasons – only one of which is $$ saved on not buying 3rd party converters.

Russ

Definitely, Russ. I'm an idiot for not doing it already. I'll post again with the outcome. Thanks for all the help (so far!!).

Ah, Russ. Remembering now why I didn't update. FCP 10.1 requires a 10.9 O.S. I've been hesitant about Maverick having read an awful lot of negative reviews - especially when installed on older machines and its effect on saved content. Here's hoping FCP 10.9 can improve the situation.

To bed!

FCPX does import .mts, but it has to have the entire card structure, not just raw files. And those conversion programs like the one that was used are generally considered to be pretty worthless. I'm guessing that's what messed up the progressive settings.

If you can't get the entire card structure and are having to use the files alone, I think ClipWrap will rewrap those without any transcoding or image degradation. If it's a file type that ClipWrap won't rewrap (like .mxf) I've found that often Davinci Resolve Lite (free) will import them and convert to ProRes.

Good luck.

ddixon wrote: FCPX does import .mts, but it has to have the entire card structure, not just raw files....If you can't get the entire card structure and are having to use the files alone, I think ClipWrap will rewrap those without any transcoding or image degradation....

It's true having the card structure is best, but I just imported an individual .mts file to 10.1.1 and it worked fine. It was a separate file which I dragged out of the AVCHD package to the desktop, then imported it from there. I used "leave files in place", and did not use optimize or proxy media. Editing and skimming the clip in the timeline worked fine. The file was from a Canon HF-G10 camcorder.

I agree ClipWrap is a great tool and I use it when needed. However 10.1.1 apparently can handle (at least some) .mts files directly without re-wrapping.

Wow, that's good to know - that didn't always work. Similarly, the Panasonic consumer cameras from a couple of years back that were early ones to record 60fps could not be imported, but at some point in the 10.0.x months FCPX suddenly began importing those. And, the .mxf clips from Canon XF series cameras could once be either transcoded or not when imported. Along the way Apple decided those didn't need transcoding and now will not allow that option. ClipWrap doesn't work on those.

To my knowledge, none of these changes was ever documented in the FCPX update info. I hope they continue adding more file formats to the list of those that can be imported without requiring the entire card structure - it just makes things easier.

Hi ddixon,
Well, (so far) success! My brain has just been refusing to import directly from cam. My method has always been to convert the MTS to .MOV, then take it from there. I tried Clipwrap and that just couldn't seem to remove the problem. Then, after seeing your post, I loaded directly and all interlace problems were removed. It's odd; when played in the preview pane, the distortion is there but it's gone when I play full screen.
I haven't shared the project, yet, but I'm assuming it'll be OK.
So, as I'm feeling like an idiot for not taking this part of the advice from the beginning, I'll go and see how the project looks when burned to DVD.

Big, big thanks to everyone that offered advice. You're a good crowd (and not too hostile to us poor rookie editors!!!)