Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Converting raw .mts files for FCP

  • Converting raw .mts files for FCP

    Posted by Jeremy Cassar on January 12, 2010 at 6:24 am

    Hi all,

    I was given about 60 clips in the form of .mts files, without preserving the original file structure. There is no way to get that back, as the files were deleted before they were handed over to me.

    So obviously I’ve been looking for the best method to convert these files for use in FCP.

    I narrowed down Toast as the best software to do this in, and began trying different compression methods to get the footage into FCP looking right.

    When I use H.264 or Motion Jpeg (trying all available interlacing/deinterlacing options), i get horizontal motion lines pretty badly both when viewing the video and when importing into final cut, even after applying a deinterlacing filter and playing with different settings.

    The only two that seemed to get rid of the lines when importing into FCP were the Apple Pro Res 422 (and HQ), and one of the DVCPRO compressions.
    So i converted all the footage to Apple Pro Res 422 HQ (and also then tried with standard 422 and DVCPRO thingy). The only problem is the footage is ridiculously big in file size – almost 200 gigs in total, which seems way too big for the amount of footage. Each clip is over a gig, and I’m editing on a macbook (i know, i know, but it’s a tiny project. I’ve altered the quality settings and still get the large file size.

    I don’t know anything about the technicalities behind any of this, so i apologise if haven’t described the problem properly, but it would be great if someone could suggest a compression that wouldn’t result in such a large file size, without having to put up with horrible horizontal lines.

    Thanks all,

    Jeremy

    Jeremy Cassar replied 16 years, 7 months ago 2 Members · 4 Replies
  • 4 Replies
  • Andy Mees

    January 12, 2010 at 8:51 am

    What was the original source for these clips? Are they HD or SD? What format are you used to working in with your MacBook? What is your delivery requirement for this project?

  • Jeremy Cassar

    January 12, 2010 at 9:26 am

    Original source was AHVCD. I am from Australia, so we use PAL, not NTSC, not sure if that helps.
    I am not able to get information as to exactly what camera, but i know it was one of those small hd handycam’s. Nothing special. Unfortunately I can’t give any more info than that.

    The format I’m used to working with on my macbook (i no longer have access to a power mac), is .mov, i guess.

    The finishing format will be DVD PAL, as it is a wedding.

    Thanks for your quick reply Andy.

    Jeremy

  • Andy Mees

    January 12, 2010 at 10:36 am

    Hey J.

    Check out ClipWrap 2.0 : https://www.clipwrap.com/downloadtrial.php … could be just what you need.

    If the resultant files are too unwieldy for your system then I’d suggest you try a transcode (and downconvert) of the source files to something more appropriate for your system and delivery target … am thinking good old DV or DV50 might be suitable.

    Best
    Andy

  • Jeremy Cassar

    January 14, 2010 at 6:04 am

    Hi there Andy,

    I’ve tried to downconvert to DV or DV50 from the source footage in toast 9 but in both instances the horizontal lines are extreme.

    Before I go ahead and buy clipwrap (seems a shame considering i don’t plan on using it again, but am willing to as a last resort), I thought I’d give cutting the ProRes footage a try. The ProRes footage is on my sisters computer, which i cannot use to cut. Have tried copying the footage to two seperate FAT32 external drives, so that i can work off that drive and my macbook, but I keep getting an error (error code: 0 – go figure) when trying to copy. When i try and plug in my sisters FAT32 drive as a test (which i also cannot use for cutting), they copy over fine.

    Do you have any idea why the footage wouldn’t copy over? There’s plenty of space.

    If this all sounds like too specific a problem then I might just go ahead and buy clipwrap, but thought I’d check with you just in case.

    Thanks Andy,

    Jeremy

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