Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Apple Final Cut Pro Legacy › Importing M100 mov file into Final Cut

  • Importing M100 mov file into Final Cut

    Posted by Scratch Sperber on March 6, 2007 at 11:01 pm

    We have just (last week) moved from Media100 to Final Cut Pro 5 on a G5, and burned the Media100 hardware and software as we danced around the bonfire.

    For my current project, I’ve captured Sony XD-Cam footage as 10-bit uncompressed, and am editing in a 10-bit uncompressed sequence. All good. I need to incorporate several minutes of an existing program that we cut on the Media100i 8.2 and saved as a self-contained mov file. It was originally captured and edited in Media100 as 640-480 square pixels.

    With the Media100 transcoder installed, I opened the M100 file in Quicktime, and exported it as a 10-bit uncompressed quicktime movie. I’ve tried several settings, but I am still having problems when I bring the clip into FCP:

    — it requires rendering. Is that normal? Why would it have to render if it is a 10-bit uncompressed mov in a 10-bit uncompressed sequence?

    — there are some graphics in it (moving boxes) that look horrendous now. Jerky, field/frame flicker, etc. The video itself looks fine, even where there is movement.

    — what is the best export setting in QT to resize and deal with the dimension and pixel difference? The imported file must visually match the newly captured footage — no letterboxing. If I have to, I could accept an aspect ratio stretch. But ideally, it should match. Should I do the resize in the export or leave it alone and resize in FCP with the motion tab?

    — is there a problem with importing a mov file that has different settings or pixel size than the sequence? (i.e., 8-bit uncompressed, animation, square pixles vs CCIRxx, etc.)

    I’m trying many tests but would appreciate info from anyone else who has done this. I am also doing it with much trepidation because I experienced some terrible crashes doing this the first time, and even touching the mov clip to try to delete it from the sequence caused more crashes… corrupted project that could not be saved with an XML export/import… or any other method.. had to revert to previous days’ autosave. I think it was coincidence, unrelated other problems, and have since done a total erase/reinstall of everything. But importing these makes me nervous, like a dog approaching an electric fence wire…

    Thanks,

    Scratch

    Scratch Sperber replied 19 years, 6 months ago 2 Members · 2 Replies
  • 2 Replies
  • Rafael Amador

    March 7, 2007 at 1:53 pm

    Hi Scratch,
    I’ve never worked with M100, but I would sugest you to import the clips directly to FC and make the transcoding in FC. This should be possible with any QT codec that you got installed. Make sure that in the brownser FC interprete properly the setting of your clips and them try to lay them down in the 10b Unc time-line.
    Anyway I think opening the clips with QT and export, is not the most recomendable option or a transcoding. You have not much control on the process. Better try Compressor.
    Good luck,
    Rafael

  • Scratch Sperber

    March 7, 2007 at 5:19 pm

    I just tried that again, and got an instant FCP crash (“unexpectedly quit”) as soon as I tried to play the imported clip. Luckily it didn’t corrupt my project again (although I did use a copy this time — once burned, twice shy). I think it really doesn’t like the mis-matched size, pixel aspect ratio, etc. Plus I imagine FCP would not want to play well with the Media100 quicktime component. That’s why I’m trying to save it as a more normal QT file first. Thanks anyway — I’ll try this question in some more Media100-ish forums.

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